| 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
| ||
|
Message-ID: <55C1D207.3040905@iogearbox.net> Date: Wed, 05 Aug 2015 11:06:15 +0200 From: Daniel Borkmann <daniel@...earbox.net> To: Zang MingJie <zealot0630@...il.com> CC: linux-kernel@...r.kernel.org, netdev@...r.kernel.org Subject: Re: [BUG] net/ipv4: inconsistent routing table [ please cc netdev ] On 08/05/2015 10:56 AM, Zang MingJie wrote: > Hi: > > I found a bug when remove an ip address which is referenced by a routing entry. > > step to reproduce: > > ip li add type dummy > ip li set dummy0 up > ip ad add 10.0.0.1/24 dev dummy0 > ip ad add 10.0.0.2/24 dev dummy0 > ip ro add default via 10.0.0.2/24 > ip ad del 10.0.0.2/24 dev dummy0 > > after deleting the secondary ip address, the routing entry still > pointing to 10.0.0.2 > > # ip ro > default via 10.0.0.2 dev dummy0 > 10.0.0.0/24 dev dummy0 proto kernel scope link src 10.0.0.1 > > but actually, kernel considers the default route is directly connected. > > # ip ro get 1.1.1.1 > 1.1.1.1 dev dummy0 src 10.0.0.1 > cache > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@...r.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists