On Thu, Feb 06, 2003 at 04:40:02PM -0500, Eble, Dan wrote: > In that case, what do you think about taking the 802.1D reference code > and building an STP daemon? Would it require more than the following > changes to the kernel? > > * add CONFIG_802_1D to enable STP independent of software bridging
How do you mean this? I would love to just cut away the STP code from the kernel at all. > * add net_device::stp_state to record the state Ok. > * add SIOCSSTPSTATE ioctl to change the state Please, no ioctl. /proc interface, maybe? > * add code to the network core to drop non-STP frames received in the > "blocking", "listening". In the "learning" state, allow frames to > be handled by master devices (namely the software bridge), but do not > allow them to pass to the protocol drivers. This is already how it is done now, I think? > * add code to the network core to drop non-STP frames transmitted in > the "blocking", "listening", and "learning" states It should already be done like this.. > * add net_device::change_stp_state(dev, state) for hardware features Sounds sane. I'll write the daemon if you do the kernel part? cheers, Lennert _______________________________________________ Bridge mailing list [EMAIL PROTECTED] http://www.math.leidenuniv.nl/mailman/listinfo/bridge
