Re: off-by-one error in ip_fragment, recently.

2004-01-10 Thread David Gilbert
> "Andre" == Andre Oppermann <[EMAIL PROTECTED]> writes: Andre> There are two possible ways this can happen: The function Andre> m_copym was called with off == 0, or off == m->m_len. Neither Andre> is supposed to happen (obviously) so the bug must be in Andre> ip_fragment. Lets have a look a

Re: prism 2.5 timeout in wi_cmd 0x010b

2004-01-10 Thread Marko Zec
On Sunday 11 January 2004 01:34, Kevin Oberman wrote: > > Marko, > > I just started re-building my kernel with this patch. I have > previously reported this under CURRENT and hope that this might fix > the problem. It has also been reported by several others under > slightly different circumstances

Re: prism 2.5 timeout in wi_cmd 0x010b

2004-01-10 Thread Kevin Oberman
> From: Marko Zec <[EMAIL PROTECTED]> > Date: Sat, 10 Jan 2004 15:11:04 +0100 > Sender: [EMAIL PROTECTED] > > > --Boundary-00=_4fAAAunGWPP68/U > Content-Type: text/plain; > charset="iso-8859-2" > Content-Transfer-Encoding: 7bit > Content-Disposition: inline > > Hi Lorenzo, > > can you try the

Re: off-by-one error in ip_fragment, recently.

2004-01-10 Thread Andre Oppermann
Andre Oppermann wrote: > > David Gilbert wrote: > > > > I just updated a machine that uses GRE to -CURRENT. Upon rebooting, > > the debugger stopped at the following: > > > > "panic: m_copym, offset > size of mbuf chain" > > There are two possible ways this can happen: The function m_copym > wa

Re: off-by-one error in ip_fragment, recently.

2004-01-10 Thread Andre Oppermann
Andre Oppermann wrote: > > David Gilbert wrote: > > > > I just updated a machine that uses GRE to -CURRENT. Upon rebooting, > > the debugger stopped at the following: > > > > "panic: m_copym, offset > size of mbuf chain" > > There are two possible ways this can happen: The function m_copym > wa

Re: off-by-one error in ip_fragment, recently.

2004-01-10 Thread Andre Oppermann
David Gilbert wrote: > > I just updated a machine that uses GRE to -CURRENT. Upon rebooting, > the debugger stopped at the following: > > "panic: m_copym, offset > size of mbuf chain" There are two possible ways this can happen: The function m_copym was called with off == 0, or off == m->m_len

RE: 3NIC+ 2NAT

2004-01-10 Thread Aaron Burke
> I have 3 Nics lets name them NIC1-NIC2-NIC3 > NIC1 --> Internal Network /24 > NIC2 --> OutSide World (A) > NIC2 --> OutSide World (B) I have a similar situation (I think). I also have two seperate connections to the internet. fxp0: 11.22.33.44 gateway 11.22.33.1 fxp1: 66.77.88.99 gateway 66.77.88

off-by-one error in ip_fragment, recently.

2004-01-10 Thread David Gilbert
I just updated a machine that uses GRE to -CURRENT. Upon rebooting, the debugger stopped at the following: "panic: m_copym, offset > size of mbuf chain" panic() m_copym() ip_fragment() ip_output() gre_output() ip_output() udp_output() upd_send() sosend() kern_sendit() sendit() sendto() syscall()

Re: (revised) 4.0-stable & Linksys WRT54G won't talk w/each other

2004-01-10 Thread Anthony Volodkin
Hey, Apparently the WRT54G is having some arp issues. I'd check the following: - install latest firmware - install Ethereal on the windows machine and watch the traffic exchange when you would ping/access the WRT54G. It is important that this is done right after boot so that the Windows machin

(revised) 4.*9*-stable & Linksys WRT54G won't talk w/each other

2004-01-10 Thread Kenneth W Cochran
oops, mistype, that should've been 4.9-stable instead of 4.0... stupidfingers... Hello: I'm having problems getting a FreeBSD machine and a Linksys WRT54G talking with each other. Interfaces: dc0 - "public" to outside Internet dc1 - internal 192.168.0.1/24, connects to a hub dc2 - internal 192.1

Re: (revised) 4.*9*-stable & Linksys WRT54G won't talk w/each other

2004-01-10 Thread Kenneth W Cochran
>Date: Fri, 9 Jan 2004 12:56:20 -0500 (EST) >From: Anthony Volodkin <[EMAIL PROTECTED]> >To: Kenneth W Cochran <[EMAIL PROTECTED]> >cc: [EMAIL PROTECTED], <[EMAIL PROTECTED]> >Subject: Re: (revised) 4.0-stable & Linksys WRT54G won't talk w/each other > >Hey, > >Apparently the WRT54G is having some

(revised) 4.0-stable & Linksys WRT54G won't talk w/each other

2004-01-10 Thread Kenneth W Cochran
Hello: I'm having problems getting a FreeBSD machine and a Linksys WRT54G talking with each other. Interfaces: dc0 - "public" to outside Internet dc1 - internal 192.168.0.1/24, connects to a hub dc2 - internal 192.168.1.100/24, connects to a switched LAN port on the router dc3 - currently unused

Re: prism 2.5 timeout in wi_cmd 0x010b

2004-01-10 Thread Marko Zec
Hi Lorenzo, can you try the attached patch, it does seem to help on my ThinkPad X30, which has an internal mini-PCI Prism2.5 card with the same firmware. Cheers, Marko On Saturday 10 January 2004 03:43, Lorenzo Vicisano wrote: > Hi, > > This is the context: > > - Stable as of Jan 9 (FreeBSD

Re: Intermittent problems with LAN transfer speeds

2004-01-10 Thread .
> On Sat, 10 Jan 2004 00:48:26 +0300 (MSK) > [EMAIL PROTECTED] wrote: > > Does > > ifconfig xx down; ifconfig xx up > > helps? > Tried that many many times; no effect. > > > Can be packet loss triggered by a lot of small > > packets on this interface? > Not that I've noticed. Any suggestions on h