Processed: Re: Bug#837759: network configuration stops working reliably

2016-09-20 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 confirmed upstream pending -moreinfo
Bug #837759 [systemd] network configuration stops working reliably
Added tag(s) pending, confirmed, and upstream.
Bug #837759 [systemd] network configuration stops working reliably
Removed tag(s) moreinfo.
> forwarded -1 https://github.com/systemd/systemd/issues/4186
Bug #837759 [systemd] network configuration stops working reliably
Set Bug forwarded-to-address to 
'https://github.com/systemd/systemd/issues/4186'.

-- 
837759: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#837759: network configuration stops working reliably

2016-09-20 Thread Martin Pitt 
Control: tag -1 confirmed upstream pending -moreinfo
Control: forwarded -1 https://github.com/systemd/systemd/issues/4186

Hello Wolfgang,

thanks for the further information. I can reproduce the problem now
and forwarded it upstream.

I dropped the patches from current packaging git, so -7 will fix this
again.

Thanks!

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


signature.asc
Description: PGP signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#837759: network configuration stops working reliably

2016-09-19 Thread Felipe Sateler 
Control: tags -1 - unreproducible

On 19 September 2016 at 11:24, Martin Pitt  wrote:
> Control: severity -1 important
> Contro: tag -1 unreproducible
>
> In accordance with the severity definitions [1] I downgrade this to
> "important". It does not completely break systemd, we don't enable
> networkd by default, and it does not affect every installation (it's
> not reproducible on our side yet).

I managed to reproduce. Interestingly, this appears to occur only
during boot, but not if networkd is restarted after the boot. To
reproduce I created a bootable debian raw image with mkosi, and
configured as follows:

0. Install $EDITOR
1. Enable networkd (and add a config for ens* with dhcp)
2. Install iproute2
3. Add the service as described in the first post (make sure to add
DefaultDependencies=no to the unit).

After a reboot, I could see that TEST has no addresses.

Use the following to boot the image:
qemu-system-x86_64 -m 512 -vga virtio -bios /usr/share/ovmf/OVMF.fd \
--enable-kvm -drive file=image.raw,format=raw

-- 

Saludos,
Felipe Sateler

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processed: Re: Bug#837759: network configuration stops working reliably

2016-09-19 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 - unreproducible
Bug #837759 [systemd] network configuration stops working reliably
Ignoring request to alter tags of bug #837759 to the same tags previously set

-- 
837759: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#837759: network configuration stops working reliably

2016-09-19 Thread Wolfgang Walter 
Hello Martin,

On Monday, 19 September 2016 16:24:12 CEST Martin Pitt wrote:
> Control: severity -1 important
> Contro: tag -1 unreproducible
> 
> In accordance with the severity definitions [1] I downgrade this to
> "important". It does not completely break systemd, we don't enable
> networkd by default, and it does not affect every installation (it's
> not reproducible on our side yet).
> 
> Don't worry, I'm still eager to find out what's happening here; I'll
> look at your logs as soon as possible.
> 
> Martin
> 
> [1] https://www.debian.org/Bugs/Developer#severities

Ok, here as attachment is the log with debugging enabled for systemd-networkd.

In this boot net and TEST have lost all there ip-adresses. The logs shows that 
it is systemd-networkd which removes them.

