Thanks I changed the server address to 192.168.20.1 and it worked.

I'm offering it as a suggestion rather than a request, that and I don't have money to put on something like this. I do offer my time in designing / spec'ing this however.

@superwormy: Now, I realize that a firewall rule could be used to stop this. HOWEVER, SecurityMetrics requires us to have a rule which allows all traffic from them through- i.e. I can't just put a deny rule to reject UDP port 53 from the WAN. Is there a way to turn this off in pfSense 2.x so that we can pass our PCI scans? How do others get around this? I also got the same errors on SecurtityMetrics scan, but I don't see anywhere where they dissallow firewall rules that apply to everyone.  You have to exempt them from any IDS/IPS system which makes sense, but they are testing the firewall as well as everything else.  Deny rules are how firewall's work.

Yeah, I just spliced cables to get the DSL modem in the same room as pfsense, works fine now. Signals aren't the best, but get very close to my advertised speeds(which is rare for at&t dsl lol)

Congrats! :)

No problem. I'll be there ;-)

@jimp: Any particular reason? Or just a matter of preference? Just preference really, I know it sounds silly but it's just how I wanted to do it. Even though it would work with bridged networking, it just isn't very ideal.

I'm running the IPV6 snapshots… I did try from console, Mac (Terminal) and Windows (puTTY)... and I was quite frustrated when I originally posted... 2.0-RC1-IPv6 (i386) built on Fri Apr 8 18:33:38 EDT 2011 I just tested "o" and it works just like it should, "i" on the other hand doesn't, it will either capitalize the first letter of the line, or randomly jump around. Either way, its not a big deal, my problems have been solved. :)

So open up /tmp/rules.debug and see what is on the lines it's talking about. Usually the macros it's referring to are for interface names and so on.

I have also seen that message with bad media, not just full media. So be wary that even if your disk doesn't appear full, you could still have a problem.

Thanks! I think that answers my question. Generally speaking, have you noticed any other issues with using Windows 2008 DNS servers with pfSense? Thanks again!

No way to make it "permanent" on any install as it would be overwritten on every upgrade. I had thought you could pkg_add -r openssh-portable, but that appears to only be at version 5.2p1.

Ok, i sloved the problem. The box died. I still have no clue why it allowed that single connection but the box was dead when i checked on it the following morning. I went to restart it and it couldnt even load BIOS.

I see, thanks a lot for the answers! Cheers

Talked to the ISP and they've had a look and reset the password and I'm now getting the static IP. I've changed the password again since and the IP's sticking so seems to be sorted.

well I finally figured the problem out. Wasn't a bad nic. I could ping google from wan, lan and wlan, but could not access with computers on each *lan. so, I reset my settings from scratch and started over, works great now the internal routing mechanism stopped working right. Never sure what exactly was wrong, but somehow pfsense internally f'd up enough to partially route intermittently.

Couldn't get bridge mode working : / I don't know, pfsense never got an IP, put it in PPPOE on the interface, put correct username and pass, but could never get an IP… oh well, stupid DSl being on 192.168.1.254 and not awesome like cable and being 192.168.100.1 lol

That's typical of switching a time zone and then not rebooting/restarting a process. Processes only pick up a new time zone when (re)started.

Guess I can narrow down my problem. It seem's to be a DNS problem and I'm able to browse site's like: www.google.de, www.youtube.de etc. Since my SDSL need's a static IP and I'm not receiving any DNS IP from my provider: 1. I've set up manually two DNS IP addresses - 8.8.8.8 and 217.237.151.115 in the "General setup" and assigned them to the WAN interface 2. Unchecked the option "Allow DNS server to be overridden by DHCP/PPP" 3. Enabled the DNS forwarder because of the note: "The DNS forwarder will use the DNS servers entered in System: General setup or those obtained via DHCP and …" I was able to use my MacBook for pinging my WAN interface, my WAN gateway and 8.8.8.8. But it was not possible to browse like www.google.de. 1. Then i added the DNS IP to the Service: DHCP server under DNS servers: 8.8.8.8 and tried again. It worked... 2. I've deleted the assigned DNS IP's on the "General setup" and it worked either Now the question: Did and do I understand the option of the "General setup" with the entering of the DNS IP's and assigning them to the WAN interface in a wrong way? I have a second WAN connection from T-Online and want to use it with the LoadBalance but with the DNS IP's given by this provider and not by the Google DNS IP's. Using the option of entering a static DNS IP would mean, my DHCP will push allways the DNS 8.8.8.8, wouldn't it? Cheers