--- lwr1@bellatlantic.net wrote:
Are you running off of a DSL line with linux off of BellAtlantic? If so, could use a few pointers. Running 6.3, have kernel properly configured and two NICs, both are loaded properly and can config them statically to work, however can't get DHCP to talk to the Westel device for it's IP. NICs: 3c905C and eepro100-old. Once I get the NIC to talk to the box I'm fairly certain that pppoed will run flawlessly. Ideas?
Yup - I picked up the cheapie BA DSL PPPOE line. It's been working just fine for quite a while now, although it does get dropped now and again. And I'm no Linux expert. Let me get this right - you've installed the roaringpenguin PPPOE client and have everything up and running but only with static ips on both nics? Your Linux box is acting as a router/gateway to your local network then, and you most likely have reserved ips addresses internally. Check your YAST configuration setup - this sounds familiar (I wish I took better notes ;) ). If eth0 is your local network interface, it should be configured something like ifconfig_0 = 192.168.0.1, broadcast 192.168.0.255 netmast 255.255.255.0 up. Assuming eth1 is connected to your Westell box, ifconfig_1 should be null. If you assign it an ip address, dhcp will not be able to assign it one. The pppd script that is called by the adsl-connect script handles all of this. Hope this helps. Let me know how it goes. - Steve __________________________________________________ Do You Yahoo!? Send online invitations with Yahoo! Invites. http://invites.yahoo.com -- 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/