Stephen, This sounds like the right approach. I'm still not sure what you are proposing in terms of where the RSTP code should come from. would you expect we should be able to pull the code out of the existing bridge module? Thanks Seth > -----Original Message----- > Actually, I would like to make RSTP (and all the spanning tree > protocols) > a user space utility. There are some infrastructure changes necessary > to propagate sufficient information to do it. I was going to leave existing STP in kernel for now, but not enable it. For 2.6.17, I made sure that STP packets are received so application can receive them (via LLC). The next part would be adding a netlink interface to bridge module to report and modify: * interface added/deleted from bridge * interface status change (carrier up/down) * interface forwarding enable/disable * forwarding table flush by interface.
