[tulip] Still no go with multiple Linksys cards

[Michael Olson]

Well, no one except Donald might believe it, but sometimes the most
obvious solution, the one we overlook, is the correct one.  Thought I've
become vastly more familiar with the way networking works in Linux thanks
to my "problem," it never occurred to me that I might have assigned the
two networks incorrectly.  I had read somewhere that the cards were
detected top to bottom and it did not cross my mind that such might not be
the case for all motherboards or in all situations.

In other words, upon making eth0 = eth1 and eth1 = eth0, everything worked
perfectly.  I can't believe I let this be a headache without trying the
most obvious thing, but such is the way of things.  Thank you, Donald, for
your help before and now with what should have been a no-brainer.

Ugh.  Well, if anyone needs me I'll be banging my head against a wall
repeatedly before embarking on the adventure of configuring Samba.

Thanks a bunch.

-A much relieved and happy to be functioning correctly in Linux Michael


On Wed, 1 Aug 2001, Donald Becker wrote:

> On Tue, 31 Jul 2001, Michael Olson wrote:
> 
> > Despite some advice and mostly my own tinkering around, I have failed to
> > get my two Linksys EtherFast 10/100 LAN Cards (LNE100TX V4) working under
> > Linux.
> 
> They appear to be working fine.
> Your problem seems to be with routing.
> 
> > Debian Unstable, Kernel Version 2.2.19
> > Tulip driver v0.92
> > 
> > [ifconfig]
> > eth0      Link encap:Ethernet  HWaddr 00:04:5A:4C:D4:1A  
> >           inet addr:192.168.10.13  Bcast:192.168.10.255  Mask:255.255.255.0
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:309 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:49 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:100 
> >           RX bytes:18955 (18.5 Kb)  TX bytes:7749 (7.5 Kb)
> >           Interrupt:5 Base address:0x1000 
> > 
> > eth1      Link encap:Ethernet  HWaddr 00:03:6D:1E:A5:11  
> >           inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:102 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:49 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:100 
> >           RX bytes:10178 (9.9 Kb)  TX bytes:7749 (7.5 Kb)
> >           Interrupt:11 Base address:0x3000 
> 
> This looks normal.  You are both sending and receiving packets.  No
> errors have been reported.
> 
> > [route -n]
> > Kernel IP routing table
> > Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> > 208.20.85.250   0.0.0.0         255.255.255.255 UH    0      0        0 ppp0
> > 192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1
> > 192.168.10.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0
> > 0.0.0.0         208.20.85.250   0.0.0.0         UG    0      0        0 ppp0
> 
> Your default route is through the ppp0 link.
> 
> > [log of attempt to transmit packets to one computer on each network and
> > their affects on /proc/net/dev]
> 
> Note that 'ping' must resolve the address using ARP before sending its
> packets.  Thus the "packets sent" report from 'ping' is not meaningful
> when there is no ARP response.
> 
> This *really does* look like a routing problem.  Make certain that you
> understand which cable is plugged into which network card.
> 
> Donald Becker				becker@scyld.com
> Scyld Computing Corporation		http://www.scyld.com
> 410 Severn Ave. Suite 210		Second Generation Beowulf Clusters
> Annapolis MD 21403			410-990-9993
> 
> 

-- 
Michael Olson
Carnegie Mellon University
School of Industrial Administration