To build images and such, yeah, those steps work great – but that's done from a FreeBSD box these days and not from within a "Dev ISO" environment.

This is really embarrasing..

it was just an broken nic… so i bought a new one and it works like charm!

What confiused me was the fact that i could ping from pfsense to my pc but not the other way around but what wireshark told me that the wan interface was pinging me... so i switched the network cables... en i could go to the network interface!!

Thnx!

Thank you all for the suggestion

I had a very drastic approach: I built a spare firewall with new mobo, new HD and new NICs.
I loaded pfsense 1.2.3 and my configuration.
In office non-working hours I plugged in and tested / stressed for few hours with no problem at all from various workstations. I even increased the download speed to 15/20 MB/sec (depending from the OS of the workstation).
Yesterday I definitively changed the firewall with the new one.

The old firewall (Pentium III 800EB + shuttle mobo) has been on 24/24 from 2001, working as a PC, as a little server, as a Winroute server, as a monowall firewall and lately as a pfsense server.
It still seems operational, but probably the NICs have suffered most.

Max

There is no way to duplicate a nic card. They are physical cards in the machine. I'm not sure I'm following what you're saying you did.

I submitted this as FreeBSD problem report i386/144045.
Thanks,
Darin Peshev

oooh  :(

we only have our FX5622, we will try to boot from a multicard reader in a standard PC,

when I'll get it, I'll let you know.

Many thanks!

@Augustino:

I want to know how is working pfsense with this server, mainly detecting 2 networks cards Broadcom 5722 1GbE Single Port NIC

Are there some issue with sata harddrives?

If it works with FreeBSD 7.2 it will work.

@Augustino:

Are there some issue running over vSphere of vmware?

Countless people run in production that way, and much of our development and testing is done in ESX, works well.

Thanks, :-) will try to get it working this week. :-D

Why not use a free ESXi from VmWare to do all this??? Very easy to manage and configure….

Update:

I have added the line vfs.root.mountfrom="ufs:ad0s1a" to /boot/loader.conf and it now works fine.

Can anyone give me some clue as to what is actually going on here?

This box is a new model that I suspect many people will buy. There MUST be a better way to install than this?

Thanks,

Chris

PS.

Instructions to install that work for me:

Run LiveCD with a blank USB stick in the front.

Select install to Hard Drive. When asked, select the hard drive ignoring the USB device.

When it asks about the boot blocks, disable packet mode. Disable everything on the USB stick as it is not needed.

When the device reboots at the end of the installation, power off and remove the USB stick. Power back on.

It now boots but stops and asks for the root filesystem. When prompted enter: "ufs:ad0s1a"

Follow normal install process.

Once it is running edit (either through the UI or through the shell) /boot/loader.conf and add the line:
  vfs.root.mountfrom="ufs:ad0s1a"

All Done!

YMMV

Oh, jeez.  I gathered you could only have the serial access by installing the embedded version.  Thanks for the quick reply.

In 1.2.2 embedded, I think it defaults to sis0 and sis1 for LAN and WAN respectively, though I may have that backward.

In 1.2.3 NanoBSD it defaults to vr0 as LAN and vr1 as WAN.

If your network card is neither of these, you will need to hook up a null modem serial cable and assign then interfaces by hand (or modify the config using a technique like these: http://doc.pfsense.org/index.php/Modifying_Embedded )

And pfSense may pull an IP with DHCP on WAN, but you cannot get to the WebGUI from that side initially. It blocks all inbound connections by default on the WAN. You need to hook a PC up to the LAN port and then go to http://192.168.1.1.

The adapter is completely transparent to the software, so if the HDD is detected in the BIOS it should not be the problem.

sorry for late respond. actually i already install PFsense on 80 gb IDe hard disk. When i had all those problem.

Another information. I am using pfsense for quit a time. But i never able to install on sata hard disk.

I hope BSD developer should do something about this sector.

Right now i am using my Pfsense on my Net cafe. which has 22 workstation.

And i am very much glad that pfsense developer made such a product with enterprise label feature. Right now we are using pfsense 4 different net cafe. and all are running very smoothly.

I have a question about Squid. and i will ask it on package section.

take care and ba bye

You should probably reinstall, just to be safe. If you do a normal install (not quick) you can pick the gmirror as the installation target.

Both drives should be identical, really, or at least the smaller of the two should be the 'primary' one.

Update your BIOS:

http://doc.pfsense.org/index.php/ALIX_BIOS_Update_Procedure

It should work then.

It will prompt you to re-assign the interfaces when you restore the config. Should be easy.

It should work fine. Upgrading a config from 1.2 has worked flawlessly for anyone I've heard try it.