Hi,

Something strange with the netlink messages which are sent if 'modprobe -r dummy' is run while the dummy device is UP. The following commands:

# modprobe dummy0
# ip li set dev dummy0 up
# modprobe -r dummy0
# modprobe dummy0
# ip li set dev dummy0 up
# modprobe -r dummy0

Produce:

ZEBRA: netlink_parse_info: netlink-listen type RTM_NEWLINK(16), seq=0, pid=29001
ZEBRA: netlink_parse_info: netlink-listen type RTM_NEWLINK(16), seq=0, pid=29001
ZEBRA: netlink_parse_info: netlink-listen type RTM_DELLINK(17), seq=0, pid=29001
ZEBRA: interface dummy0 index 86 is now inactive.
ZEBRA: netlink_parse_info: netlink-listen type RTM_NEWLINK(16), seq=0, pid=29001
ZEBRA: interface dummy0 index 86 becomes active.

The NEWLINK for the UP->DOWN flags change is sent /after/ the DELLINK, which obviously is a problem - we don't know the NEWLINK refers to a deleted interface. 'ip monitor' does print out the messages in the right order though:

86: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop
    link/ether 46:cc:76:33:44:2d brd ff:ff:ff:ff:ff:ff
86: dummy0: <BROADCAST,NOARP,UP> mtu 1500 qdisc noqueue
    link/ether 46:cc:76:33:44:2d brd ff:ff:ff:ff:ff:ff
86: dummy0: <BROADCAST,NOARP,UP> mtu 1500 qdisc noqueue
    link/ether 46:cc:76:33:44:2d brd ff:ff:ff:ff:ff:ff
86: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noqueue
    link/ether 46:cc:76:33:44:2d brd ff:ff:ff:ff:ff:ff
Deleted 86: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop
    link/ether 46:cc:76:33:44:2d brd ff:ff:ff:ff:ff:ff

Not sure how it manages this.

I havn't tested yet whether this is specific to the dummy device, or devices in general. If general, it's a problem - what's the correct way to tell the NEWLINK is 'stale'? (please don't say by ifindex :) ).

regards,
--
Paul Jakma      [EMAIL PROTECTED]       [EMAIL PROTECTED]       Key ID: 64A2FF6A
Fortune:
The road to ruin is always in good repair, and the travellers pay the
expense of it.
                -- Josh Billings
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to