> > > > What about latest netdev tree rather than 2.6.13.2? > > > > There have been changes going on... > > Yep..but the answer is always to try one later build..and > it takes time (I reported similar problems in 2.6.11 and was > told that 2.6.12 (or maybe .13) was going to fix it...) > I am afraid that if I go to the effort to reproduce the problem > in 2.6.14, someone is just going to tell me to try the latest > pre-15 code. > Unless you are going to provide full bug reports etc then you have to work off the latest tree for networking which is currently Dave Miller's netdev tree.
Developers are just like you - they don't have unlimited time either and are often unpaid. If you want to ask users experience and help then there is also linux-net mailing list. Ian -- Ian McDonald http://wand.net.nz/~iam4 WAND Network Research Group University of Waikato New Zealand - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
