Routing problems ...

Routing problems ...

Post by Tom Hutto » Fri, 31 Oct 1997 04:00:00



I have a linux box that I am attempting to get to act as a router, then
perhaps if I can get this working, I'll turn on firewalling.  The Cisco
router to the internet's interface is at 249.149.6.1, which plugs into a
hub where the Linux router is.  The linux box has two NICs in it, the
one plugged into the Cisco hub is 209.149.6.2/255.255.255.224, the card
plugged into a hub with various servers is
209.149.6.38/255.255.255.224.  

Ifconfig returns the following:
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
          UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
          RX packets:86 errors:0 dropped:0 overruns:0 frame:0
          TX packets:86 errors:0 dropped:0 overruns:0 carrier:0 coll:0

eth0      Link encap:Ethernet  HWaddr 00:60:08:03:95:A5
          inet addr:209.149.6.2  Bcast:209.149.6.31
Mask:255.255.255.224
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:232 errors:0 dropped:0 overruns:0 frame:0
          TX packets:54 errors:0 dropped:0 overruns:0 carrier:0 coll:0
          Interrupt:9 Base address:0x6100

eth1      Link encap:Ethernet  HWaddr 00:60:08:03:95:4C
          inet addr:209.149.6.38  Bcast:209.149.6.63
Mask:255.255.255.224
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:426 errors:1 dropped:0 overruns:0 frame:1
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 coll:0
          Interrupt:11 Base address:0x6200

Route returns the following:
Kernel IP routing table

Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
209.149.6.0     0.0.0.0         255.255.255.224 U     0      0        2
eth0
209.149.6.32    0.0.0.0         255.255.255.224 U     0      0        0
eth1
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        1
lo
0.0.0.0         209.149.6.1     0.0.0.0         UG    1      0        1
eth0

When pinging a host on the other side of the Linux box from either
direction, the ping fails.  The Linux box itself can be pinged (both
interface).  It appears to have a routing problem, although it isn't
obvious to me what the problem is.

TIA

 
 
 

Routing problems ...

Post by Walker Auma » Fri, 31 Oct 1997 04:00:00



> I have a linux box that I am attempting to get to act as a router, then
> perhaps if I can get this working, I'll turn on firewalling.  The Cisco
> router to the internet's interface is at 249.149.6.1, which plugs into a
> hub where the Linux router is.  The linux box has two NICs in it, the
> one plugged into the Cisco hub is 209.149.6.2/255.255.255.224, the card
> plugged into a hub with various servers is
> 209.149.6.38/255.255.255.224.  

Your routing table looks right, so I'd guess that you don't have IP
forwarding enabled.  Make sure it's built into your kernel.  You may also
need to do something like:

ipfwadm -F -a a -S 209.149.6.32/224 -D 0.0.0.0/0

Walker

 
 
 

Routing problems ...

Post by Tom Hutto » Sat, 01 Nov 1997 04:00:00




> > I have a linux box that I am attempting to get to act as a router, then
> > perhaps if I can get this working, I'll turn on firewalling.  The Cisco
> > router to the internet's interface is at 249.149.6.1, which plugs into a
> > hub where the Linux router is.  The linux box has two NICs in it, the
> > one plugged into the Cisco hub is 209.149.6.2/255.255.255.224, the card
> > plugged into a hub with various servers is
> > 209.149.6.38/255.255.255.224.

> Your routing table looks right, so I'd guess that you don't have IP
> forwarding enabled.  Make sure it's built into your kernel.  You may also
> need to do something like:

> ipfwadm -F -a a -S 209.149.6.32/224 -D 0.0.0.0/0

> Walker

I do have forwarding turned on in the kernel, and doing a cat on a file
in proc (I can't remember right now as I am not at work) shows that
forwarding is on.  One thing that I am not sure of, however, is whether
a subnet of the C address with a network address of 0 is legal, as this
is what the first three bits of the C area (.224) are set to on the
router side of the Linux box.

I'll try adding the forwarding stuff in IPFWADM to see, although I don't
have firewalling turned on, and when I did it was defaulting to
accepting everything and forwarding turned on with no rules applied by
me.

Thanks, if you have further ideas please let me know.

--

Remove the <<!!!!>> and !! from the address to reply ..

For the auto-spamers, here's a few addresses from the FCC...




And for good measure......

---------------------------------------------------------------------
|  By sending me unsolicitated commercial email you agree to pay my |
| standard consulting fee of $250/hr for examining your message (a  |
| minimum charge of one (1) hour).  The bill for my service will be |
| sent to you along with my analysis of your message.               |
---------------------------------------------------------------------

 
 
 

Routing problems ...

Post by Radovan Bra » Sat, 01 Nov 1997 04:00:00



   Yes, your tables look right (more cautiously: I didn't see anything
   wrong), but have you told your router and your machines on the
   other side that your local net is subnetted ? Yes, network 0 is
   legal (nowdays), but you may have to configure your Cisco box with
   "ip subnet-zero" (if I remember correctly). And some older machines
   may not accept this. So you have to configure your Cisco so that
   the gateway for 209.149.6.32/27 (this is the usual notation, the
   length of the netmask) is 209.149.6.2, and the machines on the
   other subnet so that  the gateway to 209.149.6.0/27 is 209.149.6.38.
   If you can't do this (e.g. the router is not under your administrative
   control, or some machines don't understand subnetting correctly)
   you'll have to use Proxy ARP for the subnet on the "opposite"
   interface; see "man arp", and there may be a HOWTO or mini-HOWTO on
   Proxy ARP-ing.

      RB



>> > I have a linux box that I am attempting to get to act as a router, then
>> > perhaps if I can get this working, I'll turn on firewalling.  The Cisco
>> > router to the internet's interface is at 249.149.6.1, which plugs into a
>> > hub where the Linux router is.  The linux box has two NICs in it, the
>> > one plugged into the Cisco hub is 209.149.6.2/255.255.255.224, the card
>> > plugged into a hub with various servers is

>> > 209.149.6.38/255.255.255.224.

>> Your routing table looks right, so I'd guess that you don't have IP
>> forwarding enabled.  Make sure it's built into your kernel.  You may also
>> need to do something like:

>> ipfwadm -F -a a -S 209.149.6.32/224 -D 0.0.0.0/0

>> Walker
>I do have forwarding turned on in the kernel, and doing a cat on a file
>in proc (I can't remember right now as I am not at work) shows that
>forwarding is on.  One thing that I am not sure of, however, is whether
>a subnet of the C address with a network address of 0 is legal, as this
>is what the first three bits of the C area (.224) are set to on the
>router side of the Linux box.
>I'll try adding the forwarding stuff in IPFWADM to see, although I don't
>have firewalling turned on, and when I did it was defaulting to
>accepting everything and forwarding turned on with no rules applied by
>me.
>Thanks, if you have further ideas please let me know.
>--

>Remove the <<!!!!>> and !! from the address to reply ..
>For the auto-spamers, here's a few addresses from the FCC...




>And for good measure......

>---------------------------------------------------------------------
>|  By sending me unsolicitated commercial email you agree to pay my |
>| standard consulting fee of $250/hr for examining your message (a  |
>| minimum charge of one (1) hour).  The bill for my service will be |
>| sent to you along with my analysis of your message.               |
>---------------------------------------------------------------------