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.

Awesome . Alright thanks for ur help …

Ill be more specific. here is my setup 10.10.1.0\24 Internet –-> pfSense (LAN INT 10.10.1.254\24)------>LAN --------> Home PC (10.10.1.200\24)                         |      DMZ INT (10.10.2.254\24)                         |                         |           DMZ (10.10.2.0\24)                         |                    Web Server (10.10.2.100\24) When i try to ping from Home PC to Web Server: Pinging 10.10.2.100 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 10.10.2.100:    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss) However when i ping using the pfSense ping tool Ping output: PING 10.10.2.100 (10.10.2.100) from 10.10.2.254: 56 data bytes 64 bytes from 10.10.2.100: icmp_seq=0 ttl=64 time=0.689 ms 64 bytes from 10.10.2.100: icmp_seq=1 ttl=64 time=0.372 ms 64 bytes from 10.10.2.100: icmp_seq=2 ttl=64 time=0.307 ms --- 10.10.2.100 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.307/0.456/0.689/0.167 ms same story for pinging pfsense on my Home PC: Pinging 10.10.1.254 with 32 bytes of data: Reply from 10.10.1.254: bytes=32 time<1ms TTL=64 Reply from 10.10.1.254: bytes=32 time<1ms TTL=64 Reply from 10.10.1.254: bytes=32 time<1ms TTL=64 Reply from 10.10.1.254: bytes=32 time<1ms TTL=64 Ping statistics for 10.10.1.254:    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:    Minimum = 0ms, Maximum = 0ms, Average = 0ms And for pinging my Home PC from pfSense: Ping output: PING 10.10.1.200 (10.10.1.200) from 10.10.1.254: 56 data bytes 64 bytes from 10.10.1.200: icmp_seq=0 ttl=128 time=0.446 ms 64 bytes from 10.10.1.200: icmp_seq=1 ttl=128 time=0.309 ms 64 bytes from 10.10.1.200: icmp_seq=2 ttl=128 time=0.316 ms --- 10.10.1.200 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.309/0.357/0.446/0.063 ms I can also ping pfSense from my ubuntu Web Server PING 10.10.2.254 (10.10.1.254) 56(84) bytes of data. 64 bytes from 10.10.2.254: icmp_req=1 ttl=64 time=0.261 ms 64 bytes from 10.10.2.254: icmp_req=2 ttl=64 time=0.209 ms This is a base pfSense install with the default Lan -> any rule being untouched. Insert foot in mouth Was on static IP with no gateway. Figured it would work for some reason. Set it to DHCP and it works.

@papou: I bought an other usb wifi with a RT2770 to see if work better….. I keep you informed Papou So i bought an "High Power 802.11a/n/b/g 300Mbps USB 2.0 WiFi Wireless Network Dongle" by Kinamax (26.50$ at DealExtrem Shop…) and it work perfectly in WPA2. So my ARGTek has clearly and incompatibility problem with FreeBSD. ;)