muiz wrote: > I tried this: > modified masq file as: > #INTERFACE SUBNET ADDRESS PROTO PORT(S) > IPSEC > eth1 192.168.1.0/27 > eth1 192.168.1.139 > #LAST LINE -- ADD YOUR ENTRIES ABOVE THIS LINE -- DO NOT REMOVE > and then update the client computer's ip to 192.168.1.139. and it can > access internet! > > Then change masq to : > #INTERFACE SUBNET ADDRESS PROTO PORT(S) > IPSEC > eth1 192.168.1.0/27 > eth1 192.168.1.140 > #LAST LINE -- ADD YOUR ENTRIES ABOVE THIS LINE -- DO NOT REMOVE > then restart the shorewall, > and also update the client computer's ip to 192.168.1.140, but it can > NOT access internet! > > Why?
Whatever the cause of the problem, it is not your shorewall configuration. From the dump, there is no obvious reason. But then 'can NOT access internet' tells us nothing: a) Can 192.168.1.140 ping 192.168.1.20? b) Can 192.168.1.140 ping 192.168.0.250? c) Can 192.168.1.140 ping 192.168.0.249? d) Can 192.168.1.140 ping 206.124.146.177? -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
------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge
_______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
