31 Jul
2013
31 Jul
'13
7:54 p.m.
44.0.0.1 doesn't respond to pings from amprnet
because of brokeness.
It's a bug in the kernel on amprgw which I've never been able to track
down.
Ok, that solves that part of the mystery. I'm still curious as to why I
cannot get to the webpage however.
I note that your gateway machine is not responding to
pings from the
Internet on its commercial address.
Well, that's very curious indeed. I just pinged my machine, and it
responded just fine for me.
$ ping ampr.k1qv.com
PING ampr.k1qv.com (54.214.234.149): 56 data bytes
64 bytes from 54.214.234.149: icmp_seq=0 ttl=42 time=67.445 ms
64 bytes from 54.214.234.149: icmp_seq=1 ttl=42 time=86.558 ms
64 bytes from 54.214.234.149: icmp_seq=2 ttl=42 time=84.399 ms
64 bytes from 54.214.234.149: icmp_seq=3 ttl=42 time=98.167 ms
--- ampr.k1qv.com ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 67.445/84.142/98.167/10.970 ms
Not really sure what's going on here. As I said, I pinged
n6mef-gw.ampr.org(44.4.2.153)
as a test with tcpdump running. I see the IPIP encapsulated ICMP requests
and replies working as they should between my machine and his gateway...
So... we know that I'm receiving IPIP encapsulated traffic from 44.0.0.1
because I'm receiving the RIP traffic, however, tcpdump shows no inbound
traffic when trying to ping my 44.4.36.1 address from the internet.
Stupid question here, was I correct in assuming that my net44 subnet was
routable from the internet?
--
Blaine Forbort, K1QV