Well if you don't necessarily need it to be even and odds, you could do it
based on subnets.
so a.b.c.0-a.b.c.127 go to WAN1
and a.b.c.128-a.b.c.255 go to wan2
alternatively you could download your configuration and add an alias list
to the XML directly then re-upload it.
<alias>
<name>Group1</name>
<address>a.b.c.1 a.b.c.3 a.b.c.5</address>
<descr/>
<type>host</type>
<detail><![CDATA[IP 1||IP 2||IP3||]]></detail>
</alias>
That should be pretty easy to rig up quickly in excel or a quick script for
the entire block.
On Fri, Jun 14, 2013 at 4:18 PM, Chris Bagnall <pfse...@lists.minotaur.cc>wrote:
> Greetings list,
>
> I've been a fan of pfSense's multi-WAN support for a long time, and
> usually write a set of rules to separate latency critical traffic from
> other more general traffic (so things like SSH, email, VoIP, streaming
> protocols etc. go down one link, leaving all the other dross to take the
> other link).
>
> From time to time I need to implement 'traditional' load balancing; for
> example, I'm currently writing rules for a pfSense deployment for a hotel's
> guest wifi, where it's important to try and even out the load on the pair
> of WAN connections.
>
> The normal strategy here would be to set up a gateway group with 2
> members: WAN1 and WAN2, both Tier 1, so they're treated equally. However,
> sooner or later you'll come across fancywebsite.com which redirects to
> (or includes content from) members.fancywebsite.com and gets horribly
> confused if the client's connections come from two entirely separate IP
> addresses.
>
> So in an ideal world, I'd like to set up some source-based rules, so
> effectively:
> a.b.c.1
> a.b.c.3
> a.b.c.5 all go via WAN1, and:
> a.b.c.2
> a.b.c.4
> a.b.c.6 all go via WAN2, and so on.
>
> Obviously I don't really want to have to define each IP manually in the
> rules (or indeed in an alias list).
>
> Any suggestions about how one might achieve this?
>
> Thanks in advance.
>
> Kind regards,
>
> Chris
> --
> This email is made from 100% recycled electrons
> ______________________________**_________________
> List mailing list
> List@lists.pfsense.org
> http://lists.pfsense.org/**mailman/listinfo/list<http://lists.pfsense.org/mailman/listinfo/list>
>
_______________________________________________
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list
