1 |
On Tue, 18 Aug 2009 07:55:13 -0400 |
2 |
"Walter Dnes" <waltdnes@××××××××.org> wrote: |
3 |
|
4 |
> I have things set up to allow me to connect to dialup, and still keep |
5 |
> connections going to my other machine ("LAN" = 2 machines). I think this |
6 |
> is similar to your situation. The key is in my /etc/conf.d/net file as |
7 |
> per the following excerpt... |
8 |
> |
9 |
> |
10 |
> routes_eth0=( |
11 |
> "default via 192.168.123.254 metric 2 mss 1454" |
12 |
> "192.168.123.248/29 via 192.168.123.254 metric 0" |
13 |
> ) |
14 |
> |
15 |
> My home machine is 192.168.123.250 on my "LAN", my hot-backup is |
16 |
> 192.168.123.251, and the ADSL-modem-cum-router is 192.168.123.254. Note |
17 |
> the 2 statements. The default connection to the world is "metric 2", |
18 |
> while the connection to the LAN is given "metric 0". The ppp0 |
19 |
> connection, when active, has priority over the default connection, but |
20 |
> not over the LAN connection. So I don't have to tear down the eth0 |
21 |
> connection when dialing up, and re-start it after disconnecting from |
22 |
> dialup. |
23 |
|
24 |
Thanks for the solution. |
25 |
|
26 |
Guess I'll settle for similar scheme for now, adding all the gateway IPs |
27 |
to the routing table via preup() function, parsing output of dig with |
28 |
awk. |
29 |
|
30 |
Still, overriding garbage route like that is a hack and it should be |
31 |
easy to write a patch for that behavior, when I'll have some spare time, |
32 |
provided I won't forget about the issue... ;) |
33 |
|
34 |
-- |
35 |
Mike Kazantsev // fraggod.net |