| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sun, 15 Jul 2007 17:07:26 +0200 From: Patrick McHardy <kaber@...sh.net> To: bugzilla@...e.lp0.eu CC: Andrew Morton <akpm@...ux-foundation.org>, netdev@...r.kernel.org, "bugme-daemon@...nel-bugs.osdl.org" <bugme-daemon@...nel-bugs.osdl.org> Subject: Re: [Bugme-new] [Bug 8755] New: "ip -6 route change " behaves like "ip -6 route add" Andrew Morton wrote: > On Sat, 14 Jul 2007 15:21:21 -0700 (PDT) bugme-daemon@...zilla.kernel.org wrote: > >>The "ip -6 route change" command behaves as though "ip -6 route add" was used. >>The source of iproute2 shows that "change" uses the "NLM_F_REPLACE" netlink >>flag only. >> >>ip utility, iproute2-ss070313 >> >>Changing an existing route: >># ip -6 r show 2002::/16 >>2002::/16 dev sit0 metric 1024 expires 4482618sec mtu 1480 advmss 7140 >>hoplimit 4294967295 >># ip -6 r change 2002::/16 dev sit0 mtu 1280 >>RTNETLINK answers: File exists >> >>Adding a route using "change": >># ip -6 r change 2002::/17 dev sit0 mtu 1280 >># ip -6 r show 2002::/17 >>2002::/17 dev sit0 metric 1024 expires 21334368sec mtu 1280 advmss 1220 >>hoplimit 4294967295 There is a difference between "add" and "change". "add" will only add a new address if there isn't already one with the same identity, "change" will allow to change attributes of an existing address, like flags, lifetime, ..., or behave similar to "add" in case the address doesn't already exist. What kind of behaviour are you expecting? - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists