On Thu, 30 Jun 2011 06:13:28 -0700, Tom Eastep wrote:
> On Thu,
2011-06-30 at 06:05 -0700, Tom Eastep wrote:
>> On Thu, 2011-06-30 at
09:26 -0300, Ricardo Rios - Shorewall List wrote:
>>
>>> Hi Tom, sorry
if i re-open this, i have another issue now, i dunno if is something of
shorewall or the tproxy support.
>> It's your configuration. You don't
have an ACCEPT rule for port 80 from lan to fw.
> And please let me know
if that works so I can update the HOWTO. I didn't have the software to
properly test TPROXY support when I developed it, so I could only verify
that it was generating the same rules as were recommended in the HOWTO
that I followed. -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 [1]
________________________________________________
Well, i set the rule
for allow lan to fw port 80, now there is nothing show on
/var/log/firewall.
But navigation is not working, and when i check
squid logs shows : http://pastebin.com/b0j3rjhH [2]
Links:
------
[1] http://shorewall.net
[2]
http://pastebin.com/b0j3rjhH
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
