Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 23 Jan 2009 09:14:49 -0800
From:      "Michael VanLoon" <>
To:        "Odhiambo Washington" <>
Subject:   RE: Dumb ipnat question
Message-ID:  <>
References:  <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
I didn't find "IPFILTER" in either the GENERIC or NOTES kernel files, so =
no, I didn't compile it in.  I was wondering about it, though, based on =
older kernel help messages I found on the net (> 10 years old).
I'll give both of those options a try.  Thanks!
- Michael


From: Odhiambo Washington []
Sent: Fri 1/23/2009 6:39 AM
To: Michael VanLoon
Subject: Re: Dumb ipnat question

On Fri, Jan 23, 2009 at 2:43 AM, Michael VanLoon =
<> wrote:

	I have built a simple 7.1 system in a VM.  I built a custom kernel that =
is basically GENERIC minus some hardware stuff I don't need, plus a few =
things that look cool.
	When I attempt to run the ipnat command, I get the error:
	/dev/ipnat: open: No such file or directory
	Sure enough, there are no ip* devices in /dev/.  In the "olden days", =
when I used to do a lot of BSD hacking, you used MAKEDEV to make the =
devices you wanted.  Nowadays, it's done with devfs.  I believe the =
upshot is that it's supposed to be semi-automagic, isn't it?
	Anyway, what am I doing wrong?  What do I need to configure to use =
ipnat and then later ipfw or ipfilter?

Did you load the modules?
ipl_load=3D"YES" in /boot/loader.conf and reboot OR
kldload ipl

If you did not compile IPFILTER in the kernel, then you must load the =

Best regards,
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _=20
"The only time a woman really succeeds in changing a man is when he is a =
                             - Natalie Wood

Want to link to this message? Use this URL: <>