EAP650-Desktop, Broadcast/Multicast bleeding from other VLANs on Wired Port set to Default
If you have the unit using a Mesh uplink (unknown if the issue happens with wired uplink, but I would suspect it would) and a Wired port set to the Default VLAN that port is passing Broadcast and Multicast traffic from ALL VLANS, not just VLAN 1 (the default).
A) This is a security issue as devices in isolated VLANs are able to use Broadcast or Multicast to send stuff to devices in the Default VLAN.
B) This causes issues with IPv6 because IPv6 RAs bleed over from other VLANs causing the devices to configure non-usable addresses on the interface, potentially breaking connectivity.
Apparently "Default" is similar to setting a port to be a member of All VLANs (i.e. send all VLANs) but just with a PVID of 1 (i.e. Incoming untagged is tagged/associated with said VLAN), which is TOTALLY inappropriate and stupid.
This does not happen on a port set to a specific VLAN.
Note, I cant even force set the VLAN to 1 because it errors out saying you cant set the VLAN to the same as the default.
It should also be noted this effects port ETH0 as well when not using it for an uplink, ofcourse it is unconfiguerble, but trying to use it for a client on the "Default" VLAN.
Also side note, in the Port configuration screen, when setting the VLAN, it calls the settings PVID, thats not exactly inline with industry nomenclature in this context. PVID would only be what incoming untagged packets are tagged/associated with, I suggest PVID be changed to "VLAN ID" or something similar.
And while dealing with this, another plea to allow configuering ETH0 on this device for a set VLAN in the first place.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thanks for posting here.
For EAP650-desktop, we are going to release a new firmware that support edit ETH0 port, options are like below:

Please have a look and see if this is what you need.
- Copy Link
- Report Inappropriate Content
@Vincent-TP I'm assuming that is going to be the configuration screen for all the ports, just now that it also includes eth0?
And just based on a visual it looks like in theory it should do what it's supposed to, and in theory would solve this issue, of course we'll have to see when the firmware comes out.
But it does look promising.
- Copy Link
- Report Inappropriate Content
Napsterbater wrote
@Vincent-TP I'm assuming that is going to be the configuration screen for all the ports, just now that it also includes eth0?
And just based on a visual it looks like in theory it should do what it's supposed to, and in theory would solve this issue, of course we'll have to see when the firmware comes out.
But it does look promising.
Yes, it's for all the ETH ports.
- Copy Link
- Report Inappropriate Content
@Vincent-TP Is there any timeline for the beta with this change? I know generally there's not much information on that other than "soon"
- Copy Link
- Report Inappropriate Content
Around April.
Note: ETA is provisional and actual delivery may vary depending on implementation conditions.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I sincerely apologize for the incorrect information I provided earlier. We have no plans to add these configuration options to the ETH0 port. They will only be added to ETH1, 2, and 3.
Regarding the scenario you mentioned, we have already submitted feedback; the relevant team will consider whether to add this feature. Sorry for the confusion caused.
Vincent-TP wrote
Napsterbater wrote
@Vincent-TP I'm assuming that is going to be the configuration screen for all the ports, just now that it also includes eth0?
And just based on a visual it looks like in theory it should do what it's supposed to, and in theory would solve this issue, of course we'll have to see when the firmware comes out.
But it does look promising.
Yes, it's for all the ETH ports.
- Copy Link
- Report Inappropriate Content
@Vincent-TP
BTW, the VLAN leaking has not been fixed yet either.
Setting a port to "Default" still transmits packets for ALL VLANS on that port, again this is completely incorrect behavior and breaks IPv6 for any deivce on thee ports among the security implications as previously mentioned.
1.5.6 Build 20260629 Rel. 20690
Utter incompetence.
- Copy Link
- Report Inappropriate Content
Thank you for your feedback. We have forwarded this request to the relevant department. They are currently considering whether to add this feature.
You can also create a thread under the Requests & Suggestions block to gather more voters and ideas. The title could be: Add the feature to configure VLAN for ETH0 port of EAP devices.
In the meantime, we suggest using the EAP wired connection to the uplink device as a temporary solution.
Napsterbater wrote
If you have the unit using a Mesh uplink (unknown if the issue happens with wired uplink, but I would suspect it would) and a Wired port set to the Default VLAN that port is passing Broadcast and Multicast traffic from ALL VLANS, not just VLAN 1 (the default).
A) This is a security issue as devices in isolated VLANs are able to use Broadcast or Multicast to send stuff to devices in the Default VLAN.
B) This causes issues with IPv6 because IPv6 RAs bleed over from other VLANs causing the devices to configure non-usable addresses on the interface, potentially breaking connectivity.
Apparently "Default" is similar to setting a port to be a member of All VLANs (i.e. send all VLANs) but just with a PVID of 1 (i.e. Incoming untagged is tagged/associated with said VLAN), which is TOTALLY inappropriate and stupid.
This does not happen on a port set to a specific VLAN.
Note, I cant even force set the VLAN to 1 because it errors out saying you cant set the VLAN to the same as the default.
It should also be noted this effects port ETH0 as well when not using it for an uplink, ofcourse it is unconfiguerble, but trying to use it for a client on the "Default" VLAN.
Also side note, in the Port configuration screen, when setting the VLAN, it calls the settings PVID, thats not exactly inline with industry nomenclature in this context. PVID would only be what incoming untagged packets are tagged/associated with, I suggest PVID be changed to "VLAN ID" or something similar.
And while dealing with this, another plea to allow configuering ETH0 on this device for a set VLAN in the first place.
- Copy Link
- Report Inappropriate Content
To be clear, there's two different things here, The primary is VLAN traffic bleeding over, the secondary minor thing was the feature request. Any Port configured as default allows packets from other vlans to be tagged and transmitted put on the port, this is wrong. Not only is it a security issue, it can break IPv6 for devices connected to that port because they see IPv6 RAs from all VLANS causing them to configure addresses from every single one they see, and then they relatively randomly pick one which may or may not work on the native/Default VLAN. Because you treat default as Set default as native but Trunk ALL VLANS TAGGED, which is absolutely incorrect. The minor issue of being able to fully configure ETH0 isn't really solved by working it either because the port is still useless, I can still only connect three downstream clients, and if I could wire it I wouldn't have got this device in the first place.
Edit: I also had all of this text formated, But you're ridiculously crap form software absolutely broke it in mobile.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 1182
Replies: 10
