I did update the kernel, during boot it prints '1.4.2 GENERIC' so I 
assume I'm using the right kernel.... :^)

Basically, I wrote a little for loop to go through all of the .tgz files
and extract them from the root directory.  Here's the command I used:

%cd /
%foreach i (/usr/dl/NetBSD-1.4.2/*.tgz)
	echo $i
	if ("$i" == "/usr/dl/NetBSD-1.4.2/pkgsrc.tgz")
		cd /usr/src
		tar --unlink -zxpvf $i >>& /var/extract.log
		cd /
	else if ("$i" == "/usr/dl/NetBSD-1.4.2/xsrc.tgz")
		cd /usr/src
		tar --unlink -zxpvf $i >>& /var/extract.log
		cd /
	else
		tar --unlink -zxpvf $i >>& /var/extract.log
	endif
end

The contents of the /usr/dl/NetBSD-1.4.2 directory is:
base.tgz
comp.tgz
games.tgz
gnusrc.tgz
kern.tgz
man.tgz
misc.tgz
pkgsrc.tgz
sharesrc.tgz
src.tgz
syssrc.tgz
xsrc.tgz
text.tgz
xbase.tgz
xcomp.tgz
xcontrib.tgz
xfont.tgz
xserver.tgz

I went through the /var/extract.log file to see if any error messages
appeared
and no were found.

I did not change the ipnat.conf or ipf.conf files and ipfilter seems to load
correctly and indicates that it is v3.3.6.

Any other thoughts?

Thanks,

Dave St. John


-----Original Message-----
From: Frederick Bruckman [mailto:fb@enteract.com]
Sent: Friday, March 31, 2000 9:52 AM
To: St John, David R
Cc: 'port-mac68k@netbsd.org'
Subject: Re: upgrading to 1.4.2


On Fri, 31 Mar 2000, St John, David R wrote:

> I used 'tar --unlink -zxpvf <filename>.tgz' to extract all of the
> tarballs except for etc.tgz.  I extracted etc.tgz into a separate
> directory and updated files by hand.

You did update the kernel, too?

> Now after rebooting into multi-user mode, ipnat no longer works.  I'm
using
> a real basic config file, taken from
> one of the example files.  It sets up a N:1 port mapping and a ftp proxy.
> For each line in the file, I get an
> ioctl(SIOCADNAT) error (I'm pretty sure that's the error).  
> 
> Has anyone else seen this problem or has upgraded from the release 1.4.1
to
> release 1.4.2 without using
> -current?

The only problem I had was the NAT simply doesn't function with a
1.4.2 kernel and 1.4.1 binaries, no error messages. After updating
userland, it was OK again.