@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:

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!

sometimes rebooting wont be necessary, just disable then enable an Interface will do.

its like issuing administrative shutdown and power up to the interfaces.

if you have a spare ps/2 use it, for the sake of installing pfsense on your box.

@stephenw10:

The only thing that has happened since is that you rebooted the box, something that I said shouldn't be necessary but Wallabybob recommended.

My experience has been that things like moving a subnet from one interface to another and deleting a conflicting subnet from an interface seem to require a reboot to take effect. They are probably not things experienced users do regularly.

@stephenw10:

Also I can see that I made some assumptions early on that turned out to be wrong. A lesson for me there I think.

Often problems are reported with inadequate information so it is necessary to make some assumptions to get started. After a few request/reply exchanges with nothing conflicting with the assumptions its easy to forget that the starting point was assumptions.

@hezten:

all 3 options throws me to mount root terminal, even though i hit 3 in the menu (the boot from usb device option)

PERHAPS your box has a USB connected "disk device" (such as a SD card reader) that is found on the bus BEFORE the boot device. That would cause the boot device to become (perhaps) /dev/da1 whereas configuration script would be expecting the boot device to be /dev/da0.

@hezten:

Is there any other way to install this ? I cant seem to get past the mountroot shell / terminal.

What is reported if you type a question mark then hit the enter key? You should be able to continue by typing the correct string to that prompt but I can't tell you what the correct string would be since I don't know the device configuration of your system. In the case of you moving a hard drive from another system the boot drive probably changed ints unit number, for example, it might have been  /dev/ad4 in the install PC and then became /dev/ad6 in the target PC. After typing the correct device string to the mountroot prompt the startup should contnue, then when get the console menu type 8 to get a shell prompt then edit /etc/fstab to specify the correct partition for the root file system.

Hi,

bgp shows his log lines in System => Routing.

you can also go onto console and run config check manually:

[2.0.3-RELEASE][root@fw2.jws1.local]/root(19): bgpd -v -n -f /var/etc/openbgpd/bgpd.conf
/var/etc/openbgpd/bgpd.conf:4: syntax error
<… more errors/config file informations>

(on this firewall I have BGPd deactiavated by writing wrong content in ;))