1
18.1 Legacy Series / [solved] Can I set lagg LAN ip4 to None and have ip4 set on VLANs only
« on: July 19, 2018, 08:06:49 am »
Hi
I am trying to work out how to set up my management vlan.
Initially, before I put various hosts on their own subnet/VLANs, I had everything set to the same subnet with no VLANs, 192.168.110.x/24 including all routers, switches, hosts and APs in a bid to finally (after creating the others first) create a management VLAN110 with that subnet.
On top of a lagg interface set as LAN, I now have set up all the VLANS (except management vlan) with static IP interfaces assigned and their own DHCP server all to a common gateway on LAN. My hosts are now all working in their own tagged VLANs as they should.
But the last step, getting my switches, opnsense router and APs on to VLAN110 I cant achieve yet. I already have a static ip set on LAN 192.168.110.1 (the initial subnet) from the beginning. All my switches have their management ip in that subnet as well.
I guess part of the issue is: opnsense LAN is set to 192.168.110.1, so I cant assign VLAN110 interface to that ip. I have it set to 192.168.110.240 and from a host on a dedicated management tagged vlan110 physical port I cant reach opnsense gui.
I would like to be able to have my opnsense LAN set to None in the IPv4 config type so that I can have VLAN110 interface ip set to 192.168.110.1 but when I tried to set LAN interface to None opnsense locked up and got a startup loop from a boot script (froze at loading Squid). I didnt know how to circumvent that so I had to re-install and start again.
Can I do this without hosing my install? If not what should I be doing with VLAN110/LAN interface ip assignments to get my management vlan happening?
Sidenote: I dont want VLAN110 - 192.168.110.0/24 to be the default vlan if untagged. I have VLAN1 192.168.1.0/24 for that.
I am trying to work out how to set up my management vlan.
Initially, before I put various hosts on their own subnet/VLANs, I had everything set to the same subnet with no VLANs, 192.168.110.x/24 including all routers, switches, hosts and APs in a bid to finally (after creating the others first) create a management VLAN110 with that subnet.
On top of a lagg interface set as LAN, I now have set up all the VLANS (except management vlan) with static IP interfaces assigned and their own DHCP server all to a common gateway on LAN. My hosts are now all working in their own tagged VLANs as they should.
But the last step, getting my switches, opnsense router and APs on to VLAN110 I cant achieve yet. I already have a static ip set on LAN 192.168.110.1 (the initial subnet) from the beginning. All my switches have their management ip in that subnet as well.
I guess part of the issue is: opnsense LAN is set to 192.168.110.1, so I cant assign VLAN110 interface to that ip. I have it set to 192.168.110.240 and from a host on a dedicated management tagged vlan110 physical port I cant reach opnsense gui.
I would like to be able to have my opnsense LAN set to None in the IPv4 config type so that I can have VLAN110 interface ip set to 192.168.110.1 but when I tried to set LAN interface to None opnsense locked up and got a startup loop from a boot script (froze at loading Squid). I didnt know how to circumvent that so I had to re-install and start again.
Can I do this without hosing my install? If not what should I be doing with VLAN110/LAN interface ip assignments to get my management vlan happening?
Sidenote: I dont want VLAN110 - 192.168.110.0/24 to be the default vlan if untagged. I have VLAN1 192.168.1.0/24 for that.