Hi, Herbert, On Thu, 18 Nov 2004 06:17 pm, you wrote: > This means that there is queue somewhere in the tx path that's too long. > You can start by looking at the queue for your tuntap device. If it's > a tap device, then you'll have a queue of 100 packets. That may be too > long depending on your application. > > You can adjust the queuelen using ifconfig(8)/ip(8). More detail about change the queue length, I don't think simply input the command will do:-( I looked at the docu on tuntap, it just mentioned that the first time to configure the tap interface: mknod /dev/net/tun c 10 200 or mkdir /dev/net. Is the number "200" the queue length? What's the number "10" for?? If I did "mkdir /dev/net", then what is the queue length will be?? And after that, how can I change the queue length and another number?? BTW: I checked the packets captured by etherreal, I found the packets queued each time after the ping flood is around 200. > If that's not the problem, then you should examine your application for > any hidden queues there. Thanks for this, Rita - : send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
