Some time ago IPv6 tunnelbroker I manage started to behave strangely.
Loosing neighbors, packet loss, attempt to load ip6_tables module failed
with message "Cannot allocate memory". I discovered that number of tunnels
is problem. When problems apeared, there was 513 tunnels. I reduced number
of tunnels and problems disappeared. Of course it was temporary only.
At first I thought that it's related to size of IPv6 routing table, but
changing /proc/sys/net/ipv6/route/max_size didn't make any difference.
I can reproduce problem on my desktop and laptop as well (tested with
2.4.29-rc1 and 2.6.10 kernels) with attached script. When I run this, about
500 tunnels work fine, but for the rest there will be address added on
tunnel, but not route to the interface for this address (adding route to the
neighbor fails therefore too). About same time neighbors in LAN stop
answering (ping6 -I eth0 ff02::1, only ::1 will answer). Removing tunnels
makes all work again. I tried with vlans as well and can reproduce same
problem, although for some reason number of vlans have to be bigger.
I'm hitting some IPv6 related limit in kernel probably. Is it known limit?
Is there way to change this limit or is there workaround?
--
Hasso Tepper
Elion Enterprises Ltd.
WAN administrator
tunnels.sh
Description: application/shellscript
|