[EMAIL PROTECTED] wrote:
> On Mon, 6 Feb 2006 23:54:21 -0500, Steven S wrote:
> 
>> [EMAIL PROTECTED] wrote:
>>> John R. Shannon wrote:
>>>> On Monday 06 February 2006 06:46, Nickolay A Burkov wrote:
>>>>> Hi, All!
...
> 
> I don't see any ping commands of the form:
> 
> ping -I fxp0 ..........
> 
> in examples of ifstated use. I would think that forcing the interface
> to be used would be useful to prevent misleading results.
> 
> Whilst I'm at it:
> Why wouldn't I change the default route by doing a route
> delete default
> && route add default $SecondChoice type command and the reverse when a
> link comes up on $FirstChoice ?
> 
> In general I'd love to see some more configurations with all the
> relevant pf.conf bits so that I can study an example or three in
> conjunction with the ifstated manpage.
> 
> I think I'm going to have to set up a lab test and see what works well
> but some other viewpoints may may choosing a better way easier.

I force the interface by creating a static route and not creating any
route-to pf rules for the tested IP's.  In my case one gw is bridged via
wireless to the ISP2 interface, so no route is needed.  Never tried the
'ping -I' but it sound easier than the creating routes, so thanks!  I'll
have to try that against a carp interface for my second ISP since I only
have one address and it is assigned to a carp interface.

I'm using the round-robin, load balanced route-to command in pf.conf to load
share among the available ISPs.  So my default gw isn't used much. 

-Steve S.

Reply via email to