802.1ad (AKA: QinQ, Service Tag) #1083

Closed
opened 2025-12-29 16:28:38 +01:00 by adam · 4 comments
Owner

Originally created by @cre8rnz on GitHub (Jul 9, 2017).

Any chance we can reopen this? 802.1ad is being used more and more ..
We have to use VRFs for IPs and VLAN Groups to do this currently and it makes things a tad messy for us.
Not sure how complex it would be to effectively duplicate the VLAN functions, Call it ServiceTAG, make it all masters for vlans and add a new column for ServiceTAG under vlans?

Enable creation of QinQ VLANs #116l
VLAN “Service Identifier” field (VXLAN or ISID) #777l

Originally created by @cre8rnz on GitHub (Jul 9, 2017). Any chance we can reopen this? 802.1ad is being used more and more .. We have to use VRFs for IPs and VLAN Groups to do this currently and it makes things a tad messy for us. Not sure how complex it would be to effectively duplicate the VLAN functions, Call it ServiceTAG, make it all masters for vlans and add a new column for ServiceTAG under vlans? [Enable creation of QinQ VLANs #116l](https://github.com/digitalocean/netbox/issues/116) [VLAN “Service Identifier” field (VXLAN or ISID) #777l](https://github.com/digitalocean/netbox/issues/777)
adam added the status: duplicate label 2025-12-29 16:28:38 +01:00
adam closed this issue 2025-12-29 16:28:38 +01:00
Author
Owner

@jeremystretch commented on GitHub (Jul 10, 2017):

Duplicate of #116. Please avoid opening new issues for topics which have already been addressed.

@jeremystretch commented on GitHub (Jul 10, 2017): Duplicate of #116. Please avoid opening new issues for topics which have already been addressed.
Author
Owner

@cre8rnz commented on GitHub (Jul 19, 2017):

Hi Jeremy,

Not sure why you have deleted my previous comment, however...
I had a college ask me what was the outcome of this so thought I would ask again.
Is there anyway we can re-open an issue (for discussion among yourself and other users) that has been addressed without it being closed before discussion?

There was a good few people interested in this in the beginning (Which I have linked to in my original post). And I imagine with all of the active users now there may be more interest ?

@cre8rnz commented on GitHub (Jul 19, 2017): Hi Jeremy, Not sure why you have deleted my previous comment, however... I had a college ask me what was the outcome of this so thought I would ask again. Is there anyway we can re-open an issue (for discussion among yourself and other users) that has been addressed without it being closed before discussion? There was a good few people interested in this in the beginning (Which I have linked to in my original post). And I imagine with all of the active users now there may be more interest ?
Author
Owner

@cre8rnz commented on GitHub (Aug 29, 2019):

Hey Guys,
Have had 2 more people say +1 for reopening on the following; https://github.com/netbox-community/netbox/issues/116
Those comments were deleted and the issue has been closed.
Seems people are after this as an option.

Any plans to add this at any stage?

Thanks

@cre8rnz commented on GitHub (Aug 29, 2019): Hey Guys, Have had 2 more people say +1 for reopening on the following; https://github.com/netbox-community/netbox/issues/116 Those comments were deleted and the issue has been closed. Seems people are after this as an option. Any plans to add this at any stage? Thanks
Author
Owner
@cre8rnz commented on GitHub (Aug 29, 2019): FYI Also have https://github.com/netbox-community/netbox/issues/1725 and https://github.com/netbox-community/netbox/issues/1800 and https://github.com/netbox-community/netbox/issues/2800 and https://github.com/netbox-community/netbox/issues/777 related to this. Thanks
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1083