X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:subject:mime-version:content-type :content-transfer-encoding:date:from:in-reply-to:references :message-id; q=dns; s=default; b=yfU5L2J/bfUyz7CZD3jd6aiogR5JEyT xxVHgAARKPBAmBsxEh4c8Q2bOlBS4fHwno/xkngzSP2VC1PeLJuuphCjUcoxq4hX /Xi/Vs2dzf69v1lYi8d8W1Qtp63ndGXXfWRDRMiYp8kxaJH05MjineQdXt5Zb7Uj vSC+5HFIxWzk= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:subject:mime-version:content-type :content-transfer-encoding:date:from:in-reply-to:references :message-id; s=default; bh=UZRigquAd5Pbd9mydqNBPLCfKTU=; b=pCxtL 4cMpJBc18XTqE1kcJhW5INp1krnBh8Fcmp2bQu5Ia5K6Ru/dRHOMsv6H14iakoCg U7E3CNtI7mXBb+L9qpbWhDGlUCGTY6FsFDfF9PKYSTHoE/mJOiAajESZ2lsfrGTH qMB8JjmlRPS5camYpv9LVhXhItqbvHntV7N+Ro= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.6 required=5.0 tests=AWL,BAYES_05,FROM_STARTS_WITH_NUMS,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=H*f:sk:CAOC2fq, H*f:sk:P-jCG5Z, enright, Enright X-HELO: smtp-out-so.shaw.ca X-Authority-Analysis: v=2.1 cv=VIR9547X c=1 sm=1 tr=0 a=WiYoHcCliNeVponEdG0Ckg==:117 a=WiYoHcCliNeVponEdG0Ckg==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=IkcTkHD0fZMA:10 a=SMorJkV_YP8A:10 a=7OsogOcEt9IA:10 a=ixt_Hem4weDH9PMFUZ8A:9 a=QEXdDO2ut3YA:10 To: cygwin AT cygwin DOT com Subject: Re: ctrl-c doesn't reliably kill ping X-PHP-Originating-Script: 501:rcmail.php MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Date: Wed, 16 Mar 2016 10:33:42 -0700 From: Kaz Kylheku <920-082-4242 AT kylheku DOT com> In-Reply-To: References: "<56E6F25A DOT 7070000 AT gmx DOT de> <56E75B3E DOT 7020102 AT farance DOT com> <54382838 DOT 20160315140038 AT yandex DOT ru> <9ee672500661e37c240d30d8413ca0af AT mail DOT kylheku DOT com>" <56E972EB DOT 9000204 AT gmail DOT com> Message-ID: X-Sender: 920-082-4242 AT kylheku DOT com User-Agent: Roundcube Webmail/0.9.2 X-CMAE-Envelope: MS4wfDFWDDI5cWCOixLLozMvvQ8wMPpHbWxfjaK/qWftVvWPyjuc6h1o9YSeL9pEiA/9W0Bs4+DmYllRl7pYzRfHSrD35R/0wDXPoqGdFClsNeyorwz6lwh9 Kvv+Q97rTnIe02b9c6NTI0F/yE1zfDfMShtWexp/WT9mxISyFYtb0slo X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id u2GHYDjC027855 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 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. You have to point your local network's router to some alternative DNS servers. You shouldn't have to do anything in an individual client workstations and devices. Example: I have dnmasq running on a Linksys wireless router. All my machines here obtain their DHCP from that and point their DNS resolvers to it (because the DHCP tells them to). 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. -- 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