[Bridge] Re: bridge

Wayback MachineAbout this captureCOLLECTED BY Organization: Alexa Crawls Starting in 1996, Alexa Internet has been donating their crawl data to the Internet Archive. Flowing in every day, these data are added to the Wayback Machine after an embargo period. Collection: Alexa Crawls DE Crawl data donated by Alexa Internet. This data is currently not publicly accessible TIMESTAMPSloadingLennert Buytenhekbuytenh@gnu.org
Tue, 15 Feb 2000 11:43:34 +0100 (CET)On Sun, 13 Feb 2000, Benoit LOCHER wrote:> Hello :)Hi! Welcome, all who enter here…> First, congrat for your “review” of the bridging code, that’s very flexible now !> I’m playing with the firewalling, but something doesn’t work as it should:>> I have two interfaces: eth0 & eth1, both member of br0.> I have applied the bridge & ipchains patches to the kernel (2.2.14), but> when I add a rule:>> ipchains -A br0 -i eth0 -p icmp -j DENY>> it doesn’t work. >> The only situation where I can filter packets is to use br0 instead of eth0 or eth1, > but I cannot control the source or destination of the packet, that is, I cannot know if the packet> comes from “inside” my LAN or from the Internet.I’m looking at the code right now… Hm, this must be a thinko. Yes, I seeit now. The bridge name is passed as interface name. Obviously wrong.What would suit you better: having the incoming or the outgoing interfaceunder ‘-i’ ?Lennert

Leave a Reply

Your email address will not be published. Required fields are marked *