From: Devaney, Matthew (matthew.devaney_at_convergys.com)
Date: 2002-06-12 19:47:45 UTC
I had this problem .. I needed to add a couple of iptables lines as follows:
iptables -A FORWARD -i eth1 -s 192.168.0.0/16 -d 192.168.1.0/16 -j ACCEPT iptables -A FORWARD -i wlan0 -s 192.168.1.0/16 -d 192.168.0.0/16 -j ACCEPT
(where eth1 is over the network 192.168.0.0,
wlan0 is over the network 192.168.1.0)
Then it all suddenly started working.. A computer with address of 192.168.1.X can now ping/connect to a machine with ip addi 192.168.0.X and vice-versa.
Maybe it'll work for you too, or maybe not =)
Matt
>-----Original Message-----
>From: Ted Phelps [mailto:phelps_at_dstc.edu.au]
>Sent: 12 June 2002 20:40
>To: Scott Weisman; hostap_at_lists.ssh.com
>Subject: Re: routing question - please help
>
>
>Scott Weisman may have said:
>> I am attempting to setup a STRIP network (which uses
>wireless Ricochet
>> modems). The wireless network is set up on a server I have
>on my LAN. Here
>> are the particulars:
>>
>> LAN: 10.0.0.0/16
>> STRIP: 10.1.0.0/16
>> Server: 10.0.0.1 eth0, 10.1.0.1 st0
>
>Hi Scott,
>
>Your routing table looks fine to me. A couple of things to try:
>
>- Can you ping the server from both networks?
>- Have you enabled forwarding on all of the interfaces?
> (echo 1 > /proc/sys/net/ipv4/conf/all/fowarding)
>
>If that doesn't work, I recomment the Network Administrators Guide:
>
> http://www.tldp.org/LDP/nag2/
>
>Cheers,
>-Ted
>
-- NOTICE: The information contained in this electronic mail transmission is intended by Convergys Corporation for the use of the named individual or entity to which it is directed and may contain information that is privileged or otherwise confidential. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by telephone (collect), so that the sender's address records can be corrected.