DUMMYNET broken on 4.11 (was: dummynet and vr(4)/egress broken
in 4.11 ?)
Jeremie Le Hen
jeremie at le-hen.org
Mon Jan 31 17:33:29 PST 2005
On Tue, Feb 01, 2005 at 02:05:12AM +0100, Jeremie Le Hen wrote:
> On Tue, Feb 01, 2005 at 01:20:34AM +0100, Jeremie Le Hen wrote:
> > > I'll give a try to a 4.10 kernel ASAP.
> >
> > I compiled the lastest kernel from RELENG_4_10 CVS branch and DUMMYNET
> > pipes works well. I am able to use one pipe on my external interface
> > egress without breaking TCP streams.
> >
> > I'm now recompiling the lastest kernel from the RELENG_4 branch to test
> > the same configuration but I'm pretty sure it won't work.
> >
> > Any ideas of what could break this ?
>
> I run the lastest 4.11 kernel and using exactly the same configuration
> breaks my TCP streams coming from my internal network.
As I said, I took the lastest kernel from RELENG_4. DUMMYNET pipes
will break any TCP stream coming from my internal network (which are
thus NATed by IPFilter), but not the ones originated from the router
itself.
I checked the differences between RELENG_4_10 and RELENG_4 :
o netinet/ nothing relevant
o net/ nothing relevant
o contrib/ipfilter/ could be the point given that IPFilter
was updated from 3.4.31 to 3.4.35 and
problems occur only when packets are
NATed
So I did:
%%%
# cd /sys/contrib/ipfilter
# cvs up -r RELENG_4_10 -dP
# config; make depend; make; make install ...
%%%
And it works !
So changes in IPFilter between 4.10 and 4.11 obviously broke DUMMYNET
pipes (see my^H^Hthe entire thread for more details).
Good night.
Best regards,
--
Jeremie Le Hen
jeremie at le-hen.org
More information about the freebsd-net
mailing list