>ipportfw -C
># internal services
>ipportfw -A -t$dynip/80 -R 192.168.1.1/80
>ipportfw -A -t$dynip/21 -R 192.168.1.1/21
FTP will NOT portfw unless you are using the new IP_MASQ_FTP module.
Please read the new HOWTO on PORTFW for full details:
http://www.ecst.csuchico.edu/~dranch/LINUX/ipmasq/ipmasq-HOWTO-1.71-6.html#ss6.8
>ipportfw -A -t$dynip/25 -R 192.168.1.1/25
Don't portfw DNS. Either point your NT server to your ISP's DNS
server or, better yet, setup a cachine DNS server on your Linux box
and point your NT server to it. This will not only speed things up
but also fix this issue.
>but I can't connect to the other forwarded ports: 21, 25, and 110.
>
>If port 80 is forwarding correctly, why wouldn't the others?
FTP needs the special FTP module and to have port 20 forwarded as well.
DNS shouldn't be forwarded unless absolutely required. POP3 should
work.
>I would also like to be able to connect from the NT box, to the external IP,
>and then forwarded back to the same NT box. Is this crazy?
Yes. Don't to this. If this is required, you must use REDIR instead of
IPPORTFW.
>Because there
>is an external DNS name mapping to the external IP, internal clients using
>the external DNS will have to connect to the external IP as well, being
>forwarded to the internal NT box.
You should have two DNS zones. One for external IPs and one for internal
IPs.
--David
.----------------------------------------------------------------------------.
| David A. Ranch - Linux/Networking/PC hardware [EMAIL PROTECTED] |
!---- ----!
`----- For more detailed info, see http://www.ecst.csuchico.edu/~dranch -----'
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
http://tiffany.indyramp.com/mailman/listinfo/masq
Admin requests can be handled by web (above) or [EMAIL PROTECTED]
