Current problem reports assigned to you

2007-08-27 Thread FreeBSD bugmaster
Current FreeBSD problem reports Critical problems S Tracker Resp. Description o kern/115360 net[ipv6] IPv6 address and if_bridge don't play well toge 1 problem total. Serious problems S Tracker

Bug in vr(4) driver

2007-08-27 Thread Bill Paul
I recently started writing a driver for the Via Rhine family of chips for VxWorks (they turn up on various x86-based single board systems, and I figured it'd be nice to actually support them out of the box), and along the way, I noticed a subtle bug in the FreeBSD vr(4) driver. The vr_attach() ro

nc captures 1024 bytes

2007-08-27 Thread Weiguang Shi
Hi, My system is FreeBSD 6.2. I sent a UDP datagram of 1464 bytes to port 1234 where nc was waiting % nc -n -u -l 1234 >tt Afterwards, the size of tt, however, was only 1024 bytes. I noticed this piece of code in nc 341 if (uflag) { 342

Re: nc captures 1024 bytes

2007-08-27 Thread Weiguang Shi
To get the larger packets, I have to fix another hard-coded "1024" 630 readwrite(int nfd) 631 { 632 struct pollfd pfd[2]; 633 unsigned char buf[8192]; 634 int n, wfd = fileno(stdin); 635 int lfd = fileno(stdout); 636 int plen; 637 638 plen = jflag

Re: nc captures 1024 bytes

2007-08-27 Thread John-Mark Gurney
Weiguang Shi wrote this message on Mon, Aug 27, 2007 at 16:37 -0700: > To get the larger packets, I have to fix another hard-coded "1024" This is also a performance problem on slower machines... nc should be fixed to use larger buffers, maybe to the tune of 64KB if not larger... W/ TSO, doing 64

Re: Bug in vr(4) driver

2007-08-27 Thread Pyun YongHyeon
On Mon, Aug 27, 2007 at 08:18:08PM +, Bill Paul wrote: > > I recently started writing a driver for the Via Rhine family of chips > for VxWorks (they turn up on various x86-based single board systems, > and I figured it'd be nice to actually support them out of the box), > and along the wa

infinite loop in esp6_ctlinput()?

2007-08-27 Thread blue
Dear all: When receiving a "packet too big" ICMP error message, FreeBSD will call the ctlinput() function of the upper protocol. If the preceding packet is an ESP IPv6 packet, then FreeBSD will call esp6_ctlinput(). In esp6_ctlinput(), pfctlinput2() will be executed to traverse all possible

Re: infinite loop in esp6_ctlinput()?

2007-08-27 Thread blue
Since our device adopts the IPsec codes from BSD, our device will have infinite loop after receiving ICMP packet too big message. I am not sure whether BSD itself will have the problem or not (maybe needs further testing). In IPSEC, esp6_ctlinput() still calls pfctlinput2(), which is the root c

Re: infinite loop in esp6_ctlinput()?

2007-08-27 Thread JINMEI Tatuya / 神明達哉
At Tue, 28 Aug 2007 10:15:31 +0800, blue <[EMAIL PROTECTED]> wrote: > When receiving a "packet too big" ICMP error message, FreeBSD will call > the ctlinput() function of the upper protocol. If the preceding packet > is an ESP IPv6 packet, then FreeBSD will call esp6_ctlinput(). In > esp6_ctli