e (in)famous ethtool vs autonegotiation issue. If you do ethtool -s eth0 autoneg off speed 10 duplex half I think it will probably work. The behavior you're describing ap
Hi Dave, This patch keeps fragment queues private to each ip_defrag user to avoid skbs jumping between different callers. It shouldn't change any wanted behaviour, the only questionable one was ip_ca
Patch looks good. However, I think this is still not enough. What about fragments that come from different interfaces? Fragments with different security paths? Cheers, -- Visit Openswan at http://www
However, I think this is still not enough. What about fragments that come from different interfaces? Fragments with different security paths? Fragments with different security paths are indeed a pro
Well consider an IPIP interface over a transport mode ESP SA... -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana
Please fix the CONFIG_SMP build. You use some variable "user" in ip_frag_intern(), yet don't add this as an argument or anything like that. The "user" use you added is protected by CONFIG_SMP, so my
This patch keeps fragment queues private to each ip_defrag user to avoid skbs jumping between different callers. It shouldn't change any wanted behaviour, the only questionable one was ip_call_ra_ch
Thanks. I'll apply this and the 2.4.x variant. Although I have a theoretical objection to this thing. It is extending a namespace we have no such control over. The namespace is saddr/daddr/ID. But pe