Hello Peplink Team,
We would like to put forward that Port Based VLANs be made available to the LAN port(s) of the SpeedFusion engine (and any other models not currently supporting Port Based VLANs on the LANs).
Here is the current LAN options with FW 8.0.2 for a SFE.
Here is the current LAN options with FW 8.0.2 for an MBX.
Here are some similar requests & discussions from the past for other models and this feature:
Any idea when VLAN tagging will be supported on the LAN ports of the Balance series?
Need this to support IPTV VLAN tagging for the largest broadband ISP in Malaysia. The Vigor Draytek range of products already support this.
Enable the ability to set a VLAN for each LAN port rather than the default of trunk. This would be very helpful, helping to minimize the additional cost of having a to get a 802.11Q switch and taking up precious rack space on radio sites.
Are port based VLAN’s in the road map for future firmware?
Inbound/Outbound Firewall Rules - It would be nice to be able to allow multiple IP’s to be pointed to a certain VLAN.
WAN - ANY
Protocol - UDP
Source IP - 24.54.34.X (East Coast SIP Server)
173.45.65.X (Midwest SIP Server for Redundancy)
26.45.45.X (West Coast SIP Server for Redundancy)
Port - 5060
Destination - 10.10.20.0/24
Port - ANY
WAN - ANY
Protocol - UDP
Source IP - 10.10.20.0/24
Hi Peplink support,
Understood that in firmware 6.3, there is a port based VLAN feature that is supported in the lower series of the Peplink model but not the higher ends. Wondering why is it so?
We have use case whereby endpoints ie. workstation or notebook will be directly connected to the Balance 710 and 380 Peplink routers that we have recently purchased and found out that this feature is not supported. We do not wish to configure VLAN tagging on the connected endpoints and would like the …
Good day all,
I have upgrade a pepwave 300m to the latest firmware and now only one SSID can get an IP from the DHCP server.
I have 3 SSIDs
SSID1 = 10.10.1.x
SSID2 = 10.10.2.x
SSID3 = 10.10.3.x
After the upgrade only SSID1 is getting an IP address. Nothing was changed on the router just on the AP. The AP is being controlled by the Balance 20 running Firmware 6.3.3.
I know this is an old thread but I don’t want to make a new one as I think the answer is on the forums somewhere, I just can’t find it.
I have tried to assign an Access VLAN to the ‘untagged’ lan but I lose all contact with the router. I already have wifi turned off and none of the ports allow access to my laptop, the one I used to make the changes.
I have to reset the router and change the setting so that there are only 3 Access VLAN ports and leave the ‘untagged’ port alone.
I assume it ha…
Hello Peplink/Pepwave Teams,
From our experience currently only some of the Peplink/Pepwave range allows for the full customisation of the LAN port from the default of TRUNK all VLANs. It would be very useful to see the ability to have Customised Trunk & Access assignments of the VLANs to the individual ports across the entire range and for these options to be uniform across all models.
Take these example from Firmware 7.1.1 comparing the LAN assignment options as seen in these images.
Looking through these past posts, it appears the SFE was missed in having Port Based VLAN added for the LAN port(s).
Note: We raised a ticket #20020689 thinking it was a firmware bug with 8.0.2, so this is why we are making a formal Feature Request.
So where would this be useful? When using a VPN such as SpeedFusion and there is a need to separate traffic into segregated VLANs as per the client’s requirements or as the solution may need.
Happy to Help,