TransACT shared servers

[Alex Satrapa]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday, March 24, 2002, at 03:23 , Jeremy wrote:

> This true, but it still needs a way to find it's companion proxies, 
> either by DNS name or IP.

The way we've addressed this issue with our Work/Home networks so far is 
to use private addresses internally, with fixed network numbers for each 
home network.  The networks communicate using e-mail (something out 
there has to be fixed, such as an email address that you get from your 
ISP), with messages typically looking like:

> Subject: Connection telstra-bigpond has IP Address 203.51.24.147.
>
> The connection telstra-bigpond has come up, and apparently it has IP 
> Address 203.51.24.147.
> PPP_IFACE=ppp0
> PPP_TTY=
> PPP_SPEED=38400
> PPP_LOCAL=203.51.24.147
> PPP_REMOTE=172.31.20.24
> PPP_IPPARAM=telstra-bigpond

Most of this is just debugging information - I can probably leave a lot 
of it out.  The weird thing is that pppd sets a bunch of environment 
variables, then calls the ip-up scripts with the above six command line 
parameters.  Redundant data galore repeated over again.

Admittedly, at this stage we manually extract the IP address to pass on 
to the PPTP server, but that's only because I don't want the links 
coming up automatically yet - we don't have encryption on the PPTP link, 
and I haven't gotten around to setting up IPSec yet.

Alex

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (Darwin)
Comment: For info see http://www.gnupg.org

iD8DBQE8nR06pI0CVGhePOkRAgGgAKCd57W1Jf+N2knzR7lHwfteHmjWoQCfXAMc
/PtRK7AG01UcH3PG+aGgB6A=
=nPdj
-----END PGP SIGNATURE-----