26 Feb
2018
26 Feb
'18
8:17 a.m.
On Mon, Feb 26, 2018 at 03:11:01PM +0100, Benoit Panizzon wrote:
Hi Thomas
thousand people, thousand and one answers.
Anyway, just believe in that what the sysop for amprgw (44.0.0.1), Brian
Kantor, wrote in his mail two days ago:
==
However, NO addresses on the 44.142.162.x subnet are in the allowed
filter list at AMPRGW, so there will be NO connectivity to your
DHCP address from the Internet via AMPRGW. Thus the traceroute you
show is correctly reflecting your unreachability. You will have
to ask your coordinator or your hamnet manager why this is so.
===
There's still no reverse lookup for
44.142.162.123 ; as discussed
before, until fixed, 44.0.0.1 will not respond.
Well, this is where I got confusing replies...
Some state I only need a PTR if this IP should be reachable from the
internet. So no need for a PTR for it to communicate with any other ip
within the 44.0.0.0/8 range.
Some, like you, state that a PTR is needed for any communication, even
within hamnet.
I tend to believe the first statement is the more correct one as this
makes more sense to me and filtering based on PTR is done at the
gateway @ UCSD and not on every hamnet router.