On Mon, Sep 10, 2018 at 11:55 AM, Stephen Hemminger <step...@networkplumber.org> wrote: > > > Begin forwarded message: > > Date: Mon, 10 Sep 2018 04:04:37 +0000 > From: bugzilla-dae...@bugzilla.kernel.org > To: step...@networkplumber.org > Subject: [Bug 201071] New: Creating a vxlan in state 'up' does not give > proper RTM_NEWLINK message > > > https://bugzilla.kernel.org/show_bug.cgi?id=201071 > > Bug ID: 201071 > Summary: Creating a vxlan in state 'up' does not give proper > RTM_NEWLINK message > Product: Networking > Version: 2.5 > Kernel Version: 4.19-rc1 > Hardware: All > OS: Linux > Tree: Mainline > Status: NEW > Severity: normal > Priority: P1 > Component: Other > Assignee: step...@networkplumber.org > Reporter: liam.mcbir...@boeing.com > Regression: Yes > > If a vxlan is created with state 'up', the RTM_NEWLINK message shows the state > as down, and there no other netlink messages are sent. > As a result, processes listening to netlink are never notified that the vxlan > link is up.
thanks for the fwd. looking... > > eg. > # ip link add test up type vxlan id 8 group 224.224.224.224 dev eth0 > > Output of ip monitor link > # 4: test: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN group default > link/ether ee:cd:97:1a:cf:91 brd ff:ff:ff:ff:ff:ff > > Output of ip link show (expected from netlink message) > # 4: test: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state > UNKNOWN group default qlen 1000 > link/ether ee:cd:97:1a:cf:91 brd ff:ff:ff:ff:ff:ff > > This is a regression introduced by the following patch series. > https://patchwork.ozlabs.org/patch/947181/ > > -- > You are receiving this mail because: > You are the assignee for the bug.
