[WBEL-users] Newby at Ip Forwarding

[Bill Davidsen]

Jesús García González wrote:
> Hello, 
> 
> Please Help
> 
> I just added a second network card to a Compaq Proliant ML 310. At first it
> stopped recognizing the original card (had to remove both cards from kudzu
> database to have them both reinstalled) Anyway, now I have both cards
> working (properly?):
> 
> eth0      Link encap:Ethernet  HWaddr 00:0B:CD:CF:CA:87
>           inet addr:10.90.35.7  Bcast:10.90.35.255  Mask:255.255.255.0
>           (…)
> 
> eth1      Link encap:Ethernet  HWaddr 00:40:F4:84:AD:9C
>           inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
>           (…)
> 
> I then turned IP forwarding on:
> 
> [root@minerva etc]# echo "1" > /proc/sys/net/ipv4/ip_forward
> 
> 
> The route table on the server is the following:
> 
> [root@minerva log]# route
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> 10.90.35.0      *               255.255.255.0   U     0      0        0 eth0
> 192.168.2.0     *               255.255.255.0   U     0      0        0 eth1
> 192.168.1.0     *               255.255.255.0   U     0      0        0 eth1
> 169.254.0.0     *               255.255.0.0     U     0      0        0 eth1
> 127.0.0.0       *               255.0.0.0       U     0      0        0 lo
> [root@minerva log]#
> 
> The test PC has this route table:
> 
> ===========================================================================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x2 ...00 08 74 9f b0 6e ...... 3Com 3C920 Integrated Fast Ethernet
> Controller (
> 3C905C-TX Compatible) - Packet Scheduler Miniport
> ===========================================================================
> ===========================================================================
> Active Routes:
> Network Destination        Netmask          Gateway       Interface  Metric
>           0.0.0.0          0.0.0.0       10.90.35.1     10.90.35.61       20
>        10.90.35.0    255.255.255.0      10.90.35.61     10.90.35.61       20
>       10.90.35.61  255.255.255.255        127.0.0.1       127.0.0.1       20
>    10.255.255.255  255.255.255.255      10.90.35.61     10.90.35.61       20
>         127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
>       192.168.1.0    255.255.255.0       10.90.35.7     10.90.35.61       1
>       192.168.2.0    255.255.255.0       10.90.35.7     10.90.35.61       1
>         224.0.0.0        240.0.0.0      10.90.35.61     10.90.35.61       20
>   255.255.255.255  255.255.255.255      10.90.35.61     10.90.35.61       1
> Default Gateway:        10.90.35.1
> ===========================================================================
> Persistent Routes:
>   None
> 
> The server can ping pc's on both networks (10.90.35.0) & (192.168.1.0) but a
> pc on one network can't ping the other.
> 
> When I run a tracert at 10.90.35.61 I get:
> 
> C:\ >tracert -d 192.168.1.1
> 
> Tracing route to 192.168.1.1 over a maximum of 30 hops
> 
>   1    <1 ms    <1 ms    <1 ms  10.90.35.7
>   2     *        *        *     Request timed out.
>   3     *        *        *     Request timed out.
>   4     *        *        *     Request timed out.
>  (...)
> 
> I should conclude that my Linux Server is not forwarding packets from one
> network to the other.
> Please, can somebody help me? What Am I doing wrong?
> 
> Note: (IPTables has no rules and the default policy is accept)

This is not really a WBEL problem, this is a general networking problem. 
  Unless someone wants to do your search for you, google for 
linux+forwarding or ask in a Linux networking group.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me