[racktables-users] Re: Patch for VLAN support

Hey, Justin.

> I found support for "Live VLANs", but I want "Dead VLANs" - I don't
> want to have the webapp configure my switch for me, I want my webapp
> to *document* how the switch is configured.  Live VLAN support also
> uses Telnet which is not an option for me.

There's enough space for any transport in Live VLANs. This feature was
intentionally implemented as a "gateway".

[...]

> Not for sure if this is the place to post a patch, but here goes.  I
> would love to see this feature in trunk - any feedback is much
> appreciated.

This would be a very useful feature, but I should say, it needs some
finish before being merged into the mainline. First of all, the VLAN
table you were referring to is a must. For a VTP-enabled network, it
would be a straight copy of the VTP VLAN list. Then, there should be
duplicate VLAN IDs possible by a mean of "realm", IOW, VTP domain.
Anyway, if a VLAN ID falls off the "realm" of its switch, this
misconfiguration must be detected.

Then, assigning each port into one VLAN isn't always correct. There
could be more, that one VLANs assigned to a port (dot1Q, ISL). So a
more correct model should include a dedicated table for listing VLANs
assigned to a port (and some flag to show, which of them are tagged).
This structure could also be filled with data from the gateway (or
compared with it).

I hope it's not difficult for you to reshape this work accordingly.

-- 
    DO4-UANIC

Other related posts: