You could try disabling services/packages one by one until the problem goes away.

The symbol in the column "Act" shows you, what happened to the connection. If you click on this symbol, you will get the rule, which caused this action. If you click on the red/green symbol with the little black plus, this IP will be added to an Alias and this Alias will be added to your firewall rules.

This forum does actually have a working search function ;) http://doc.pfsense.org/index.php/What_are_the_512M,_1G,_2G,_and_4G_NanoBSD_files%3F

If it works, it's fine. Usually it will work, since it's still 7.x, but there is always the chance that a given program will want a newer base system library that doesn't exist on 1.2.3. It shouldn't hurt to try it.

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