I just finished troubleshooting a similar issue. It seems that once pfSense was installed, there was no gateway setup. We had to add the gateway, and then select it as "default", then reset the firewall state. At that point everything worked as expected. The odd thing was that we had a 1:1 inbound mapping setup, and that worked fine without a gateway. This definitely threw off our troubleshooting path a bit. Hopefully this helps someone.

hi spiritbreaker.. i'm still dealing around with this problem and it's difficult since i can't access internet all the time, at least for the moment… but hey, thanks for your reply.. what about the (outbound) nat rule you & azzido had to create.. because local networking is allright, but this (outbound traffic with ipec-ip's) may be one of the causes, why i have outbound problems.. still changing the local network to none solved the problem with the routing table, i.r. routing all traffic trough tunnel. thanks for your help, man.. S.

Just installed it yesterday trying it out for the local lan only to block p2p especially bittorent. Works REALLY nice. Great and easy interface! Thanks for this awesome work!

Externally keeping track of who the voucher codes are given to could probably also be a way to take care of that.  Even if someone else used the code, you would still have the information of someone it belonged to.  However, I can see uses for this when you might let people get codes on their own, either from a system you have out for this purpose or just preprinted cards you give out with codes on them.  The system for actually registering the user name and associating their information and the voucher code with it would likely be out of the scope of what will be supported, though - especially for the 2.0 release.

I have tried to enable polling but that cause the WebGUI almost impossible to work with… I understant why the CPU get to 100% all the time when polling is enabled, but something must be wrong is slow down everything else... Yes the polling does lower the interrupts usage, but then without any traffic at all the WebGUI is too slow to be workable.

Selecting an existing CA (internal or external) should be OK now in the wizard. It won't be in the next snapshot, but it will be in the one after that.

@gnhb: I'm interested in this also. Ermal and Chris, do you have any ideas or suggestions about the GUI and backend design for this feature, or where the GUI would even fit in to the menu scheme? Not sure. Status>Interfaces isn't exactly intuitive for something like that, but probably the best place I can think of. Don't want to add yet another menu item just for that. @gnhb: Ermal is right, it shouldn't be too hard to do. That serial port utility I was going on about a few months ago would be a handy tool for this situation too. http://forum.pfsense.org/index.php/topic,23955.msg128271.html#msg128271 Any news on that? No plans for any changes there in the near future.

Good to know, thanks. That's why I didn't report it earlier since I figured I'd wait and see if it was a temporary issue :-)

Odd. Glad you have it working…I didn't mean "anywhere" but rather your NAT rule can only be defined with a source interface and not more specific (thus "from anywhere, as long as it's on this interface"), and further restrictions are at the firewall rule level.

You'll be fine to upgrade to final release. We have numerous production installs on 2.0 out there that we're supporting, so we're making sure that's a smooth transition.

Yeah you may get bit by some bugs with gateways if you're upgrading from early 2.0 releases as Efonne said. Going from 1.2.3 straight to 2.0 now is fine, but if you were on 2.0 from several months ago or older, you can hit that. After you fix it, it won't recur.

@wallabybob: Previously configured Service Provider information is not displayed when an interface configuration is edited after saving a previous configuration. That part is actually by design - it does not store your selection there, it only fills the appropriate settings for what you select. Not the best design though IMO. http://redmine.pfsense.org/issues/830

This turns out to be less urgent than I thought.  My wife incorrectly told me it was sending everything out their VPN - in fact the whole issue is they are putting their DNS server in, so it bypasses the split-DNS setup.  I hard-coded her webmail URL with the IP address and she is okay.  I'd like to know why this happens though…

for faster response use the paid support options that are available,, the forums are where people donate their time and expertise when they can. like dreamslacker stated, you dont need two devices, just set up a dual wan config without the load balancing, but possibly with failover. there is a wiki on how do both.

@peterclark4: Am I right to assume that I should keep an eye out on http://redmine.pfsense.org/issues/729 before trying to upgrade to a newer snapshot? yes

@horsedragon: Now ipsec VPN client(such as shrewnet) can work fine with the newest snap version? yes