Nice add stephen ;D I just updated the main post with another one regarding wireless NICS, which I thought useful for people setting up an AP inside pfsense

On each rule, edit, change the interface to the other OpenVPN, save.

Close this thread. The better place is here: http://forum.pfsense.org/index.php/topic,48459.0.html :)

Get the latest version from the Downloads link at www.pfsense.org. Lot of other information there, at doc.pfsense.org, in http://pfsense.org/book and elsewhere you should read up on.

@wallabybob: I know next to zilch about NETBIOS and I replied only because no one else seemed to want to have a go. If we're all having a go then…  ;) Some things I note: Bridging is handled slightly differently in 2.0.X compared to 1.2.3. Here we have two cases of a bridged WAN producing exactly the same symptoms after an upgrade. You have STP enabled on your bridge member interfaces, it isn't enabled by default on either 2.0.X or 1.2.3. You have bge1 set to 10baseT full duplex rather than auto. Is that intentional? Since bridging is handled slightly differently are all the settings correctly translated to the new config? The other post mentions a flag setting of some kind. The ifconfig output you have provided is from the working 1.2.3 install, it be good to have a similar output from 2.0.X working or not. What sort of firewall rules do you have in place? Steve

Worked Great! Thanks guys!!!!

Hehehe, tell me about it, Easter Long Weekend was the only time I was able to get this server running  :D But as to bridging the interfaces, that was the thing i had read on a few other peoples posts on the forums, as to how they've had issues, and how they got everything they wanted working "As they want it" I ended up crashing out on the foldout bed that night (didnt sleep till late the next morning, and yes, i have a spare bed in the mancave for that reason ;D) But now I have it all running, I dont want to stuff anything else up, as the XBOX360 is functioning as expected (uPnP & Port Forwarding through Pfsense as it needs it successfully), and my FetchTV is also working, the only things I am doing now is just fine tuning, like the network stack to better suit the connection (ADSL1 7610/384) My partner is also pleased that now I've set everything up and verified it all works, that I cant hog all the bandwidth now,  :( she doesnt want me to change anything, hehehehe Ive got a few documents I picked up from looking round the net on what I can do to better fine tune my connection, so it should be interesting Main thing I wanna change is the squid stuff, but I'll fix that when i get home

Just to wrap this up for any future searchers on this problem I have found a solution that works for me. With the USB SanDisk and mSata in the Soekris 6501 change the BootDrive to 81, FF ,FF, FF with the command set bootdrive=81 This forces the USB drive to boot first which then lets you install the pfsense onto the mSATA drives. To boot from the mSata drive change the boot order back to 80 which is the mSata drive with set bootdrive=80 This all works perfectly. This pissed me off all day but it works. I hate working with console cables and terminal screens! Good luck

I have live migrated the good pfsense installation (from the second Debian host without LVM) to the first Debian host with LVM (which was having installation problem).  After a reboot of the pfsense guest, there was some some disk error which leads to kernel panic. This was solved after I ran fsck.  Now the guest pfsense is running ok. Attached is the pfsense crash report after the live migration. pfsense-crash.txt

I just wanted to follow-up on my own thread to let anyone in the future know that I've resolved this issue.  I have been able to get the transparent firewall up and running with just 2 interfaces, the LAN port set to type "none" as cmb suggested, the WAN port is still a static ip address port.  I still haven't tried the LAN, Any rule yet that wallabybob suggested to allow all traffic on the local network through; I'm still using the manually added rules in the firewall to get traffic out. The ssh requirement I posted about is also working, I just had to make sure the port forwarding on my gateway was pointed to the correct address/port.

FreeBSD also won't partition the drive. LBA set in BIOS causes errors, can't format. Auto it sees the drive but cannot format, errors.

m0n0wall will have issues with both NICs on the same subnet as well, but such issues with both are intermittent generally, you're lucky if that didn't break with m0n0wall. It's not a valid or useful config anyway with any router or firewall.

sounds like you don't actually have a default gateway ("no route to host" indicates as such), though the other thing you pasted, "ping: sendto: Host is down" indicates a wrong subnet mask somewhere, or a wrong route. That indicates it can't ARP the destination host, which it won't ever attempt for an Internet-reachable host unless you do something crazy like assign a /1 mask to an interface or similar. It may also do that if it can't ARP the route for that network.

I ended up figuring it out.  It was a combination of a lot of things (rules, gateways, ips in general, etc) :D

More than 4 Gbps is out of my scope since I have 4Gbits static aggregated links between core switches. Not more. And this is more than enough.. Only thing I have tested so far was 2 x Quad Gigabit adapters teamed as single 8Gbit LACP and was fine to accepct many client connections. update: can any admin move this thread to join into http://forum.pfsense.org/index.php/topic,7668.msg122803.html ? (probably not :()

I take it that output is from the serial console? It's a known bug. There are several work arounds, this is the one I used: http://forum.pfsense.org/index.php/topic,7458.msg241783.html#msg241783 Of course to do that you need access to the box. If you have setup the interfaces on the first boot, it looks like you have, you should be able to connect to the web GUI on LAN. Alternatively you can try mounting the CF card under OSX and editing the files there. Steve

It's still a capable box, like you say easily able to keep up with an ADSL connection. The Pentium 3 Tualatin was a highly efficient CPU, when the Pentium 4 was introduced many people saw it as a backwards step. The actual CPU in the X-Core is a 1.2GHz Celeron but it has the same architecture. It uses about the same power as the X-e but has less processing power. Don't dismiss it yet. There are many users who have no trouble with the Realtek NICs. It does seem to be largely dependent on what they're connected to but no hard facts have been established. It's shiny and red!  :) Steve

Thanks, I changed on the BIOS and the installation continued. I removed the LIVEcd but it seems stuck on the configurations it doesnt get to the web interface

@stephenw10: The first thing to check is that your updater settings are correct. Go to System: Firmware: Settings: in the WebGUI. Select one of the 'Default Auto Update URLs'. Make sure you select the correct one, i386 for 32bit amd64 for 64bit, for your system. Don't select the development snapshots unless you really want that.  ;) Steve It worked. I though I tried that before though. Thank you very much.