Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 13 Sep 2012 13:26:46 -0400
From:      Dominic Blais <dblais@interplex.ca>
To:        Adrian Chadd <adrian@freebsd.org>, =?utf-8?B?0JLQsNC00LjQvCDQo9GA0LDQt9Cw0LXQsg==?= <tretuliy2@gmail.com>
Cc:        "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>
Subject:   RE: kernel: arpresolve: can't allocate llinfo for 65.59.233.102
Message-ID:  <2DE61B0869B7484997BCA012845482C7EBE62DDDDE@WIN2008.Domnt.abi.ca>
In-Reply-To: <CAJ-VmonE0wuGWG6oyHu9oZjCOGJbJqfWzR2Ke=J7NqMT_xk5BA@mail.gmail.com>
References:  <2DE61B0869B7484997BCA012845482C7EBE62DDD88@WIN2008.Domnt.abi.ca> <20120910140300.GV44854@FreeBSD.org> <2DE61B0869B7484997BCA012845482C7EBE62DDDAE@WIN2008.Domnt.abi.ca> <20120911142355.GM44854@glebius.int.ru> <2DE61B0869B7484997BCA012845482C7EBE62DDDB5@WIN2008.Domnt.abi.ca> <CAJ-VmomU7kQOHY1j0VE5%2B3jsmD%2Bh5r_ZPDCdqydAaYSCVZrv1A@mail.gmail.com> <CALCNsJSo1PEPrB9tQ7H%2BA9NLOaKtCQkEh70Yhs4wtNhcOcpBRQ@mail.gmail.com> <20120911195836.GQ44854@FreeBSD.org> <CALCNsJTpOcQS8%2BFyvuHf01Tg5NquHSCQUv6KrEhJXfeS4jXiCQ@mail.gmail.com> <B143A8975061C446AD5E29742C53172301742F6F@pwsvl-excmbx-03.internal.cacheflow.com> <CAAEEwq1fPtqHpcA7Qkc6t-5mT0_P65o16Q%2BmWQWc1y8t182ruQ@mail.gmail.com> <CAJ-VmonE0wuGWG6oyHu9oZjCOGJbJqfWzR2Ke=J7NqMT_xk5BA@mail.gmail.com>

index | next in thread | previous in thread | raw e-mail

Hi,

Altough I'm using ipfw for traffic shaping, I'm not using it for NAT. I'm using PF for NAT.


--



-----Message d'origine-----
De : owner-freebsd-net@freebsd.org [mailto:owner-freebsd-net@freebsd.org] De la part de Adrian Chadd
Envoyé : 13 septembre 2012 13:04
À : Вадим Уразаев
Cc : freebsd-net@freebsd.org
Objet : Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102

On 13 September 2012 03:04, Вадим Уразаев <tretuliy2@gmail.com> 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 itself when I started to use  ipfw nat functionality ).

OOO.

Wait. Is ipfw nat the common thread with all the people demonstrating this issue?




Adrian
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"

help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2DE61B0869B7484997BCA012845482C7EBE62DDDDE>