You could try a 2.1 RC snapshot. Chances are either one of two things is happening: 1. The other changes on 2.0.3 are interacting poorly with that NIC 2. The other changes on 2.0.3 are driving that hardware a little harder and exposing some other electrical issue The base OS on 2.0.1 and 2.0.3 is the same, but some drivers were updated there. The base OS on 2.1 is a bit newer and has even more recent drivers, so it would be the next thing to try.

Maybe may last posting is a bit long. That's why I ask in short terms: Is there anybody out there who could solve the "/tmp/filterdns_cpah.pid" issue by gitsyncing? For me it did not work. Peter

Hi, My observations:   CF card detected by BIOS during cold and warm boot   CF card detected by FreeBSD only after warm boot Changing hw.ata.atapi_dma="1" in /boot/loader.conf (did it directly using vi hoping that is ok) gave the same results as above. I changed from 2.0.2 to 2.0.3 and have the same issue. (I don't know why 2.0.3 don't give me a loop anymore, but I added bs=16k when using dd) My Lexar 4GB CF card is 80x (which I calculate to 12MB/s) I have also tried with a SanDisk 4GB 30MB/s (which I calculate to approx. 200x) (I base my calculatons on a 1 gen. CD-ROM reading at 150KB/s, correct or….?). Using the Lexar CF I have to wait several seconds after BIOS have counted onboard memory. 5-10 secs. There is no waittime when using the SanDisk CF,  FreeBSD starts right away. Without going into much detail the Sandisk gives a completly different error which I won't add to this thread. One question pops up. Does it matter that they have different metrics, while both claims to be 4GB, BIOS shows the LBA differs? From BIOS: Pri Mas  LEXAR ATA FLASH CARD            LBA Xlt 971-128-63  3915 Mbyte Pri Mas  SanDisk SDCFH-004G                  LBA Xlt 968-128-63  3906 Mbyte Regards, Bjørn

Excellent suggestions, Steve and that moved me much further along: after running the 2.1 snapshot, the text scrolls down the page as it should and the system didn't hang at SCSI-0. We got all the way to "Do you want to Proceed [y:n] which after I entered "y" displayed "Writing configuration…". Unfortunately this is where the system hung. I searched the forum and found a post where someone else experienced this "Writing configuration..." problem and they solved it by auto selecting the interfaces instead of entering them manually; however, for me that produced the same problem with a freeze at "Writing configuration...". It appears like it's not recognizing the NIC. Has anyone had this problem? Regards,

Thanks Stan! I can't believe I forgot to do something so simple. Oh well, now I get to play with it :D

@PistolPete: Not sure how that issue is related to mine.  I got the NSSwitch problem immediately after upgrading, but it disappeared just as quick. My issue was the Pfsense kept sending multiple copies of the same line Also, I upgraded to the latest Beta as of 25th June and it's solved the problem and I'm back to 8MB log files again, so whatever the problem was has been fixed…...either that or maybe the old fix for repairing the broken Syslog where is breaks lines in two no longer works correctly as i've not applied it. I've probably not got what the "multiple copies of the same lines" really mean in your syslog as this is particularly true for the "NSSWTICH" entries. Maybe your initial description has been a bit to abstract at least to me - a few lines from your syslog could have clarified it :). Nevertheless, it seems unclear why your syslog problems have gone with 2.1 beta. If you're still interested in getting it solved, you'll probably have to send some representive parts of your multiple syslog entries. Peter

Thank you.

I understand, thank you. I'll try to

Can you run the install from the console and then try to do the assignment after rebooting from the hard drive?

DONT TRY TO FIND YOUTUBE IP. LOL i been try before. massive of them on this earth.

Some code not got the correct permissions? Are you not seeing an error when you try to load pkg_tester.php? In the server logs? I have done this but it was a while ago. I do remember having a number of difficulties getting it up and running but nothing specific to this. Steve

I ran into this same problem, my issue turned out to be a comcast captive portal.  It was a bit more subtle than I would have expected, they were only giving the captive portal to my PFSense box, everything else on my network had full connectivity. Google didn't find that as a possible solution so I thought I'd dump it here. Kilgore

Thanks so much for the help stephenw10 & wallabybob! Really did help answer a lot of my questions! The good news is…. I managed to get it all working, only as a test run though.... I allowed the WAN IP to be set by my BTHH's DHCP to 192.168.1.102, and as you both suggested I run the LAN on a different subnet, I put the LAN on 10.0.0.1, and enabled DHCP on the LAN interface, maybe when I choose to run it full time I will set the WAN to class A and LAN to class C, not the other way around ;) I did Ipconfig and it came back saying I got the IP 10.0.0.10 which is the start of the DHCP rule, so that shows that DHCP is working, which is great! I'm waiting on a new modem to come though the post, I've read on this forum in posts that its one that will work with a ADSL2 line and support the BT PPPOA authentication aswell as PPPOA bridging! So hopefully, when its all going as it should, I hope to have my WAN IP as my Public IP, and my LAN IP set to class C. As stephenw10 suggested, having double NAT could be a pain. Especially because I do allot of port forwarding, so thats why I want the WAN to be set up for the Public IP, and therefore I dont have to run the awful BT Home Hub!  ;) The only thing I'm left to now is to learn how to use all the great features that PFsense has to offer! I know forums are made for questions and support, but I really do appreciate both of your help. Many Thanks, Josh.

It's directly in the root on the file system so you would type at the command line: cd /tmp But why are you trying to get to /tmp? There is no need to do that to get the LCD working. Steve

is there any update on this one?

after many & many & many check. I simple recreate OpenVPN server with differrent network number and it's work fine. I don't know why… but it's work! mattia

Looking at that spec page it looks like you are seeing the output of the console redirect bios code, you are seeing the POST information. However is says that appears by default on com2. As soon as the kernel loads it will switch the output to com1. Could that be your issue? Steve Edit: A bigger problem is that that board has only 16MB RAM which is, unfortunately, far too little for pfSense. Minimum requirement is 128MB is believe. Perhaps m0n0wall would be a better target OS? Edit2: Even m0n0wall recommends 64MB. Perhaps OpenWRT then.

Didn't realize this.  Makes perfect sense now.  Appreciate the response!