On 02/01/2013 01:55 PM, Ville Walveranta wrote: > Simon, > > Thanks for that guidance! It was enough for me to complete the > configuration. As you suggested, adding the return route to LAN2's > router helped – I had completely overlooked it thinking that the return > route would automatically follow the same path as the incoming request > (from LAN1). I also added a specific address in masq (the interface > address of the Shorewall box facing LAN2) to ensure that all the > requests will appear to be coming from the Shorewall gateway, in other > words: > > $LAN2_IF 10.0.0.0/24 10.0.0.253 >
I doubt that entry is doing anything useful. It says "Any packets routed out to LAN2 that have a source address in 10.0.0.0/24 should have the source changed to 10.0.0.253". -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
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
