3 Mar
2019
3 Mar
'19
3:51 p.m.
This is a normal system behavior.
For it to work, you need to mark incoming connections from internet
addresses to the ampr tunnel interface, and then use this connection
mark to add a routing mark on the replies, so they get routed back via
your ampr table and to the ampr-gw.
I have no working example on a linux system to give you, but the hint is
that it is done via iptables...
Marius, YO2LOJ
On 03.03.2019 22:13, Bent Bagger via 44Net wrote:
(...)
All of this works of course as it should for ordinary IP addresses
(non-44) and it also works fine when comming from a 44-address.
Furthermore it works fine when I ping my 44-address from any IP address
(which isn't surprising as ICMP is not forwarded). But it fails
miserablywhen accessing my 44-address (44.145.40.3) from an ordinary IP
address. The incomming request comes nicely in on the ampr interface,
but the reply goes out the WAN interface to the Internet at largeand is
thus not recognized as a reply on the originating host.