Bug#854423: Does not work on IPv6-only networks

[Steve McIntyre]

On Thu, Feb 09, 2017 at 12:44:48AM +, Steve McIntyre wrote:
>
>I've tried this now. It's slightly problematic, as wicd tries to ping
>the gateway it's given to validate connectivity. By using the local v4
>address as the gateway too, that defeats this check. Then wicd keeps
>the network interface up. Beyond that, I can't say much - I'm not
>getting much useful networking beyond that but that's possibly my
>network setup... :-/

Sussed that bit - I didn't have rdnssd installed. With that added, and
the static v4 hack, I get working networking on my test network at
home.

Back to the v6 hacking in the code now... :-)

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Since phone messaging became popular, the young generation has lost the
 ability to read or write anything that is longer than one hundred and sixty
 characters."  -- Ignatios Souvatzis

Bug#854423: Does not work on IPv6-only networks

[Axel Beckert]

Control: severity -1 important

Hi Steve,

sorry, botched the severity you've set with my merging the other day.

Steve McIntyre wrote:
> I've tried this now. It's slightly problematic, as wicd tries to ping
> the gateway it's given to validate connectivity.

That may be optional. In wicd-curses, go to "P" for "Preferences",
then 2x "→" to "Advanced Settings", then uncheck "Ping static gateways
after connecting to verify association". (I though fear that this
setting only affects statically configured network connections. Not
sure, though.)

OTOH, in a pure IPv6 setting, this should probably cause to ping the
IPv6 gateway, too. (I though consider that optional for now, so if
someone comes up with a patch without pinging the IPv6 gateway, I'd be
fine.)

> By using the local v4 address as the gateway too, that defeats this
> check. Then wicd keeps the network interface up.

*nod*

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#854423: Does not work on IPv6-only networks

[Steve McIntyre]

On Mon, Feb 06, 2017 at 11:53:41PM +, Steve McIntyre wrote:
>On Tue, Feb 07, 2017 at 12:39:23AM +0100, Axel Beckert wrote:
>>
>>Same question to you as to the other reporter: Have you tried to
>>configure a static IPv4 dummy address as workaround? (Just out of
>>curiosity if that's a workaround which could be recommended until
>>the issue is fixed properly.)
>
>Ah, didn't think of that. That's a possible thing to try,
>yes. As/when/if I get the time to play with this again (maybe on a
>separate test network at home), I'll give that a try.

I've tried this now. It's slightly problematic, as wicd tries to ping
the gateway it's given to validate connectivity. By using the local v4
address as the gateway too, that defeats this check. Then wicd keeps
the network interface up. Beyond that, I can't say much - I'm not
getting much useful networking beyond that but that's possibly my
network setup... :-/

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Into the distance, a ribbon of black
Stretched to the point of no turning back

Bug#854423: Does not work on IPv6-only networks

[Steve McIntyre]

On Tue, Feb 07, 2017 at 12:39:23AM +0100, Axel Beckert wrote:
>Control: retitle -1 wicd: Does not work on IPv6-only networks
>Control: forcemerge 854176 -1
>
>Hi Steve,
>
>Steve McIntyre wrote:
>> I found this over the weekend at FOSDEM.
>
>You're not the only one: https://bugs.debian.org/854176 :-)

ACK. When I first looked for an existing bug, that wasn't there... :-)

>Merging these two bug reports.
>
>> I've dug into this, and I can see why. If DHCP doesn't return a v4
>> lease on a connection attempt (dhcp_failed), it aborts the
>> connection.
>
>Same question to you as to the other reporter: Have you tried to
>configure a static IPv4 dummy address as workaround? (Just out of
>curiosity if that's a workaround which could be recommended until
>the issue is fixed properly.)

Ah, didn't think of that. That's a possible thing to try,
yes. As/when/if I get the time to play with this again (maybe on a
separate test network at home), I'll give that a try.

>> I've started to hack on this a little bit over the weekend to see if
>> there's an easy fix (if no v4 lease acquired, check to see if a
>> global v6 address has been assigned),
>
>Much appreciated!
>
>> but I ran out of time to test this properly.
>
>Understandable. FOSDEM is always too short and there's too much to
>see. :-)