Regards,
-- 
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts-- Logs begin at Sat 2016-07-02 20:15:26 CEST, end at Mon 2016-09-19 21:24:41 
CEST. --
Sep 19 21:24:03 maiskolben systemd-journald[182]: Runtime journal 
(/run/log/journal/) is 1.2M, max 9.9M, 8.7M free.
Sep 19 21:24:03 maiskolben kernel: Initializing cgroup subsys cpuset
Sep 19 21:24:03 maiskolben kernel: Initializing cgroup subsys cpu
Sep 19 21:24:03 maiskolben kernel: Initializing cgroup subsys cpuacct
Sep 19 21:24:03 maiskolben kernel: Linux version 4.4.21-debianlike64x+1.4 
(root@maiskolben) (gcc version 6.2.0 20160901 (Debian 6.2.0-3) ) #1 SMP PREEMPT 
Thu Sep 15 21:25:55 CEST 2016
Sep 19 21:24:03 maiskolben kernel: Command line: root=/dev/sda quiet
Sep 19 21:24:03 maiskolben kernel: x86/fpu: Legacy x87 FPU detected.
Sep 19 21:24:03 maiskolben kernel: x86/fpu: Using 'lazy' FPU context switches.
Sep 19 21:24:03 maiskolben kernel: e820: BIOS-provided physical RAM map:
Sep 19 21:24:03 maiskolben kernel: BIOS-e820: [mem 
0x-0x0009fbff] usable
Sep 19 21:24:03 maiskolben kernel: BIOS-e820: [mem 
0x0009fc00-0x0009] reserved
Sep 19 21:24:03 maiskolben kernel: BIOS-e820: [mem 
0x000f-0x000f] reserved
Sep 19 21:24:03 maiskolben kernel: BIOS-e820: [mem 
0x0010-0x3ffdcfff] usable
Sep 19 21:24:03 maiskolben kernel: BIOS-e820: [mem 
0x3ffdd000-0x3fff] reserved
Sep 19 21:24:03 maiskolben kernel: BIOS-e820: [mem 
0xfeffc000-0xfeff] reserved
Sep 19 21:24:03 maiskolben kernel: BIOS-e820: [mem 
0xfffc-0x] reserved
Sep 19 21:24:03 maiskolben kernel: NX (Execute Disable) protection: active
Sep 19 21:24:03 maiskolben kernel: SMBIOS 2.8 present.
Sep 19 21:24:03 maiskolben kernel: DMI: QEMU Standard PC (i440FX + PIIX, 1996), 
BIOS Debian-1.8.2-1 04/01/2014
Sep 19 21:24:03 maiskolben kernel: Hypervisor detected: KVM
Sep 19 21:24:03 maiskolben kernel: e820: update [mem 0x-0x0fff] 
usable ==> reserved
Sep 19 21:24:03 maiskolben kernel: e820: remove [mem 0x000a-0x000f] 
usable
Sep 19 21:24:03 maiskolben kernel: e820: last_pfn = 0x3ffdd max_arch_pfn = 
0x4
Sep 19 21:24:03 maiskolben kernel: MTRR default type: write-back
Sep 19 21:24:03 maiskolben kernel: MTRR fixed ranges enabled:
Sep 19 21:24:03 maiskolben kernel:   0-9 write-back
Sep 19 21:24:03 maiskolben kernel:   A-B uncachable
Sep 19 21:24:03 maiskolben kernel:   C-F write-protect
Sep 19 21:24:03 maiskolben kernel: MTRR variable ranges enabled:
Sep 19 21:24:03 maiskolben kernel:   0 base 008000 mask FF8000 
uncachable
Sep 19 21:24:03 maiskolben kernel:   1 disabled
Sep 19 21:24:03 maiskolben kernel:   2 disabled
Sep 19 21:24:03 maiskolben kernel:   3 disabled
Sep 19 21:24:03 maiskolben kernel:   4 disabled
Sep 19 21:24:03 maiskolben kernel:   5 disabled
Sep 19 21:24:03 maiskolben kernel:   6 disabled
Sep 19 21:24:03 maiskolben kernel:   7 disabled
Sep 19 21:24:03 maiskolben kernel: x86/PAT: PAT not supported by CPU.
Sep 19 21:24:03 maiskolben kernel: x86/PAT: Configuration [0-7]: WB  WT  UC- UC 
 WB  WT  UC- UC  
