Hello guys! Well, I reinstalled my pfSense, and still have dual-wan configuration, but now I configured it with static WAN IPs (for WAN and OPT1). Now everything works fine. So at this time I setted up in modem-router mode my ADSL modems  ;D But the problem is that the modem router is not able to handle so many connections … I plan to install 2 old PCs for router only (pfSense or other ...) So with static WANs configuration, based on tutorials it's all OK  ::)

Your problem was not the "static port option" but more that you forgot to follow the note which is on the AON-page. Note: If advanced outbound NAT is enabled, no outbound NAT rules will be automatically generated any longer. Instead, only the mappings you specify below will be used. With advanced outbound NAT disabled, a mapping is automatically created for each interface's subnet (except WAN). –> you have to add your outbound-NAT rules manually. To avoid such problems you could create a single rule with as source "any".

Turn the static port off and see what happens. It may fix it, if those phones don't require static port. That's the only reason it would work in a default 1.0.1 and not 1.2.

So you're saying the server won't know it has any public IPs at all, it will simply have multiple private IPs? That could pose issues as the server runs cPanel and may get confused if it's unaware of what it's public IP is. Then again it might work great. I'll have to try that, I can't come up with any other ideas… Thanks!

Hi! I've found that generally access to server from behind the same NAT is impossible. Does new version of pfsense solve that problem? Is it problem only with BSD or under linux is the same? Regards, Hans

ok then..  ??? any foolproof method to fix the FTP entry one last time anyone? :)

Other than the management WEBgui: NO. And you don't want anybody but an admin to surf to a firewall. On the other hand, under the hood is a FreeBDS 6.2 install. You can do whatever you want…

I think the pfSense server redirects the port 21 traffic to its own server, and not to NAT. I see this when I nmap scanned the server from WAN, where port 21 is open to the pfSense server itself all the time

Thank you very much -) Especially I liked "port is a port" -)))

I apologize for the length of my post.  I was trying to give as much detail as possible.  I hadn't actually checked back on this topic until today but I did want to let everyone know I have managed to get the interface working, just not quite in the configuration I wanted. I had to leave my Netopia configured the same as it was previously - establishing the PPPoE connection and doing the default NAT, with its ethernet interface set up as a gateway.  PF I set both interfaces to a static IP and the WAN pointed to the Netopia gateway.  I've also left the automatic NAT rules on, not even messing with NAT.  Everything works!  I can see traffic going across the nice graph interface and have begun to try a couple of firewall rules. It isn't quite the way I was hoping the configuration would be set up, but so far since it's working fine and I've been able to test blocking addresses locally, it seems to be doing the job.  Many thanks.

Hint: Use aliases if you don't want to change multiple settings.  ;)

Hi, I succeeded into making a similar config up and running. I had to add Firewall rules on the OPT1 to allow traffic to 192.168.1.231 jy  :)

@Cry: This has previously been discussed, if you searched the archive you'd already have the answer. Firewall -> NAT -> Port Forward Assuming you're trying to direct all systems on the LAN to an external mail server on an alternate port, pick LAN as the interface, "any" as the external address, 25 as the external port range, the public mail server's IP as the NAT IP and 2525 as the "local port". Thanks. I didn't guessed this used in such way.