I'm trying to get NAT going, and apparently failing to
understand large parts of the concept,
1) Per the handbook I have added
options IPFIREWALL
options IPDIVERT
to the kernel.
2) The firewall is active, and configured so it works for the
machine itself.
On Wednesday 19 March 2008 03:02:59 pm Robert Huff wrote:
I'm trying to get NAT going, and apparently failing to
understand large parts of the concept,
1) Per the handbook I have added
options IPFIREWALL
options IPDIVERT
to the kernel.
2) The firewall is active,
Josh Paetzel wrote:
I don't see much in the man page for ipfw concerning nat, certainly not the
rules you are specifying. Try man natd
NAT support was added to ipfw with the 7.0 release. You don't need to
run natd if you're using ipfw nat.
Robert Huff wrote:
ipfw nat 10 config log ip
I'm trying to get NAT going, and apparently failing to
understand large parts of the concept,
If natd is no longer needed as of 7.*, then this page of the
Handbook
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-natd.html
needs revision.
1) when I add the nat instance, it assigns it rule # 65100. Is
this a problem? Is there a way to assign my own rule #? (ipfw
seems not to like two adds in the same line.)
2) NAT still doesn't work. Still connected, but can't surf to
www.google.com using Firefox.
Being I am a newcomer to freeBSD, on my first install google turned up
a how to for getting my box on the Internet as a firewall/DHCP/DNS
server. Since, I've been learning the packet filtering program (pf).
Everytime I read a question on ipfw I quickly get confused.
What are the major
Robert Huff wrote:
1) when I add the nat instance, it assigns it rule # 65100. Is
this a problem? Is there a way to assign my own rule #? (ipfw
seems not to like two adds in the same line.)
2) NAT still doesn't work. Still connected, but can't surf to
www.google.com using
Christopher Cowart writes:
2) NAT still doesn't work. Still connected, but can't surf to
www.google.com using Firefox.
My kernel conf:
| options IPFIREWALL
| options IPFIREWALL_VERBOSE
| options IPFIREWALL_VERBOSE_LIMIT=100
| options IPFIREWALL_FORWARD
| options
Christopher Cowart wrote:
Josh Paetzel wrote:
I don't see much in the man page for ipfw concerning nat, certainly not the
rules you are specifying. Try man natd
NAT support was added to ipfw with the 7.0 release. You don't need to
run natd if you're using ipfw nat.
I Need to
David Alanis wrote:
Being I am a newcomer to freeBSD, on my first install google turned up
a how to for getting my box on the Internet as a firewall/DHCP/DNS
server. Since, I've been learning the packet filtering program (pf).
Everytime I read a question on ipfw I quickly get confused.
What
Robert Huff wrote:
Christopher Cowart writes:
2) NAT still doesn't work. Still connected, but can't surf to
www.google.com using Firefox.
My kernel conf:
| options IPFIREWALL
| options IPFIREWALL_VERBOSE
| options IPFIREWALL_VERBOSE_LIMIT=100
| options IPFIREWALL_FORWARD
|
Christopher Cowart writes:
Do you have gateway_enable=YES in your /etc/rc.conf?
huff@ grep gate /etc/rc.conf
gateway_enable=YES
$ sysctl -a net.inet.ip.forwarding
net.inet.ip.forwarding: 1
huff@ sysctl -a net.inet.ip.forwarding
net.inet.ip.forwarding: 1
Is the interface mentioned
On Wed, Mar 19, 2008 at 03:51:12PM -0500, David Alanis wrote:
Being I am a newcomer to freeBSD, on my first install google turned up a
how to for getting my box on the Internet as a firewall/DHCP/DNS server.
Since, I've been learning the packet filtering program (pf). Everytime I
read a
Robert Huff wrote:
Christopher Cowart writes:
Do you have gateway_enable=YES in your /etc/rc.conf?
huff@ grep gate /etc/rc.conf
gateway_enable=YES
$ sysctl -a net.inet.ip.forwarding
net.inet.ip.forwarding: 1
huff@ sysctl -a net.inet.ip.forwarding
net.inet.ip.forwarding: 1
14 matches
Mail list logo
