On 16-Jul-07, at 11:56 PM, Tom Eastep wrote:
>>
>> Follow the above advice and it will work for N external addresses
>> on M
>> external interfaces with L internal LANs for all values of L, M
>> and N.
>
> I've added a section to http://www1.shorewall.net/MultiISP.html
> which should
> clarify.
I had more or less figured that out on my own, but it is nice to see
it in black and white. I really appreciate the time you have taken to
clarify the points and the documentation. I configured it and it is
working (touch wood). The output of ip route ls is:
[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.
--
regards
Kenneth Gonsalves
Associate, NRC-FOSS
[EMAIL PROTECTED]
http://nrcfosshelpline.in/web/
-------------------------------------------------------------------------
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
