Any news about this problem? Sorry to say, but I have
the impression that neither #805445 nor
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1510098
get the focus they deserve (unless ifupdown is considered
as deprecated).
Regards
Harri
On Wed, Nov 18, 2015 at 11:28:49AM +0100, Jeroen Massar wrote:
> Debian stable 0.7.53.1, I avoid Ubuntu like a plague :)
[...]
> Note that we zero out /etc/sysctl.d/10-ipv6-privacy.conf (empty file
> with just comments) to avoid privacy parameters to be set (Ubuntu
> actually does do that, not
On 2015-11-18 11:12, Guus Sliepen wrote:
> severity 805445 important
> thanks
>
> On Wed, Nov 18, 2015 at 10:16:29AM +0100, Jeroen Massar wrote:
>
>> Package: ifupdown
>> Version: 0.7.53.1
>> Severity: critical
>>
>> Marking critical as it breaks IPv6 connectivity after a reboot, thus
>> hope
On Wed, Nov 18, 2015 at 11:28:49AM +0100, Jeroen Massar wrote:
> > It's not dropping your SQL tables or blowing up your house, so:
> >
> > important
> > a bug which has a major effect on the usability of a package,
> > without rendering it completely unusable to everyone.
>
> Well
On 2015-11-18 11:46, Guus Sliepen wrote:
[..]
>> Indeed, Ubuntu sets use_tempaddr=2 in their sysctl (hence the empty file
>> mentioned above) and then when sysctl this custom file the setting is
>> reverted and you lose your default...
>>
>> hmmm, that might actually be affecting this too now I
severity 805445 important
thanks
On Wed, Nov 18, 2015 at 10:16:29AM +0100, Jeroen Massar wrote:
> Package: ifupdown
> Version: 0.7.53.1
> Severity: critical
>
> Marking critical as it breaks IPv6 connectivity after a reboot, thus
> hope you got IPv4 still (or KVM :) if it is a remote machine ;)
Package: ifupdown
Version: 0.7.53.1
Severity: critical
Marking critical as it breaks IPv6 connectivity after a reboot, thus
hope you got IPv4 still (or KVM :) if it is a remote machine ;)
See Ubuntu bug report here:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1510098
Btw,
On Wed, Nov 18, 2015 at 02:25:35PM +0100, Jeroen Massar wrote:
> > Ok, tried it with and without these settings, but on a fresh install
> > setting the IPv6 address, netmask and gateway just works as expected,
> > both on Debian stable and unstable.
>
> Did you try at-boot or post-boot?
Both.
On 2015-11-18 13:54, Guus Sliepen wrote:
[..]
>> 8<-
>> $ cat /etc/sysctl.d/99-custom.conf
>> # Disable Accept of Router Advertisements
>> net.ipv6.conf.all.accept_ra=0
>> net.ipv6.conf.default.accept_ra=0
>>
>> # Make sure that privacy addresses are disabled
>>
9 matches
Mail list logo
