Virtual LANs (VLANs) Best Practices
Creating VLANs on eth0 can prove challenging. Since VLANs can only be created via the Web User Interface (WUI), it is very important that access to the WUI is not disrupted. Therefore, the WUI will need to be temporarily moved to a different interface.
First, configure the addresses for an interface other than eth0. Once you have configured addresses for the new interface and connected it to the relevant network, please connect from that subnet via SSH to ensure connectivity on the new network is working correctly.
Once SSH access is confirmed, move the web administrative interface. From the SSH menu, select:
- 3 Local Administration
- 4 Web address
Choose the address that corresponds to the new interface.
After that, connect to the web interface from a workstation on that subnet. At this point, remove the addressing from eth0 entirely. Once the interface is cleared, the desired VLANs can be added. After adding all the VLANs, confirm connectivity on each VLAN by connecting to the LoadMaster using SSH on each VLAN address.
Once all VLANs have been successfully added, the default gateway must be added to the correct interface. To do this, Alternate Gateway Support must be enabled in System Configuration > Miscellaneous Options > Network Options. After this is enabled, navigate to the desired interface or VLAN and select the Use for Default Gateway check box. You will then be brought to a page to set the gateway on that interface.
The last step is to move the administrative interface to its final destination. This can be done from the WUI in Certificates & Security > Remote Access. Change the Allow Web Administrative Access option to the interface you would like to use.
Note: As soon as you change this, you will lose access on the current interface.
Connect to LoadMaster using the new interface. If desired, you can set up an administrative default gateway that all web interface and SSH traffic to LoadMaster will use