Messages

Not sure where you're seeing ntop 4.2.210309 (0).  I have a fully updated OPNSense and just installed ntopng and it's at version 3.4.0 as reported in the web ui.

There's also an issue with the ntopng-geopip2update.sh file.  The URL's in the file are wrong - the subdomain doesn't exist.  Needed to update the URL's, which need to include the MaxMind license key.

There should also be a way to enter the MaxMind key in the OPNsense UI.

I have absolutely no idea why, but it keeps requesting the IP of 172.16.0.6 via DHCP request.  I figured I'd add a new WAN NIC and try that - set up the WAN NIC on the console, it refuses to get a lease 0.0.0.0/8, but now all my VLAN's are not associated with my LAN interface anymore.

About ready to ditch OPNsense. 

The VLAN is tagged on the port on the switch, as well as the port group in VMWare.  And it's working since I can connect it up to my router and get an internal IP without issue.

I'm quite stumped as to what may be going on here.

Setup:
CableModem -> switch port (vlan 500) -> trunked to vDS -> port group (vlan 500) -> OPNsense WAN NIC

If I connect the OPNsense WAN NIC to my existing router, I can DHCP and get an IP successfully in the assign 10.0.1.x range.  That should mean my VLAN's and trunking is fine up the stack.

As soon as I connect directly to the cable modem, I get either no IP, or somehow I started getting a 172.16.1.4 IP that I have no idea where it's coming from.  And I get that address even though I have the block 1918 and BOGON enabled on that interface. 

Cable Company (Spectrum) says things look good on their side.  Cable modem will give out a public IP to my old router, or to my laptop without issue.

I changed the VM WAN NIC's MAC address to match the old router's WAN MAC thinking it could possibly be an issue with them blocking VMWare MAC's, didn't help at all.

I'm going to try to sniff the interface to see what goes haywire in the DORA, but wondering if someone might have any leads in the mean time.

Thanks!