Many times need to use the "boot from USB" option at the first boot menu you see with USB CD/DVD drives.

It means that your WAN is trying to reach 192.168.1.1 on that interface, and it can't reach it because it can't contact it via ARP. Usually that maens that IP is not actually on that interface. Perhaps you are using 192.168.1.1 as your LAN IP, and your gateway on WAN is also trying to be 192.168.1.1. If that is the case, one or the other would have to be renumbered to a completely different subnet.

You could try to take a photo of the point where pfsense stops starting on the laptop. Perhaps someone could help you with that.

OK, admit to having my head in a rather dark place here,,! Turns out I had been pressing F3, not just 3 I guess I am too used to the RHEL/CentOS console. I wonder if others are making the same error?

@UnEsxi: (As my system has no way to do this in the BIOS and using an old cable does not achieve the same thing… ) There's no such thing as a Non-UDMA cable.  The difference between the 40 and 80 conductor cable is that the former supports up to UDMA-33 whereas the latter supports 66/100/133 modes. Using the older cable still enables UDMA-33 mode; it does not downgrade the link to PIO mode.

So, next step? Have to reinstall fresh image?  Wait for final 2.0 release and hope it's fixed?

I guess so. I'm running a full install with countryblock, bandwidthd, pfflowd and siproxd on a 1GB SSD.

@ionosphere: can all settings of 1.2.3 be exported and imported to 2.0 without any problem? (my primary concern is the local user database for captive portal) Yes. (Except the traffic shaper) @ionosphere: One of the reasons that I prefer 2.0 is multiple WANs. Can 1.2.3 handle more than 1 WAN? (plus load-balancing) Yes.

I seem to be going through a similar problem – I get the same "Could not connect to the LDAP server. Please check your LDAP configuration." message -- see my post at http://forum.pfsense.org/index.php/topic,38257.0.html When I run the test, it does connect and bring up some OUs and objects for me, as described in the link, but I'm stuck at either allowing all users in the domain to log in (by manually adding CN=Users to the Authentication containers) or none, as any other group I enter doesn't seem to work. I note that you're trying to authenticate against an SBS – while I'm using a Windows 2003 standard server, the domain itself was created on an SBS 2000 server many moons ago but has since been migrated to non-SBS DCs. I wonder if the issue is the AD/OU structure created by SBS being slightly different than a non-SBS-created AD, which the LDAP connector in pfSense in its current form doesn't know how to traverse properly. UPDATE: See my post linked above for a workaround for filtering by group.

It isn't difficult. Start on the pfSense home page (http://www.pfsense.org/) and click the Downloads button ;)

It may be supported by the urtw driver but it looks like it doesn't support access point mode.  :( Steve

yes, any newer or equal version is always fine.

What Metu69salemi said is right. Most of the time, if you have a 2GB card you can use the 2GB image, but using a smaller size is safe as well. Some manufacturers have been slowly shrinking the size of flash media without changing part numbers or giving any other indication that they have changed. So if you use the 2GB image and you find that it doesn't fit, you can use the 1GB image.

Thanks, well I have 4 interfaces in it but created a lagg with them, I didn't know that by bridging the 2 you created a third interface.. :-) So, I checked this in my interfaces and indeed it is there the third one called OPT1. Now, when I assign this OPT1 to the WAN as you said, then I have assigned my external IP to the bridge, do I understand this correct now? sorry English is not my mother tongue… and I have sometimes trouble to understand what others try to explain :-)) I have it like this at the moment; thanks very much for your time to explain.     [image: Interfaces.jpg] [image: Interfaces.jpg_thumb]

From the Boot Troubleshooting Guide: If after installation, you get a "cannot load kernel" error or it hangs at the spinner (/): Make sure BIOS is up to date     Reinstall but do not check the packet mode option during boot block installation process     Set your HDD mode in BIOS to LBA (don't use "auto", the detected geometry is different if it is set to auto and it fails)     Set your HDD mode in BIOS to CHS if the above fails         Set AHCI mode in the BIOS Steve