@egarnel:

The 7206vxr could sit behind the pfsense box and perform traffic-shaping and/or policing before it gets to the pfsense box

internal networks –---> 7206 ------- pfsense [nat] –- internet

We do something similar

we have 3845 routers running as a glbp pair that shape traffic, police protocols, perform ip sla checks and then do policy based routing to send particular traffic out either of the pfsense servers or firewalls or nat routers - based on priority & availability.

You can use class-maps & service polices to give certain protocols more or less bandwith, qos, etc...  For example:  We choke down bandwidth hogs to a trickle before they even reach the pfsense servers

The 7206 is a bad ass router that can do a lot of stuff as above, as well as vlan support & firewalling.
We have one here in our shop, it just cranks right along

I have an ATM connection to ISP. So I can't put anything in front of my router because of hardware requirements.
But your suggestion seems smart.

But I think I will work on Hoba's suggestion.

ok thanks for your quick replies - I'll keep on experimenting :-)

Update on problem:

If I choose 99 in the menu - but from a ssh session as opposed from the "console" (keyboard/VGA screen) the Ncurses GUI works :-)

If invoked from the "console" the system freezes - only possible option is the hw-reset button - it seems that the problem is related to the VGA shared-memory…

This is why we advocate reinstalling.  We didnt handle every update case for betas.

Hello,

now it rocks! We have changed the HDD from Seagate Barracuda 7200.9 (80 GB) to Samsung SP4011N (40 GB PATA). We did not change anything in the BIOS from Defaults. I loaded the newest RELENG Build and all runs fine.

The Seagate 7200.9 SATA and PATA runs definitely not with the Intel Board E7221 and Pfsense.

You need to use another HDD.
Greetings
Heiko

@Darth_Potato:

My local time is 8:54PM now. Also I have and different measures in RRD Graphs - on WAN in 114.64MB, but on LAN out 129.43MB :o Maybe this is linked with time-bugs

Different Traffic between interfaces is normal. You have some traffic at WAN for example that will be blocked but that is seen from your WAN interface. Also some broadcasts that are seen at the LAN interface won't be routed out the WAN though they hit your LAN interface.

Btw, this ACPI-fast is the setting that works on my IBM eserver x330 server. You probably don't have this counter at your system but maybe others. My server offers 3 timecounters but this is the one that I found out to work ok. Check what counters are available at your system and try all of them.

We covered it in the other thread.  Locking this one.

@sullrich:

@Emab:

Just upgrade to the leatest snapshot:

Now the web interface work correctly

Duing the boot, I can read via serial console these last line:

....... Starting OpenNTP time client...done. Starting CRON... done. Syncing packages: XML error: not well-formed (invalid token) at line 1 Executing rc.d items... Starting /usr/local/etc/rc.d/*.sh...done. Bootup complete

Unfortunately you probably need to restore a config.xml backup prior to the 03/28/07 image.

I restored an old config file and now all run ok!
Perfect!

Thank you!!

http://forum.pfsense.org/index.php/topic,3955.0.html

Although proprietary, the Cisco ASA is a nice firewall.  Why would you want to load pfSense on it?  That would be like trying to retrofit Vyatta on a Cisco IOS router.  ???  :o

(No offense to the pfSense or Vyatta developers….)

Robert

I too have the "disk is dirty" messages during boot on a standard pc with 256 mb CF (platform set to embedded)

this looks scary but everything's performs OK

You shouldn't run different Accesspoints at the same channel (not even if they share the same SSID and Settings). Everything not at least 2 channels away is influencing each other and will cause impact on throughput though it will work.

Thanks Hoba.

Writing a 64 mb partition to a 128 mb card will work as well. However you might want to try the latest snapshot as these images are 128 mb by default: http://snapshots.pfsense.com/FreeBSD6/RELENG_1/embedded/

Thankyou Sai, I will try that soon.

ok thanks hoba for the point for download looks like a good improvement from 9 months ago.  Look forward to seeing it stable.

Thanks Again hoba,
  But still no go :(

My Loader.conf looks like this :-
autoboot_delay="10"
hint.acpi.0.disabled=0

But when boot the Box using option 1,  It crashes with a general protection fault when load the network card drivers.  If I use option 2 it boots fine.  I'm just concerned that if the power goes down,  the box will not start unless there is someone here to select option 2 :)

Thanks for your help

Knotty

Sounds like a DNS Issue maybe? If you can reach the modem you can pass through pfsense.