[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pfsense-discussion
Subject:    Re: [pfSense] Creating effective Multi-WAN rules
From:       Chris Bagnall <pfsense () lists ! minotaur ! cc>
Date:       2013-06-14 20:47:05
Message-ID: 51BB8149.6020007 () lists ! minotaur ! cc
[Download RAW message or body]

On 14/6/13 9:38 pm, Adam Stasiak wrote:
> 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

That's basically what I was trying to avoid: the DHCP server hands out 
leases in a linear manner, so if there's only a few clients connected, 
they're all going to go down WAN1, and it's only when more than 128 
clients connect (in the example above) that WAN2 comes into operation.

> 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.

That's probably what I'll end up doing: knock up a quick perl script to 
produce that. I was hoping for a more elegant way of doing it than 
having an alias with a very long list of IPs though :-)

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
[prev in list] [next in list] [prev in thread] [next in thread]