Messages

Hi,

thanks for feedback. Sorry for confusions, but in the meantime I solved the issue.

It had nothing to do with routing on Opnsense router, but it was internal firewall bug on cloud platform (openstack) where VM was running.

Hello everyone,

My opnsense router has interface (vtnet11) in our local subnet 100.112.241.0/25. That subnet is part of the supernet 10.64.0.0/10 for which gateway (100.112.241.1) is on same interface obviously. We have added a static route to supernet 10.64.0.0/10 in opnsense.

When I ping  VM in local subnet from other opnsense interface, it is routed to supernet 10.64.0.0/10 over GW 100.112.241.1 instead of sending packet directly to subnet to link vtnet11. When I check routing table, I see that static route to GW is displayed before link route and it is probably the reason why the router doesn't send packet directly to VM in subnet.

netstat -rn
100.64.0.0/10      100.112.241.1      UGS     vtnet11
100.112.241.0/25   link#12            U       vtnet11

For better understanding I'm attaching the picture with network diagram.

Is there a possibility to set higher priority on link route, so packets to 100.112.241.0/25 would be always routed to vtnet interface, or is there any other solution how to prefer 100.112.241.0/25 route?

Thanks for all suggestions

Hello,

I'm new to OPNsense. I just installed version OPNsense 20.7.5 (amd64/OpenSSL) on supermicro server with 6 on board nics and 4 nics on expancion pci board. I can see all nics in a system (igb0-igb9)

When I insert cable, link is detected, but when I disconnect the cable, link stays active. When I do ifconfig igb0 down; ifconfig igb0 up status switches to no carrier, but as I need to make lagg on interfaces it is quite an issue.

I found that there was a bug in freebsd https://www.freebsd.org/security/advisories/FreeBSD-EN-20:09.igb.asc, which has been fixed. Was it already implemented into OPNsense?

Thanks.