curl has apparently started attempting IPv6 even when it's not available

Bug #1205185 reported by Scott Kitterman
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
curl (Ubuntu)
Confirmed
Undecided
Unassigned
Raring
Won't Fix
Undecided
Unassigned

Bug Description

eth0 was not connected. The network connection was through wlan1 which, as you can see, only has a link local IPv6 address. IPv6 is disabled for the connection in NetworkManager (and there's no IPv6 here anyway). It doesn't affect anything (that I've noticed except curl (which affects rmadison, when affects syncpackage, which is a pain). This just started recently, so it's some kind of regression. Rmadison fails for both Debian and Ubuntu, so I don't think it's something related to the server on the distant end.

$ rmadison -u debian pyspf
curl: (7) Failed to connect to 2607:f8f0:610:4000:216:36ff:fe40:3860: Network is unreachable
kitterma@Scott-Latitude-E6320:~/devel/kde$ ifconfig
eth0 Link encap:Ethernet HWaddr 5c:26:0a:48:2f:48
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:20 Memory:e2e00000-e2e20000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:65536 Metric:1
          RX packets:38535 errors:0 dropped:0 overruns:0 frame:0
          TX packets:38535 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:6149913 (6.1 MB) TX bytes:6149913 (6.1 MB)

wlan1 Link encap:Ethernet HWaddr 24:77:03:e6:33:08
          inet addr:192.168.111.110 Bcast:192.168.111.255 Mask:255.255.255.0
          inet6 addr: fe80::2677:3ff:fee6:3308/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:606062 errors:0 dropped:0 overruns:0 frame:0
          TX packets:315570 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:699409894 (699.4 MB) TX bytes:50265821 (50.2 MB)

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: curl 7.29.0-1ubuntu3.1
ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
Uname: Linux 3.8.0-26-generic i686
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: i386
Date: Fri Jul 26 00:18:36 2013
EcryptfsInUse: Yes
InstallationDate: Installed on 2011-04-04 (843 days ago)
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
MarkForUpload: True
SourcePackage: curl
UpgradeStatus: Upgraded to raring on 2013-04-24 (92 days ago)

Revision history for this message
Scott Kitterman (kitterman) wrote :
tags: added: regression-release
Revision history for this message
Rolf Leggewie (r0lf) wrote :

raring has seen the end of its life and is no longer receiving any updates. Marking the raring task for this ticket as "Won't Fix".

Changed in curl (Ubuntu Raring):
status: New → Won't Fix
Revision history for this message
mc0e (xgcsufw02) wrote :

I don't think this is specific to raring.

I suspect my report at https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1457192 is a duplicate, but since this is closed...

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in curl (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.