Sep 19 21:24:03 maiskolben kernel: found SMP MP-table at [mem 
0x000f6610-0x000f661f] mapped at [880f6610]
Sep 19 21:24:03 maiskolben kernel: Base memory trampoline at [88099000] 
99000 size 24576
Sep 19 21:24:03 maiskolben kernel: BRK [0x01c7a000, 0x01c7afff] PGTABLE
Sep 19 21:24:03 maiskolben kernel: BRK [0x01c7b000, 0x01c7bfff] PGTABLE
Sep 19 21:24:03 maiskolben kernel: BRK [0x01c7c000, 0x01c7cfff] PGTABLE
Sep 19 21:24:03 maiskolben kernel: BRK [0x01c7d000, 0x01c7dfff] PGTABLE
Sep 19 21:24:03 maiskolben kernel: RAMDISK: [mem 0x3f08c000-0x3ffc]
Sep 19 21:24:03 maiskolben kernel: ACPI: Early table checksum verification 
disabled
Sep 19 21:24:03 maiskolben kernel: ACPI: RSDP 0x000F6440 14 (v00 
BOCHS )
Sep 19 21:24:03 maiskolben kernel: ACPI: RSDT 0x3FFE1737 30 (v01 
BOCHS  BXPCRSDT 0001 BXPC 0001)
Sep 19 21:24:03 maiskolben kernel: ACPI: FACP 0x3FFE1613 74 (v01 
BOCHS  BXPCFACP 0001 BXPC 0001)
Sep 19 21:24:03 maiskolben kernel:

Bug#837759: network configuration stops working reliably

2016-09-19 Thread Martin Pitt 
Control: severity -1 important
Contro: tag -1 unreproducible

In accordance with the severity definitions [1] I downgrade this to
"important". It does not completely break systemd, we don't enable
networkd by default, and it does not affect every installation (it's
not reproducible on our side yet).

Don't worry, I'm still eager to find out what's happening here; I'll
look at your logs as soon as possible.

Martin

[1] https://www.debian.org/Bugs/Developer#severities

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processed: Re: Bug#837759: network configuration stops working reliably

2016-09-19 Thread Debian Bug Tracking System 
Processing control commands:

> severity -1 important
Bug #837759 [systemd] network configuration stops working reliably
Severity set to 'important' from 'grave'

-- 
837759: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#837759: network configuration stops working reliably

2016-09-19 Thread Martin Pitt 
Hello Wolfgang,

Wolfgang Walter [2016-09-14 23:34 +0200]:
> > > I tested this with a script:

FTR, I tried this as welll, and I cannot reproduce the bug either.

Wolfgang Walter [2016-09-14 17:56 +0200]:
> Yes, systemd-networkd ist active. But on most machines I only have *.link
> entries, usually one to name the device:

*.link entries are handled by udev, not networkd. So if you can
reproduce this on a machine with only has files like

> ==
> [Match]
> MACAddress=11:22:33:44:55:66
> 
> [Link]
> Name=net
> WakeOnLan=off
> ==

then can you please "systemctl disable --now systemd-networkd" and
check if the problem still happens? I suppose not, but if so, this
tells us that this is being done through udev.

If networkd itself is really the culprit, can you please try the
following:

 * Keep it disabled, run your test.sh to set up the dummy interface,
   and run

 SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd

  (as root). Does this now cause the addresses to be removed? This
  will run much later than test.sh, so this will tell us if this is a
  principal logic error or a race condition, i. e. only happens if
  networkd starts at the right time after test.sh.

 * Enable networkd again, and boot with "debug" in the kernel command
   line. Does this still reproduce the bug?

   If so, please attach the output of "journalctl -b".

   If not, just enable debugging for networkd with

   mkdir -p /etc/systemd/system/systemd-networkd.service.d/
   printf '[Service]\nEnvironment=SYSTEMD_LOG_LEVEL=debug' > 
/etc/systemd/system/systemd-networkd.service.d/debug.conf

   and reboot. If you catch the bug, please attach "journalctl -b".

Thanks,

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#837759: network configuration stops working reliably

