RE: kernel: arpresolve: can't allocate llinfo for 65.59.233.102

2012-09-11 Thread Dominic Blais
Hi! I just noticed that it is my default route that is changing for the aforementioned in the subject IP address. What the "$?% could cause that? Could MPD push that route as default? For what reason? That IP address doesn't even belong to us. -- -Message d'origine- De : Gleb Smirn

Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102

2012-09-11 Thread Krzysztof Barcikowski
W dniu 2012-09-11 15:19, Dominic Blais pisze: Hi! I just noticed that it is my default route that is changing for the aforementioned in the subject IP address. What the "$?% could cause that? Could MPD push that route as default? For what reason? That IP address doesn't even belong to us.

Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102

2012-09-11 Thread Gleb Smirnoff
On Tue, Sep 11, 2012 at 09:19:59AM -0400, Dominic Blais wrote: D> Hi! D> D> I just noticed that it is my default route that is changing for the aforementioned in the subject IP address. What the "$?% could cause that? Could MPD push that route as default? For what reason? That IP address doesn't

RE: kernel: arpresolve: can't allocate llinfo for 65.59.233.102

2012-09-11 Thread Dominic Blais
I could do something about the route monitor but not the fstat | grep route... I mean, I would have to run it in a loop endlessly until the bug happens... Even with it, it's not even sure I would catch it... Is there some way we can fstat everything so I don't miss what's happening between 2 ca

Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102

2012-09-11 Thread Adrian Chadd
On 11 September 2012 09:01, Dominic Blais wrote: > I could do something about the route monitor but not the fstat | grep > route... I mean, I would have to run it in a loop endlessly until the bug > happens... Even with it, it's not even sure I would catch it... The route monitor is a good idea

Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102

2012-09-11 Thread Vijay Singh
On Tue, Sep 11, 2012 at 10:29 AM, Adrian Chadd wrote: > On 11 September 2012 09:01, Dominic Blais wrote: >> I could do something about the route monitor but not the fstat | grep >> route... I mean, I would have to run it in a loop endlessly until the bug >> happens... Even with it, it's not eve

RE: kernel: arpresolve: can't allocate llinfo for 65.59.233.102

2012-09-11 Thread Dominic Blais
Ok, I'll try the route monitor. Please note that Krzysztof Barcikowski already did it and got nothing: http://lists.freebsd.org/pipermail/freebsd-net/2012-March/031879.html -- -Message d'origine- De : adrian.ch...@gmail.com [mailto:adrian.ch...@gmail.com] De la part de Adrian Chadd

Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102

2012-09-11 Thread Gleb Smirnoff
On Tue, Sep 11, 2012 at 10:35:25AM -0700, Vijay Singh wrote: V> On Tue, Sep 11, 2012 at 10:29 AM, Adrian Chadd wrote: V> > On 11 September 2012 09:01, Dominic Blais wrote: V> >> I could do something about the route monitor but not the fstat | grep route... I mean, I would have to run it in a loo

Re: kern/171524: [ipmi] ipmi driver crashes kernel by reboot or shutdown

2012-09-11 Thread Sean Bruno
The following reply was made to PR kern/171524; it has been noted by GNATS. From: Sean Bruno To: bug-follo...@freebsd.org, dhoj...@brainbits.net Cc: Subject: Re: kern/171524: [ipmi] ipmi driver crashes kernel by reboot or shutdown Date: Tue, 11 Sep 2012 12:56:16 -0700 It looks like the fix i

Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102

2012-09-11 Thread Vijay Singh
> V> > V> Could this be > http://svnweb.freebsd.org/base/head/sys/netinet/in.c?r1=226120&r2=226224&pathrev=226331 > > Why do you suspect this one? I was hitting a similar issue in 8.2. After down/up on the interface to the default gateway, I saw this message and arpresolve would never complete. I

Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102

2012-09-11 Thread Gleb Smirnoff
On Tue, Sep 11, 2012 at 01:03:56PM -0700, Vijay Singh wrote: V> > V> V> > V> Could this be http://svnweb.freebsd.org/base/head/sys/netinet/in.c?r1=226120&r2=226224&pathrev=226331 V> > V> > Why do you suspect this one? V> V> I was hitting a similar issue in 8.2. After down/up on the interface V> t

Issue with igb and lagg (was Re: Problem with link aggregation + sshd)

2012-09-11 Thread Giulio Ferro
Well, there definitely seems to be a problem with igb and lagg. igb alone works as it should, but doesn't seem to work properly in lagg. To be sure I started from scratch from a 9.0 release with nothing but: /etc/rc.conf --- ifconfig_igb0="inet ..

Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd)

2012-09-11 Thread Freddie Cash
On Sep 11, 2012 2:12 PM, "Giulio Ferro" wrote: > > Well, there definitely seems to be a problem with igb and lagg. > > igb alone works as it should, but doesn't seem to work properly in lagg. > > To be sure I started from scratch from a 9.0 release with nothing but: > > /etc/rc.conf >

Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd)

2012-09-11 Thread Daniel Eischen
On Tue, 11 Sep 2012, Giulio Ferro wrote: Well, there definitely seems to be a problem with igb and lagg. igb alone works as it should, but doesn't seem to work properly in lagg. To be sure I started from scratch from a 9.0 release with nothing but: /etc/rc.conf ---

Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd)

2012-09-11 Thread Daniel Eischen
On Tue, 11 Sep 2012, Freddie Cash wrote: On Sep 11, 2012 2:12 PM, "Giulio Ferro" wrote: cloned_interfaces="lagg0" ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport igb3 192.168.x.x/24" sshd_enable="YES" --- This doesn't eve

Account Closed * (SECURITY NOTICE) *

2012-09-11 Thread RCBC
Your email program does not support HTML. To view an online version of this email, please click the link below. http://a.eb04.executivemailingservices.com/new/en_send_preview_iframe2.aspx?SID=1&NewsletterID=1182759&SiteID=205248&EmailID=146747893&HitID=134747850&token=0e3934e1622a93ef448eb5c

Re: kern/167325: [netinet] [patch] sosend sometimes return EINVAL with TSO and VLAN on 82599 NIC

2012-09-11 Thread Andre Oppermann
On 07.09.2012 23:44, Jeremiah Lott wrote: On Apr 27, 2012, at 2:07 AM, lini...@freebsd.org wrote: Old Synopsis: sosend sometimes return EINVAL with TSO and VLAN on 82599 NIC New Synopsis: [netinet] [patch] sosend sometimes return EINVAL with TSO and VLAN on 82599 NIC http://www.freebsd.org/