Package: netcfg Version: 0.63 Severity: normal Tags: d-i I have seen two systems where I don't always get a default route after dhcp succeeds: 1. My (probably misconfigured) vmware virtual machine. I never seem to get a default route set up on this machine via dhcp. If I add one by hand, it's ok. 2. My test laptop, connected directly to my cable company's interface box. Here I got one IP address without a default route, and then 10 seconds later (when the first lease expired!) an different IP with a default route. Weirdness. Things go wrong in suprising ways when there is no default route, and it's not at all obvious what the real problem is. So I think that netcfg should check for a default route, at least when using dhcp (not sure about static), and complain if there isn't one. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.4.26 Locale: LANG=en_US, LC_CTYPE=en_US -- see shy jo
Attachment:
signature.asc
Description: Digital signature