Date: Sun, 21 Oct 2012 18:08:12 +0700 From: Eugene Grosbein <egrosbein@rdtc.ru> To: Nikolay Nevzorov <nevzorovn@gmail.com> Cc: freebsd-net@freebsd.org, yongari@freebsd.org Subject: Re: kern/171520: [alc] alc network driver + tso + vlan does not work. Message-ID: <5083D79C.4010309@rdtc.ru> In-Reply-To: <CAHtHi9m=pd38d7mh5o56EQ3eA%2BODZ15ZRe0UQ%2BZ3yEnEyHayqA@mail.gmail.com> References: <201210180141.q9I1f53s052539@freefall.freebsd.org> <CAHtHi9kphRZnX53mKeWzG3HcJoq8-E1Cb1JJTQsrybqLwPGk1g@mail.gmail.com> <50830F8B.4030204@rdtc.ru> <CAHtHi9m=pd38d7mh5o56EQ3eA%2BODZ15ZRe0UQ%2BZ3yEnEyHayqA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
21.10.2012 12:19, Nikolay Nevzorov wrote: > There is libalias in my kernel config, and i use it on ng0, not on alc0. And libalias used not in ipfw - netgraph with it builded by mpd. Anyway this bug? AFAIK, mpd uses ng_nat(4) that is based on kernel version of libalias, the same as ipfw nat is based on. So, the warning applies to mpd's internal NAT too. I guess this should be a culprit. Can you exclude NAT to perform "clean" experiment? Does the issue disappear when you do? Eugene Grosbein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5083D79C.4010309>