network weirdness, link encap:USPEC

byte.chaser · 08-18-2005, 08:44 AM

hey guys,

Wasnt to sure where to put this, but i hope someone can help
I installed a few more programs to try on my debian etch 3.2(?) box, k3b, gftp, and i believe cups.. Everything was going great, i burnt one cd, played some tunes, browsed LQ for awhile, checked email etc.. Then i got sleepy and decided to shut down for the night. So i shut down my clarkconnect router, debian box and xp box... all is nice and quiet ZZZZZZ
I wake up, turn on the router xp and debian box and "starting MTA hangs....
uhoh.. finishes booting, i log in... startX no inet, gaim cant connect hmmmm I check the router, dnsmasq is running and i can ping ip and dns.. XP box (wifes) is ok, no issues, can surf, ping etc... cant ping the debian box though (192.168.1.5)

So i go hunting some more. ifconfig eth0 gives

Link encap:UNSPEC HWaddr XXXXXXXXXX
static ip of 192.168.1.5

ping loopback 127.0.0.1 is ok
cant ping names or ip i get "destination host unreachable" eith on internal ips (gateway 192.168.1.1) or XP box (192.168.1.2)

cat/etc/network/interfaces looks ok

iface etho inet static
address 192.168.1.5
netwask 255.255.255.0
gareway 192.168.1.1

my resolv.conf file seems ok

nameserver 192.168.1.1
## i added my isp as well... i thought maybe something had changed as a requirement

nameserver 64.x.x.x
nameserver 64.56.x.x

cant ping either again, but can ping and surf via lynx (sp?) on my gateway

I have checked my switch, changed ports just in case, no change.

The only thing i can see different after i restarted is
Link encap:UNSPEC

instead of Link encap:ethernet

I thought that was alittle odd

there are no collision or dropped packets in ifconfig eth0 either

I can however do a modprobe sk98lin, which adds an eth1... but i have no other nic either... I even tried going into the interfaces file and changing eth0 to eth1 just to see... alas no change

any suggestions on how to get this working again ?

Thanks,

EDIT:
Just Checked the ethernet cable, its working. Using knoppix now so i can at least chedk files on debian box... and i can surf in knoppicx now... debian still broke though
ifconfig shows below, note now in knoppix Link encap:Ethernet now not Link encap:UNSPEC

code:Link encap:Ethernet HWaddr 00:11:2F:A8:FA:32
inet addr:192.168.1.5 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::211:2fff:fea8:fa32/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3162 errors:0 dropped:0 overruns:0 frame:0
TX packets:3374 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2244092 (2.1 MiB) TX bytes:702308 (685.8 KiB)
Interrupt:22 Memory:feaf8000-0

PenguinPwrdBox · 08-18-2005, 10:24 AM

Code:

ifconfig eth0 down
ifconfig eth0 hw ether in:se:rt:ma:ca:dd up
dhclient eth0

Please replace that mac with yours. If you don't know it, get it off of your card, or make one up. Just don't use all F's

byte.chaser · 08-18-2005, 02:13 PM

great thanks, i will try that...

I ass ume i can just use what knoppix gave me for hwaddr..?

Code:

Link encap:Ethernet HWaddr 00:11:2F:A8:FA:32

i use static ips, so do i still need to "dhclient eth0" ?

PenguinPwrdBox · 08-18-2005, 06:16 PM

Yeah - you can use that MAC
And no, if you are static, then you can just do this:

Code:

ifconfig eth0 hw ether 00:11:2F:A8:FA:32 192.168.0.1 netmask 255.255.255.0 up

Replacing with your addy's, of course

byte.chaser · 08-18-2005, 08:10 PM

hmmm well i tried

Code:

ifconfig eth0 hw ether 00:11:2F:A8:FA:32 192.168.0.1 netmask 255.255.255.0 up

but i got an error

Code:

SIOCSIFHWADDR: invalid argument

gonna google for a bit to see what comes up

thanks, again

EDIT:

Well everything i have found so far points to either wireless which i dont have or something called axattach. I cant find that on my system using locate. I dont know if itsa program, module or what..
I'm using 2.6.8-11 kernel if that helps.
I also found reference to mkiss module... that seems to appear in /usr/src/kernel-headers and kernel-source-26.8-X

cant find a bug report on it though... :/

EDIT:

i found thins as well http://he.fi/archive/linux-hams/200411/0005.html

looks like a patch... although i dont know if it applies or not seems to be 2.6.8 kernel perhaps not playing well with something else...?

PenguinPwrdBox · 08-18-2005, 08:19 PM

what happens if you say ethernet instead of ether?

byte.chaser · 08-18-2005, 08:26 PM

Quote:

Originally posted by PenguinPwrdBox
what happens if you say ethernet instead of ether?

i just get options... almost like a syntax error... ether is an option in there for "hw" ethernet is not...

i added more to the above as well, .. did nt see your reply quick enough..

byte.chaser · 08-18-2005, 08:48 PM

ok heres some more weirdness

using knoppix with linux26 switch i set up my nic with netcardconfig... all is working i then ran the following

Code:

root@ttyp0[knoppix]# ifconfig eth0 down
root@ttyp0[knoppix]# ifconfig eth0 hw ether 00:11:2F:A8:FA:60 192.168.1.5 netmask 255.255.255.0 up

