On Mon, 2 Feb 2004 11:26 pm, Andrew Robson wrote: *SNIPPED* > I have read and tried everything I can about setting up Optus cable, so I > have turned here as a last resort. > > some other facts. > > I also run windows on the same machine "yes I know it blows" :P > it is a dual boot. > the NIC works as I am using it now. > > this is most frustrating as under winblows all I have to do is have the > interface set to DHCP and it works....
Make sure there is an alias in your modules for your card. Here's what's in my config: First make sure the module is being loaded at boot for your NIC (the tulip driver will usually work - but check your NIC's chipset): -------------- # /etc/modules: kernel modules to load at boot time. ... 8139too # my ethernet card yours will be "tulip" - FA310TX ... -------------- Then make sure your interface is being configured at boot too: -------------- # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface auto lo eth0 iface lo inet loopback # This entry was created during the Debian installation iface eth0 inet dhcp -------------- This should cover it. GRAIN-O-SALT: I'm not using Optus cable but I am using DHCP on Debian in a number of environments (some quite strange) and it "Just Works" (tm) provided your NIC is configured correctly. Good luck, James -- Fortune cookies says: Life is a process, not a principle, a mystery to be lived, not a problem to be solved. - Gerard Straub, television producer and author (stolen from Frank Herbert??) -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
