> From: Lennert Buytenhek [mailto:[EMAIL PROTECTED]] 
... 
> Of course this would all be a dirty hack at best.  STP shouldn't be in
> the kernel at all.. wish I realised that earlier :/

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

  * add net_device::stp_state to record the state

  * add SIOCSSTPSTATE ioctl to change the state

  * 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.

  * add code to the network core to drop non-STP frames transmitted in
    the "blocking", "listening", and "learning" states

  * add net_device::change_stp_state(dev, state) for hardware features

-- 
Dan Eble <[EMAIL PROTECTED]>  _____  .
                           |  _  |/|
Applied Innovation Inc.    | |_| | |
http://www.aiinet.com/     |__/|_|_|
_______________________________________________
Bridge mailing list
[EMAIL PROTECTED]
http://www.math.leidenuniv.nl/mailman/listinfo/bridge

Reply via email to