7 Jun
2017
7 Jun
'17
11:14 a.m.
Ruben,
I'm trying to understand how tunneling works on various OSes. Many thanks.
OK, this issue could only be solved at migration. Similar to the Cisco,
your devices use multiple tunnels; apparently linked to the subnets
routed to them. I understand standard RIPv2 considers where the
announcement was received to be it's ENCAP Gateway. This needs to be
placed in the Wiki too. *This an anomaly due to the workaround on Mikrotik.*
- Lynwood
KB3VWG
If it gets in the RIP table, the tik script will
autoadd an IPIP tunnel for it towards the new gateway (and 44.0.0.1 to the old gw)
This renders all future RIP broadcasts from 44.0.0.2 & 44.0.0.1 non functional.