PFSense 2.1 Release - NAT Reflection not working
-
When would you be available to do a Team Viewer session and try to figure this out?
-
What part of the world are you in Daniel?
-
Utah (Mountain Time) Currently UTC-6.
-
Perfect. Catch you on PM.
-
Problem solved!
-
I'm dying with curiosity - What was the problem?
-
On the LAN interface configuration under Static IPV4 Configuration, the gateway should be set as none but I had it set to an internal address on my network. I guess it confused PFSense or something. The fix was to set the gateway back to "none".
Thanks to Supermule for solving that one!
-
Really? I never would have guessed:
Second page of thread, halfway down:
"I've seen that gateways have been renamed or changed mysteriously upon upgrade by some.
In one case it just killed his RRD data.In another case the gateway inserted its self into the openvpn and WAN firewall rules.
Could some sort of gateway rename/change/insertion have happened to you?
I'm reaching…"
haha - But yeah. I think supermule would have known it anyway.
I'm going to put the words "please ignore this" at the bottom of all my posts from now on. ;D
-
It was a pleasure working with Daniel and nice to meet a fellow pfsense'r!! :)
-
Really? I never would have guessed:
Second page of thread, halfway down:
"I've seen that gateways have been renamed or changed mysteriously upon upgrade by some.
In one case it just killed his RRD data.In another case the gateway inserted its self into the openvpn and WAN firewall rules.
Could some sort of gateway rename/change/insertion have happened to you?
I'm reaching…"
haha - But yeah. I think supermule would have known it anyway.
I'm going to put the words "please ignore this" at the bottom of all my posts from now on. ;D
Well, the difference is that it didn't somehow change during an upgrade or something, I set it that way thinking that was the way it was supposed to be set. I did pay attention to the above statement but when I checked the gateways everything was as I set it.
-
Haha - Just giving you minor crap…
I can see that happening. Just yesterday I didn't think I could effectively run several websites off my one IP and kurianoftheborge (or something like that) set me straight. (At least I think so - haven't tried it yet).
-
Why cant you do that? Its either controlled through pfsense or the webserver delivering the sites :)
-
I'm not a website admin guy so yeah - Lets just say its new info to me. I've not ever had a need for a reverse proxy, but if I did, clearly that would save me some $$$.
-
Its only needed if you deliver sites to different servers. If you have only one webserver with multiple sites, its fine with one ext. ip.
-
Well - As of yesterday I understand it it fine, but the day before that I didn't know that a reverse proxy could work with HTTPS like that. Every day its something new…
-
Hi all,
I would like to ask a question. When enabling the NAT Reflection mode for port forwards to NAT+proxy in pfsense 2.1 stable, does it break the ftp proxy helper? I am trying to login through ftp to a device (from outside my network) with passive mode, with only port 21 forwarded to the IP of the device on lan (outside port is 57483) , but i get error on passive mode on filezilla client, like the many errors i have found for the ftp problems in posts on this forum. The problem is that the nat helper does not automatically configure the range for passive transfers, so i should disable the helper and forward a range of ports, but i would prefer this done automatically.
Thank you.
-
Hi all! I have same trouble, but my lan gw is already none.
Simple config, i have two int WAN and LAN, pfsense is VM, 64bit.NAT:
WAN TCP * * WAN address 15555 10.20.0.253 15555Firewall:
IPv4 TCP * * 10.20.0.253 15555 * none NATPortforward not working.
-
Same here. Nat refelction isnt working :/
-
Having trouble. I'm at work and connecting to my home internal networking using SSH localforward-ing.
Failing Scenario: (Me at work computer) Chrome with Proxy SwitchySharp (SOCKS5 or localforward SQUID) -> trying to connect to a web interface (synology disk station) using public ip address and port -> fail/timeout.
Working Scenario: (Me at work computer) Chrome with Proxy SwitchySharp (SOCKS5 or localforward SQUID) -> trying to connect to a web interface (synology disk station) using private ip address of the synology disk station and port -> success.
Any ideas how to get this working?
-
Is your Synology using port 5001 as of the webinterface? Normally not. Set it to HTTP instead of 5001 as the target port redirect.