13 Aug
2021
13 Aug
'21
2:31 a.m.
On Aug 12, 2021, at 13:50, pete M via 44Net
<44net(a)mailman.ampr.org> wrote:
Echolink, IRLP and probably Allstar, require a single IP. An endpoint (“node”) registers
with respective network which becomes the address every one else uses to reach them. A not
uncommon problem is the node rapidly flips between two addresses, usually caused by
someone with multiple ways to get out on the Internet, and a misconfigured router.
Eventually the network gives up and ignores them until they can stabilize their address
(at least that is what IRLP does).
IRLP does not require static address, but we expect relatively stable addresses, like
hopefully changing no more than daily. We can handle changes more often than that, but
when you get multiple changes per hour, things will begin to break and your node will not
be accessible.
-k9dc
Tony,
It would seem to me that IRLP or Echolink nodes would need to be in the public space (now
44.190). Both require open unfettered access to/from any public IP in 0/0. I >always
suggest IRLP nodes ideally, are setup directly on a public IP, outside any local firewall
(though quite often that is not possible). Perhaps your proxies could be in >Backbone
routed nets, depends on how the routing out of the backbone is set up.
If any IRLP or echolink node want to announce themself on both segment of the network I
dont see any problem with that. their could be some echolink proxy's that could easily
fix any connection problem.
The same with allstarlink. ( not talking for them) but they already use 44 net addresses
so having some dual address for their server should not be that difficult to implement.