Learn to look through the code, matrix style!  :P

The config file to look at is: http://www.pfsense.org/packages/pkg_config.8.xml

Any package containing <noembedded>true</noembedded> can't be run on Nano. However some that can, Squid for example, are very restricted.

Packages that can't run on nano/embedded look to be:
pure-ftpd
ntop
Light Squid
Freeswitch
phpSysinfo

Steve

When you're booted, from a shell, try this:

/sbin/sysctl kern.geom.debugflags=16 gpart set -a active -i /dev/ad0s1a ad0 /usr/sbin/boot0cfg -s ad0s1a -v /dev/ad0 /sbin/sysctl kern.geom.debugflags=0

Assuming your drive is ad0

Or you could try running "boot0cfg -B" on its own to replace the MBR.

Or failing all of that, backup your config, run a low-level format on the drive from start to end, and reinstall. That would be the last resort "dust off and nuke it from orbit" option.

You probably need to bridge the WAN and LAN if your servers inside have to recognize it's own IP. If you need an internal network too then add a add a second interface for it.

I think that most use a second interface OPT1, renamed DMZ or SERVERS etc. as the Bridged interface and the LAN for a NAT internal network. The Book has some info on setting up a bridge, and I am sure there is some info online etc.

There are some routing challenges between the networks in this senario, because you gateway is now your ISP's router and that won't know how to get to your internal LAN network.

If you don't need a second interface then just bridge the WAN and LAN.

Select Interfaces -> Assign: Select 'Bridges' tab and click the + in the grey box to assign the bridge. Select WAN and LAN and away you go. Only click advanced if u know what you are doing.

Hope this helps.

Thanks for the assistance.  I RTFM'd on the VM front so now have a better understanding :O) and it works.

@jerfeb2oo9:

I think the IMAGE FILE of the pfsese.iso is missing, cause when i extract
it i didn't see any image file in it.
what should i do to that?
please reply :-[
[/quote]

You must be downloading the wrong file then. Get the iso from a mirror of your choice here:
http://www.pfsense.org/mirror.php?section=downloads

Hi there,

Take a look at all of these:
http://forum.pfsense.org/index.php?topic=11217.0
http://forum.pfsense.org/index.php/topic,9382.msg59670.html#msg59670
http://forum.pfsense.org/index.php/topic,10926.msg60878.html#msg60878
http://doc.pfsense.org/index.php/Access_Point2
http://doc.pfsense.org/smiller/pfSenseQuickStartGuide.pdf

Explanation, compatibility, troubleshooting and tutorials.

KR,
Canefield

It doesn't go away until you acknowledge it. That message means something in your config was corrupted, which is generally impossible short of buggy packages. Some more context on what you were attempting, what's in the system log from around that time, and any more details on exactly what you're trying may be helpful.

I did this on a FreeBSD 8.1 server and had to install and tweak a load of stuff to get this working but if you already have a functioning Apache server then you may need only the two lines you mentioned.
Make sure you test it as shown.

Steve

There is no .bash_history because the shell isn't bash. If you set the items ccesario noted, your history will be saved across logins and visible by running 'history'.

It's unlikely to be that since this is immediately after installation and the serial console is not enabled by default.
Interesting solution though, I'll have to remember that for future trouble shooting.  :)

Steve

@cmb:

that's never been permitted. can either very carefully manually edit the config with viconfig and make sure you don't orphan any references, or backup the config and do the same edit and restore it.

I imagine it's easy to miss something and find yourself without a gateway (or worse).  ::)

Steve

@Itwerx:

Do a hard reset and boot to single user, shell, whatever, and add these lines:

kern.ipc.nmbclusters="131072"
hw.bce.tso_enable=0
hw.pci.enable_msix=0

…to /boot/loader.conf.local, as per this article, (note that I misread the article and added them directly to /boot/loader.conf with no ill effects - and I'm sure as hell not changing them now!):

The boot loader processes /boot/loader.conf then /boot/loader.conf.local. The first file COULD be overwritten by a firmware upgrade, the second shouldn't. Therefore to "future proof" your system you should add those lines to /boot/loader.conf.local. There should be no harm in having duplicate entries.

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