Messages

OK, progress at least. I reconfigured and am just using igc1 directly as the LAN and everything seems to be working, so your comment about the bridge seems on target. Guess I need to do some more reading and figure out what I did wrong setting it up. Duplicating the Fortinet isn't a requirement, but it would be convenient to use the extra ports as I specifically bought that hardware to avoid needing a switch at that location.

I guess we can flag this a solved and I'll address bridge issues separately if required.

Thanks for the assist.

I haven't tried the diagnostics yet but I did look at the live log, that's why I say traffic isn't making it to the LAN interface. Those pings don't show up in the log if I ping via IPv4, but do via IPv6.

I'm not familiar with VDOMs. Virtual Domains perhaps? References or clarification would be greatly appreciated.

Thanks

Hello all,

I'm attempting to replace my existing Fortinet F60 with a MiniPC (N100) running OPNSense. The OPNSense unit has 6 i226 nics configured as WAN (ig0), LAN (ig1) with ig2 and ig3 bridged to the LAN. The remaining 2 interfaces are currently unused.

I have an Eero 6 pro mesh network configured as a bridge for wifi access. At this point there are no plugins, etc., just base code. I'm having issues getting access for anything connecting via the Eero side of things via IP4. I have removed any devices connected to anything except the LAN interface and moved them all to a switch. At this point switching between the Fortinet and the OPNSense consists of simply plugging the LAN interface into the switch from whichever FW I want active.

DHCP is provided by my internal AD integrated DHCP servers. This all works flawlessly connected to the Fortigate but when I switch to the OPNSense the only things that have full access are wired connections. Anything connected via the Eero can't even ping the LAN interface on the FW. I did discover during troubleshooting that IPV6 does appear to work, just IPV4 is failing. I can ping all internal devices via IPv4 regardless, just no traffic getting to/through the FW. Kind of out of ideas on where to look next.

This is all setup behind my AT&T fiber connection. The FW WAN interface is on the 192.168.1.x subnet, the LAN is on 192.168.16.x.
At this point I'm wondering if there's some weirdness going on with the Eero but given that it's passing all the IPv4 traffic internally I don't know what that might be or where to look.

Any suggestions would be appreciated.