Frustrating network issue

John Oliver joliver at connectnet.com
Mon Jun 18 21:22:33 PDT 2001


David Rees wrote:

> Need more information like the output from `ifconfig` and `route -n`.

That machine is in Kearny Mesa with (needless to say) no network
connectivity... :-)  ifconfig is fine... both interfaces are up up, eth0
is 216.120.50.128/25 and eth1 is 216.120.58.8/29  route looks just like
you'd expect... two entries for the interfaces themselves, two more for
the networks (on the proper devices), and the default gateway of
207.110.58.9 on eth1  I can't find how/where it determines which device
the default gw should be on... like I said, one of the weird things was
when 216.120.58.8/29 was on eth0 but it determined that the default gw
device should be eth1 regardless.

> PS - I've given up on cheap network cards, I've had too many problems with them not working in
> various situations.  I'd get problems with having some weird chipset that only the latest
> 2.4.X kernel can detect (and it's a PITA to get 18MB to a computer with no network).  I had
> other problems with cards not picking up on a 100BT network.
> 
> I'd recommend sticking with the old 3Com cards you had, or if you need 100Mbps, go with new
> 3Com or Intel cards.

I agree.  However, I've always had good luck with NetGears.  A lot of
people like them just as much as Intels, just as I know several people
who hate 3Com and prefer Intel all the way.  Besides, having the same
problem with two different cards seems to rule out cards/drivers here. 
I feel that this is either a routing issue or a dual-home issue.  I just
have a deep-seated feeling that somebody's going to come up with "Oh,
you need to edit this file" or "Having the interface start working when
the switch pings it and not before is caused by Y".

Besides, if I bring it home and change all the settings to work on my
network (so I can copy files and such), it'll probably work just fine. 
The only difference I can think of is I think I had one NIC in it here. 
But I know I had both in it when I had it at work.  Maybe some weird
issue with two identical cards and the drivers getting confused?  Maybe
I'll try one 3Com and one NetGear, although I've never had a problem
like this before...

-- 
John Oliver, System Administrator        http://www.allegiancetele.com
ConnectNet, an Allegiance Telecom company    http://www.connectnet.com
6370 Lusk Blvd. Ste F103                                (858) 638-2020
San Diego, CA. 92121                               FAX: (858) 623-1505



More information about the KPLUG-List mailing list