2016-09-17 Thread Felipe Sateler 
On 15 September 2016 at 12:36, Felipe Sateler  wrote:
> On 14 September 2016 at 18:34, Wolfgang Walter  
> wrote:
>> On Wednesday, 14 September 2016 10:00:28 CEST Felipe Sateler wrote:
>>> Control: tags -1 moreinfo
>>>
>>> On 14 September 2016 at 06:59, Wolfgang Walter  
>>> wrote:
>>> > Package: systemd
>>> > Version: 231-6
>>> > Severity: grave
>>> >
>>> > Starting with version 231-6 the configuration of network interfaces stops
>>> > working reliably when rebooting a system. Downgrading to 231-5 fixes the
>>> > problem.
>>> >
>>> > Symptoms: If a network interface is configured using
>>> > /etc/network/interfaces it seems that systemd now sometimes removes the
>>> > configured ip4 and/or ipv6 addresses in the boot process. It also seems
>>> > to remove routes of network interfaces configured manually or with
>>> > /etc/network/interfaces if the link state changes.
>>> >
>>> > This seems not only be the case with interfaces configured via
>>> > /etc/network/ interfaces but with any interface one creates and assigns
>>> > ip addresses manually.
>>> >
>>> > I tested this with a script:
>>> >
>>> > #!/bin/sh
>>> > if [ "$1" = start ]; then
>>> > ip link del TEST >/dev/null 2>&1 || true
>>> > ip link add name TEST type dummy
>>> > ip -b - <<"EOF"
>>> > link set TEST up
>>> > addr add 10.10.10.10/32 dev TEST nodad
>>> > addr add 2a01:1:1:1::1/128 dev TEST nodad
>>> > addr add 2a01:1:1:1::2/128 dev TEST nodad
>>> > addr add 2a01:1:1:1::3/128 dev TEST nodad
>>> > addr add 2a01:1:1:1::4/128 dev TEST nodad
>>> > addr add 2a01:1:1:1::5/128 dev TEST nodad
>>> > EOF
>>> > ip addr ls TEST
>>> > sleep 2
>>> > elif [ "$1" = stop ]; then
>>> > ip addr flush dev TEST
>>> > ip link del TEST
>>> > fi
>>> >
>>> > which I start with as a systemd oneshot service with
>>> >
>>> > Before=systemd-networkd.service
>>> >
>>> > I can see in the journal that TEST has all adresses assigned but with
>>> > 231-6 it looses them again (probably when systemd-networkd.service
>>> > starts). With 231-5 or earlier this in not the case.
>>>
>>> It appears you are using systemd-networkd. Could you please attach
>>> your networkd configuration?
>>>
>>> Version 231-6 is built with iptables support, so that may be causing
>>> an interaction that was not visible before.
>>
>> I think this is the problem:
>>
>> https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=debian/231-6=79e10aaee1cdd412bd42f13f26e558ba1cd2196b
>>
>> I suppose is that the check for LINK_STATE_UNMANAGED may be racy.
>> The interface may go down and up before LINK_STATE_UNMANAGED is set.
>> Maybe the state is LINK_STATE_PENDING ?
>
> Interesting. Did you test with that patch disabled? (sorry, I have not
> had time to test).

BTW, I have tested manually on my system during runtime and cannot
reproduce. If this is a race maybe my laptop while idle managed to
configure faster than networkd managed to react.

-- 

Saludos,
Felipe Sateler

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#837759: network configuration stops working reliably

