PaulDotCom mailing list archives
transparent proxy and iptables failing
From: dninja at gmail.com (Robin Wood)
Date: Thu, 8 Oct 2009 13:38:52 +0100
2009/10/8 Ben Greenfield <bcg at struxural.com>:
I think you need to add a route for your bridge. ?Assuming your bridge device is still br-lan, with the 192.168.0.0/24 network, you need to add this route to the kernel routing table for that device, and this command should do it: route add -net 192.168.0.0/24 dev br-lan When I was debugging my setup, I was using tcpdump on the various interfaces while pinging different networks to see if the traffic was flowing. Let me know if that fixes things..
I'll be testing things tonight but all the routing works fine. Devices on both sides of the bridge and see the other and ones on the far side can see the internet. Why would routing affect whether iptables drops or redirects packets from one port to another? Robin
Current thread:
- transparent proxy and iptables failing Robin Wood (Oct 07)
- transparent proxy and iptables failing Will Metcalf (Oct 07)
- transparent proxy and iptables failing Robin Wood (Oct 07)
- transparent proxy and iptables failing Robin Wood (Oct 07)
- transparent proxy and iptables failing Will Metcalf (Oct 07)
- transparent proxy and iptables failing Robin Wood (Oct 07)
- transparent proxy and iptables failing Ben Greenfield (Oct 07)
- transparent proxy and iptables failing Robin Wood (Oct 07)
- transparent proxy and iptables failing Ben Greenfield (Oct 08)
- transparent proxy and iptables failing Robin Wood (Oct 08)
- transparent proxy and iptables failing Will Metcalf (Oct 07)
- transparent proxy and iptables failing Will Metcalf (Oct 07)
- transparent proxy and iptables failing Robin Wood (Oct 13)
- transparent proxy and iptables failing chris mewett (Oct 13)
- Message not available
- transparent proxy and iptables failing Robin Wood (Oct 14)