Messages

Ok. I created a new interface igc0 for MGMT. Migrated my firewall rules over and deleted my Management VLAN. The other VLANS still tied to igc0, so sounds like this isn't best practice but typically works? Otherwise I'd need to run another cable as the VLAN trunk for non-MGMT traffic? Anything else to consider for right now?

Will test with the Internet connection moved back from its temporary nighthawk workaround this weekend.  Aside from learning VLAN quirks between Unifi and OPNsense the other takeaway is don't tinker with the network during the work week.

Thanks so much and will update after I test. Again, thanks so so much!!

The MGMT network is set as Native (1), the rest are the 20, 30, and 50. https://imgur.com/a/H3YghWU

In OPNsense I have them setup with MGMT VLAN of 1, then 20, 30, 50 etc.
MGMT VLAN with DHCP setup as 192.168.1.1. and the others on their respective subnets.

https://imgur.com/a/v5JAav1

Initially, I had all of the MGMT traffic on VLAN 10 for Switch|APs|Servers but was having a nightmare getting it adopted this second go-around (I must have accidently got it working at first or something :-)

So VLAN1 isn't really a tag of 1 but untagged? I had a LAN Interface initially that I used to setup the Unifi switch on a 192.168.5.0/24 subnet. Once everything seemed to work, I disabled that which I thought was creating my trunk. So it sounds like that's how I got it working. When I had the network controller running on my laptop, that was a bit easier to be switching IPs around as needed but now running on a PI it's more of a pain (as it's a bit of a juggling act to connect to it with the network down). I guess I'd prefer to have the MGMT network as 10, all of my NAS VMs and Servers are setup for that but it seemed like Unifi wasn't going to play nice with that approach.

Really appreciate the help!! Have been super happy with OPNsense so far, like the quality of the Unifi gear but just feels like the OG Nintendo where sometimes you just need to blow in the cartridge to get things working (even if that didn't really do anything). :-)

Side question, is all prosumer networking gear as finnicky about the "controller" as Unifi? It feels like a total chicken-egg where I need to get this controller running to be able to do anything but without a network connection, I can't seem to get it setup. It stopped working on my laptop and even a couple hours with Unifi support they pretty much said to try their new early release option. It's been a frustrating journey to say the least. I would be more than happy setting this up in the CLI but could not find a guide that seemed to match the CLI shell that was on my switch, I could make changes but they didn't seem to take. Anyway, I at least am able to get to settings in the NEtwork Controller for now (until it makes me reset everything for some random reason).

I had this all working for a couple weeks but moved the Unifi Network Controller and when I reset the switch to adopt it, lost everything and haven't been able to get this working in a week. Pulling what little hair I have left out!

I am trying to setup a 8 port Lite POE switch. I have a trunk port setup with 4 VLANS. A MGMT(VLAN1), TRUSTED(20), IOT(30), and GUEST(50). DHCP setup on each VLAN and tied to igc0 (port 0). I would expect that plugging port 0 into the switch would come up and give it IPs from the MGMT network (192.168.1.0/24). It will pop up on and off but when it does either is listed as being in the TRUSTED or IOT networks which doesn't make any sense. What makes even less sense is that I'd then expect that the switch would pick up an IP from the Trusted network but it doesn't do that either. I'm new to OPNsense so maybe I have some setting wrong but I did have this working before. Initially I had the MGMT network as VLAN 10, (x.x.10.0/24) but when I was trying to set this up again couldn't get the switch adopted to save my life so went with their default network to move forward.

Any help would be greatly appreciated, happy to grab any logs, screenshots. Thanks!