Routing problem

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Jorgen (jorgen.nordqvist_at_intelliwhere.com)
Date: 05/25/04 

Date: 25 May 2004 03:18:40 -0700

In the diagram below, from B I can ping all interfaces on A and C.
>From C I can only ping B's 10.1.1.9 interface. Given the routing
tables below, is anybody able to tell me where my problem lies?

+-----+
| A | (ADSL modem, NAT enabled, 10.1.1.3 to 10.1.1.32
+-----+ available)
   | 10.1.1.1
   |
   | 10.1.1.3
+-----+
| B | (Win 2k Prof + SP4, IP forwarding enabled
+-----+ in registry, RRAS service running)
   | 10.1.1.9
   |
   | 10.1.1.14
+-----+
| C | (Win 2k Prof + SP4)
+-----+

B's routing table:
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000003 ...00 0e a6 0d ca 90 ...... 3Com EtherLink PCI
0x1000004 ...00 30 bd 4f 5c af ...... Belkin 11Mbps Wireless Desktop
Network Card
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
          0.0.0.0 0.0.0.0 10.1.1.1 10.1.1.3
1
         10.1.1.0 255.255.255.248 10.1.1.3 10.1.1.3
1
         10.1.1.3 255.255.255.255 127.0.0.1 127.0.0.1
1
         10.1.1.8 255.255.255.248 10.1.1.9 10.1.1.9
1
         10.1.1.9 255.255.255.255 127.0.0.1 127.0.0.1
1
   10.255.255.255 255.255.255.255 10.1.1.3 10.1.1.3
1
   10.255.255.255 255.255.255.255 10.1.1.9 10.1.1.9
1
        127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
        224.0.0.0 224.0.0.0 10.1.1.3 10.1.1.3
1
        224.0.0.0 224.0.0.0 10.1.1.9 10.1.1.9
1
  255.255.255.255 255.255.255.255 10.1.1.3 10.1.1.3
1
Default Gateway: 10.1.1.1
===========================================================================
Persistent Routes:
  None

C's routing table:
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 30 bd 4f 5c 4f ...... Belkin 11Mbps Wireless Desktop Network
Card
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
          0.0.0.0 0.0.0.0 10.1.1.3 10.1.1.14
1
         10.1.1.8 255.255.255.248 10.1.1.14 10.1.1.14
1
        10.1.1.14 255.255.255.255 127.0.0.1 127.0.0.1
1
   10.255.255.255 255.255.255.255 10.1.1.14 10.1.1.14
1
        127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
        224.0.0.0 224.0.0.0 10.1.1.14 10.1.1.14
1
  255.255.255.255 255.255.255.255 10.1.1.14 10.1.1.14
1
Default Gateway: 10.1.1.3
===========================================================================
Persistent Routes:
  None

Relevant Pages

  • Point-to-Point interfaces and routing
    ... I have found to myself strange behaviour and difference between routing to IPs on ngX, ... So now I can ping ip on tun0, ... interface: tun0 ...
    (freebsd-net)
  • Re: ethernet routing
    ... > can ping the 10.20.4.48 interface. ... > my routing table is as follows: ... To UNSUBSCRIBE, email to debian-user-request@lists.debian.org ...
    (Debian-User)
  • Re: Traffic NOT moving through the correct network interface?
    ... Kernel IP routing table ... loopback interface, but that's not part of this problem. ... Everything is done by the kernel. ... Policy based routing requires you ...
    (alt.os.linux)
  • Re: PIX: Ping VPN host from inside network
    ... to ping hosts in the vpn subnet pool or vice-versa. ... The same capture applied to the outside interface shows pings heading ... access-list inside_nat0_outbound extended permit ip any 192.168.24.0 ... access-group outside_access_in in interface outside ...
    (comp.security.firewalls)
  • Re: Linux routing mystery. No replies until machine sources traffic.
    ... The machine has an interface on each of these ... You cannot have more than one default route. ... A machine can ping ... 1.1.1.0/24 dev eth0 proto kernel scope link src 1.1.1.5 ...
    (comp.os.linux.networking)