????

@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. ;)

Hi, i already change the IP from 192.168.1.0 to 2.0 for optional 1 and it works.now i can ssh my server….thanks for the reply and help :D

I drawing of the network, with subnets, would help us a lot.

Yes, we have got movement in the rules. Vnc works! Thanks for your help. Now gradually moving machines and rules to pfs. Default gateway change. Also we have to get it working with 2 isp's

So, can someone shed some light on that setting - what's its value (as I would think you'd always want Unique - thus I would have expected that to be the default). Thx.

Gilrod, Just a word of caution. I've run into the same problem on 512 MB images and 1GB images as well. Depending on your uptime and how much as been written to logs, etc, the 1GB image is not a guaranteed safe workaround to this problem.

http://forum.pfsense.org/index.php/topic,29660.msg163436.html#msg163436 If you create a /conf/mpd_wan.conf file according to gnhb's instructions then you don't need the dummy interface and your ppp log file won't fill up.

I am very sorry but this may caused by my computer hardware. I have successfully install pfSense on another computer with the same hardware. I will do something more to determine which hardware is broken. However, that computer can run pfSense 1.2.3 perfectly.

@ermal: There is a advanced setting controlling that behavior now. Could I find the answer from any documents like http://doc.pfsense.org/index.php/Category:FAQ ? I have also tried the floating rule with the following setting: action=block disabled=false quick=true interface=did not select any options direction=any protocol=any source=192.168.13.3(the target) destination=any All the settings that do not listed are default.However, the result is fail. Thank you. ;)

now on 2.0-RC3 (amd64) built on Thu Sep 8 15:43:15 EDT 2011 - problem solved!

Hi Steve, thanks for that hint. I didn't see this before. I'll give it a try. Great, thanks. Tim

What was the problem? you could also edit first post subject with [SOLVED]