Subject: Re: dialup server (pppd)
To: Frederick Bruckman <firstname.lastname@example.org>
From: Chan Yiu Wah <email@example.com>
Date: 02/16/2000 19:43:21
On Wed, 16 Feb 2000, Frederick Bruckman wrote:
> On Wed, 16 Feb 2000, Chan Yiu Wah wrote:
> > > > Feb 16 22:43:21 lts159 pppd: Remote IP address changed to
> > > > 126.96.36.199
> > > > Feb 16 22:43:21 lts159 pppd: IPCP terminated by peer (Unauthorized
> > > > remote IP address)
> > Feb 16 17:02:34 pc77 pppd: Peer is not authorized to use remote
> > address 188.8.131.52
> > Feb 16 17:02:34 pc77 pppd: Connection terminated.
> > 184.108.40.206:220.127.116.11
> You have four different ip addresses here, where there should only be two.
> Are either of 18.104.22.168 or 22.214.171.124 valid ips? Neither one
> looks up for me. In any case, I would set up the ppp link as a private
> network. The server gets
> and not much else, and the client gets only...
> so you can make any required changes on the server. You don't even
> need to specify a tty and baud rate--the getty does that for you.
> "silent persist" is also wrong if you're using a getty with a "ppp"
> With that arrangement, you'll be able to telnet/ftp/rsh from the
> server to the Mac client and vice-versa. Once you get ppp working, you
> can complete the set-up by supplying legal addresses in the server
> options and setting up routes, or by setting up ipnat on the server.
The valid IPs are 126.96.36.199 (server) and 188.8.131.52 (client).
184.108.40.206 acts as the router for LAN-A and 220.127.116.11 is the router
for LAN-B. Users in LAN-B will ask for services on one of the machines
(application for users in LAN-A and LAN-B) in LAN-A. While LAN-A and
LAN-B are in two different location. The connection is the dialup ppp.
That is the only purpose of our porject.