Date: Wed, 22 May 2013 19:07:23 +0200 From: Spil Oss <spil.oss@gmail.com> To: pyunyh@gmail.com Cc: freebsd-ipfw@freebsd.org, Gleb Smirnoff <glebius@freebsd.org>, current <freebsd-current@freebsd.org> Subject: Re: Problems with ipfw/natd and axe(4) Message-ID: <CAEJyAvMx7kgo1Q_mSpud3uf%2BCd9mrwhbXZsYSoDjhJNWqQMKPQ@mail.gmail.com> In-Reply-To: <20130513043639.GA1480@michelle.cdnetworks.com> References: <CAEJyAvOZ6fW0i3yT_D4fH1huje-qsJwA7GGeXqAO1PKzge-YNw@mail.gmail.com> <20130415015850.Y56386@sola.nimnet.asn.au> <CAHu1Y73Xu64NY1B=idaKmHKDGOB3AHbcXKi4A48-SNkhJrMy6Q@mail.gmail.com> <20130415160625.K56386@sola.nimnet.asn.au> <CAEJyAvP-4FZ7eZ0o4c3qMzC0nY_gT4GfS3KjBVQiuzNY3aXz4Q@mail.gmail.com> <CAEJyAvMGKr9gZEEhg2KCD2FkZ=F4Xbx20v8iWyu8hhA_Pq8phw@mail.gmail.com> <20130417133637.W56386@sola.nimnet.asn.au> <CAEJyAvO_KA8dYSLkFXCoBqcogTkurBX_X=KZn25R4MKoeUGaVQ@mail.gmail.com> <CAEJyAvNL4NWmm8BMGkT6usZgGt2VWJNqQXeXBgYY9%2BMiNoUBVw@mail.gmail.com> <20130510200409.GT15182@FreeBSD.org> <20130513043639.GA1480@michelle.cdnetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi YongHyeon, Without natd this seems to work fine (both on RELEASE and CURRENT). Both my Hong-Kong no-name and Edimax EU-4208 seem to behave the same. This works with natd on RELEASE as well, but just for a limited time. I've yet to establish if it's time or #packets that cause the processing to stop. I'll try to generate some tcpdump output and compare working / non-working connected to NIC with txcsum/rxcsum disabled. Any pointers how to dig deeper? Kind regards, Spil. On Mon, May 13, 2013 at 6:36 AM, YongHyeon PYUN <pyunyh@gmail.com> wrote: > On Sat, May 11, 2013 at 12:04:09AM +0400, Gleb Smirnoff wrote: >> Spil, >> >> On Fri, May 10, 2013 at 09:06:35AM +0200, Spil Oss wrote: >> S> There seems to be quite a bit of overhaul on the firewall code, pf and >> S> ipfw have been moved to sys/netpfil? Can there be some regressions in >> S> there that I hit? >> >> Yes, a regression is possible there. However, the issue seems to be >> axe(4) specific, since there are no reports on more common NICs. > > There was no change to axe(4) except added a new device id so it > seems the issue is not in driver. In addition, AX88772B engineering > sample I have works without problems on CURRENT. > I didn't use ipfw(4) or natd though.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAEJyAvMx7kgo1Q_mSpud3uf%2BCd9mrwhbXZsYSoDjhJNWqQMKPQ>