From owner-freebsd-stable Mon Jan 15 17: 5:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www3.infolink.com.br (www3.infolink.com.br [200.255.108.4]) by hub.freebsd.org (Postfix) with ESMTP id 1963037B6C4 for ; Mon, 15 Jan 2001 17:04:56 -0800 (PST) Received: from diala11 (unverified [200.255.108.11]) by www3.infolink.com.br (Vircom SMTPRS 4.2.181) with SMTP id ; Mon, 15 Jan 2001 23:04:54 -0200 Message-ID: <003701c07f58$567b88c0$0b6cffc8@infolink.com.br> From: "Antonio Carlos Pina" To: "Peter Jeremy" Cc: References: <3a62e370.5b5.0@infolink.com.br> <20010116092017.G91029@gsmx07.alcatel.com.au> Subject: Re: Dummynet stopping ? Date: Mon, 15 Jan 2001 23:04:54 -0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4029.2901 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4029.2901 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Peter, Thank you for your kind reply. > That's really weird. The rules you posted are symmetrical, as is a > ping - if you can ping his IP address, he should be able to ping your > IP address. Did you check for other network problems (correct routes > in both machines, appropriate ARP entries in both machines)? Did > netstat or tcpdump show any traffic to/from that address via ep0? > I presume there were no messages from the kernel. I think I didn't make myself clear, sorry. I can ping his IP address from WITHIN the Bridge and I believe he can ping the bridge too (of course, since there aren't rules to forbid this). But, I can NOT ping his IP address from my machine (for instance) neither he can ping me. Oh yes, under normal circunstances we can ping each other throught the pipes. I think I found something at least interesting: 00003: 128.000 Kbit/s 0 ms 50 sl. 1 queues (1 buckets) droptail mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000 BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes Pkt/Byte Drp 0 tcp 200.xxx.xxx.xx/110 200.yyy.yyy.yy/64905 48150 41482697 0 0 0 00004: 128.000 Kbit/s 0 ms 50 sl. 1 queues (1 buckets) droptail mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000 BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes Pkt/Byte Drp 0 tcp 200.yyy.yyy.yy/64905 200.xxx.xxx.xx/110 41463 6912193 0 0 0 yyy.yyy.yyy is my IP while xxx.xxx.xxx is a POP server outside our network (it's not smart to show IP addresses like I did before ;-)). Apparently our IP is reading a 40MB message or something (the number is growing) but this connection DOESN'T appears in tcpdump ! It's seems to me that our IP has closed the connection, and the pipe is still piping something. This is the position after the time I took to write this explanation above: 00003: 128.000 Kbit/s 0 ms 50 sl. 1 queues (1 buckets) droptail mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000 BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes Pkt/Byte Drp 0 tcp 200.xxx.xxx.xx/110 200.yyy.yyy.yy/64905 48243 41515518 0 0 0 00004: 128.000 Kbit/s 0 ms 50 sl. 1 queues (1 buckets) droptail mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000 BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes Pkt/Byte Drp 0 tcp 200.yyy.yyy.yy/64905 200.xxx.xxx.xx/110 41545 6917583 0 0 0 Perhaps this will cause memory allocation errors ? > Obvious causes for the pipe not working are: > - The dummynet scheduler has stopped. This can be checked with the > sysctl net.inet.ip.dummynet.curr_time, which should be incrementing > at HZ counts/sec. (This will affect all pipes). > - Dummynet can't allocate memory for queued packets. This can be > checked with "vmstat -m | grep IpFw". I will look deeper into this. Thank you very much for your answer. Best regards, Antonio Carlos Pina apina@infolink.com.br To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message