Well... looks like at least some people have used diald with isdn... but
what about really complex setups? ;)
Here is my current setup; aka what happens when I do an "isdnctrl dial ippp0":
localnet 10.1.16.0/20
|
\- router box 10.1.31.254 (eth0:gw IP alias; masquerading enabled)
|
\- ipppd # dynamic IP
| |
xxx.yyy.0.0/16 <-/ \-> ip-up -> ip-up.d/part1
|
ptsfwd -r ssh -... <-/ # pty setup program for virtual ppp stuff
| \
xxx.yyy.3.4 <- ssh \-> pppd # .3.4 is a machine with outside network access in
xxx.yyy
| | |
ptsfwd \--------/
|
\- slirp (ppp emu) # pty0<->ttyp0 pppd<->slirp link to the world
outside
In another words ipppd starts up pppd which connects through an ssh tunnel
to slirp running on the xxx.yyy network...
The isdn device is in manual dialing mode.
ip-up also handles killing the line at 30 minute intervals.
Diald is needed for what it was originally meant for: dialing
automatically when there's traffic that is worth dialing up...
FYI current telco monopolistic pricing:
0.47 FIM/call [ + 0.00092FIM/second if (time e {Mon-Fri 07-17}) OR (length_of_call >
30 minutes) ]
that would make say a 4 hour call 3.2 times more expensive than eight � hour calls...
So the line should be killed at 30 minute intervals during the cheap time
and with a timeout of 205 seconds during the "expensive" time
And in case of cheap time an immediate redial should be done if there has
been traffic of type x in say... 10 minutes
Now anyone happen to have an idea on how to handle the two-dependant-interfaces
case involved? that is how to make diald route packets to both xxx.yyy through isdn
and to the rest of the world through the ttypX pppd?
Any help w/ setting this up will be appreciated.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
