On 2/17/2014 8:07 AM, Rodrigo Cortes wrote: > HTTP access to 190.153.181.212
I can see nothing in the dump that would prevent that from working -- and there are many existing connections to 190.143.181.212 port 80. One thing that I do notice in the dump is that you have asymmetric routing in your local LAN. Packets from 192.168.1.0/24 to 10.*.*.* go through the Shorewall box but response packets do not. I doubt that is relevant to the connection problems you are experiencing. My only suggestion is to use tcpdump or Wireshark to try to understand what is happening when connections are not working. -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
------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
