19 Jan
2024
19 Jan
'24
2:03 p.m.
Hi Steve,
I assume you registered your gateway with a dynamic IP address. In that
case afaik the behavior is like expected.
- The mesh connections are updated on the first RIP sending via DNS
resolution on the gateway side.
- The forwarding rules of the ucsd gateway are scheduled for update once
per hour or so, giving that delay you are noticing.
If you have a fixed IP address this should not happen, since no change
in the IP configuration at ucsd is necessary.
Marius, YO2LOJ
On 19/01/2024 17:20, kc8qba--- via 44net wrote:
Hello!
I've been working on getting my IPIP mesh gateway set up on Debian & feel like
I'm almost there. One thing I’ve noticed is every time I reboot the router, it takes
around 45-60 minutes before I can start passing traffic to the public internet again via
the ucsd gateway. For example, after rebooting the router, once rip44d has retrieved the
routes I can:
(a) Ping and curl across tunl0 to n2nov.ampr.org
(b) Use yo2tm’s nettools to successfully ping my ampr ip and see that traffic locally via
tcpdump
But cannot:
(c) Ping 8.8.8.8 across tunl0 (via 169.228.34.84) or
(d) Curl to ifconfig.me across tunl0 (via 169.228.34.84)
However, if I just leave everything running and come back 45-60 minutes later, (c) and
(d) work fine with no additional configuration changes and (d) returns the assigned 44net
ip address.
Just curious if the above is an expected behavior or a sign that I’ve got something
misconfigured.
-Steve
kc8qba
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org