[ILUG] ref : Multihomed Linux

From: Mark (nvm1 at domain yahoo.com)
Date: Sun 19 Sep 1999 - 20:52:00 IST


Hi Guys,

Can you please have a look at the message below.
I have had this problem recently myself, but thought
the problem was with myself & not linux routing.

Couple of fellow newbies have asked me the same
question ...

I trust you guys can solve this simple problem.
Ps: I had similar problems with redhat 5.2 / free bsd
2.2.7 .

Cheers

-----Original Message-----
From: Richard Carroll [mailto:rich_carroll at domain yahoo.com]
Sent: 19 September 1999 20:26
To: syscon at domain oceanfree.net
Cc: rich_carroll at domain yahoo.com
Subject: Linus Routing Query

Mark,

Here goes......

 

         Win 98 Client #1
          SuSE Linux 6.1
         Win 98 Client #2
 

 IP 10.0.0.14
 10.0.0.10 IP 137.213.188.12
       IP 137.213.188.11
 NM 255.255.255.0
255.255.255.0 NM 255.255.254.0
  NM 255.255.254.0
 GW 10.0.0.10
    ne2000 3c509
          GW 137.213.188.12
                                                      
               eth1 eth0
                                   |
            |
                 | |
                                        |
            |
                 | |
                                        |
            |__________________________________|
                         |________________________ |

 From the 10. network, the workstation
                                              
Likewise, the # 1client on 137. can ping the two IP
 (client #1) will ping the eth1 I/F in the
                                                    
addresses configured on the Linux machine -
 Linux machine - 10.0.0.10 and also the
                                              
137.213.188.12 and 10.0.0.10 BUT cannot ping
 137.213.188.12 address. However, it gets
                                              any
devices futher on such as client #1 at
 a request timed out when trying to ping
                                                
10.0.0.14
 another machine on the 137 network e.g.
 137.213.188.11 (Client #2)

 

 

   The ifconfig from the Linux machine is:

   dummy0 Link encap:Ethernet HWaddr
00:00:00:00:00:00
          inet addr:137.213.188.12
Bcast:137.213.255.255 Mask:255.255.255.255
          UP BROADCAST RUNNING NOARP MTU:1500
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

eth0 Link encap:Ethernet HWaddr
00:10:4B:41:BD:8B
          inet addr:137.213.188.12
Bcast:137.213.189.255 Mask:255.255.254.0
          UP BROADCAST RUNNING MULTICAST MTU:1500
Metric:1
          RX packets:132 errors:0 dropped:0 overruns:0
frame:0
          TX packets:42 errors:0 dropped:0 overruns:0
carrier:0
          collisions:0 txqueuelen:100
          Interrupt:10 Base address:0x200

eth1 Link encap:Ethernet HWaddr
00:00:1B:3E:5B:B3
          inet addr:10.0.0.10 Bcast:10.0.0.255
Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500
Metric:1
          RX packets:1234 errors:0 dropped:0
overruns:0 frame:0
          TX packets:1104 errors:0 dropped:0
overruns:0 carrier:0
          collisions:0 txqueuelen:100
          Interrupt:5 Base address:0x300

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:194 errors:0 dropped:0 overruns:0
frame:0
          TX packets:194 errors:0 dropped:0 overruns:0
carrier:0
          collisions:0 txqueuelen:0

 

  The contents of the /etc/route.conf:

#
# /etc/route.conf

#
# Net devices
# 193.141.17.192 0.0.0.0
255.255.255.192 eth0

# Net behind a Gateway
# 193.141.17.145 193.141.17.193
255.255.255.0
#
# Multicast route for e.g. eth0. IP multicasting,
forwarding and perhaps
# multicast routing in kernel should be enabled.
More information will
# be found in the NET-3-HOWTO. Most people do NOT
need this feature.
#
# 224.0.0.0 0.0.0.0 240.0.0.0 eth0
#
# ISDN (i4l)
# 192.168.0.1 0.0.0.0
255.255.255.255 ippp0
# default 192.168.0.1
137.213.188.0 0.0.0.0
255.255.254.0 eth0
10.0.0.0 0.0.0.0
255.255.255.0 eth1

 

  and the output from the route command is:

Kernel IP routing table
Destination Gateway Genmask
Flags Metric Ref Use Iface
suse.homenet.or * 255.255.255.255 UH
   1 0 0 dummy0
10.0.0.0 * 255.255.255.0
     U 0 0 0 eth1
137.213.188.0 * 255.255.254.0
 U 0 0 0 eth0
loopback * 255.0.0.0
      U 0 0 0 lo

My (weak) understanding of the routing table seems to
suggest that access to the 10. network
is through eth1 and to the 137 network is thru eth0.
Although I can ping both cards in the
Linux server from each side, packets don't seem to be
able to progress any further. Without
any documentation (other that the exquisitely
translated book that came with the distribution),
do I still need to enable forwarding in some way -
e.g. rebuild the kernel for example.
 

__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com



This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:04:34 GMT