Dual wan

[Stefan]

Hello

I'm runnig beta3 on viaboard using pfsense as Firewall and captiv portal ..since a few days i got
my second adsl2 line now i try to setup outgoing loadbalncing but i every time i set my lan port in 'Firewall/rules/ to 'pool'
name of my wanpooll in loadbalancer i get this message .

There were error(s) loading the rules: /tmp/rules.debug:106: syntax error pfctl: Syntax error in config file: pf rules not loaded - The line in question reads [106]: pass in quick on $lan route-to { } round-robin route-to ( pool ) from 10.10.1.0/24 to any label "USER_RULE: Default LAN -> any

Hoba helped me in the german Forum out with a lot answers about the basics of the loadbalancerfunktion (thanks for that man I like learning)

my basic setup looks lik this:

Lan: Static-10.10.1.1/24 dhcp on und Captiv portal on" authmetod Radius auf 10.10.1.2'' captivfunktion works like charme

Wan: Static-12.12.1.2/24 gateway=12.12.1.1/24'modemrouter on adsl line 1'

Opt1: Static 192.168.1.2/24  gateway=192.168.1/24'modemrouter on adslline2'

Nat: Enable advanced outbound NAT  Rules for wan und opt1  both  source 10.10.1.0/24  No staticport

Loadbalancer : gateway  Monitorip 1 Providergateway and Ip  modemrouter on wan '12.12.1.1'  Monitorip 2 first  hop after  Providergateway and  Ip der modemrouter an opt1'192.168.1.1' i

Both adsl lines are from same provieder this is why took as 1Monitor ip the Traced Providergateway an as 2Monitorip on hop after the Providergateway . The adsle lines are normaly ppoe lines with no static ip therefor are the modemrouter (simpel Elcheapo modems who can hand out a static ip and do a little bit more stuff like dmz ).

Thanks for any help :Stefan

ps: sorry for my bad english

[billm]

This error is fixed post beta3.  I can't comment on the setup, but the bug you see is definitely a result of an incorrect setup.  You might want to delete the entire load balance/policy based routing and reset it up from scratch following the load balance instructions in the wiki.

–Bill

[Stefan]

hmm..

I can't comment on the setup, but the bug you see is definitely a result of an incorrect setup.

think so too..

You might want to delete the entire load balance/policy based routing and reset it up from scratch following the load balance instructions in the wiki.

same result ..it looks like pfsense cant ping the Providergateways  but i can ping them if i conect for testing direkt to the modemrouter .

Stefan

[hoba]

Turned out to be only a matter of the way it was tested. It seems that it worked right from the start :)