IP routing troubles

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi there.

I have a small problem here with configuring some linux boxes in a way
to route ip traffic to another gateway. Maybe someone in here could help
me with it or point me to the correct piece of documentation...?

The situation is as follows:
Assume we have a corporate network, using the class c network
192.168.1.0/24. The gateway between this network and the internet is
situated at the host 192.168.1.30, which is an isdn dialup router and
works fine so far. Now I have another box within this subnet, lets call
it wired2. wired2 has two interfaces, eth0 with 192.168.1.101 (which is
a normal ethernet interface connected to the corporate network) and
wvlan0 with 10.0.0.1 (which is a wireless lan interface that works in
network 10.0.0.0/24). There is a third box, called wired1. wired1 has an
ethernet interface eth0 with ip 192.168.2.1 but no connection to any
physical network, and again a wvlan0 with ip 10.0.0.100. 

What I want to do is to set up wired1 and wired2 in a way that allows me
to ping any host within the corporate network and any host in the
internet. This means that wired2 works as gateway for wired1.

wired{1,2} work with kernel 2.2.15, which has ip_forwarding included, as
well as "optimize as router, not as host", because both boxes will act
as router in a later step (wired1 will be the router for the
192.168.2.0/24 network).

wired1 has the following routes:
network 192.168.2.0/24 reachable on eth0
network 10.0.0.0/24 reachable on wvlan0
default route via gateway 10.0.0.1

wired2 has the following routes:
network 192.168.1.0/24 reachable on eth0
network 10.0.0.0/24 reachable on wvlan0
default route via gateway 192.168.1.30

What works up to now is the following:
- ping from wired1 to wired2´s wvlan0 (10.0.0.100 -> 10.0.0.1) and vice
versa
- ping from wired1 to wired2´s eth0 (10.0.0.100 -> 192.168.1.101)
- ping from wired2 to any host in 192.168.1.0
- ping from wired2 to hosts within the internet

What does not work is:
- ping from wired1 to hosts in 192.168.1.0
- ping from wired1 to hosts in the internet

I configured wvlan0 and eth0 to be in promiscious mode on wired{1,2},
/proc/sys/net/ipv4/ip_forward is set to 1,
/proc/sys/net/ipv4/conf/*/forwarding is set to 1. I even tried to use
forwarding rules for ipchains, but that did not work, as well as any
other step made by now.
A traceroute from wired1 to 192.168.1.30 shows that wired1 correctly
sends out the packet to 10.0.0.1 as expected, but then there is no
response. So it seems that wired2 does not forward the package
correctly.

I have no further idea what could be missing. Is there anyone who could
give me a hint what to look for? I´m going crazy because of this sh...
:)

Bye, Mike
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux