Default Route Addition Fails

johnoatwork · Dec 14, 2021, 6:44 AM

Hi All,

I've run up the latest Home Lab version of tnsr and have started configuring. I initially set the default route using the instructions at https://docs.netgate.com/tnsr/en/latest/routing/default.html and was able to ping external hosts. However, I lost the config when I restarted as I hadn't copied it to the startup config.

Now, when I follow the same steps I get this message:

"Commit failed.: application operation-failed add:vpp/route/0.0.0.0/0, Unknown nlmgmt error, Route add failed
CLI command error"

tnsr looks like it will solve a problem for me and I'm pretty keen to get proof of concept working.

Can anyone out there help?

johnoatwork · Dec 14, 2021, 10:03 AM

There appear to be two instances of the routing table for IPv4 and IPv6. Is this normal?

tnsr(config)# show route

Route Table ipv4-VRF:0  AF: ipv4  ID: 0
-----------------------------------------

Route Table ipv4-VRF:0  AF: ipv6  ID: 0
-----------------------------------------

Route Table ipv6-VRF:0  AF: ipv4  ID: 0
-----------------------------------------

Route Table ipv6-VRF:0  AF: ipv6  ID: 0
-----------------------------------------

johnoatwork · Dec 14, 2021, 10:51 AM

Solved. You need to include the device when specifying the route e.g.

next-hop 0 via xxx.xxx.xxx.xxx WANPORT0

The steps set out at https://docs.netgate.com/tnsr/en/latest/routing/default.html don't specify this. I expect the reason it worked initially is that there was only one interface when I first configured the route.

jimp · Dec 14, 2021, 8:46 PM

You don't need to specify the interface on a route if the next hop is in a directly attached subnet on an interface. It's possible that for some reason that interface was temporarily unavailable (not enabled, for example) so it couldn't resolve the route.

There was also a possibly related bug somewhere along those lines which is fixed in the 21.11 release that is coming very soon.

johnoatwork · Dec 15, 2021, 1:35 AM

Thanks jimp. Maybe just a newbie issue. Anyway, I've got an initial build up now. Throughput is about twice as fast as testing I've done with FreeBSD packet filters but still tops out at about 3-4Gbps. I'm hoping I can improve this with tuning.

Looking forward to the next release. Debian distro's are my preferred Linux flavour