@Citymesh:

well i've tried it but the forwarding just doesnt work .. i see entries when i set packet inspection on but nothing arrives on my destination machine.

I might try the upgrade first .

Have you configured a firewall rule to allow the traffic through?

If you are filtering by destination you need to use the internal ip.

The NAT defines the mapping between the internal and external Ip address however the traffic will still pass through the packet filter and therefore will need appropriate rules to be configured on the incoming interface.  ;)

Hope that helps.

The way traceroute works I think that is expected. If the IPs are really routed to the CARP VIP, I wouldn't worry about it, though if you want to be absolutely certain, you can always do a traceroute, force a failover, and try it again.

If it works both times, it's probably just a quirk of how traceroute shows up in the scenario.

okay, thanks much.

Rolling back won't help - the package binary on the package server is the problem. It would be the same on the old build when it reinstalls (unless you're talking about a VM snapshot…)

Go to routing–> Gateways and open a Gateway and click save. This activates apinger and the status will appear correctly.  doesn't survive reboot though.. so there's still an issue

Did you follow http://doc.pfsense.org/index.php/Use_an_existing_wireless_router_with_pfSense?

If not, does the wireless client have access to the pfSense GUI if you follow the referenced recommendations?

Good news:   Once I installed the AMD64 from the iso cleanly by remounting the rootfs, everything including the RRD graphs appear to be working.   The version I'm currently running is:

2.0-BETA4  (amd64) built on Thu Sep 30 21:08:20 UTC 2010

Hope this helps someone else.

Well, well, well…this has been two weeks from hell as far as what lightning can do.

The board has another sata port and finally, PFsense 2.0 got installed. Yeeehaw!

I simply can't wait...to see what else goes wrong now.

Jits.

It would help me to help you if you answered my previous questions.

@mikenl:

any protocol

I suspect you have tried only a small subset of all the known protocols. Please list the protocols you have tried. If you have tried more than about six, it would probably be sufficient to list about six of the more common protocols you tried. The responses you saw to those attempts may not mean very much to you but they can be quite informative to others.

@mikenl:

it looks like there is no route ?

In the absence of supporting evidence I will assume this is speculation (and quite reasonable speculation). Please provide any supporting evidence you have.

Well, then update to latest snap and try again. It is beta software and you need to update as the first step. Always…

And how? Thanks for the info…

@abeowitz:

So, was hoping to setup queues to prioritize ping and ACK on each of my gateways.

The wizard did have an option to make ICMP high priority, which I did.  But what about ACK?

When I click on the queue graphs, it has qACK on WAN, for example.  Is this already prioritizing ACK, or should I look into trying to implement the technique listed on that blog?

How large should be qACK's bandwidth depends on the ratio between uplink and downlink bandwidth. In most cases the default setting should be fine.

Yeah that's what I meant.  ;D

Good to hear it's working

I get the same Errors:

Sep 29 20:29:04 php: : The command 'chown -R -v havp /usr/local/etc/havp' returned exit code '1', the output was 'chown: havp: Invalid argument'
Sep 29 20:29:04 php: : The command 'chown -R -v havp /var/tmp/havp' returned exit code '1', the output was 'chown: havp: Invalid argument'
Sep 29 20:29:04 php: : The command 'chown -R -v havp /var/tmp/havpRAM' returned exit code '1', the output was 'chown: havp: Invalid argument'
Sep 29 20:29:04 php: : The command 'chown -R -v havp /usr/local/share/examples/havp/templates' returned exit code '1', the output was 'chown: havp: Invalid argument'
Sep 29 20:29:04 php: : The command 'chown -R -v havp /usr/local/share/examples/havp/templates_ex' returned exit code '1', the output was 'chown: havp: Invalid argument'
Sep 29 20:29:04 php: : The command 'chown -R -v havp /var/log/havp' returned exit code '1', the output was 'chown: havp: Invalid argument'
Sep 29 20:29:04 php: : The command 'chown -R -v havp /var/run/havp.pid' returned exit code '1', the output was 'chown: havp: Invalid argument'
Sep 29 20:29:04 php: : The command 'chown -R -v havp /usr/local/etc/freshclam.conf' returned exit code '1', the output was 'chown: havp: Invalid argument'
Sep 29 20:29:04 php: : The command 'chown -R -v havp /var/log/clamav' returned exit code '1', the output was 'chown: havp: Invalid argument'
Sep 29 20:29:04 php: : The command 'chown -R -v havp /usr/local/etc/rc.d/havp_avupdate' returned exit code '1', the output was 'chown: havp: Invalid argument'
Sep 29 20:29:04 php: : The command 'chown -R -v havp /usr/local/etc/clamd.conf' returned exit code '1', the output was 'chown: havp: Invalid argument'
Sep 29 20:29:04 php: : The command 'chown -R -v havp /usr/local/etc/havp' returned exit code '1', the output was 'chown: havp: Invalid argument'

@xbipin:

could u provide a sample screenshot of a single queue under floating tab and the rule under lan for the limiter?

In floating: queues are the same ones created by shaper wizard. Nothing changed here.

In LAN default pass(*) rule just put your limiter(s) in In/Out setting WITHOUT anything in Ackqueue/Queue setting.
If for any reason you populate the Ackqueue/Queue setting, all floating rules will go ineffective and only that Queue will be applied to all traffic.

(*) If you have a MultiWAN setup, you have to put it in you LAN default pass with the loadbalancer/failover Gateway setting.

Same bug, discussed here.

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

good advise. thank you!

setup two times pppoe.
right now one is working.
Will take a closer look at the system -> routing.

Ok. Thanks a lot.