> Thomas J Pinkl wrote:
>> I'm attempting to construct a communications server on a Linux 2.0.36
>> box, running pppd 2.3.5. The ppp driver in the kernel is FILEVERSION
>> 980512.
>>
>> This system must initiate outgoing ppp links to multiple target
>> systems, both Unix and NT. Ultimately, it must handle 128 or more
>> simultaneous connections.
>>
>> Currently, I can manually initiate connections to both Unix and NT ppp
>> "servers". I am now trying to determine how I can do this on demand,
>> in response to network packets destined for the target systems.
>>
>> I've read everything I can find on Linux pppd's 'demand' option and on
>> the diald package. It seems that these are geared towards managing a
>> single, predefined ppp link, such as an Internet connection. While
>> these are certainly valuable services, I don't see them scaling well
>> for my application.
>>
>> Are there other solutions for establishing connections on demand? I'd
>> appreciate it if people would share their thoughts and experiences
>> with this type of setup. Thanks.
[EMAIL PROTECTED] wrote:
> I've just configured my linux router for dial on demand!
> Started out with RedHat 5.1 and found that allthough pppd 2.3.5 supports
> "demand", the kernel didn't. Upgraded to RH5.2 and was disappointed
> once more. Then I learned that the source kernel (the tar'ed and gzip'ed
> - the real thing) 2.0.36 and above supports "demand". I got the kernel
> source 2.2.1 - compiled it and installed it into my RH5.2 and now I'm a
> "dial on demand guy". Diald is not needed.
>
> Allthough I for now just have configured only ppp0, but with a different
> IP-address from the eth0, I think it will work fine configuring several
> ppp's. You should beware that "demand" requires configuration of remote
> IP-address. I guess otherwise it wouldn't be possible to resolve which
> link to establish. (If someone thinks I'm wrong on this - please speak
> up!) By the way: The pppd supports locks and when the line is down there
> is no lock!
Thanks for the tip on the kernel. I'll eventually be running this on
Red Hat 5.2, so this information may be useful.
I don't see pppd's "demand" option as a good solution for me, however.
If I understand it correctly, I'd need to preconfigure a pppd process
for every potential connection. I'm going to have *hundreds* of
potential connections and I need to allow for 128 *simultaneous*
connections, to some mix of Unix and NT systems. Due to the nature of
the NT RAS server, I'll need to statically assign the IP addresses for
those links (RAS won't allow the "client" to specify the "server's"
address). So I need to dynamically configure the pppd processes,
based upon the destination IP address.
Diald may be a little closer to what I need, as it supports modem
pools and, if memory serves, invokes a script to bring up the
connection. I'm just not thrilled with the idea of pre-starting so
many diald processes.
What I'd like to have is a sort-of-proxy for the subnet I'll be using
for these connections. For example, an interface on the 10.1.0.0
network. When a network packet arrives for 10.1.1.2, a new ppp#
interface is created by invoking pppd with the parameters that are
appropriate for that specific connection. Does anyone have any
suggestions on how to go about constructing such a thing?
--
Thomas J. Pinkl 738 Louis Drive
Unix Systems Programmer Warminster, Pa 18974
Health Business Systems, Inc. (215) 442-9300 x9260
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
