18 May
2017
18 May
'17
10:25 a.m.
I do that for security, but ok.
I just re-enabled ICMP.
Ping away! :)
Thanks
Craig
On Thu, May 18, 2017 at 10:17 AM, Brian Kantor <Brian(a)ucsd.edu> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
On Thu, May 18, 2017 at 10:08:09AM -0400, Craig Brauckmiller wrote:
Nope, that's my firewall dropping that. I
don't allow ICMP to hit the
96.86.86.53 address.
Then you have cut your own throat by disabling one of the internet's
primary troubleshooting tools.
As a test, you can go to : https://96.86.86.53
This is my VPN
appliance
and you will get a login page there. At
least...you should.
Yes, it connects from 169.228.66.251:
telnet 96.86.86.53 443
Trying 96.86.86.53...
Connected to 96-86-86-53-static.hfc.comcastbusiness.net.
Escape character is '^]'.
^]
telnet> q
Connection closed.
I have been told that comcast-provided CPE doesn't allow protocol 4
through it unless it is placed in raw bridge mode.
- Brian
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net