Cannot access NAT'd services
-
WAN gateway (default GW)?
Outbound NAT? -
WAN gateway (default GW)?
The WAN is the gateway; it talks over PPPoE to my provider.
Outbound NAT?
This would be for inbound NATing; "port forwarding".
-
This would be for inbound NATing; "port forwarding".
Anyway the firewall has to translate outbound traffic to your external address. However, this is done for the hole subnet automatically by default. I.e. other services on the internal subnet would be affected too.
The POP server configuration is right to allow external connections.
You may use a packet capture tool to verify the traffic.
-
I'm having the same issues. I upgraded this morning to 2.1.1 and none of my NAT services are working.
-
I have the same problem…I just installed the Pfsense 2.1.2 i386 and NAT don't works. Anyone help?
-
I'm having the same issues.
I have the same problem…
This is an utterly useless "description" of a problem!
As for the OP here, I cannot even see how's pfSense related, except if you produced some PEBKAC like setting up a gateway on a LAN interface in pfSense… Seems like the packets don't get routed back to WAN at all.
-
And do you have a firewall on your pop3? As mentioned does your pop3 box know to talk back to pfsense to for traffic from the internet?
While your logging of the rule shows that pfsense forwarded it on.. Its better to do a simple sniff on the lan interface connected to your pop3 box so you can pfsense forward the traffic and your pop3 box answer back, etc.
-
Not sure if this is related, but sounds like it could be.
https://forum.pfsense.org/index.php?topic=75221.0 -
im having the same problem…. did u solve it?
-
I never reported back; but i was able to solve it by wiping pfSense and starting over, again, from scratch.
Sometimes the pfSense configuration just gets itself into a state.
Wiping the configuration and starting over has been the solution on four other occasions. Sometimes the UI must put the config files into an inconsistent state.
