Comment FreeBSD -not- Linux ... read his original question (Score 1) 212
In his original question, he states he's using FreeBSD and NAT (the natd daemon). NAT on FreeBSD is similar in concept but not in usage to IP Masq on Linux.
While most answers here would be greatly helpful if he were running Linux or had an old Mac lying around, he may not.
We have clients using both FreeBSD and Linux, and here at my office we use FreeBSD 3.1-RELEASE for our NAT.
With NAT properly configured, ICQ, DCC, IRC, Half-Life TFC, Quake 3, anything else I can think of - all work without any problems.
Follow these steps (this is FreeBSD not Linux):
If you're using 3.1-RELEASE or better, you're 90% of the way there.
1. Set GATEWAY="YES", NATD="YES", FIREWALL="YES", FIREWALL_TYPE="open" in /etc/rc.conf
2. Rebuild the kernel to include IPFIREWALL and IPDIVERT.
Rebuild the kernel and you're all set. Reboot.
-Hivelord
While most answers here would be greatly helpful if he were running Linux or had an old Mac lying around, he may not.
We have clients using both FreeBSD and Linux, and here at my office we use FreeBSD 3.1-RELEASE for our NAT.
With NAT properly configured, ICQ, DCC, IRC, Half-Life TFC, Quake 3, anything else I can think of - all work without any problems.
Follow these steps (this is FreeBSD not Linux):
If you're using 3.1-RELEASE or better, you're 90% of the way there.
1. Set GATEWAY="YES", NATD="YES", FIREWALL="YES", FIREWALL_TYPE="open" in
2. Rebuild the kernel to include IPFIREWALL and IPDIVERT.
Rebuild the kernel and you're all set. Reboot.
-Hivelord
