Traffic NOT moving through the correct network interface?

Machine is running Debian 4.0r1 2.6.22-3-686. This machine has three network
connections.

eth0:
- static IP of 10.0.11.16 with a mask of 255.255.255.0
- connected to a router, which is connected to the rest of my LAN and a
cable modem #1
- This is the onboard Intel gigabit LAN port of my Asus P4C800E-Dlx
- Pingable from a Windows PC on my LAN

eth1:
- dynamic IP
- connected directly to cable modem #2
- This is an Intel Pro100 PCI network card
- Pingable from a Windows PC on my LAN
- NOT pingable from an external internet connection

eth2:
- dynamic IP
- connected directly to cable modem #1
- This is using the USB connection of the cable modem
- Pingable from a Windows PC on my LAN
- NOT pingable from an external internet connection

I've pasted the results from ifconfig below. You'll notice that there are
almost NO packets going out of eth1 and eth2. The only way that I can
increment these counters is to ping out from the specific interface (ping
google.ca -I eth1).

There have only been 24 packets transmitted out of eth1, yet I currently
have an SSH session open from a Windows PC on my LAN to the IP addess on
eth1. This means that the Windows PC should be going out through the router
and cable modem #1 then to the Linux box through cable modem #2. Netstat
confirms that there are sessions established on the ports used by SSH.

WHAT is going on here? Can someone point me in the right direction as far as
troubleshooting this?


eth0 Link encap:Ethernet HWaddr 00:0e:a6:0b:2d:4d
inet addr:10.0.11.16 Bcast:10.0.11.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2504496 errors:0 dropped:0 overruns:0 frame:0
TX packets:1457281 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3390613882 (3.1 GiB) TX bytes:266230328 (253.8 MiB)
Base address:0xcf80 Memory:f79e0000-f7a00000

eth1 Link encap:Ethernet HWaddr 00:a0:c9:a2:2e:85
inet addr:68.333.444.555 Bcast:255.255.255.255
Mask:255.255.252.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:409302 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:25242346 (24.0 MiB) TX bytes:2664 (2.6 KiB)

eth2 Link encap:Ethernet HWaddr 00:0e:5c:13:07:e5
inet addr:68.999.888.777 Bcast:255.255.255.255
Mask:255.255.252.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:408253 errors:0 dropped:0 overruns:0 frame:0
TX packets:51 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:19461994 (18.5 MiB) TX bytes:7555 (7.3 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


.

Relevant Pages

  • Re: NETWORK CONNECTIONS query
    ... "In 2 adjacent PCI slots are 2 LAN cards ... Ethernet cable modem goes to one, ... Where, please, is Local Area Connection 2, and why isn't it reporting? ... the second LAN connection is named "Local Area ...
    (microsoft.public.windowsxp.basics)
  • Re: Connecting TWO Routers
    ... The FIRST is a WRT100 that is connected to the Cable modem. ... With a LAN IP of 192.168.251.1 and DHCP turned on (range ... The second is a WRT54G. ... connection available at the remote end to connect back to the WRT100. ...
    (alt.internet.wireless)
  • Re: Connecting TWO Routers
    ... The FIRST is a WRT100 that is connected to the Cable modem. ... With a LAN IP of 192.168.251.1 and DHCP turned on (range ... The second is a WRT54G. ... connection available at the remote end to connect back to the WRT100. ...
    (alt.internet.wireless)
  • Re: New modem and iptables...
    ... because it starts connection by himself ... I had this set of rules on my my computer acting as a router. ... But the LAN didn't work. ... UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 ...
    (Fedora)
  • Re: Cablemodem/connection
    ... > but it doesnt seem to see my cable modem ... > connection?, i'm a complete linux newbie so need some help. ... I can tell you how to set it up so that it does work: route if via LAN to ...
    (alt.os.linux.suse)