I have previously reported here that ipnat seems to break when I upgrade to FreeBSD 5.4 (from 5.3). I have seen reports that this is the case for installing 5.4 from source CD, too. Anyway, the issue is that ipnat seems to load and run, but its tables are missing or not loaded, etc. during the boot process. ipnat will begin to run normally if the tables are manually cleared and loaded using the commandline.

Anyway, here is a possible issue. If I didn't rename my Ethernet interface(s), would this problem still be around? If I rename fxp0 to oo0, for example, will this break ipnat? Looking at the rcorder script for FreeBSD, the ipnat is loaded before the Interface is renamed. So guess what is in my /etc/ipnat.rules? The renamed interface, oo0. Also looking at the rcorder of the bootup scripts in /etc/rc.d, I see that ipfilter is reloaded immediately after the interfaces are renamed. Should ipnat get the same treatment?

Thanks for help troubleshooting. I have this PR filed for FreeBSD, if anyone wants to look into it in detail (Darren should have already read it, as he is the guy listed as the Responsible): :)

http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/81606

Billy

Reply via email to