http://bugzilla.novell.com/show_bug.cgi?id=555095 http://bugzilla.novell.com/show_bug.cgi?id=555095#c5 Robert Davies <rob.opensuse.linux@googlemail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|jnelson-suse@jamponi.net | Status|NEEDINFO |ASSIGNED Info Provider|jnelson-suse@jamponi.net | --- Comment #5 from Robert Davies <rob.opensuse.linux@googlemail.com> 2009-11-21 15:21:37 UTC --- Have used 11.1's dhclient on same 64 bit machine with same ISP modem & interface it worked as expected creating a default route (same config file worked 32 bit 10.3 release with dhclient). The dhclient "prepend" feature is important due to netconfig's uncoperative handling of /etc/resolv.conf; if you change the file from what it expects it won't update the name servers dynamically. Using a static configuration only works so long as the allocated IP addresses doesn't change. A script to add a default route if not made, would be possible, but likely to need trial & error to discover the GW address by brute force (I guess most will be .1). There are no wireless complications, this is a basic Internet GW/firewall configuration with 2 Wired Ethernet cards, one dedicated LAN to external ISP, the other on internal local network. Please Marius, except this as the needed info, as it seems Jon Nelson's not around to log into Bugzilla. dhclient has to set 3 things, interface address & mask, return DNS servers, and set default route, without any one of those it is totally broken from end user point of view. --- Comment #6 from Robert Davies <rob.opensuse.linux@googlemail.com> 2009-11-21 15:21:42 UTC --- Have used 11.1's dhclient on same 64 bit machine with same ISP modem & interface it worked as expected creating a default route (same config file worked 32 bit 10.3 release with dhclient). The dhclient "prepend" feature is important due to netconfig's uncoperative handling of /etc/resolv.conf; if you change the file from what it expects it won't update the name servers dynamically. Using a static configuration only works so long as the allocated IP addresses doesn't change. A script to add a default route if not made, would be possible, but likely to need trial & error to discover the GW address by brute force (I guess most will be .1). There are no wireless complications, this is a basic Internet GW/firewall configuration with 2 Wired Ethernet cards, one dedicated LAN to external ISP, the other on internal local network. Please Marius, except this as the needed info, as it seems Jon Nelson's not around to log into Bugzilla. dhclient has to set 3 things, interface address & mask, return DNS servers, and set default route, without any one of those it is totally broken from end user point of view. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.