VLAN Config Question

[MartinLangmaid]

@bthurston

I’m suspecting we’d have to temporarily re-IP the untagged LAN and setup the new LAN interface with the 192.168.254.1/24 IP, tagged to VLAN 254 and then remove the old untagged LAN interface IP config.

Almost. That is the right approach but you can’t leave the untagged interface without an IP set. I tend to treat the untagged LAN as the management VLAN. If it was me I would:

1. Change the untagged LAN IP to something well away from enterprise norms ie 172.16.254.1/30 and disable DHCP
2. Create a new VLAN with VID 254 and set to 192.168.254.1/24

Then because I don’t allow local management of devices as a general rule I would go and remove the management vlan from the trunk on all LANs ports and disabled web ui access from all other VLANs apart from the management VLAN.

What’s the right way to do this on the peplink balance without losing connectivity given the configuarion shown.
In your configuration there, the Balance has its own WAN connection so it will be accessible and manageable via InControl2 even if you make a mess of the LAN config.

@bthurston

I can’t see any way to do this via the CLI which would be kinda ideal.

InControl2, its API and the local Peplink Device API are the best ways to bulk manage and script Peplink device configuration.
eg:

Automated deployment for batch of 100 BR1 mini's

I have create a set of scripts to automated the deployment for batch of BR1 mini’s. Next week I have a batch of 100 units to deploy and I wanted to automate the process. The scripts are 100% hands off, no chrome browser, or manual login required. I wrote it in batch scripts as I wanted to be able to use a lot of windows laptops without having to set up the correct environment for it to run. If any one would like to contact me to rewrite in another language we can do so. I was think about redo…