On Mon, Sep 19, 2011 at 1:37 PM, Jim Pingle <[email protected]> wrote:
> On 9/19/2011 1:25 PM, Jesse Vollmar wrote: > > Sounds like you are hitting this: > > > > > http://doc.pfsense.org/index.php/Why_does_enabling_NAT_Reflection_break_web_surfing%3F > > > > Jim > > > > _______________________________________________ > > List mailing list > > [email protected] <mailto:[email protected]> > > http://lists.pfsense.org/mailman/listinfo/list > > > > > > > > That seems like it might be the problem. We had multiple port forward > > rules for internal web servers. How do I go about just disabling NAT > > reflection with no access to the GUI? > > If you have ssh access, setup an ssh port forward to get to port 80/443 > on localhost and go that route. If you only have console access, it's a > bit trickier, you'd have to hand edit the config and change the > reflection setting, then reboot. > > It usually lets you get to the firewall's IP though even in cases there > the port forward isn't right. > > Jim > _______________________________________________ > List mailing list > [email protected] > http://lists.pfsense.org/mailman/listinfo/list > Resolved. Thanks so much for the quick replies. I was already editing the config.xml manually before I even got your second reply. I had to add a line: <disablenatreflection>yes</disablenatreflection> inside the <system> block.
_______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
