I have things set up to allow me to connect to dialup, and still keep
connections going to my other machine ("LAN" = 2 machines). I think this
is similar to your situation. The key is in my /etc/conf.d/net file as
per the following excerpt...
routes_eth0=(
"default via 192.168.123.254 metric 2 mss 1454"
"192.168.123.248/29 via 192.168.123.254 metric 0"
)
My home machine is 192.168.123.250 on my "LAN", my hot-backup is
192.168.123.251, and the ADSL-modem-cum-router is 192.168.123.254. Note
the 2 statements. The default connection to the world is "metric 2",
while the connection to the LAN is given "metric 0". The ppp0
connection, when active, has priority over the default connection, but
not over the LAN connection. So I don't have to tear down the eth0
connection when dialing up, and re-start it after disconnecting from
dialup.
If I wanted to get really fancy, I could assign separate "metric 0"
routes for streaming video or audio sites, where dialup won't hack it.
This would allow me to listen to internet radio on ADSL, while
simultaneously downloading updates/email/usenet over dialup, or even
surfing the web on dialup.
Why bother, you ask? Bell Canada will soon be be ramming
billing-by-the-byte on all its users and its resellers' users. The only
"alternative" in Toronto is Rogers Cable, and they're not attractive
either. I intend to divert update/email/usenet downloads to dialup.
This will apply to any files where I don't care if it's an overnight
download.
This would also be a great idea for usability testing for some web
developers, to see how piggy their Schlockwave-Trash websites are on
dialup.
--
Walter Dnes <waltd...@waltdnes.org>
