Re: [systemd-devel] unable to create bridge name "default"

2017-04-27 Thread William Tu
On Thu, Mar 30, 2017 at 8:55 AM, Lennart Poettering
 wrote:
> On Sat, 11.03.17 08:41, William Tu (u9012...@gmail.com) wrote:
>
>> Hi,
>> I'm not sure if this is caused by systemd-udev, apology if it's not
>> the right place. When doing
>> # brctl addbr default
>> add bridge failed: Invalid argument
>
> If brctl fails with EINVAL, then this suggests that the kernel refuses
> this already, and udev is not involved. Please ping the
> bridging/networking community.
>
> Lennart
>
> --
> Lennart Poettering, Red Hat

Hi Lennart,
Thanks for your reply. I've found out that it is indeed kernel refuses
"default" name of the netdev. By executing "brctl addbr default" and
tracing the kernel source, it shows "default" isn't allowed in one of
the netdev notifier, a call stack is below if anyone is interested:
  sysctl_dev_name_is_allowed
devinet_sysctl_register
  inetdev_event
notifier_call_chain
  raw_notifier_call_chain
call_netdevice_notifiers_info
  register_netdevice
register_netdev
  br_add_bridge

Regards,
William
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] unable to create bridge name "default"

2017-03-30 Thread Lennart Poettering
On Sat, 11.03.17 08:41, William Tu (u9012...@gmail.com) wrote:

> Hi,
> I'm not sure if this is caused by systemd-udev, apology if it's not
> the right place. When doing
> # brctl addbr default
> add bridge failed: Invalid argument

If brctl fails with EINVAL, then this suggests that the kernel refuses
this already, and udev is not involved. Please ping the
bridging/networking community.

Lennart

-- 
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


[systemd-devel] unable to create bridge name "default"

2017-03-11 Thread William Tu
Hi,
I'm not sure if this is caused by systemd-udev, apology if it's not
the right place. When doing
# brctl addbr default
add bridge failed: Invalid argument
or
# ip link add name default type bridge

Debugging with
# systemd-udev --debug

I think the bridge "default" is created successfully first, then
somehow get remove immediately after it gets created. Is this related
to systemd disallow using "default" as device name? Thanks

--William

the systemd-udev log is below
seq 8872 queued, 'add' 'net'
Validate module index
Check if link configuration needs reloading.
seq 8872 forked new worker [7466]
seq 8873 queued, 'add' 'queues'
seq 8874 queued, 'add' 'queues'
seq 8875 queued, 'remove' 'queues'
seq 8876 queued, 'remove' 'queues'
seq 8872 runningseq 8877 queued, 'remove' 'net'

RUN 'bridge-network-interface'
/lib/udev/rules.d/40-bridge-network-interface.rules:1
value '[dmi/id]sys_vendor' is 'Dell Inc.'
value '[dmi/id]sys_vendor' is 'Dell Inc.'
RUN 'vlan-network-interface' /lib/udev/rules.d/60-vlan-network-interface.rules:1
RUN '/lib/open-iscsi/net-interface-handler start'
/lib/udev/rules.d/70-iscsi-network-interface.rules:2
IMPORT builtin 'net_id' /lib/udev/rules.d/75-net-description.rules:6
IMPORT builtin 'net_id' returned non-zero
RUN 'ifupdown-hotplug' /lib/udev/rules.d/80-ifupdown.rules:5
IMPORT builtin 'path_id' /lib/udev/rules.d/80-net-setup-link.rules:5
IMPORT builtin 'path_id' returned non-zero
IMPORT builtin 'net_setup_link' /lib/udev/rules.d/80-net-setup-link.rules:9
Assertion 'udev_device' failed at ../src/libudev/libudev-device.c:128,
function udev_device_get_driver(). Ignoring.
Config file /lib/systemd/network/99-default.link applies to device default
RUN '/lib/systemd/systemd-sysctl --prefix=/net/ipv4/conf/$name
--prefix=/net/ipv4/neigh/$name --prefix=/net/ipv6/conf/$name
--prefix=/net/ipv6/neigh/$name' /lib/udev/rules.d/99-systemd.rules:51
created db file '/run/udev/data/n303' for '/devices/virtual/net/default'
starting 'bridge-network-interface'
Process 'bridge-network-interface' succeeded.
starting 'vlan-network-interface'
Process 'vlan-network-interface' succeeded.
starting '/lib/open-iscsi/net-interface-handler start'
Process '/lib/open-iscsi/net-interface-handler start' succeeded.
starting 'ifupdown-hotplug'
Process 'ifupdown-hotplug' succeeded.
starting '/lib/systemd/systemd-sysctl --prefix=/net/ipv4/conf/default
--prefix=/net/ipv4/neigh/default --prefix=/net/ipv6/conf/default
--prefix=/net/ipv6/neigh/default'
Process '/lib/systemd/systemd-sysctl --prefix=/net/ipv4/conf/default
--prefix=/net/ipv4/neigh/default --prefix=/net/ipv6/conf/default
--prefix=/net/ipv6/neigh/default' succeeded.
passed device to netlink monitor 0x56514ed418b0
seq 8872 processed
passed 159 byte device to netlink monitor 0x56514ed3b0f0
seq 8873 running
value '[dmi/id]sys_vendor' is 'Dell Inc.'
seq 8874 forked new worker [7531]
value '[dmi/id]sys_vendor' is 'Dell Inc.'
passed device to netlink monitor 0x56514ed418b0
seq 8873 processed
passed 162 byte device to netlink monitor 0x56514ed3b0f0
seq 8875 running
seq 8874 running
value '[dmi/id]sys_vendor' is 'Dell Inc.'
value '[dmi/id]sys_vendor' is 'Dell Inc.'
passed device to netlink monitor 0x56514ed418b0
seq 8875 processed
value '[dmi/id]sys_vendor' is 'Dell Inc.'
value '[dmi/id]sys_vendor' is 'Dell Inc.'
passed device to netlink monitor 0x56514ed39a50
seq 8874 processed
passed 162 byte device to netlink monitor 0x56514ed3b0f0
seq 8876 running
value '[dmi/id]sys_vendor' is 'Dell Inc.'
value '[dmi/id]sys_vendor' is 'Dell Inc.'
passed device to netlink monitor 0x56514ed418b0
seq 8876 processed
passed 192 byte device to netlink monitor 0x56514ed3b0f0
seq 8877 running
value '[dmi/id]sys_vendor' is 'Dell Inc.'
value '[dmi/id]sys_vendor' is 'Dell Inc.'
RUN '/lib/open-iscsi/net-interface-handler stop'
/lib/udev/rules.d/70-iscsi-network-interface.rules:3
RUN 'ifupdown-hotplug' /lib/udev/rules.d/80-ifupdown.rules:5
IMPORT builtin 'path_id' /lib/udev/rules.d/80-net-setup-link.rules:5
IMPORT builtin 'path_id' returned non-zero
starting '/lib/open-iscsi/net-interface-handler stop'
Process '/lib/open-iscsi/net-interface-handler stop' succeeded.
starting 'ifupdown-hotplug'
Process 'ifupdown-hotplug' succeeded.
passed device to netlink monitor 0x56514ed418b0
seq 8877 processed
cleanup idle workers
Unload module index
Unload module index
Unloaded link configuration context.
Unloaded link configuration context.
worker [7466] exited
worker [7531] exited
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel