Here is a more up-to-date wireless list:

https://spreadsheets.google.com/spreadsheet/ccc?key=0AojFUXcbH0ROdHgwYkFHbkRUdV9hVWljVWl5SXkxbFE&hl=en_US

It depends on the reason the gateway was marked down. If it marked it down because of "loss" then perhaps your gateway did stop responding to pings, either because it drops out like you said, or because there is actual loss on the line.

If you watch the gateway status widget on the dashboard as it happens, you should see the loss or latency as it gets marked down. The quality RRD graph should also show you.

You could increase the thresholds for the WAN to be marked down on the gateway settings, and also change the monitor IP address to something besides your gateway (DNS server, google, etc).

hey guys,
i have solved, the issue was in WAN interface (bridge solutions)

Now i am natting with Cisco ROUTER but i  want to NAT with Pfsense.
Have you any idea when come out Pfsense 2.0 stable ?

thanks to all
S.

RTFM: http://doc.pfsense.org/index.php/What_is_policy_routing%3F

I should add:

Hosts on either VLAN20 or VLAN250 can reach each other through FW02.

If this is only for testing and not in a "real" environment, why not learn the basics on a new system with many new features :)

You can update from 1.2.3 to the actual pfsense 2.0RC-3 snapshots without losing you configuration.

iam trying upgrade to latest 2.0 RC 3 ::) ,,,

it works perfectly….

thanx :D :D :D :D :D

solved

Manual NAT:Outbound
and subnet added

that's all folks!

Sorry for replying so late, was unable to get on to the forum for all of yesterday.

I have reset states as well as moved the rules around and still no luck.

attached screen captures of the rules and associated aspects.

lan_alias.JPG
lan_alias.JPG_thumb
lan_rule.JPG
lan_rule.JPG_thumb
wan.JPG
wan.JPG_thumb

Hi, I am also very concerning about the load balancing algorithm in Pfsense as you do. Did you manage to implement another algorithm rather than round-robin?

Kind regards

Richard Chen

Dear chanrio13

Thank you for your reply.
I think the static IP Address is better way for router.

Alright, so after a ton of digging I came across a site with someone having the same issue as me. It turned out to be a acpi issue. So I followed in his footsteps and disabled acpi in the bios and booted pfsense with the disable acpi flag. This seems to have done the trick for me. I no longer lose one of my wans now. It appears to have completely corrected my issues. I could not be happier right now!!!

I can't tell you how many nics I swapped in out, cheapo routers I swapped, etc.

I hope this may help others who were in my boat. Time to get this beast back together, and back in the rack.

Thank you to the people who responded to my plea!

i think its possible if you will make your modem / router to router mode (the modem is the one that dials PPPoe) and leases a static IP

I believe the issue displayed here is only cosmetic on the Status>Interfaces page. Though there could be some other issue there on 1.2.3, would be fixed on 2.0 though.

That's great, thanks for the information.

Glad to know I wasn't going completely mad in my understanding.

Yes that's right.