Re: ctrl-c doesn't reliably kill ping

2016-03-20 Thread cyg Simple
On 3/15/2016 7:43 AM, Adam Dinwoodie wrote: > On Tue, Mar 15, 2016 at 02:00:38PM +0300, Andrey Repin wrote: >> Greetings, Frank Farance! >> >>> A little digression, so you understand the background ... The workstation I >>> am >>> doing this from is connected to a Verizon router to their FIOS netw

Re: ctrl-c doesn't reliably kill ping

2016-03-19 Thread Marco Atzeri
On 15/03/2016 01:45, Frank Farance wrote: I have been having this problem with "ping". If I "ping" a location that doesn't exist, then "ping" just hangs and cannot be killed via "kill -KILL [pid]". Back to the problem, so when I type $ ping some.unknown.host I do not succeed to replicate

Re: ctrl-c doesn't reliably kill ping

2016-03-19 Thread Kaz Kylheku
On 16.03.2016 08:57, Michael Enright wrote: On Wed, Mar 16, 2016 at 7:51 AM, cyg Simple wrote: My ISP for my connection to the WWW is the one that is doing the inappropriate redirects. I sometime get these even when using VPN to my employer's intranet. My ISP also provides phone and TV Cabl

Re: ctrl-c doesn't reliably kill ping

2016-03-19 Thread Lee
Hi, On 3/14/16, Frank Farance wrote: > I have been having this problem with "ping". If I "ping" a location that > doesn't exist, then "ping" just hangs and cannot be killed via "kill -KILL > [pid]". > > A little digression, so you understand the background ... The workstation I > am > doing this

Re: ctrl-c doesn't reliably kill ping

2016-03-19 Thread Marco Atzeri
On 17/03/2016 22:10, Frank Farance wrote: Folks- Anyway, as we'd say in standardizing the C programming language, this behavior is a "surprise" ... and we should look to eliminate "surprises". Again, thank you in advance for your help. -FF as mentioned on: https://cygwin.com/ml/cygwin/

Re: ctrl-c doesn't reliably kill ping

2016-03-19 Thread Michael Enright
On Wed, Mar 16, 2016 at 7:51 AM, cyg Simple wrote: > > My ISP for my connection to the WWW is the one that is doing the > inappropriate redirects. I sometime get these even when using VPN to my > employer's intranet. My ISP also provides phone and TV Cable and I'm > guessing that the accepted pra

Re: ctrl-c doesn't reliably kill ping

2016-03-19 Thread Frank Farance
Folks- Thank you for the thoughtful observations, responses, and suggestions, which I will summarize: - Suggestion #1: Try different DNS settings not using Verizon. - Suggestion #2: Try different Verizon configuration. - Suggestion #3: Try Windows version of ping. - Observation #4: This should

Re: ctrl-c doesn't reliably kill ping

2016-03-19 Thread Lee
> If I weren't happy with upstream DNS, I'd go into the router's > configuration and tell dnsmasq to send its queries to some alternative > DNS. Instructions for Verizon customers to opt out of "DNS Assistance" are here: https://www.verizon.com/support/consumer/internet/opt-out-of-dns-assist Le

Re: ctrl-c doesn't reliably kill ping

2016-03-19 Thread cyg Simple
On 3/16/2016 12:56 AM, Kaz Kylheku wrote: > On 15.03.2016 04:00, Andrey Repin wrote: >> Greetings, Frank Farance! >>> So all of this is normal ISP stuff: they actually resolve unknown >>> addresses to >>> their own website (which is 90.242.140.21). >> >> This is NOT "normal", this is a violation of

Re: ctrl-c doesn't reliably kill ping

2016-03-19 Thread Warren Young
On Mar 16, 2016, at 10:07 AM, Lee wrote: > > The last time I tried the cygwin ping program it didn't return a > failure status It does if you don’t Ctrl-C out of it. So, if you’re using it from a script, you just ask for one packet: # ping does.not.exist 1 1 ping: unknown host does.no

Re: ctrl-c doesn't reliably kill ping

2016-03-19 Thread Andrey Repin
Greetings, Kaz Kylheku! > On 15.03.2016 04:00, Andrey Repin wrote: >> Greetings, Frank Farance! >>> So all of this is normal ISP stuff: they actually resolve unknown >>> addresses to >>> their own website (which is 90.242.140.21). >> >> This is NOT "normal", this is a violation of protocol. >> W

Re: ctrl-c doesn't reliably kill ping

2016-03-18 Thread Lee
On 3/16/16, Warren Young wrote: > On Mar 16, 2016, at 10:07 AM, Lee wrote: >> >> The last time I tried the cygwin ping program it didn't return a >> failure status > > It does if you don’t Ctrl-C out of it. So, if you’re using it from a > script, you just ask for one packet: > > # ping does.

Re: ctrl-c doesn't reliably kill ping

2016-03-15 Thread Kaz Kylheku
On 15.03.2016 04:00, Andrey Repin wrote: Greetings, Frank Farance! So all of this is normal ISP stuff: they actually resolve unknown addresses to their own website (which is 90.242.140.21). This is NOT "normal", this is a violation of protocol. Whoever encounter such behavior should call thei

Re: ctrl-c doesn't reliably kill ping

2016-03-15 Thread Warren Young
On Mar 14, 2016, at 6:45 PM, Frank Farance wrote: > > I have been having this problem with "ping". If I "ping" a location that > doesn't exist, then "ping" just hangs and cannot be killed via "kill -KILL > [pid]”. Are you certain that you’re using the Cygwin ping, and not the native Windows

Re: ctrl-c doesn't reliably kill ping

2016-03-15 Thread Adam Dinwoodie
On Tue, Mar 15, 2016 at 02:00:38PM +0300, Andrey Repin wrote: > Greetings, Frank Farance! > > > A little digression, so you understand the background ... The workstation I > > am > > doing this from is connected to a Verizon router to their FIOS network. > > Now the > > reason I mention this is

Re: ctrl-c doesn't reliably kill ping

2016-03-15 Thread Andrey Repin
Greetings, Frank Farance! > A little digression, so you understand the background ... The workstation I am > doing this from is connected to a Verizon router to their FIOS network. Now > the > reason I mention this is that the router's DNS (via DHCP to my workstation) is > 192.168.1.1, which I p

ctrl-c doesn't reliably kill ping

2016-03-14 Thread Frank Farance
I have been having this problem with "ping". If I "ping" a location that doesn't exist, then "ping" just hangs and cannot be killed via "kill -KILL [pid]". A little digression, so you understand the background ... The workstation I am doing this from is connected to a Verizon router to their F