27 Sep
2019
27 Sep
'19
4:11 a.m.
Hi Brian,
Thanks for answer. It's strange because of this host has IP registered in AMPR DNS. I
suppose it is a routing trouble: ICMP packet cannot find a way back to tunnel (because of
I can ping Raspberry PI connected to this interface).
It's not a big problem but I would like to know why id doesn't work.
Regards,
Tomek
--- 2019-09-25 15:31:00 +0200 CEST 44net-bounces+hf8n=winlink.org(a)mailman.ampr.org wrote:
---
On Wed, Sep 25, 2019 at 02:23:06PM +0100, Alistair
Mackenzie via 44Net wrote:
Are you running rip to tell the amprgw of your
prefix?
Amprgw doesn't listen for RIP. All its routing information comes
from the encap file published by the portal, which contains the route
44.165.1.48/28 via 91.199.89.253
However, only the addresses 44.165.1.49 and 44.165.1.50 are entered
in the DNS, so only they will be pingable from outside 44net. Any
other address on that subnet will not due to /32-level filtering on
amprgw. If it is desired to be able to ping 44.165.1.48, for example,
there must be an entry in the DNS for it to enable the ingress filter.
- Brian
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net