-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vlan association issue #104
Comments
Hi, I have the same issue.. I assume that only the vlan used as key and the amount of subnets which is returned from DB is more then one in the array.. We tried to analyse the bug .. Is it possible to fix this issue ? Or do you have a hint for me where i have to look and change the code ? I'm on the master release v13.03.01 Thanks a lot regards Chris |
The problem is one of identifying the vlan number and how the code treats it. It is treating the number as the ID column in the table. I need to update the GUI code to pass the right data to the underlying functions. I recall this one being pretty simple to fix but I just didn't have the time right then so thus I opened the bug here. Now that it is directly impacting someone else I'll see about getting it fixed. I believe if you are using the dcm.pl CLI interface it should work for you. That might get you going while I get it fixed. |
Any chance this could be looked into. It's a bit odd that VLAN-ids can't be reused across campuses. |
When adding a vlan to a subnet when the vlan utilzes vlan number that is duplicated within another campus via the GUI, you get an error that it can not find the vlan.
However if you add it using DCM and specify campus and vlan it does seem to work.
May be related to issue #99
The text was updated successfully, but these errors were encountered: