public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Michael Enright <mike@kmcardiff.com>
To: cygwin@cygwin.com
Subject: Re: ctrl-c doesn't reliably kill ping
Date: Wed, 16 Mar 2016 15:57:00 -0000	[thread overview]
Message-ID: <CAOC2fq80JudLuzgtg+P-jCG5ZiS0jMNqTE86Tn3ynJm3=6kFSQ@mail.gmail.com> (raw)
In-Reply-To: <56E972EB.9000204@gmail.com>

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 practiced exception is practiced by all such
> companies.
>

Can confirm. Readers may be interested to learn that I tried to set
the DNS manually in the connection properties of my VPN connection (to
the exact same thing the VPN connection would have configured anyway)
but this did not work either. I used my ISP's opt-out page and that
didn't help. I also learned how to empty DNS caches in Windows
(ipconfig /flushdns) and Google Chrome (chrome://net-internals/#dns)
and none of those measures was effective. I couldn't use the wiki with
its IP address because the links apparently are full paths and there's
redirects involved (with full paths) and every complete URL goes to
name resolution. It was as if  (that means I'm speculating here) as if
using the standard DNS port was causing the ISP to DPI my DNS
requests. Or maybe they are just looking in all the packets. Could the
revenue from those bogus links be so high???

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2016-03-16 15:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14 17:18 ctrl-c doesn't reliably kill applications Björn Stabel
2016-03-14 23:39 ` Kaz Kylheku
2016-03-15  0:46 ` ctrl-c doesn't reliably kill ping Frank Farance
2016-03-15 11:05   ` Andrey Repin
2016-03-15 11:43     ` Adam Dinwoodie
2016-03-16 14:46       ` cyg Simple
2016-03-16  4:56     ` Kaz Kylheku
2016-03-16 11:50       ` Andrey Repin
2016-03-16 14:51       ` cyg Simple
2016-03-16 15:57         ` Michael Enright [this message]
2016-03-16 17:33           ` Kaz Kylheku
2016-03-16 18:10             ` Lee
2016-03-17 21:10               ` Frank Farance
2016-03-17 21:29                 ` Marco Atzeri
2016-03-15 15:13   ` Warren Young
2016-03-16 13:25   ` Marco Atzeri
2016-03-17 20:04     ` ctrl-c doesn't reliably kill applications Björn Stabel
2016-04-18 21:38       ` Aaron Digulla
2016-04-19  9:13         ` Corinna Vinschen
2016-04-19 16:30           ` Aaron Digulla
2016-03-16 16:07   ` ctrl-c doesn't reliably kill ping Lee
2016-03-16 16:50     ` Warren Young
2016-03-16 17:52       ` Lee

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAOC2fq80JudLuzgtg+P-jCG5ZiS0jMNqTE86Tn3ynJm3=6kFSQ@mail.gmail.com' \
    --to=mike@kmcardiff.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).