Date: Thu, 1 Nov 2001 12:25:14 -0600 From: Chris Davis <cdavis@aspv.edu.mx> To: freebsd-questions@FreeBSD.ORG Subject: can't see port redirect from inside Message-ID: <jUsT.aNoTheR.mEsSaGe.iD.100463948913377@webmail.webserver1010.com>
next in thread | raw e-mail | index | archive | help
Ok, so I have a FreeBSD box that is running ipfw and nat which accepts traffic on port 80 just fine on both inside and outside interfaces. I have a port redirect that takes http requests on port 5040 and shoots them to an internal web server. this works fine from the outside but does not from the inside. Why? example: If 192.168.1.3 types http://192.168.0.1:5040 into their browser it doesn't connect. But if 192.168.0.2 types http://192.168.0.1:5040 it works like a charm. I have looked for other posts on this topic but all I have found is some business about running two copies of natd and some other stuff about training my users to type in the inside address when on the inside and the outside address when at home. I don't want a split DNS either. Where is the elegant solution that I'm looking for...like "just do a route add blah blah blah..." ------------------------ Outside__________________| some remote machine | | | 192.168.0.2 | 192.168.0.1 ------------------------ -------------------- | Fbsd box NAT | | | -------------------- 192.168.1.1 | ------------------------- |_____________________| some local machine | | | 192.168.1.3 | --------------------- -------------------------- |internal web server | | 192.168.1.2 | | | ---------------------- My /etc/natd.conf redirect_port tcp 192.168.0.2:80 5040 Thanks ahead of time Chris Davis Maestro de Computacion Colegio Americano de Puerto Vallarta To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?jUsT.aNoTheR.mEsSaGe.iD.100463948913377>