*grin* Exactly.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
The two hard things in computing:
 * naming things
 * cache invalidation
 * off-by-one errors  -- Stig Sandbeck Mathisen

Bug#854423: Does not work on IPv6-only networks

[Axel Beckert]

Control: retitle -1 wicd: Does not work on IPv6-only networks
Control: forcemerge 854176 -1

Hi Steve,

Steve McIntyre wrote:
> I found this over the weekend at FOSDEM.

You're not the only one: https://bugs.debian.org/854176 :-)

Merging these two bug reports.

> I've dug into this, and I can see why. If DHCP doesn't return a v4
> lease on a connection attempt (dhcp_failed), it aborts the
> connection.

Same question to you as to the other reporter: Have you tried to
configure a static IPv4 dummy address as workaround? (Just out of
curiosity if that's a workaround which could be recommended until
the issue is fixed properly.)

> I've started to hack on this a little bit over the weekend to see if
> there's an easy fix (if no v4 lease acquired, check to see if a
> global v6 address has been assigned),

Much appreciated!

> but I ran out of time to test this properly.

Understandable. FOSDEM is always too short and there's too much to
see. :-)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#854423: Does not work on IPv6-only networks

[Steve McIntyre]

Package: wicd
Version: 1.7.4+tb2-2
Severity: important
Tags: upstream ipv6

Hi,

I found this over the weekend at FOSDEM. Their default wifi network is
v6 only, with no v4 config at all. This would be fine for me (all the
services I need are functional on v6), but wicd does not work on such
a network.

I've dug into this, and I can see why. If DHCP doesn't return a v4
lease on a connection attempt (dhcp_failed), it aborts the
connection. I've started to hack on this a little bit over the weekend
to see if there's an easy fix (if no v4 lease acquired, check to see
if a global v6 address has been assigned), but I ran out of time to
test this properly.

-- System Information:
Debian Release: 8.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-0.bpo.2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages wicd depends on:
ii  wicd-cli [wicd-client] 1.7.4+tb2-2
ii  wicd-curses [wicd-client]  1.7.4+tb2-2
ii  wicd-daemon1.7.4+tb2-2
ii  wicd-gtk [wicd-client] 1.7.4+tb2-2

wicd recommends no packages.

wicd suggests no packages.

Versions of packages wicd-cli depends on:
pn  python:any   
ii  wicd-daemon  1.7.4+tb2-2

Versions of packages wicd-cli recommends:
ii  sudo  1.8.10p3-1+deb8u3

Versions of packages wicd-gtk depends on:
ii  python-glade2  2.24.0-4
ii  python-gtk22.24.0-4
pn  python:any 
ii  wicd-daemon1.7.4+tb2-2

Versions of packages wicd-gtk recommends:
ii  gksu   2.0.2-9
ii  python-notify  0.1.1-4

Versions of packages wicd-curses depends on:
ii  python-urwid  1.2.1-2+b1
pn  python:any
ii  wicd-daemon   1.7.4+tb2-2

Versions of packages wicd-curses recommends:
ii  sudo  1.8.10p3-1+deb8u3

Versions of packages wicd-daemon depends on:
ii  adduser  3.113+nmu3
ii  dbus 1.8.22-0+deb8u1
ii  debconf  1.5.56
ii  ethtool  1:3.16-1
ii  iproute2 3.16.0-2
ii  iputils-ping 3:20121221-5+b2
ii  isc-dhcp-client  4.3.1-6+deb8u2
ii  lsb-base 4.1+Debian13+nmu1
ii  net-tools1.60-26+b1
ii  psmisc   22.21-2
ii  python-dbus  1.2.0-2+b3
ii  python-gobject   3.14.0-1
ii  python-wicd  1.7.4+tb2-2
pn  python:any   
ii  wireless-tools   30~pre9-8
ii  wpasupplicant2.3-1+deb8u4

Versions of packages wicd-daemon recommends:
ii  rfkill 0.5-1
ii  wicd-cli [wicd-client] 1.7.4+tb2-2
ii  wicd-curses [wicd-client]  1.7.4+tb2-2
ii  wicd-gtk [wicd-client] 1.7.4+tb2-2

Versions of packages wicd-daemon suggests:
ii  pm-utils  1.4.1-15

Versions of packages python-wicd depends on:
pn  python:any  

-- debconf information excluded