Re: --resend-on-iif status
Stephen Hemminger <[email protected]>
| Newsgroups | gmane.linux.network.bridge.ebtables.devel |
|---|---|
| Organization | Open Source Development Lab |
| Message-ID | <20040604130005.06e5c456@dell_ss3.pdx.osdl.net> |
On Fri, 4 Jun 2004 21:54:55 +0200 Bart De Schuymer <[email protected]> wrote: > On Friday 04 June 2004 20:16, Stephen Hemminger wrote: > > Rather than hacking the bridge code and risking routing loops and other > > nasty's, why not change the wireless driver to have a "reflect all packets" > > flag? > > Some devices which appear as one single interface to Linux are really some > kind of (wireless?) bridge with many ports. If I understood correctly, more > control over what this hardware forwards is wanted. The hardware can be made > to give the packets to Linux instead of bridging them, but after Linux has > played with the packets, they should go back to that hardware. A way to do > this is make a bridge port out of this interface and force the bridge code to > deliver the packets back to the input bridge port. > AFAIK the requested functionality (being able to filter, tc, etc. the packets) > can't be implemented by only altering the driver code. I understand the concept, but if the device doesn't really act like a multicast network device, it isn't really appropriate to bridge. It just seems like doing the quick and dirty add a flag hack will introduce more support and other problems. ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504