"Jeffery S.Norman" wrote:
I found the following information regarding the Telocity DSL modem I am trying to hook up that might mean something to someone about why I can't get an internet connection from SuSE 6.3 (from telocity.com's faq pages):
"The Expressway modem is actually a residential gateway that also functions as a router. The router configuration is set through Telocity's systems."
"Network Address Translation is not currently enabled, but will be offered as a future enhancement. "
"The modem acts as a DHCP client during the initial communication with the network, and as a host to allocate the IP addresses assigned to the device (such as your PC) during configuration."
Does this tell anyone why dhclient and dhcpcd just hang waiting for a valid dhcp offer?
This sounds *exactly* as my own (solved) problem with my DSL provider. I used SuSE 6.2 with dhclient from The Software Consortum, version 2. I wanted to use my Linux box as a router using NAT, but it jut wouldn't work, no matter what I did. I ended up moving the NIC to a Windoze host, asked an IP address using DHCP, and moving it back to my Linux Box where it worked just fine (after altering the current leased address). After a couple of hours, the connection died of course, because the lease was never refreshed. I was amazed how easily I could solve the problem. I just went to www.isc.org and downloaded version 3, which is still in beta, but works fine for me. I compiled it, installed it, and voila. No adjustments, it just worked. And it still does. Now I'm running SuSE 6.3, but I still had to download dhcp 3. Some users say dhcpcd is fine, I've never tried it, but maybe it works for you. I wanted to find out *why* it didn't work. I compared the requests Windoze and Linux made, and found out that windoze sent '0.0.0.0' as the current IP address, while Linux sent the currently setup IP address, in my case 192.168.1.1. Probably the DHCP server of my ISP didn't like that very much. ISC dhcpd 3 sends 0.0.0.0 as the current IP address. I couldn't change the address in YaST, because the address was declared an invalid address. Enabling DHCP in YaST didn't work for me either, because I still had the other card in the box my LAN was on, and it needed an address too. I hope this works for you. The best of luck with it. Rogier Maas -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/