go to system –> routing. Add gateway group.

combining will not work on pfsense. it will flip over from one to the other all the time (round-robin)

Thanks for the help. I think I got it now, but I cannot test it yet because my default ISP is down.
But in my firewall log, all traffics are going out to the my default ISP even it is down. Is this okey?
I just put the:

1.) first rule for accessing subnet on WAN1 *    *    *    WAN1 net    *    WAN1    none 2.) first rule for accessing subnet on WAN2 *    *    *    WAN2 net    *    WAN2    none 3.) third rule for LoadBalancing *    *    *    *            *    LoadBalancingGroupe    non

Trigger: Packet loss

Figured out this was mostly due to an old package (nrpe) not being uninstalled properly. I am unsure of the specific details, as I ended up having a tech from pfSense fix it for me.

-Sean

Yes.

I ended up doing what JIMP suggested.  Thank god it worked.  I lost all my rules and IP config, no big deal.  I got everthing fixed.  I see more changes that everybody is working on.  It is looking good.
RC

You have to disable scrub during multi-link.

That is only useful if you spend less time tracking it down than reinstalling. If you want to figure it out, have at it, but when there are workable alternatives that get you a working system in less time then I don't see how spending more developer resources on tracking down what happened in one specific odd case would be worth the time.

I hoped that updating the firmware might fix whatever the issue was, but the updatefailed, stating I was 2 MB short or something typical like that, so I just dumped the USB drive for a CF.

Too bad, USB drives are so cheap and easy these days compared to buying a faster CF and an adapter, then trying to dig up a floppy power adapter for the CF adapter.

MS-CHAP has never been supported, maybe at some point in the future post-2.0.

Yes, but that's only one ftp server, and that's only passive.  I need to be able to support passive and active connections, and do it for two ftp servers.  I can do this with a Cisco ASA, but not with PFSense, from what I can tell.  The firewall will need to rewrite a bunch of information in the packet headers for this to work.

OK,
I've spent all weekend on this.

Reinstalled RC2 i386, got all the updates as of 18 June.

No addons or packages.

Used wizard for single LAN and Multi WAN (Chose 1 WAN) using HFSC

Setup queues for penalty box. and so forth.

reduced total upload and download to half of what it actually is so I could try a get some response from it.

All traffic is sent to the correct queues but qLow is not limited or slowed in any way when there is traffic in qhigh or q default?

Surely someone can point me in the right direction as this has taken days and days of screwing around.

What do i need to do to get qlow to reduce bandwidth whan other traffic is present?

Ok, update !
Now my R310 work perfectly with 2.0 RC1 and update to the latest snapshot.

My simple workaround :
Open Bios setting and disable all onboard Nics (and remove any pci ethernet card)
Boot with pfsense cd and install this perfectly.
Shutdown, reactivate any nic and reboot.
All works !
The Issue is caused by ethernet nic configuration.
Please send a feedback !

You can change RedBoot's IP quite easily if you have access to the boot loader prompt.
Simply run fconfig and hit return across each parameter you don't want to change until you get to the IP.

Steve

using the firmware "2.0-RC2 (amd64) built on Sat Jun 18 01:57:22 EDT 2011" solved my problems…

first difference compared to "2.0-RC2 (amd64) built on Wed Jun 8 17:13:48 EDT 2011" I detected was while booting pfsense it took quite a long time to start the openNTP client.

It's something that will be addresses as soon as time allows. The dev who works on the shaper is off for a few days. We've had a lot of projects with time-sensitive deadlines around here, and though shaping is important, it has not been as important as fixing panics, CARP bugs, etc, etc. As we get closer to release it will of course be fixed, but that takes time (in both the sense of time to fix, and the availability of said time of someone who has the know-how to fix it).

Hi,

i did an update and now all works fine for me, thx to you.

BR
wkn

I'm running the current snapshot and don't have this issue anymore.

I updated the first port with issue details and resolution steps.  please feel free to let me know if I have any inaccuracies / bad advice listed.

Thanks again.