Kenneth Gonsalves wrote:

> 
> [EMAIL PROTECTED] lawgon]# ip route ls
> 202.71.146.208/28 dev eth1  proto kernel  scope link  src  
> 202.71.146.210  metric 5
> 192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.201   
> metric 5
> 192.168.10.0/24 dev eth2  proto kernel  scope link  src 192.168.10.3   
> metric 5
> 192.168.107.0/24 dev eth3  proto kernel  scope link  src  
> 192.168.107.55  metric 5
> default
>          nexthop via 202.71.146.209  dev eth1 weight 1
>          nexthop via 192.168.10.1  dev eth2 weight 2
>          nexthop via 192.168.107.1  dev eth3 weight 2
> default via 192.168.107.1 dev eth3  metric 5
> 
> i am worried about the last line - eth3 is an unreliable ISP, but it  
> is shown as default. I want eth1 as default. I have listed eth3 last  
> in every config, so how do I prevent it from being the default.

I don't know -- Shorewall isn't doing that; you are in the rest of your
routing configuration. The fact that it has a metric of 5 prevents it
from being replaced by the route above it (which Shorewall *is*
generating). But so long as the route above it is in place, the last one
is irrelevant.

-Tom
-- 
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ [EMAIL PROTECTED]
PGP Public Key   \ https://lists.shorewall.net/teastep.pgp.key

Attachment: signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to