heh, offtopic the above pasted into konquerer crashed it *shrug* yeah firefox

anyway i got

Code:

root@ttyp0[knoppix]# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:11:2F:A8:FA:60
          inet addr:192.168.1.5  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::211:2fff:fea8:fa60/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:861 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:351432 (343.1 KiB)  TX bytes:128 (128.0 b)
          Interrupt:22 Memory:feaf8000-0

root@ttyp0[knoppix]# ping google.com
PING google.com (216.239.37.99): 56 data bytes
ping: sendto: Network is unreachable
ping: wrote google.com 64 chars, ret=-1
ping: sendto: Network is unreachable
ping: wrote google.com 64 chars, ret=-1
ping: sendto: Network is unreachable
ping: wrote google.com 64 chars, ret=-1

hmmm odd...

so i reran netcardconfig again... and again all is working so i try more...

Code:

root@ttyp0[knoppix]# ifconfig eth0 down
root@ttyp0[knoppix]# ifconfig eth0 192.168.1.5 netmask 255.255.255.0 broadcast 192.168.1.255 up
root@ttyp0[knoppix]# route add default gw 192.168.1.1

and everything is ok..

Code:

root@ttyp0[knoppix]# ping google.com
PING google.com (216.239.37.99): 56 data bytes
64 bytes from 216.239.37.99: icmp_seq=0 ttl=243 time=72.0 ms
64 bytes from 216.239.37.99: icmp_seq=1 ttl=243 time=62.8 ms
64 bytes from 216.239.37.99: icmp_seq=2 ttl=243 time=60.4 ms
64 bytes from 216.239.37.99: icmp_seq=3 ttl=243 time=63.4 ms
64 bytes from 216.239.37.99: icmp_seq=4 ttl=243 time=67.0 ms
64 bytes from 216.239.37.99: icmp_seq=5 ttl=243 time=72.2 ms
64 bytes from 216.239.37.99: icmp_seq=6 ttl=243 time=67.9 ms
64 bytes from 216.239.37.99: icmp_seq=7 ttl=243 time=74.8 ms
64 bytes from 216.239.37.99: icmp_seq=8 ttl=243 time=65.7 ms

the above is exactly what netcardconfig seems to do

EDIT:

I tried the above on the debian box no go, commands took (except netcardconfig ofcourse)
but same issue

Code:

eth0      Link encap:UNSPEC  HWaddr 00-E0-18-00-00-A6-24-B9-00-00-00-00-00-00-00-00  
          inet addr:192.168.1.5  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:103 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:3708 (3.6 KiB)

and from knoppix... same nic

Code:

root@ttyp0[knoppix]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:11:2F:A8:FA:32
          inet addr:192.168.1.5  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::211:2fff:fea8:fa32/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2218 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2441 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1045425 (1020.9 KiB)  TX bytes:369571 (360.9 KiB)
          Interrupt:22 Memory:feaf8000-0

byte.chaser · 08-18-2005, 11:17 PM

ok i found the problem
ieee 1394 yup firewire

i read a ton of articels on this and discvered it has something to do with net tools

apparently it was trying to load eth0 as firewite over ethernet hence the errors.
so what did i do.. well first i disabled my onboard FW port to test. booted up.. hmmm no eth0 BUT " starting MTA:" did not hang it loaded exim4 ... looks like good news
booted up, logged in

ifconfig eth0: device not found"

well thats at least something new, so i "modprobe sk98lin" it finds eth0 yahoooo!!
ifconfig eth0 gives some more info and it says ethernet this time, but no ip
so i ifdown eth0 then

Code:

ifconfig eth0 192.168.1.5 netmask 255.255.255.0 broadcast 192.168.1.255 up

ping an ip

"network unreachable" ick

so again ifconfig eth0 down

then

route add default gw 192.168.1.1

then ifconfig eth0 up

ping an ip and dns

Code:

debian:/home/nexus# ping google.com
PING google.com (216.239.39.99) 56(84) bytes of data.
64 bytes from 216.239.39.99: icmp_seq=1 ttl=244 time=59.5 ms
64 bytes from 216.239.39.99: icmp_seq=2 ttl=244 time=59.0 ms
64 bytes from 216.239.39.99: icmp_seq=3 ttl=244 time=80.7 ms
64 bytes from 216.239.39.99: icmp_seq=4 ttl=244 time=62.2 ms
64 bytes from 216.239.39.99: icmp_seq=5 ttl=244 time=59.9 ms
64 bytes from 216.239.39.99: icmp_seq=6 ttl=244 time=61.1 ms

[1]+  Stopped                 ping google.com
debian:/home/nexus# ping 216.239.39.99
PING 216.239.39.99 (216.239.39.99) 56(84) bytes of data.
64 bytes from 216.239.39.99: icmp_seq=1 ttl=244 time=73.5 ms
64 bytes from 216.239.39.99: icmp_seq=2 ttl=244 time=69.6 ms
64 bytes from 216.239.39.99: icmp_seq=3 ttl=244 time=63.0 ms

[2]+  Stopped                 ping 216.239.39.99

now the questions is why did this happen and i'm thinking i will need to run through this everytime i boot up ...ick

but for now it is solved

thanks again for all the help !!!