On Fri, 20 Jan 2012 05:12:33 -0500 nick black <[email protected]> wrote:
> Package: iproute > Version: 20120105-1 > Severity: normal > > Dear Maintainer, > > "ip l" started failing a few weeks ago: > > [skynet](0) $ ip -o l > RTNETLINK answers: No such file or directory > Error talking to the kernel > [skynet](1) $ > > oddly enough, "ip link" operates as expected: > > [skynet](1) $ ip -o link > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN \ > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > 2: eth0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq state UP > qlen 1000\ link/ether 00:25:22:bc:b1:00 brd ff:ff:ff:ff:ff:ff > 3: e100: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000\ > link/ether 00:07:e9:09:c5:23 brd ff:ff:ff:ff:ff:ff > 4: irda0: <NOARP,PROMISC,UP,LOWER_UP> mtu 2048 qdisc pfifo_fast state UNKNOWN > qlen 8\ link/irda c3:20:b8:be brd ff:ff:ff:ff > 5: wlan1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast > state UP qlen 1000\ link/ether 00:c0:ca:4f:e3:b2 brd ff:ff:ff:ff:ff:ff > 6: tap0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast > state UNKNOWN qlen 100\ link/ether c6:34:c1:4a:ff:54 brd ff:ff:ff:ff:ff:ff > [skynet](0) $ > > The failure seemed to be concurrent with the replacement of libnl-3 with > libnl-3-200, though the current ip(8) doesn't appear to be linked to libnl at > all. Perhaps the old one was? Regardless, "ip l" used to work exactly link "ip > link". Note that "ip a", for instance, works like "ip addr". > The command 'ip l' is now ambiguous. The addition of l2tp support added: ip l2tp ... which overlaps 'ip link' -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
