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:mime-version:date:message-id:subject:from:to :content-type:content-transfer-encoding; q=dns; s=default; b=XCM rDf9Ikwwd8axbsp9ZV7/KKrT9uyYx401hQkcQUiK3YaNP4SOAtTk6ZVLuzh+HJ92 CjoJcE/TcL9oS3eWRnzeqWl7HmaOqHpqAZs4zYdWhDcohvvrkpoKBl8HVbE3lJel elL4/gz1b8dPSfClpdOPBH4x5jFJR8ntym+SEIfM= 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:mime-version:date:message-id:subject:from:to :content-type:content-transfer-encoding; s=default; bh=PB572PtoN 2W6hAIssoFUob97DZU=; b=aCr4hFTEbZJt9cmxcxierGPcUSoMxBzgnrVfkcDD7 b53m9H9teA8ACS80AhE48Dr/d302z/2IJTZhVJYfc4Zz51bpUrSYa7h8/D5zb5+Q AMbu31qa041cEdeCzxKTfbJhH1MT4Mc0Fp64UF6v2JcBBrvoWTdDzyx85LdPqmBz Qg= 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=1.9 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-lb0-f181.google.com MIME-Version: 1.0 X-Received: by 10.112.27.133 with SMTP id t5mr14512441lbg.21.1397902695139; Sat, 19 Apr 2014 03:18:15 -0700 (PDT) Date: Sat, 19 Apr 2014 20:18:15 +1000 Message-ID: Subject: "Bad Address" response to many net tools after updating cygwin x86_64 1.7.29 From: repudi8or repu To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id s3JAIWQK026607 I decided to update my cygwin x86_64 environment a few days back out of concern about the openssh heartbleed bug. Since that time most of my network tools no longer work as expected, reporting "Bad address" as the failure reason Here are some samples:- rep AT WinServer:~$ ping 192.168.1.1 -bash: /cygdrive/c/Windows/system32/ping: Bad address rep AT WinServer:~$ which ping /cygdrive/c/Windows/system32/ping rep AT WinServer:~$ file /cygdrive/c/Windows/system32/ping /cygdrive/c/Windows/system32/ping: PE32+ executable (console) x86-64, for MS Windows rep AT WinServer:~$ netstat -na -bash: /cygdrive/c/Windows/system32/netstat: Bad address rep AT WinServer:~$ which netstat /cygdrive/c/Windows/system32/netstat rep AT WinServer:~$ file /cygdrive/c/Windows/system32/netstat /cygdrive/c/Windows/system32/netstat: PE32+ executable (console) x86-64, for MS Windows rep AT WinServer:~$ wget www.google.com --2014-04-19 20:03:25-- http://www.google.com/ Resolving www.google.com (www.google.com)... failed: Bad address. wget: unable to resolve host address ‘www.google.com’ and so on and so forth. Did some googling of the error, nothing recent that seems immediately obvious. The same tools work ok from windows command prompt. rep AT WinServer:~$ uname -a CYGWIN_NT-6.1 WinServer 1.7.29(0.272/5/3) 2014-04-07 13:46 x86_64 Cygwin Any suggestions how i can track down / fix whatever is going wrong here ? Thanks -- 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