On 2013-04-26 16:39:18 +0000, Tom Eastep said:
On 04/26/2013 09:32 AM, Troy Telford wrote:I did notice something on my network, and I think I'm missing a option: I have several zones, and all but one are working wonderfully. The configuration for the different zones is identical... The zone that's not working well is the zone I've created for my LXC containers. They're all bridged across a br0 interface, and my config is pretty simple: TPROXY(3129) br0:!192.168.2.1 0.0.0.0/0 tcp 80 and the rule: ACCEPT lxc $FW tcp www The LXC containers are running on the routerWe're going to need something more than two entries from your configuration and a lament that 'it doesn't work'.
I apologize. I deserve the reprimand.Hopefully I've attached the bzip2 shorewall dumps. I typically use gmane for my mailing lists, so it may not pass through the attachments. If they aren't, I'll re-send via a normal mail client.
While you're looking: I applied the suggested change: TPROXY(3129) ethX:!<ethX ip addr> 0.0.0.0/0 tcp 80However, I am still unable to connect to the apache server on the shorewall box...
(null)
Description: Binary data
-- Troy Telford
------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