2016-09-15 Thread Felipe Sateler 
On 14 September 2016 at 18:34, Wolfgang Walter  wrote:
> On Wednesday, 14 September 2016 10:00:28 CEST Felipe Sateler wrote:
>> Control: tags -1 moreinfo
>>
>> On 14 September 2016 at 06:59, Wolfgang Walter  
>> wrote:
>> > Package: systemd
>> > Version: 231-6
>> > Severity: grave
>> >
>> > Starting with version 231-6 the configuration of network interfaces stops
>> > working reliably when rebooting a system. Downgrading to 231-5 fixes the
>> > problem.
>> >
>> > Symptoms: If a network interface is configured using
>> > /etc/network/interfaces it seems that systemd now sometimes removes the
>> > configured ip4 and/or ipv6 addresses in the boot process. It also seems
>> > to remove routes of network interfaces configured manually or with
>> > /etc/network/interfaces if the link state changes.
>> >
>> > This seems not only be the case with interfaces configured via
>> > /etc/network/ interfaces but with any interface one creates and assigns
>> > ip addresses manually.
>> >
>> > I tested this with a script:
>> >
>> > #!/bin/sh
>> > if [ "$1" = start ]; then
>> > ip link del TEST >/dev/null 2>&1 || true
>> > ip link add name TEST type dummy
>> > ip -b - <<"EOF"
>> > link set TEST up
>> > addr add 10.10.10.10/32 dev TEST nodad
>> > addr add 2a01:1:1:1::1/128 dev TEST nodad
>> > addr add 2a01:1:1:1::2/128 dev TEST nodad
>> > addr add 2a01:1:1:1::3/128 dev TEST nodad
>> > addr add 2a01:1:1:1::4/128 dev TEST nodad
>> > addr add 2a01:1:1:1::5/128 dev TEST nodad
>> > EOF
>> > ip addr ls TEST
>> > sleep 2
>> > elif [ "$1" = stop ]; then
>> > ip addr flush dev TEST
>> > ip link del TEST
>> > fi
>> >
>> > which I start with as a systemd oneshot service with
>> >
>> > Before=systemd-networkd.service
>> >
>> > I can see in the journal that TEST has all adresses assigned but with
>> > 231-6 it looses them again (probably when systemd-networkd.service
>> > starts). With 231-5 or earlier this in not the case.
>>
>> It appears you are using systemd-networkd. Could you please attach
>> your networkd configuration?
>>
>> Version 231-6 is built with iptables support, so that may be causing
>> an interaction that was not visible before.
>
> I think this is the problem:
>
> https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=debian/231-6=79e10aaee1cdd412bd42f13f26e558ba1cd2196b
>
> I suppose is that the check for LINK_STATE_UNMANAGED may be racy.
> The interface may go down and up before LINK_STATE_UNMANAGED is set.
> Maybe the state is LINK_STATE_PENDING ?

Interesting. Did you test with that patch disabled? (sorry, I have not
had time to test).

-- 

Saludos,
Felipe Sateler

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#837759: network configuration stops working reliably

2016-09-14 Thread Wolfgang Walter 
On Wednesday, 14 September 2016 10:00:28 CEST Felipe Sateler wrote:
> Control: tags -1 moreinfo
> 
> On 14 September 2016 at 06:59, Wolfgang Walter  
> wrote:
> > Package: systemd
> > Version: 231-6
> > Severity: grave
> > 
> > Starting with version 231-6 the configuration of network interfaces stops
> > working reliably when rebooting a system. Downgrading to 231-5 fixes the
> > problem.
> > 
> > Symptoms: If a network interface is configured using
> > /etc/network/interfaces it seems that systemd now sometimes removes the
> > configured ip4 and/or ipv6 addresses in the boot process. It also seems
> > to remove routes of network interfaces configured manually or with
> > /etc/network/interfaces if the link state changes.
> > 
> > This seems not only be the case with interfaces configured via
> > /etc/network/ interfaces but with any interface one creates and assigns
> > ip addresses manually.
> > 
> > I tested this with a script:
> > 
> > #!/bin/sh
> > if [ "$1" = start ]; then
> > ip link del TEST >/dev/null 2>&1 || true
> > ip link add name TEST type dummy
> > ip -b - <<"EOF"
> > link set TEST up
> > addr add 10.10.10.10/32 dev TEST nodad
> > addr add 2a01:1:1:1::1/128 dev TEST nodad
> > addr add 2a01:1:1:1::2/128 dev TEST nodad
> > addr add 2a01:1:1:1::3/128 dev TEST nodad
> > addr add 2a01:1:1:1::4/128 dev TEST nodad
> > addr add 2a01:1:1:1::5/128 dev TEST nodad
> > EOF
> > ip addr ls TEST
> > sleep 2
> > elif [ "$1" = stop ]; then
> > ip addr flush dev TEST
> > ip link del TEST
> > fi
> > 
> > which I start with as a systemd oneshot service with
> > 
> > Before=systemd-networkd.service
> > 
> > I can see in the journal that TEST has all adresses assigned but with
> > 231-6 it looses them again (probably when systemd-networkd.service
> > starts). With 231-5 or earlier this in not the case.
> 
> It appears you are using systemd-networkd. Could you please attach
> your networkd configuration?
> 
> Version 231-6 is built with iptables support, so that may be causing
> an interaction that was not visible before.

