[K12OSN] OT - Linux router - I'm stuck <-long

Tom Haynes haynest at mchsi.com
Fri Mar 26 14:48:50 UTC 2004


Tim...

While I am fundamentally a nice guy, I am not really the person to be
sorting out routing problems.

I am guessing that there are other folks on the list more able with this
kind of stuff, but they are hesitating to get in the middle of this when
they are not local.

I don't know exactly what to advise, but maybe someone will speak up.

Regards...   Tom

-----Original Message-----
From: k12osn-bounces at redhat.com [mailto:k12osn-bounces at redhat.com]On
Behalf Of Tim Litwiller
Sent: Friday, March 26, 2004 8:32 AM
To: k12osn at redhat.com
Subject: Re: [K12OSN] OT - Linux router - I'm stuck <-long


Will someone tell me a better place to go ask this question?

Tim Litwiller wrote:

> here is the network diagram
>
> do=district office
> rms=middle school
> rhs=highschool
> pe=elementary school
>
> do network 172.16.96.x <-> 172.16.127.x netmask 255.255.224.0
> eth1 do router ip address 172.16.96.1
> eth0 do to rms interface ip 10.0.0.2 netmask 255.255.255.0
> static routes
> route add -net 172.16.32.0 netmask 255.255.224.0 gw 10.0.0.102
> route add -net 172.16.0.0 netmask 255.255.224.0 gw 10.0.0.102
> route add -net 172.16.64.0 netmask 255.255.224.0 gw 10.0.0.102
> |
> |  radios in bridge are set to 10.0.0.3 and 10.0.0.103
> |
> eth1 rms to do radio interface ip 10.0.0.103 netmask 255.255.255.0
> eth0 rms router ip address 172.16.32.1
> rms network 172.16.32.x <-> 172.16.63.x netmask 255.255.224.0
> eth2 rms to rhs radio interface ip 10.0.1.2 netmask 255.255.255.0
> route add -net 172.16.96.0 netmask 255.255.224.0 gw 10.0.0.2
> route add -net 172.16.0.0 netmask 255.255.224.0 gw 10.0.1.102
> route add -net 172.16.32.0 netmask 255.255.224.0 gw 10.0.1.102
> |
> | radios in bridge are set to 10.0.1.3 and 10.0.1.103
> |
> eth1 rhs to rms radio interface ip 10.0.1.102 netmask 255.255.255.0
> eth0 rhs router ip address 172.16.1.1
> rhs network 172.16.0.x <-> 172.16.31.x netmask 255.255.224.0
> rhs gateway to internet 172.16.1.254
> rhs windows file server 172.16.0.1
> eth2 rhs to pe radio interface ip 10.0.2.3 netmask 255.255.255.0
> route add -net 172.16.32.0 netmask 255.255.224.0 gw 10.0.1.2
> route add -net 172.16.96.0 netmask 255.255.224.0 gw 10.0.1.2
> route add -net 172.16.64.0 netmask 255.255.224.0 gw 10.0.2.102
> |
> | radios in bridge  are set to 10.0.2.3 and 10.0.2.103
> |
> eth0 pe to rhs radio interface ip 10.0.2.102 netmask
> eth1 pe router ip address 172.16.64.1
> pe network 172.16.64.x <-> 172.16.95.x netmask 255.255.224.0
> route add -net 172.16.32.0 netmask 255.255.224.0 gw 10.0.2.2
> route add -net 172.16.0.0 netmask 255.255.224.0 gw 10.0.2.2
> route add -net 172.16.96.0 netmask 255.255.224.0 gw 10.0.2.2
>
>
>
> the problem seems to be some setting on the rms router
> at the console of the machine
> from do I can ping rms
> from rms I can ping rhs and pe and do
> from rhs I can ping all and internet
> from pe I can ping all and internet
>
> from laptop on each network
> from do I can ping do and rms
> from rms I can ping do and rms
> from rhs I can ping all and internet
> from rhs I can ping all and internet
>
> so rms isn't passing anything from eth1 and eth0 thru to eth2
>
> in /etc/sysctrl I have
> net.ipv4.ip_forward = 1
> net.ipv4.conf.default.proxy_arp = 1
>
> cat /proc/sys/net/ipv4/ip_forward  cat
> /proc/sys/net/ipv4/conf/eth0/proxy_arp
> cat /proc/sys/net/ipv4/conf/eth1/proxy_arp
> cat /proc/sys/net/ipv4/conf/eth2/proxy_arp
>
> the output of each of these is 1
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> K12OSN mailing list
> K12OSN at redhat.com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
>
>
>



_______________________________________________
K12OSN mailing list
K12OSN at redhat.com
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.596 / Virus Database: 379 - Release Date: 2/26/2004





More information about the K12OSN mailing list