15 May
2018
15 May
'18
12:29 p.m.
Sorry, I can't agree on that. Without manual
interaction Echolink
Repeaters behind traditional IPIP-Mesh gateways are not reachable
through the NLD Echolink Relays/Proxies.
That is NOT CORRECT!
It will work just fine when the repeater is behind a traditional IPIP mesh gateway
which sends traffic to internet via amprgw (the setup described in the Wiki).
It will only fail when shortcuts are made and traffic to internet is sent via some
local NAT router instead of via the IPIP mesh. As the Echolink protocol cannot
handle this situation (as described above) one needs to make sure that Echolink
traffic is not sent via this NAT shortcut.
The Echolink system is perfectly happy with clients, proxies and relays on NET44,
it is only the bad configuration of gateway systems that will break it.
Rob
15 May
15 May
4:22 p.m.
New subject: Network 44.190.5.x work!
On 15.05.2018 18:29, Rob Janssen wrote:
it is only the bad configuration of gateway systems
that will break
it.
Since we don't agree on what is a "good" or "bad" configuration,
the
description of Network 44.190.0.0/16 seems to be pretty fine:
"The idea of 44.190.0.0/16 is to give willing stakeholders the
opportunity to improve the situation. Amateur radio internet services
can be hosted in that range while AMPRNet systems can make use of the
additional route 44.190.0.0/16 via their ISP."
So even if we don't agree we could meet in the middle with some
efforts on both ends...
73,
Jann
--
Jann Traschewski, Faber-Castell-Str. 9, D-90522 Oberasbach, Germany
Tel.: +49-911-99946898, Mobile: +49-170-1045937, E-Mail: jann(a)gmx.de
Ham: DG8NGN / DB0VOX / DB0FOX / DB0ZM / DB0DBA / DB0HZS
7 p.m.
New subject: Network 44.190.5.x work!
1+
On 2018-05-15 12:29 PM, Rob Janssen wrote:
Sorry, I
can't agree on that. Without manual interaction Echolink
Repeaters behind traditional IPIP-Mesh gateways are not reachable
through the NLD Echolink Relays/Proxies.
That is NOT CORRECT!
It will work just fine when the repeater is behind a traditional IPIP mesh gateway
which sends traffic to internet via amprgw (the setup described in the Wiki).
It will only fail when shortcuts are made and traffic to internet is sent via some
local NAT router instead of via the IPIP mesh. As the Echolink protocol cannot
handle this situation (as described above) one needs to make sure that Echolink
traffic is not sent via this NAT shortcut.
The Echolink system is perfectly happy with clients, proxies and relays on NET44,
it is only the bad configuration of gateway systems that will break it.
Rob
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
2190
days inactive
2190
days old
2 comments
3 participants
participants (3)
-
Boudewijn (Bob) Tenty -
Jann Traschewski -
Rob Janssen