All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John Cushnie" <cushnie@csi.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Routing and Shaping using RedHat7.3
Date: Wed, 25 Sep 2002 16:12:39 +0000	[thread overview]
Message-ID: <marc-lartc-103297049229358@msgid-missing> (raw)

Hi all,

I'm running RH7.3 plus errata.
I've read through the HowTo and I had something like this configuration 
working on RH7.1, but it looks like the interface to IP and ROUTE has 
changed considerably since then.....

I'm trying to set up a simple router configuration to route between 
subnets, as shown in the diagram. 
My aim is to provide traffic shaping between the 194.80.34.0 
hosts and the 148.88.0.0 and 192.168.106.0 networks. 

                                         148.88.0.0 network          
                    --------+-------------------------------+-----
        __                  |                               |
    ___/  \_         +------+-----------------+
+-------+-----------+
  _/        \__      |     eth2 148.88.155.253|     |eth1
148.88.154.150|
 /             \     |                        |     |
|  
|    network    -----+ eth0 194.80.34.202     |     |       WinXP
|
 |  194.80.34.0 |    |  Linux router          |     |
|
 \_           __/    |                        |     |    192.168.106.1
|
   \__     __/       |     eth1 192.168.106.2 |     |       eth0
|
      \___/          +------+-----------------+
+---------+---------+
                            |                                 |  
                            |       192.168.106.0 network     |
                        ----+---------------------------------+-------- 
                                         

The routes and addresses for the Linux box are as listed below. I have
enabled ip-forwarding:
# cat /proc/sys/net/ipv4/ip_forward   
1
# cat /proc/sys/net/ipv4/conf/eth2/forwarding 
1
# cat /proc/sys/net/ipv4/conf/eth0/forwarding 
1
# cat /proc/sys/net/ipv4/conf/eth1/forwarding 
1

From the Linux host I can ping all the subnets I have defined and have 
connections to.
Ie:
   Ping 192.168.106.1
   Ping 148.88.154.150
   Ping 194.80.34.35 (Remote Host)

When I try to ping from the WinXP machine I get mixed results.
Ie:
   Ping 192.168.106.2 -- works fine
   Ping 194.80.34.202 -- works fine
   Ping 194.80.34.35 (Remote Host) 
      -- doesn't work
      -- Using Ethereal I see the ARP request at eth2 rom the WinXP 
         on the Linux router but no response, and then time out at 
         the WinXP box.               

Not quite sure the pings don't work in the configuration I have, unless
I 
have missed something in the routing tables or a basic configuration 
parameter. Any suggestions ?
Do I need further routes defining ?
Do I need to enable something to allow ARP requests to be responded to ?

Is there any way to check if the required routing is enabled in the
kernel ?

Thanks in advance for any suggestions.
John Cushnie.
Email: cushnie@csi.com

=============================
Routes:
====
# /sbin/ip route list 
192.168.106.0/24 via 192.168.106.2 dev eth1  scope link 
194.80.34.0/24 via 194.80.34.202 dev eth0  scope link 
192.168.0.0/16 dev eth1  scope link 
148.88.0.0/16 via 148.88.155.253 dev eth2  scope link 
148.88.0.0/16 dev eth2  scope link 
127.0.0.0/8 dev lo  scope link 
default via 194.80.34.99 dev eth0 

Addresses:
=====# /sbin/ip address list
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: eth0: <BROADCAST,MULTICAST,PROMISC,NOTRAILERS,UP> mtu 1500 qdisc
pfifo_fast qlen 100
    link/ether 00:04:76:f3:b4:56 brd ff:ff:ff:ff:ff:ff
    inet 194.80.34.202/24 brd 194.80.34.255 scope global eth0
3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
    link/ether 00:04:76:f3:b2:65 brd ff:ff:ff:ff:ff:ff
    inet 192.168.106.2/16 brd 192.168.106.255 scope global eth1
4: eth2: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
    link/ether 00:01:02:df:c2:38 brd ff:ff:ff:ff:ff:ff
    inet 148.88.155.253/16 brd 148.88.155.255 scope global eth2


==================================




_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2002-09-25 16:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-25 16:12 John Cushnie [this message]
2002-09-26 14:29 ` [LARTC] Routing and Shaping using RedHat7.3 John Cushnie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-103297049229358@msgid-missing \
    --to=cushnie@csi.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.