Re: Default route changes unexpectedly #2 (was Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102)

2013-03-06 Thread Andre Oppermann
Courtland, the arpresolve observation is very important. Do you have flowtable enabled in your kernel? -- Andre On 06.03.2013 17:16, Adrian Chadd wrote: Another instance of it.. Adrian On 6 March 2013 07:21, Courtland wrote: Has there been any progress on resolving this problem. Does anyone

Re: Default route changes unexpectedly #2 (was Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102)

2013-03-07 Thread Nick Rogers
I'm not sure. I have not explicitly enabled/disabled it. I am using the GENERIC kernel from 9.1 plus PF+ALTQ. # sysctl net.inet.flowtable.enable sysctl: unknown oid 'net.inet.flowtable.enable' # sysctl -a | grep flow kern.sigqueue.overflow: 0 net.inet.tcp.reass.overflows: 0 net.inet6.ip6.auto_flow

Re: Default route changes unexpectedly #2 (was Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102)

2013-03-07 Thread Andre Oppermann
On 07.03.2013 17:54, Nick Rogers wrote: I'm not sure. I have not explicitly enabled/disabled it. I am using the GENERIC kernel from 9.1 plus PF+ALTQ. # sysctl net.inet.flowtable.enable sysctl: unknown oid 'net.inet.flowtable.enable' # sysctl -a | grep flow kern.sigqueue.overflow: 0 net.inet.tcp.

Re: Default route changes unexpectedly #2 (was Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102)

2013-03-07 Thread Krzysztof Barcikowski
W dniu 2013-03-07 18:09, Andre Oppermann pisze: On 07.03.2013 17:54, Nick Rogers wrote: I'm not sure. I have not explicitly enabled/disabled it. I am using the GENERIC kernel from 9.1 plus PF+ALTQ. # sysctl net.inet.flowtable.enable sysctl: unknown oid 'net.inet.flowtable.enable' # sysctl -a |

Re: Default route changes unexpectedly #2 (was Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102)

2013-03-07 Thread Andre Oppermann
On 07.03.2013 20:27, Krzysztof Barcikowski wrote: W dniu 2013-03-07 18:09, Andre Oppermann pisze: On 07.03.2013 17:54, Nick Rogers wrote: I'm not sure. I have not explicitly enabled/disabled it. I am using the GENERIC kernel from 9.1 plus PF+ALTQ. # sysctl net.inet.flowtable.enable sysctl: unk

RE: Default route changes unexpectedly #2 (was Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102)

2013-03-07 Thread Li, Qing
Hi, > > I can confirm I get these messages as well: > > Mar 7 19:40:25 opole kernel: arpresolve: can't allocate llinfo for > 86.58.122.125 > Mar 7 19:40:25 opole kernel: arpresolve: can't allocate llinfo for > 86.58.122.125 > > IP 86.58.122.125 is not from IP pool used by me. > This kernel

Re: Default route changes unexpectedly #2 (was Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102)

2013-03-07 Thread Nick Rogers
On Thu, Mar 7, 2013 at 12:51 PM, Li, Qing wrote: > Hi, > >> >> I can confirm I get these messages as well: >> >> Mar 7 19:40:25 opole kernel: arpresolve: can't allocate llinfo for >> 86.58.122.125 >> Mar 7 19:40:25 opole kernel: arpresolve: can't allocate llinfo for >> 86.58.122.125 >> >> IP 86.