@dro:

@familyguy:

If I'd like to update 1.2.1-beta-mumble to the latest code….

Why not use the inbuilt update method?

System: Firmware: Settings <– Select from the drop down box 1.2.1-snapshots
then
System: Firmware: Auto Upgrade <-- Invoke Auto Update

Backup your configuration first just in case of breakage.

When I try this, it downloads the update and then hangs after the download is complete.

Cheers,

pfSense-Full-Update-1.2.1-RC1-20080909-2058 < –- Works again, cool, thanks :)

It's not a RC btw, we will announce a official BETA-1 soon which will also be dsitributed to the mirrors and will also be a signed image.

Kind regards,

Seth

Fixed in cvs

This was a temporary snapshot regression, it is already fixed.

This should be fixed.

This doesnt really work if you have Block Private Networks checked in Interfaces: WAN as it becomes your top most rule and automatically logs the traffic

Hello,

It doesn't seem you configured port forwarding correctly…nat and port-forwarding come first before rule eval.

cheers,

@sullrich:

Please let me know if the process "slbd" uses more than normal processor usage.

Run "top" from a shell and periodically check to see if slbd is consuming > 40% cpu.

Thanks

I haven't managed to catch it "in the act" yet, but I suspect that the interface flapping I'm seeing follows a phenomenon that results in system utilization spiking up to 70%-ish for a very short period of time.  Those utilization peaks seem to occur at or near the times that my interfaces are flapping due to failing the ping test.  There is absolutely no reason for that kind of utilization since I'm only pushing about 3mbits in/out over 2 load balanced 1.5mbit links.

Cheers,

http://forum.pfsense.org/index.php/topic,2718.msg56627.html#msg56627

running 1.2, nano counts the lines: [ line 1/3316 (0%), col 1/6 (16%), char 0/120318 (0%) ]

Ok ,
I found my problem.  I set the wrong netmask. I set it to /32 instead of /24

Dumarjo

@BillHeaton:

Load Balancing working…  Continuing on to CARP.  Bill

Interested to see how this works for you. I had to switch back to standard NIC cards after issues with firewire on 6.2 based builds. Basically, when I would shut down one box, the firewire would go crazy and bring the system to it's knees. My advice is to test heavily before going live, or at least do some tests during off-hours.