Linux IPv6 routing strange behaviour

Ivan Pepelnjak ipepelnjak at gmail.com
Thu Aug 15 13:54:41 CEST 2013


Because it's faster.

http://blog.erratasec.com/2013/02/custom-stack-it-goes-to-11.html

A few more juicy Unix comments here:

http://blog.erratasec.com/2013/02/unlearning-college.html

Enjoy!
Ivan

-----Original Message-----
From: ipv6-ops-bounces+ipepelnjak=gmail.com at lists.cluenet.de
[mailto:ipv6-ops-bounces+ipepelnjak=gmail.com at lists.cluenet.de] On Behalf Of
Max Tulyev
Sent: Thursday, August 15, 2013 1:36 PM
To: ipv6-ops at lists.cluenet.de
Subject: Re: Linux IPv6 routing strange behaviour

If so - things are much worse than I afraid...

The only question is why to implement user space routing instead of fixing
the kernel code?

On 15.08.13 14:14, Pim van Pelt wrote:
> Just ad a datapoint to Max' last remark, at sixxs we moved away from 
> kernel based routing by implementing ipv6 routing in userspace (taking 
> tap input and raw socket output) largely because of neighbor cache 
> pollution and a streak of crashes when we started scaling beyond say
> 2000 interfaces.



More information about the ipv6-ops mailing list