Feature Proposal : vlan Interface which is unique on physical port - native communication
It would be nice if a physical port is bound exclusively to one vlan interface the port could be set to this vlan as native. This would allow to have end devices for which vlan selection is difficult to be connected as well.
As per today if a physical port is exclusively bound to a vlan interface it (as expected) forwards only tagged traffic
All Replies
-
I don't see how that could work…the point of VLAN is they are tagged having a interface as a untag VLAN makes no sense why not use the interface as native as in interface type Ethernet?
0 -
Oh it works but it's a switch feature usually. It's actually noting else that defining a port as access VLAN. (opposed to trunk VLAN).
The 500h assumes that as soon as a vlan is tied to a port it is a trunk port. I was just saying that it would be a cool feature if the standard behaviour for a port with a single(!) vlan interface bound to it would behave as an VLAN access port.
I like to use VLAN access ports as it allows connecting for some exotic devices on which setting distinct VLAN on their respective NICS is a headache.
0 -
It seems this function should be handled by switch, not the firewall.
0
Categories
- All Categories
- 415 Beta Program
- 2.3K Nebula
- 141 Nebula Ideas
- 94 Nebula Status and Incidents
- 5.5K Security
- 216 USG FLEX H Series
- 262 Security Ideas
- 1.4K Switch
- 71 Switch Ideas
- 1K Wireless
- 39 Wireless Ideas
- 6.3K Consumer Product
- 243 Service & License
- 382 News and Release
- 81 Security Advisories
- 27 Education Center
- 8 [Campaign] Zyxel Network Detective
- 3K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 83 About Community
- 71 Security Highlight