Re: [PATCH net-next v5 00/11] ipv6: Only create RTF_CACHE route after encountering pmtu exception

2015-08-28 Thread Alexander Holler
Am 28.08.2015 um 09:36 schrieb Martin KaFai Lau: On Mon, Aug 17, 2015 at 11:43:20AM +0200, Alexander Holler wrote: That's why I vote to check out if it's possible/reasonable to backport this series to the stable kernels. I have backported to 4.0.y without major issue, so possible. Sure

Re: [PATCH net-next v5 00/11] ipv6: Only create RTF_CACHE route after encountering pmtu exception

2015-08-28 Thread Alexander Holler
Am 28.08.2015 um 11:27 schrieb Alexander Holler: Am 28.08.2015 um 09:36 schrieb Martin KaFai Lau: On Mon, Aug 17, 2015 at 11:43:20AM +0200, Alexander Holler wrote: That's why I vote to check out if it's possible/reasonable to backport this series to the stable kernels. I have backported

Re: [PATCH net-next v5 00/11] ipv6: Only create RTF_CACHE route after encountering pmtu exception

2015-08-17 Thread Alexander Holler
Am 15.08.2015 um 09:48 schrieb Alexander Holler: Am 30.07.2015 um 13:57 schrieb Alexander Holler: Am 29.07.2015 um 11:25 schrieb Alexander Holler: Am 23.05.2015 um 05:55 schrieb Martin KaFai Lau: To complete the discussion, that annoying behaviour is also a big information leak. Because

Re: [PATCH net-next v5 00/11] ipv6: Only create RTF_CACHE route after encountering pmtu exception

2015-08-15 Thread Alexander Holler
Am 30.07.2015 um 13:57 schrieb Alexander Holler: Am 29.07.2015 um 11:25 schrieb Alexander Holler: Am 23.05.2015 um 05:55 schrieb Martin KaFai Lau: This series is to avoid creating a RTF_CACHE route whenever we are consulting the fib6 tree with a new destination. Instead, only create

Re: [PATCH net-next v5 00/11] ipv6: Only create RTF_CACHE route after encountering pmtu exception

2015-07-30 Thread Alexander Holler
Am 29.07.2015 um 11:25 schrieb Alexander Holler: Am 23.05.2015 um 05:55 schrieb Martin KaFai Lau: This series is to avoid creating a RTF_CACHE route whenever we are consulting the fib6 tree with a new destination. Instead, only create RTF_CACHE route when we see a pmtu exception. That even

Re: [PATCH net-next v5 00/11] ipv6: Only create RTF_CACHE route after encountering pmtu exception

2015-07-29 Thread Alexander Holler
to world because it avoids the IPv6 route add/delete pairs which happened before whenever an IPv6-connection was tried (e.g. by Happy Eyeballs algorithms). I think that's worse a laud. thanks. Alexander Holler -- To unsubscribe from this list: send the line unsubscribe netdev in the body

Re: [PATCH net-next v2 0/7] netns: ease netlink use with a lot of netns

2015-05-28 Thread Alexander Holler
Am 26.05.2015 um 16:36 schrieb Alexander Holler: Am 26.05.2015 um 14:10 schrieb Nicolas Dichtel: I don't understand why dumping in another netns is a problem. It isn't. I just wondered how you (or someone else) is using NETLINK_LISTEN_ALL_NSID, assuming it already serves a purpose. ;) Maybe

Re: [PATCH net-next v2 0/7] netns: ease netlink use with a lot of netns

2015-05-26 Thread Alexander Holler
Am 25.05.2015 um 15:09 schrieb Nicolas Dichtel: Le 25/05/2015 12:55, Alexander Holler a écrit : Am 25.05.2015 um 09:45 schrieb Nicolas Dichtel: Le 22/05/2015 22:50, Alexander Holler a écrit : First I think if NETLINK_LISTEN_ALL_NSID is enabled, a dump of the interfaces through RTM_GETLINK

Re: [PATCH net-next v2 0/7] netns: ease netlink use with a lot of netns

2015-05-26 Thread Alexander Holler
Am 26.05.2015 um 14:10 schrieb Nicolas Dichtel: Le 26/05/2015 12:53, Alexander Holler a écrit : Am 25.05.2015 um 15:09 schrieb Nicolas Dichtel: [snip] Hmm, sounds like we're talking in different rooms about the same thing in regard to the dump. ;) I just wanted to explain why I think

Re: [PATCH net-next v2 0/7] netns: ease netlink use with a lot of netns

2015-05-25 Thread Alexander Holler
Am 25.05.2015 um 09:45 schrieb Nicolas Dichtel: Le 22/05/2015 22:50, Alexander Holler a écrit : First I think if NETLINK_LISTEN_ALL_NSID is enabled, a dump of the interfaces through RTM_GETLINK together with NLM_F_DUMP and NLM_F_REQUEST should return all interfaces of all reachable namespaces

Re: [PATCH net-next v2 0/7] netns: ease netlink use with a lot of netns

2015-05-22 Thread Alexander Holler
, or there still is some work todo to make NETLINK_LISTEN_ALL_NSID work like expected (or like my simple mind would expect it). Thanks again for the patches, regards, Alexander Holler -- To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to majord

Re: [PATCH net-next v2 0/7] netns: ease netlink use with a lot of netns

2015-05-22 Thread Alexander Holler
Am 22.05.2015 um 23:19 schrieb Eric W. Biederman: Alexander Holler hol...@ahsoftware.de writes: Am 08.05.2015 um 14:02 schrieb Eric W. Biederman: So I am dense. I have read through the patches and I don't see where you tag packets from other network namespaces with a network namespace id

Re: [PATCH net-next v2 0/7] netns: ease netlink use with a lot of netns

2015-05-22 Thread Alexander Holler
Am 22.05.2015 um 23:29 schrieb Cong Wang: On Fri, May 22, 2015 at 2:12 PM, Alexander Holler hol...@ahsoftware.de wrote: Bridge doesn't have an underlying link, so no LINK_NETNSID. LINK_NETNSID is only added when its underlying link is in a different netns. I'm using link similiar

Re: [PATCH net-next v2 0/7] netns: ease netlink use with a lot of netns

2015-05-22 Thread Alexander Holler
Am 22.05.2015 um 23:04 schrieb Cong Wang: On Fri, May 22, 2015 at 1:50 PM, Alexander Holler hol...@ahsoftware.de wrote: Am 08.05.2015 um 14:02 schrieb Eric W. Biederman: So I am dense. I have read through the patches and I don't see where you tag packets from other network namespaces