I think this is the problem:

https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=debian/231-6=79e10aaee1cdd412bd42f13f26e558ba1cd2196b

I suppose is that the check for LINK_STATE_UNMANAGED may be racy. The interface 
may go down and up before LINK_STATE_UNMANAGED is set. Maybe the state is 
LINK_STATE_PENDING ?

Regards,
-- 
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#837759: network configuration stops working reliably

2016-09-14 Thread Wolfgang Walter 
Am Mittwoch, 14. September 2016, 10:00:28 schrieben Sie:

> Control: tags -1 moreinfo
> 
> On 14 September 2016 at 06:59, Wolfgang Walter  
wrote:

> > Package: systemd
> > Version: 231-6
> > Severity: grave
> > 
> > Starting with version 231-6 the configuration of network interfaces stops
> > working reliably when rebooting a system. Downgrading to 231-5 fixes the
> > problem.
> > 
> > Symptoms: If a network interface is configured using
> > /etc/network/interfaces it seems that systemd now sometimes removes the
> > configured ip4 and/or ipv6 addresses in the boot process. It also seems
> > to remove routes of network interfaces configured manually or with
> > /etc/network/interfaces if the link state changes.
> > 
> > This seems not only be the case with interfaces configured via
> > /etc/network/ interfaces but with any interface one creates and assigns
> > ip addresses manually.
> > 
> > I tested this with a script:
> > 
> > #!/bin/sh
> > if [ "$1" = start ]; then
> > ip link del TEST >/dev/null 2>&1 || true
> > ip link add name TEST type dummy
> > ip -b - <<"EOF"
> > link set TEST up
> > addr add 10.10.10.10/32 dev TEST nodad
> > addr add 2a01:1:1:1::1/128 dev TEST nodad
> > addr add 2a01:1:1:1::2/128 dev TEST nodad
> > addr add 2a01:1:1:1::3/128 dev TEST nodad
> > addr add 2a01:1:1:1::4/128 dev TEST nodad
> > addr add 2a01:1:1:1::5/128 dev TEST nodad
> > EOF
> > ip addr ls TEST
> > sleep 2
> > elif [ "$1" = stop ]; then
> > ip addr flush dev TEST
> > ip link del TEST
> > fi
> > 
> > which I start with as a systemd oneshot service with
> > 
> > Before=systemd-networkd.service
> > 
> > I can see in the journal that TEST has all adresses assigned but with
> > 231-6 it looses them again (probably when systemd-networkd.service
> > starts). With 231-5 or earlier this in not the case.

> 
> It appears you are using systemd-networkd. Could you please attach
> your networkd configuration?

Yes, systemd-networkd ist active. But on most machines I only have *.link 
entries, usually one to name the device:

==
[Match]
MACAddress=11:22:33:44:55:66

[Link]
Name=net
WakeOnLan=off
==

Most of them are virtual machines.


On those machine where I also habe *.netdev and *.network entries this also 
happens. The one with the simpliest has only one *.network:

==
[Match]
Name=net

[Network]
LinkLocalAddressing=ipv6
IPv6AcceptRouterAdvertisements=no
DHCP=no
Address=10.11.12.13/24
Gateway=10.11.12.1
Address=2001:1234:1::abc1
Address=2001:1234:1::abc2
Address=2001:1234:1::abc3
Address=2001:1234:1::abc4
NTP=2001:1234:1::123

[Route]
Gateway=fe80::1
PreferredSource=2001:1234:1::abc1
==

This interface works fine. But other interfaces configured by 
/etc/network/interfaces or the manually created interface TEST loose there 
ipv4 and ipv6 addresses.

Please note, that I did not create a *.link entry for TEST on any of the 
machines. 


If I later restart these interfaces (with ifdown + ifup for 
/etc/network/interfaces, systemctl restart test-network-device.service for 
TEST) they keep their addresses.



> 
> Version 231-6 is built with iptables support, so that may be causing
> an interaction that was not visible before.

Regards,
-- 
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#837759: network configuration stops working reliably

2016-09-14 Thread Felipe Sateler 
Control: tags -1 moreinfo

On 14 September 2016 at 06:59, Wolfgang Walter  wrote:
> Package: systemd
> Version: 231-6
> Severity: grave
>
> Starting with version 231-6 the configuration of network interfaces stops
> working reliably when rebooting a system. Downgrading to 231-5 fixes the
> problem.
>
> Symptoms: If a network interface is configured using /etc/network/interfaces
> it seems that systemd now sometimes removes the configured ip4 and/or ipv6
> addresses in the boot process. It also seems to remove routes of network
> interfaces configured manually or with /etc/network/interfaces if the link
> state changes.
>
> This seems not only be the case with interfaces configured via /etc/network/
> interfaces but with any interface one creates and assigns ip addresses
> manually.
>
> I tested this with a script:
>
> #!/bin/sh
> if [ "$1" = start ]; then
> ip link del TEST >/dev/null 2>&1 || true
> ip link add name TEST type dummy
> ip -b - <<"EOF"
> link set TEST up
> addr add 10.10.10.10/32 dev TEST nodad
> addr add 2a01:1:1:1::1/128 dev TEST nodad
> addr add 2a01:1:1:1::2/128 dev TEST nodad
> addr add 2a01:1:1:1::3/128 dev TEST nodad
> addr add 2a01:1:1:1::4/128 dev TEST nodad
> addr add 2a01:1:1:1::5/128 dev TEST nodad
> EOF
> ip addr ls TEST
> sleep 2
> elif [ "$1" = stop ]; then
> ip addr flush dev TEST
> ip link del TEST
> fi
>
> which I start with as a systemd oneshot service with
> Before=systemd-networkd.service
>
> I can see in the journal that TEST has all adresses assigned but with 231-6 it
> looses them again (probably when systemd-networkd.service starts). With 231-5
> or earlier this in not the case.

It appears you are using systemd-networkd. Could you please attach
your networkd configuration?

Version 231-6 is built with iptables support, so that may be causing
an interaction that was not visible before.

-- 

Saludos,
Felipe Sateler

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processed: Re: Bug#837759: network configuration stops working reliably

2016-09-14 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 moreinfo
Bug #837759 [systemd] network configuration stops working reliably
Added tag(s) moreinfo.

-- 
837759: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#837759: network configuration stops working reliably

2016-09-14 Thread Wolfgang Walter 
Package: systemd
Version: 231-6
Severity: grave

Starting with version 231-6 the configuration of network interfaces stops 
working reliably when rebooting a system. Downgrading to 231-5 fixes the 
problem.

Symptoms: If a network interface is configured using /etc/network/interfaces 
it seems that systemd now sometimes removes the configured ip4 and/or ipv6 
addresses in the boot process. It also seems to remove routes of network 
interfaces configured manually or with /etc/network/interfaces if the link 
state changes.

This seems not only be the case with interfaces configured via /etc/network/
interfaces but with any interface one creates and assigns ip addresses 
manually.

I tested this with a script:

#!/bin/sh
if [ "$1" = start ]; then
ip link del TEST >/dev/null 2>&1 || true
ip link add name TEST type dummy
ip -b - <<"EOF"
link set TEST up
addr add 10.10.10.10/32 dev TEST nodad
addr add 2a01:1:1:1::1/128 dev TEST nodad
addr add 2a01:1:1:1::2/128 dev TEST nodad
addr add 2a01:1:1:1::3/128 dev TEST nodad
addr add 2a01:1:1:1::4/128 dev TEST nodad
addr add 2a01:1:1:1::5/128 dev TEST nodad
EOF
ip addr ls TEST
sleep 2
elif [ "$1" = stop ]; then
ip addr flush dev TEST
ip link del TEST
fi

which I start with as a systemd oneshot service with
Before=systemd-networkd.service

I can see in the journal that TEST has all adresses assigned but with 231-6 it 
looses them again (probably when systemd-networkd.service starts). With 231-5 
or earlier this in not the case.


Regards,
-- 
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers