25 Mar
2018
25 Mar
'18
10:53 a.m.
That is correct - there are plenty of gateways in the portal that have no subnets
attached to them, but they are filtered out of the encap list.
Chris
On 25 Mar 2018, at 16:47, Brian Kantor
<Brian(a)BKantor.net> wrote:
As far as I know, the encap table is generated by joining the
gateways table with the subnets table, so only those gateways
with associated subnets would be in it. There are NO entries
in the encap table without a subnet listed, as a quick glance
down the file will show.
- Brian
On Sun, Mar 25, 2018 at 05:42:30PM +0200, Rob Janssen wrote:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
The RIP
sender sends RIP only to gateways listed in the encap table,
unless a bug has surfaced that I wasn't aware of. That code has been
stable for several years, so I doubt it.
Does that table contain only gateways that actually have routes to them?
Or is there also a listing for those that only are registered in the portal
but with "No subnets"?
I wonder how those gateways know the route to us to transmit tunnel data
when they do not actually route anything themselves?
They appear to be MikroTiks so most likely running the script by Marius YO2LOJ
and that would have to receive the RIP data to bring up the tunnels.
Rob
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net