Weird, every other router I've used forwards all the packets properly, even my backup linksys when I hook it up.
Really I don't want to do the split dns stuff, sadly I will have to move away from FreeBSD for performing this operation I guess. Thanks for the help! CW. -----Original Message----- From: Greg Barniskis [mailto:[EMAIL PROTECTED] Sent: Thursday, December 29, 2005 3:05 PM To: Chris S. Wilson Cc: freebsd-questions Subject: Re: NATD Internal Network problems Chris S. Wilson wrote: > Hello! :) > > I am having a problem with freebsd 5.3-release and natd. > > When I try to connect to a service on my internal network to an IP on > my external network that has a port redirected, it wont connect. > > IE: 67.128.100.2 is my external IP, on my internal network I try to > connect to 67.128.101.2:80 which is forwarded in my natd.conf and the > connection is refused. > > Does anyone know why? I don't know the exact technical reasons "why" but I will confirm for you that this simply does not work, and the reasons why center around it being a rather tortured mess. Your inside machines should reach your inside server by its inside address. Think about how you're sending your request outside the firewall (getting the request NATed on the way out) and then back in (getting the request re-NATed), and then having the reply packets from the web server have to take the reverse of that path. Yuck. Use split DNS so that that "www.example.com" appears to external clients as being your external NAT server address, and appears to inside clients as the web server's real inside address. -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) <gregb at scls.lib.wi.us>, (608) 266-6348 _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
