Thank you Ermal for taking the time to answer me questions :-)

Just wanted to note that there is built in support for running commands at boot time.  You have to download the config, then edit it, then reload the modified config.  http://doc.pfsense.org/index.php/Executing_commands_at_boot_time But it looks like from the following post, that it won't work for this function. http://forum.pfsense.org/index.php?topic=27359.0;prev_next=next Just thought I would post in case anyone else has the same thought. Josh

If this turns out to "solve" the problem, you probably want to fire your ISP.  There's no way apinger will saturate a 100mbit connection.

No one could help me? I must add rule to firewall for connect to pptp?

Te correct way to configure from initial install is to do what the documentation says. You need to complete the configuration through an interface named LAN because that gets default firewall rules that allow any traffic from LAN net to anywhere. Other interfaces get rules that block everything. You can get to the pfSense documentation by following the link on the pfSense home page: http://www.pfsense.org

@jimp: That should be fine. Aside from the additional layer of NAT going on, that should be roughly equivalent to having the public IP directly on pfSense, which is really what would be ideal. Thanks for the reply. It's good to have a second opinion!

@godinperson: Guys, I think I found something. I've went into System - Advanced, Firewall and set the firewall to Conservative and checked the Disable Firewall Scrub. I had done this before but didn't reboot the pfsense since it wasn't asking. Looks like after a reboot, everything is back to normal. What is weird is that I needed to click those only after upgrading from RC3 June 21st to September 11th. See ya! Hello, I found the same thing but back on 1.2.3 release forward. SIP intervals are longer than "Normal" state clean up. Unless you adjust SIP, you will have to use "Conservative". I have changed my SIP protocol and I can now use "Normal". I just hope my SIP provider doesn't mind. Hope that helps.

ok well i gone check the mobo when i get home and see if there is something wrong. USB is disabled and LAN is also disabled to be on the safe side.

The tutorial http://www.zomers.eu/knowledge/pfSense/Pages/Configure-pfSense-2.0-RC1-to-use-Watchdog-functionality.aspx worked very well! Even though I get trap 12s on my hardware with the latest snapshot, at least i can still connect to it after a reboot when i'm not a home. I hope to solve the trap fault soon though!

Thanks Cry Havok (Global Moderator) i'm clear now. actually i was thinking or passwing 1MB VPN data on 256Kb tunnel , which was impossible thanks kalu

OK, just checked… Very simple:- Set WAN to be PPP. Set phone number to *99# Set Modem Port to be /dev/cuaU0.0 (from the drop-down list of choices) Screen shot attached. [image: example.png] [image: example.png_thumb]

@torontob: Please bring back the copy and paste of keys and certs in the same page where I create the OpenVPN server. You can keep how it's working now but also allow the old method. Add a scroll down to copy and paste your own key or cert. Patches accepted. @torontob: I never use the same key or cert for another VPN session so the management of keys and certs is really not needed. Now, there maybe some who use it with multiple vpn server  ??? but I think the amount of work put into VPN wizard and now distributing it all over the GUI has not really made it any easier. To the novice user it's still very hard. To the experienced user you have to still go back and check your notes and play a few times until all works. It's not harder. It's harder for you, perhaps, but the system is a lot more powerful and easier for most (and pretty much everyone else agrees it's better). As the old saying goes, you can't please everyone. @root2020: What may be nice is an area on the website dedicated to 2.0 documentation and one dedicated to 1.2.3. You mean like the one we already have? :-) http://doc.pfsense.org/index.php/Category:2.0 @root2020: All this stuff seems to work great but documentation in usually difficult to find for new users of 2.0. You mean clicking the blue "?" help icon on every page in the GUI is difficult? :-)

????

@KeepGood: Reply from 192.168.1.1: TTL expired in transit. That suggests to me a routing problem. It would probably help to draw a diagram of your network and check that each system on all the paths of interest is able to forward packets correctly - you might need some additional routes. The traceroute tool might also be useful to help determine if your routing is correct.

@Wolfsokin: You can turn the localhost off as a dns server by checking the box "Do not use the DNS Forwarder as a DNS server for the firewall " in System: General Setup and see if that changes anything. It works. Thank you very much. It is interesting that the forwarder was still in effect even if it isn't enabled.