> I get the following error "arpresolve: can't allocate llinfo for 1.1.245.192
> on vlan320" I can't explain. (IP edited). I only setup 1.1.245.192/31 between
> this vlan which parent is a VF from a MLX5EN(4) card .
>
> I am using a generated mac address and
I get the following error "arpresolve: can't allocate llinfo for 1.1.245.192 on
vlan320" I can't explain. (IP edited). I only setup 1.1.245.192/31 between this
vlan which parent is a VF from a MLX5EN(4) card .
I am using a generated mac address and distribute IPs over OSP
wo vlans, but TCP does not work... and I keep getting
> these messages:
>
> kernel: arpresolve: can't allocate llinfo for
>
> I already removed IPFW from the kernel, (saw some reference to that
> being the culprit), so there is no firewall right now.
>
> This is now on FreeB
en the two vlans, but TCP does not work... and I keep getting
these messages:
kernel: arpresolve: can't allocate llinfo for
I already removed IPFW from the kernel, (saw some reference to that
being the culprit), so there is no firewall right now.
This is now on FreeBSD 8 STABLE ( to be more
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&
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 fro
he arpresolve area before digging into it.
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
OK. Then this is the common fac
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.
Krzysiek
work load.
The last time this happened I had a stream of arpresolve messages in the
kernel for the IP that the default route was changed to.
Mar 5 19:12:53 kernel: arpresolve: can't allocate llinfo for
50.142.201.101
The default route was changed to 50.142.201.101 after these messages.
--
m under FreeBSD 9.1-RELEASE. I use PF
>>> for
>>> NAT, ALTQ, and RDR/filter rules. I'm not using PPPoE or dhclient. The
>>> default gateway changes to an IP that is not on my network when under
>>> heavy
>>> network load.
>>>
>>> Th
last time this happened I had a stream of arpresolve messages in the
kernel for the IP that the default route was changed to.
Mar 5 19:12:53 kernel: arpresolve: can't allocate llinfo for
50.142.201.101
The default route was changed to 50.142.201.101 after these messages.
--
View this
oute was changed to.
> Mar 5 19:12:53 kernel: arpresolve: can't allocate llinfo for
> 50.142.201.101
> The default route was changed to 50.142.201.101 after these messages.
>
>
>
>
> --
> View this message in context:
> http://freebsd.1045724.n5.nabble.com/kerne
an IP that is not on my network when under heavy
network load.
The last time this happened I had a stream of arpresolve messages in the
kernel for the IP that the default route was changed to.
Mar 5 19:12:53 kernel: arpresolve: can't allocate llinfo for
50.142.201.101
The default route was
Ok, I will disable vlan_hwtso using
ifconfig -vlanhwtso.
Thanks.
> Try disabling tso at the global level in the kernel. Under some
> circumstances with some drives VLAN_HWTSO -> TSO.
> -Garrett
>
___
freebsd-net@freebsd.org mailing list
http://lists.fr
On Thu, Sep 13, 2012 at 11:29 PM, Вадим Уразаев wrote:
> I am using two lagg interfaces :
> lagg0: flags=8843 metric 0 mtu 1500
> options=400b8
> ether 00:1b:21:55:a7:c4
> nd6 options=9
> media: Ethernet autoselect
> status: active
> laggproto lacp
> laggport: igb1 flags=1c
> laggport: igb0 flags=
I am using two lagg interfaces :
lagg0: flags=8843 metric 0 mtu 1500
options=400b8
ether 00:1b:21:55:a7:c4
nd6 options=9
media: Ethernet autoselect
status: active
laggproto lacp
laggport: igb1 flags=1c
laggport: igb0 flags=1c
lagg1: flags=8843 metric 0 mtu 1500
options=400b8
ether 00:1b:21:63:59:c
On Thu, 13 Sep 2012 21:53:23 +0300, ? ??? wrote:
> Then my guess is wrong. I found the message, where similiar problem was
> described in ipfw mailling list
> http://lists.freebsd.org/pipermail/freebsd-ipfw/2011-March/004582.html, with
> no answer.
> Maybe it will be usefull for someb
Then my guess is wrong. I found the message, where similiar problem was
described in ipfw mailling list
http://lists.freebsd.org/pipermail/freebsd-ipfw/2011-March/004582.html, with
no answer.
Maybe it will be usefull for somebody.
___
freebsd-net@freebsd
À : Вадим Уразаев
Cc : freebsd-net@freebsd.org
Objet : Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102
On 13 September 2012 03:04, Вадим Уразаев wrote:
> I have the same issue (default gateway unexpectedly changes on some
> random
> address) on FreeBSD 9.0 Box with lot of tra
W dniu 2012-09-13 19:04, Adrian Chadd pisze:
On 13 September 2012 03:04, Вадим Уразаев wrote:
I have the same issue (default gateway unexpectedly changes on some random
address) on FreeBSD 9.0 Box with lot of traffic going through it, I have a
wild guess that it is related to libalias compille
On 13 September 2012 03:04, Вадим Уразаев wrote:
> I have the same issue (default gateway unexpectedly changes on some random
> address) on FreeBSD 9.0 Box with lot of traffic going through it, I have a
> wild guess that it is related to libalias compilled into kernel (troubles
> start showing it
I have the same issue (default gateway unexpectedly changes on some random
address) on FreeBSD 9.0 Box with lot of traffic going through it, I have a
wild guess that it is related to libalias compilled into kernel (troubles
start showing itself when I started to use ipfw nat functionality ).
>
> > V>
> > V> Could this be
> http://svnweb.freebsd.org/base/head/sys/netinet/in.c?r1=226120&r2=22622
> 4&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 woul
>
> got message of size 184 on Wed Sep 12 00:15:49 2012
> RTM_DELETE: Delete Route: len 184, pid: 0, seq 0, errno 0,
> flags:
> locks: inits:
> sockaddrs:
> default default default ### <- This looks normal, I
> usually see it when customers connect to
>
---Message d'origine-
De : Gleb Smirnoff [mailto:gleb...@freebsd.org]
Envoyé : 11 septembre 2012 16:06
À : Vijay Singh
Cc : Adrian Chadd; freebsd-net@freebsd.org; Dominic Blais
Objet : Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102
On Tue, Sep 11, 2012 at 01:03:56PM -0
11 septembre 2012 15:59
À : Vijay Singh
Cc : Adrian Chadd; freebsd-net@freebsd.org; Dominic Blais
Objet : Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102
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 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
> 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
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
rian Chadd
Envoyé : 11 septembre 2012 13:30
À : Dominic Blais
Cc : Gleb Smirnoff; freebsd-net@freebsd.org
Objet : Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102
On 11 September 2012 09:01, Dominic Blais wrote:
> I could do something about the route monitor but not the fst
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
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
ning
between 2 calls to fstat?
--
-Message d'origine-
De : Gleb Smirnoff [mailto:gleb...@freebsd.org]
Envoyé : 11 septembre 2012 10:24
À : Dominic Blais
Cc : freebsd-net@freebsd.org
Objet : Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102
On Tue, Sep 11,
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
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.
-
De : Gleb Smirnoff [mailto:gleb...@freebsd.org]
Envoyé : 10 septembre 2012 10:03
À : Dominic Blais
Cc : freebsd-net@freebsd.org
Objet : Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102
On Mon, Sep 10, 2012 at 09:29:44AM -0400, Dominic Blais wrote:
D> Hi,
D>
D> W
On Mon, Sep 10, 2012 at 09:29:44AM -0400, Dominic Blais wrote:
D> Hi,
D>
D> We have a PPPoE server running FreeBSD 9.0-RELEASE-p3 with mpd-5.6. It used
to work very well for 6 weeks and now the "Internet traffic" stops almost each
day.
D>
D> Symptoms:
D>
D> - I still can ssh to the server from
Hi,
We have a PPPoE server running FreeBSD 9.0-RELEASE-p3 with mpd-5.6. It used to
work very well for 6 weeks and now the "Internet traffic" stops almost each day.
Symptoms:
- I still can ssh to the server from the LAN.
- The users connected to mpd by PPPoE can't access Internet.
- I tried to d
Thank you Chris for the verification. I will wait a few days before committing
the patch.
--Qing
From: Chris Miller [mailto:chrismiller@gmail.com]
Sent: Monday, August 29, 2011 7:31 PM
To: Li, Qing
Cc: freebsd-net@freebsd.org
Subject: Re: arpresolve: can't allocate llinfo
Qing-
; > From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd-
> > n...@freebsd.org] On Behalf Of Chris Miller
> > Sent: Tuesday, August 16, 2011 3:05 PM
> > To: freebsd-net@freebsd.org
> > Subject: arpresolve: can't allocate llinfo
> >
> > I'm using FreeBSD
is Miller
> Sent: Tuesday, August 16, 2011 3:05 PM
> To: freebsd-net@freebsd.org
> Subject: arpresolve: can't allocate llinfo
>
> I'm using FreeBSD 8.1 and I'm seeing the following messages spit out
> frequently.
>
> IPv4 address: "169.254.231.172" is
er
> > Sent: Tuesday, August 16, 2011 3:05 PM
> > To: freebsd-net@freebsd.org
> > Subject: arpresolve: can't allocate llinfo
> >
> > I'm using FreeBSD 8.1 and I'm seeing the following messages spit out
> > frequently.
> >
> > IPv
Of Chris Miller
> Sent: Tuesday, August 16, 2011 3:05 PM
> To: freebsd-net@freebsd.org
> Subject: arpresolve: can't allocate llinfo
>
> I'm using FreeBSD 8.1 and I'm seeing the following messages spit out
> frequently.
>
> IPv4 address: "169.254.231.17
I'm using FreeBSD 8.1 and I'm seeing the following messages spit out
frequently.
IPv4 address: "169.254.231.172" is not on the network
arpresolve: can't allocate llinfo for 169.254.231.172
Background:
I have two interfaces attached to the same LAN, both configured us
44 matches
Mail list logo
