25 Sep
2019
25 Sep
'19
9:31 a.m.
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