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 interfa
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, g
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
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 :-
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
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 netwo
6 matches
Mail list logo
