Actually he doesn't say that eth0 is actually plugged in anywhere, so if it isn't it won't have an ip (i'm assuming here it is set to get an address via dhcp??)
I'd say the cards were not set up in the order they are detected on boot, so at home eth0 was wifi and eth1 was wired. When they were booted at school, wired was detected first by the kernel, therefore it was eth0, and hamish had instructed that eth0 was to be left down (because previously eth0 was the wifi). Then the kernel detected the the wifi card and applied the parameters meant for the wired card, so obtained an ip address and joined the network as eth1. moral: probably swap the configurations, or set modules.conf to detect them in a certain order (alias driver ethx???) This doesn't explain the second problem, which is what i was concentrating on in my earlier messages. I suppose the output of iwconfig would be helpful too :-) On Wed, 12 Feb 2003 13:15:35 +1300 Bjorn Nilsen <[EMAIL PROTECTED]> wrote: > On some systems shared IRQ's are normal, but the fact that eth0 has no > IP address is a bit of a problem :-) > > > > Well I can't see anything there thats wrong [1], > > eth0 neither has an ip address nor is it up, and it's on the > > same interrrupt > > as eth1. > > > > Somebody wasn't correctly orientated when they did the plug > > and pray bit. > > :-) > > > > > -- "All that was needed was to parse the cat root slash dev etcetera file for eth0 and pugle the forward identity-locking rehooliginator and symlink it to the libgc perl humongisooler module after a kernel decompile and basic repatch update." - theregister.co.uk
