Laurent Blin wrote: > Hello, > > I use Shorewall version 4.0.6. > > Our LAN is composed of 2 subnetworks. One 192.9.200.x is "local", > directly connected to our firewall (192.9.200.200). > Acces from this sublan to internet works fine (zone named "LAN") > 192.9.200.0 -> 192.9.200.200 (fw) -> NET > > The other LAN is distant (10.44.40.0/24), connected through a WAN (local > router address is 192.9.200.100, remote router address is 10.44.40.250) > I've followed the "Routing on one interface" web page. I've added the > routes on both sides, and tested: > > (remote LAN to router) Ping from 10.44.40.105 to 10.44.40.250: OK > (remote LAN to LAN) Ping from 10.44.40.105 to 192.9.200.150; OK > (remote LAN to firewall) Ping from 10.44.40.105 to 192.9.200.200: OK > (firewall to remote LAN): Ping from 192.9.200.200 to 10.44.40.105: OK: > (LAN to internet) Ping from 192.9.200.150 to www.google.fr: OK > (remote LAN to internet): Ping from 10.44.40.105 to www.google.fr: NOK > (nslookup is fine)
You need to masquerade 10.44.40.0/24 out of eth2. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
