Nope, that's my firewall dropping that. I don't allow ICMP to hit the
96.86.86.53 address.
My tests included both PING and HTTPS. HTTPS is allowed through. The
bigger point I'm making here is that I ran TCPDUMP at the OS level which
would show the packets before the firewall rules are applied.
As a test, you can go to :
This is my VPN appliance
and you will get a login page there. At least...you should.
Thanks
Craig
On Thu, May 18, 2017 at 9:47 AM, Brian Kantor <Brian(a)ucsd.edu> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
On Thu, May 18, 2017 at 09:37:59AM -0400, Craig Brauckmiller wrote:
I've got the tunnel defined on my router.
When I run a TCPDUMP on the
physical interface that is hooked up to m169.228.66.251y cable modem, I
am
not seeing any traffic from the 169.228.66.251
tunnel endpoint. Nor,
obviously, am I seeing any traffic on my tunnel interface.
How do I troubleshoot this?
Thanks
Craig
KC1ETB
Your cable modem/router is rejecting incoming packets from 169.228.66.251:
# ping 96.86.86.53
PING 96.86.86.53 (96.86.86.53): 56 data bytes
36 bytes from
96-86-86-53-static.hfc.comcastbusiness.net (96.86.86.53):
Destination Port Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 20 0054 4bd2 0 0000 2e 01 9d4c 169.228.66.251 96.86.86.53
36 bytes from
96-86-86-53-static.hfc.comcastbusiness.net (96.86.86.53):
Destination Port Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 20 0054 4d86 0 0000 2e 01 9b98 169.228.66.251 96.86.86.53
36 bytes from
96-86-86-53-static.hfc.comcastbusiness.net (96.86.86.53):
Destination Port Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 20 0054 4ee7 0 0000 2e 01 9a37 169.228.66.251 96.86.86.53
However, pseudo-RIP and IPIP are being sent to you, so once you fix the
problem with your modem/router you should be on your way.
- Brian
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net