Re: Strange problem with ppp server --MKP
Mike Patterson writes:
> He dials in, and pap is authenticated. Great! First problem, though, is that
> no entries get created via route and ifconfig, so he gets stuck.
You need to give pppd local and remote ip numbers, like this:
192.168.0.1:192.168.0.23
> So I manually put entires in right after he logs in like so:
> ifconfig ppp0 192.168.0.23 netmask 255.255.255.255 up
> route add 192.168.0.23 ppp0
> The strangest thing is when I try telnetting to his machine, it connects to
> the server! (I.E. the server is 192.168.0.1. telnet 192.168.0.23 just loops
> back to it)
Well, sure. pppd has already assigned 192.168.0.1 to the "server" end of the
link; now you are assigning 192.168.0.23 to it. Once up, a ppp link looks to
the kernel just like a two-host ethernet. ppp0 is the server's interface to
this two-host network. ifconfig operates on it, not the other end. You can't
ifconfig another host's interface.
--
John Hasler This posting is in the public domain.
john@dhh.gt.org Do with it what you will.
Dancing Horse Hill Make money from it if you can; I don't mind.
Elmwood, Wisconsin Do not send email advertisements to this address.
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: