And I have no idea what happened, but just today my 44.4.28.50 ip
address started working again.
Comcast must have pushed a button somewhere? I did get an updated
router, but nothing happened after that got put in.
But today, I tried another ping, and it's working.
On 6/30/19 9:23 AM, Cathryn Mataga wrote:
I have static IP's and a Comcast Business account.
I think I have
exactly what you have.
On 6/30/19 9:13 AM, David Ranch wrote:
>
> I have AMPR working with Comcast Business though I'm using static
> IPs. To get static IP support, Comcast requires to configure a
> screwly 1:1 NAT like setup as bridging does NOT work with statics
> (wth?!). I can give you details if you wish.
>
>
http://kb3vwg-010.ampr.org/tools/ping/php-ping44.php?host=44.4.10.41&co…
>
>
> --David
> KI6ZHD
>
>
> On 06/29/2019 10:38 AM, Brian Kantor wrote:
>> Cathryn,
>>
>> I see your ping requests arriving at 169.228.34.84 no problem,
>> and they are being encapsulated at sent to 50.79.209.150, again,
>> no problem. Nothing is coming back from 50.79.209.150.
>>
>> This suggests that something is filtering out protocol 4 (IPIP)
>> between 169.228.34.84 and 50.79.209.150.
>>
>> A traceroute from 169.228.34.84 to 50.79.209.150 using ordinary
>> UDP works, completing after 18 hops. The last few hops in that
>> path look like this:
>>
>> 14 162.151.87.226 12.097 ms 12.315 ms 12.088 ms
>> 15 162.151.79.134 12.735 ms 12.744 ms 12.773 ms
>> 16 68.87.227.122 13.080 ms 12.983 ms 12.920 ms
>> 17 * * *
>> 18 50.79.209.150 37.676 ms 42.664 ms 33.084 ms
>>
>> A traceroute from 169.228.34.84 to 50.79.209.150 using protocol 4
>> (IPIP) does not complete, and there are no responses beyond hop
>> 15. The last few hops are:
>>
>> 12 68.86.84.150 11.117 ms 12.601 ms 12.734 ms
>> 13 68.86.94.154 11.761 ms 11.743 ms 11.340 ms
>> 14 162.151.87.226 12.469 ms 12.162 ms 12.392 ms
>> 15 162.151.79.134 12.757 ms 12.800 ms 12.797 ms
>> 16 * * *
>> 17 * * *
>> 18 * * *
>>
>> This suggests that hop 16, 68.87.227.122, is not accepting/passing
>> protocol 4 packets. The hostname for that host is
>>
lag-2-240-acr07.pinole.ca.sfba.comcast.net.
>>
>> I hate to throw you to the wolves of comcast's customer service line,
>> but you may need to find out from them if they suddenly started
>> filtering
>> out inbound IPIP packets at that router.
>> - Brian
>>
>>
>> On Sat, Jun 29, 2019 at 09:50:40AM -0700, Cathryn Mataga via 44Net
>> wrote:
>>> Date: Sat, 29 Jun 2019 09:50:40 -0700
>>> From: Cathryn Mataga <cathryn(a)junglevision.com>
>>> To: AMPRNet working group <44net(a)mailman.ampr.org>
>>> Subject: Connecting to 44net
>>>
>>> I'm not connected to 44net anymore, when I ping, to me at least, my
>>> outgoing packets look correct, but I get no response ever.
>>>
>>> I'm trying to put together as much as I can. My gateway ips 44.4.28.50
>>> at 50.79.209.150, I have a static IP.
>>>
>>> I'm current on the portal, far as I can tell with no error messages.
>>>
>>>
>>> ping 44.0.0.1
>>> PING 44.0.0.1 (44.0.0.1) 56(84) bytes of data.
>>> *no response ever
>>>
>>> I see the outgoing, but never the ping back.
>>>
>>> tcpdump -vv -i enp4s0 host 169.228.34.84
>>> tcpdump: listening on enp4s0, link-type EN10MB (Ethernet), capture
>>> size
>>> 262144 bytes
>>> 09:39:25.982188 IP (tos 0x0, ttl 64, id 54479, offset 0, flags [DF],
>>> proto IPIP (4), length 104)
>>>
hamradio.junglevision.com >
amprgw.ucsd.edu: IP (tos 0x0, ttl
>>> 64,
>>> id 14161, offset 0, flags [DF], proto ICMP (1), length 84)
>>>
ke6i.ampr.org >
gw.ampr.org: ICMP echo request, id 25489, seq
>>> 105,
>>> length 64
>>> 09:39:27.006173 IP (tos 0x0, ttl 64, id 54594, offset 0, flags [DF],
>>> proto IPIP (4), length 104)
>>>
hamradio.junglevision.com >
amprgw.ucsd.edu: IP (tos 0x0, ttl
>>> 64,
>>> id 15137, offset 0, flags [DF], proto ICMP (1), length 84)
>>>
ke6i.ampr.org >
gw.ampr.org: ICMP echo request, id 25489, seq
>>> 106,
>>> length 64
>>>
>>> I occasionally see one of these, which hints to me that ipip is making
>>> it to my gateway.
>>>
>>> 09:39:15.386222 IP (tos 0x20, ttl 48, id 32657, offset 0, flags
>>> [none],
>>> proto IPIP (4), length 60)
>>>
amprgw.ucsd.edu >
hamradio.junglevision.com: IP (tos 0x0, ttl
>>> 237,
>>> id 33644, offset 0, flags [none], proto TCP (6), length 40)
>>> no-reverse-dns-configured.com.46324 > ke6i.ampr.org.finger:
>>> Flags
>>> [S], cksum 0x039d (correct), seq 2046795537, win 1024, length 0
>>>
>>>
>>> ip tunnel list tunl0
>>> tunl0: any/ip remote any local any ttl 64
>>>
>>> ifconfig tunl0
>>>
>>> tunl0: flags=4289<UP,RUNNING,NOARP,MULTICAST> mtu 1480
>>> inet 44.4.28.50 netmask 255.255.255.255
>>> tunnel txqueuelen 1000 (IPIP Tunnel)
>>> RX packets 2259 bytes 305270 (298.1 KiB)
>>> RX errors 0 dropped 0 overruns 0 frame 0
>>> TX packets 2874 bytes 233904 (228.4 KiB)
>>> TX errors 232 dropped 0 overruns 0 carrier 0 collisions
>>> 232
>>>
>>> ifconfig enp4s0
>>> enp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>>> inet 50.79.209.150 netmask 255.255.255.240 broadcast
>>> 50.79.209.159
>>> ether 8c:89:a5:64:04:4c txqueuelen 1000 (Ethernet)
>>> RX packets 140452 bytes 25244334 (24.0 MiB)
>>> RX errors 0 dropped 473 overruns 0 frame 0
>>> TX packets 53461 bytes 5807456 (5.5 MiB)
>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>>>
>>> ampr-ripd -d -t 44 -a 44.4.28.50/32 -s -L ke6i@cm87uu
>>> Using gateway 50.79.209.158 for direct 44net endpoints via
>>> interface enp4s0.
>>> Calling home
>>> Waiting for RIPv2 broadcasts...
>>> Simple password: ***********
>>>
>>>
>>> ip rule list
>>>
>>> 0: from all lookup local
>>> 44: from all to 44.0.0.0/8 lookup hamradio
>>> 45: from all iif tunl0 lookup hamradio
>>> 45: from 44.4.28.50 lookup hamradio
>>> 32766: from all lookup main
>>> 32767: from all lookup default
>>>
>>>
>>> ip route list table hamradio
>>> 44.0.0.1 via 169.228.34.84 dev tunl0 proto 44 onlink window 840
>>> 44.2.0.1 via 191.183.136.1 dev tunl0 proto 44 onlink window 840
>>> 44.2.2.0/24 via 216.218.207.198 dev tunl0 proto 44 onlink window 840
>>> ...
>>>
>>> I don't think it's a firewall issue, I've turned off firewall and
it
>>> doesn't fix anything.
>>>
>>> My route table looks healthy, so I think ampr-ripd is worrking
>>> correctly?
>>>
>>> Tried to include as much information as I can, thanks for any help!
>
> _________________________________________
> 44Net mailing list
> 44Net(a)mailman.ampr.org
>
https://mailman.ampr.org/mailman/listinfo/44net