natd no longer working - libalias is at fault
Sean McNeil
sean at mcneil.com
Wed Apr 14 19:04:09 PDT 2004
The fix with my issue was committed soon after the mistake was found.
Compiling with -O2 is a completely different beast and has not been
addressed as far as I know. The mistake was made, however, when
introducing changes to prevent alias errors from the compiler at higher
optimization (-O2).
Sean
On Wed, 2004-04-14 at 18:47, Mike Jakubik wrote:
> Steve Ames said:
>
> > ----- Original Message -----
> > From: "Sean McNeil" <sean at mcneil.com>
> >> On Fri, 2004-04-02 at 04:12, Sean McNeil wrote:
> >> > Greetings,
> >> >
> >> > System from March 30th worked fine. Today, just rebuilt everything
> >> and
> >> > tcp isn't working through nat anymore. udp still works. It isn't the
> >> > kernel as I tried my old one and got the same problem. I'm guessing
> >> the
> >> > recent changes to libalias did it.
> >>
> >> Confirmed. Rolling lib/libalias/alias.c back to version 1.40 fixed the
> >> problem.
> >
> > Ditto.
>
> NAT still does not work on -current as of today, when compiled with -O2.
> Can whatever the fix to libalias is be please commited?
>
> Thanks.
>
More information about the freebsd-current
mailing list