-
Notifications
You must be signed in to change notification settings - Fork 325
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 configuration >= v2022.1.4 #3234
Comments
@4ndr3 The configuration for the switch ports only work in case your device supports DSA, in which case each switchport is exposed as a single interface to the Linux bridge utilities. In case your device platform uses swconfig for means of configuring switching, the custom assignment of VLANs is not supported. |
Hi, The setup is as follows: The Firmware is available here: https://firmware-archiv.freifunk-nordhessen.de/1.4.0/images/ The issue we are seeing is that the communication is not working properly. You can't ping any IP addresses (IPv4 and IPv6), DHCP isn't working, pcap shows ARP-Requests and IPv6-RA's. This can be reproduced with following commands:
We are able to reproduce this issue on multiple EdgeRouter X's, i haven't found time to test more DSA targets, but we are mostly using the ERX anyway.. Thanks in advance! :) |
@dariks please post e dump of the |
Thanks for looking at this.
|
can you try removing eth4 altogether from the mesh-bridge so only the tagges client network is on the port? Also i do not understand why eth3 is in the client bridge. Can you share your |
@dariks please remove the role from |
now the situation is as follows: should i now configure the interfaces one by one to mesh? (eth1, eth2, eth4) |
Yes, don't use the builtin /lan designator in this case. Maybe we should reconsider to ensure interface assignments are XOR. Also note (while the symptoms are comparable), your circumstances are different from the one @4ndr3 is facing. |
@blocktrron
but now i am facing the exact same issue again: broken connectivity.
|
When upgrading Hamburg's firmware from gluon-v2021.1.2 to gluon-v2022.1.4, the point to point radio links (Richtfunknetz) fell apart because it heavily utilizes VLANs and apparently the VLAN configuration hast changed.
I was trying to rebuilt the VLANs according to https://github.com/freifunk-gluon/gluon/wiki/Commandline-administration#create-a-mesh-vlan-on-one-port . However, I believe, it misses a step to assign the VLAN to a certain switch port. E.g. if I wanted that VLAN 8 from the example only on switch port 2. How would I go about that?
thx!
The text was updated successfully, but these errors were encountered: