Routes priority

[kmadac]

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

[lilsense]

Hi,
   There a lot of issues here considering how you have created many inconsistent IP subnets.

- Can you explain what the Square mean that's under your control?
- Why is the 100.112.141.77 that is on the LAN 172.16.0.0/12 (how???? WOW???)???
- What is the default Gateway of the 100.112.141.77?


I am not sure why you think just using random number would make them communicate with each other?

[kmadac]

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.