havior still by design? I'm not happy about this because if the link-local address is removed, it can't be added easily anymore. "howto": 3: eth1: <BROADCAST,M
we can figure out whether this is necessary or not. -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx> Ho
Getting back to an ooooold thread... As far as I can see (please correct me) no such patch was included so far, at least with 2.6.10-rc3 I still have the old behaviour. Could you please include the p
This specific issue was not resolved, but the issue of loading the ipv6 module after bringing up your interfaces was fixed via this patch below. I've also discussed this with Herbert Xu a bit, and no
Well I still reckon that the IPv4 behaviour is just fine as it is. In fact if anything we should make the IPv6 case as similar to Ipv4 as possible. Cheers, -- Visit Openswan at http://www.openswan.or
Hi! I'm experiencing some strange problems on a 2.6.8.1 vanilla kernel. I tried to reproduce it with a minimal system: 1) address configuration (just loopback, link-local and one global) /proc/sys/ne
i just added ip6tables to get some log messages on incoming/outgoing packets (small embedded system with no tcpdump). In fact the problem disappeared with 2.6.9-rc2. I thought the idea of 2.6.8.x is