[tulip] LinkSys Etherfast 100 problems
Brian C
brianc@pcisys.net
Wed, 22 Nov 2000 21:01:40 -0600
Hi,
I'm not sure if I'm chasing the right problem or not, so here's the complete scoop.
I have a linux box (kernel 2.2.16) that I want to set up as a firewall and masquerader. I
have a 3Com 3c509 connected to the local network. I have a Linksys etherfast 100 (new
within the last two months) that needs to connect to my new Sprint broadband modem.
This is for the Sprint wireless broadband, so it's not a cable modem or DSL modem.
When it was installed two days ago, we hooked it up to a Windows machine with a 3com
3c905? 10/100 card. Using DHCP, it connected quickly to the broadband modem and got
it's assigned IP. Everything is working wonderfully in this configuration.
When I move the cable over to the Linux box, all is not so well. The local net's 3c509 is
set up as eth0 and the linksys is eth1. Yes, the driver loads fine and 'dhcpcd eth1'
configures eth1 perfectly. So it talks to the broadband modem right??
Anyway, once this is done, dhcpcd also sets the default route to eth1. My static IP is
xx.x.xx.253 and the broadband modem has an IP of xx.x.xx.252. From the linux box, I
can ping xx.x.xx.253, but not xx.x.xx.252! Everything should be working.
Here is the output from netstat -rn:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
xx.x.xx.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 xx.x.xx.252 0.0.0.0 UG 0 0 0 eth1
and here is the output from ifconfig:
eth0 Link encap:Ethernet HWaddr 00:60:8C:F4:18:3F
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:26 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:10 Base address:0x300
eth1 Link encap:Ethernet HWaddr 00:20:78:1E:FE:78
inet addr:66.1.98.253 Bcast:66.1.98.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MTU:1500 Metric:1
RX packets:11 errors:0 dropped:0 overruns:0 frame:0
TX packets:229 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:9 Base address:0x4c00
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:67 errors:0 dropped:0 overruns:0 frame:0
TX packets:67 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
and here is the output of cat /proc/pci:
PCI devices found:
Bus 0, device 12, function 0:
VGA compatible controller: Weitek P9100 (rev 0).
Medium devsel.
Non-prefetchable 32 bit memory at 0xfe000000 [0xfe000000].
Bus 0, device 14, function 0:
Ethernet controller: Unknown vendor Unknown device (rev 17).
Vendor id=1317. Device id=985.
Medium devsel. Fast back-to-back capable. IRQ 9. Master Capable. Latency=64.
Min Gnt=255.Max Lat=255.
I/O at 0xfc00 [0xfc01].
Non-prefetchable 32 bit memory at 0xffbe7c00 [0xffbe7c00].
Bus 0, device 16, function 0:
Host bridge: UMC UM8881F (rev 4).
Medium devsel. Master Capable. No bursts.
Bus 0, device 18, function 0:
ISA bridge: UMC UM8886A (rev 14).
Medium devsel. Master Capable. No bursts.
Bus 0, device 18, function 1:
IDE interface: UMC UM8886BF (rev 16).
Fast devsel. Master Capable. No bursts.
I/O at 0x170 [0x171].
I/O at 0x374 [0x375].
I/O at 0xffe0 [0xffe1].
I/O at 0xfff0 [0xfff1].
I/O at 0xffa0 [0xffa1].
What concerns me is the discrepancy between the ifconfig and the pci outputs.
Notice that according to the /proc/pci, my pci ethernet card is at I/O 0xfc00 and ifconfig
reports the I/O at 0x4c00? Anyway, tulip-diag reports the same as /proc/pci. Maybe that
just because it reads that file?
When I try to ping xx.x.xx.252, the TX packets go up considerably and the RX packets
barely move.
Remember I said that the broadband modem and cable work fine when connected to a Win
machine...
I'm looking for ideas.. do the address differences mean anything? Do I need to look
elsewhwere for the answer to this problem?
Thanks for any and all info.
Brian