Subject: Re: ipnat completely hosed in current 2.0E(?)
To: None <current-users@NetBSD.org>
From: Christian Biere <christianbiere@gmx.de>
List: current-users
Date: 04/27/2004 15:39:11
--Oiv9uiLrevHtW1RS
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Frank Kardel wrote:
> Christian Biere wrote:
> >several hours ago I've updated the sources from CVS and successfully
> >built 2.0E userland & kernels. After installing and rebooting NAT didn't
> >work at all, I couldn't get a TCP connection from behind the router.

FWIW, after a third update trial (with exactly the same kernel and
userland), ipf and ipnat work just fine. I have no clue what mistake
I made or what's the difference now.

> My experience are somewhat mixed. I do get panics during ifconfigs of=20
> bge0 in the inet6 output path (see PR/25227).

I have no use for inet6, ATM.

> Since then I do not automatically start ipnat/ipf at boot. I still have=
=20
> those panics at system shutdown.

There are no shutdowns scheduled in the foreseeable future. ;)

--=20
Christian

--Oiv9uiLrevHtW1RS
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFAjmJ/0KQix3oyIMcRAjPIAJwIkr6yLQwMwqtgDxBxnYmhsMlmSQCfZBh5
8VXzkzhts9buXGX1vfzLJ/s=
=+jhK
-----END PGP SIGNATURE-----

--Oiv9uiLrevHtW1RS--