Text 2825, 82 rader
Skriven 2005-07-14 09:36:18 av mark lewis (1:3634/12.0)
   Kommentar till text 2823 av Scott Little (3:712/848)
Ärende: networking woes
=======================
 ml> when eth1 goes wonky, i can sit at the local console and ping both
 ml> interfaces with no trouble... i can also go to a system connected to
 ml> eth0 and ping both interfaces with no trouble... however, if i go to a
 ml> system connected to eth1, i cannot ping it or eth0...

 SL> Better.  Doesn't help much :)  The stack is doing all the work
 SL> there, rather than the NIC driver.. you'd still be able to do that
 SL> with eth1's cable disconnected.

mmmmmmm, yeah, i guess so... however, i'd have thought that it would have gone
thru the cards loopback capability or something that can show that all the
card's hardware is operational...

 ml> it is... i've tried but it didn't seem to work right... i even tried
 ml> backing it out like the reverse of a bootup and then reloading it like
 ml> bootup and that didn't work either...

 SL> So.. basically the device needs to be given a hardware reset to
 SL> work.  That's probably Bad.

well, i'm not so sure that i reverse engineered the processes correctly,
either...

 ml> where can i find mii-diag? it sounds interesting...

 SL> It'll be in a package called mii-diag, mii-tools or net-tools. 
 SL> You'll have to Google it, 

i'll see what i can do... hopefully it'll run on that older box... kernel
2.2.19-6.4mdk...

 SL> I stopped worrying about where stuff is when I switched to Debian. 

 SL> $ apt-get install mii-diag

hehehe, i actually have debian here but haven't installed it yet... i need to
get a few things for this other motherboard to make a complete system... my
intention has been to get debian running and transfer the responsibilities of
the current machine to debian... then to rebuild the current machine... i just
have to ensure that samba stuff works as present with w98se boxes as well as
being able to have the automounted virtual cdrom jukebox and the routing
between several networks as described... at one time, there were actually three
networks, here...

 ml> maybe it is time that i fire up iptraf again?

 SL> If iptraf can see the packets, I'd say it's not the card or the
 SL> driver.  iptraf doesn't seem to have much low level diagnostics
 SL> either, but if the error counter moves from zero you know there's
 SL> definately a hardware problem.  You might also try looking at the
 SL> arp cache, see if it's found any hosts.

yeah, i don't recall if iptraf can see the packets or not... i had stopped
using due to the slowdowns from the monitoring it does... the box is only a
P-200 (no-MMX)...

 ml> the cable is fine... i know that... if it wasn't, a reboot wouldn't
 ml> fix it...

 SL> You'd think.. bad wiring can do all sorts of weird things.

true...

 ml> interesting... maybe i'll have to give that a go... you didn't have to
 ml> reload ipchains or such??

 SL> As long as all the IPs stay the same (no DHCP), it'll be fine. 
 SL> ipchains is in the tcp/ip stack not the NIC driver.

cool, that's what i was thinking...

 ml> now i'm starting to wonder if it is something with that card in that
 ml> other router box...

 SL> Make sure they don't have the same MAC....

they shouldn't... everything works for hours or days... then poof! and this box
is the only showing any problems...

)\/(ark

 * Origin:  (1:3634/12)