Billy Newsom wrote:
Okay, I'm going to dig up someone who might be responsible or might be
able to fix it. Two strikes while doing the same upgrade... While I'm
thinking about it, would you see if it happens on the next reboot? I
haven't tried, because my system is a firewall that I need to
Hi,
I got the same problem with NAT not working at boot time after upgrading
to 5.4. I compiled a generic kernel, so it doesn't seem to be a problem
concerning the kernel. I guess some change in the rc system.
Hope we find a solution.
sincerely,
Daniel Mester
___
On Behalf Of Billy Newsom
~>Sent: Thursday, May 26, 2005 1:54 AM
~>To: freebsd-stable@freebsd.org
~>Subject: 5-Stable (5.4) any ipnat changes?
~>
~>
~>Is there some reason why ipnat wouldn't automatically startup?
~>
~>I just upgraded from a 5-stable in February to a 5-
nd "ipnat_enable=YES" present in
the /etc/rc.conf.
~>-Original Message-
~>From: [EMAIL PROTECTED]
~>[mailto:[EMAIL PROTECTED] On Behalf Of Billy Newsom
~>Sent: Thursday, May 26, 2005 1:54 AM
~>To: freebsd-stable@freebsd.org
~>Subject: 5-Stable (5.4) any ip
Is there some reason why ipnat wouldn't automatically startup?
I just upgraded from a 5-stable in February to a 5-stable in May, so I
could essentially get 5.4 on this firewall machine. I simultaneously
was upgrading some ports, etc., but nothing too severe. When I rebooted
the machine, ever
