Hi Ferry, the problems is fixed. A tcpdump -i eth1 shows it works fine. Me goes stand in corner and writes, must forward packets both way :) The second iptables rule below was not added. To your other msg, the client I was using is 192.168.150.50 :) Thanks for the help. Regards Gary. > Oh I forgot. I only see one line.... > -t filter is default btw so I'll omit > > iptables -A FORWARD -s 192.168.150.0/255.255.255.0 -i eth0 -d > 192.168.151.0/255.255.255.0 -o eth1 -j ACCEPT > iptables -A FORWARD -s 192.168.151.0/255.255.255.0 -i eth1 -d > 192.168.150.0/255.255.255.0 -o eth0 -j ACCEPT > > Remember that traffic is always two ways. For traffic to exist not only > should 150.x be allowed to send to 151.x, 151.x should also know how to > and be allowed to send to 150.x > > In short > > The 192.168.150.x network should have routes to the 192.168.151.x > network and have firewall access > The 192.168.151.x network should have routes to the 192.168.150.x > network and have firewall access > The linux server should have both routes (it has by default since it has > network cards/interfaces in those segments) and have ip_forwarding > enabled (you did this) and shouldn't block the traffic by any means > (iptables comes to mind as does rp_filter, but rp_filter should be safe > in this case) > > Regards > >
