home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!hal.com!decwrl!sun-barr!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!jvnc.net!netnews.upenn.edu!turock.psych.upenn.edu!ross
- From: ross@turock.psych.upenn.edu (Ross Porter)
- Newsgroups: comp.protocols.ppp
- Subject: Re: PPP client routing
- Keywords: PPP route
- Message-ID: <84195@netnews.upenn.edu>
- Date: 23 Jul 92 13:55:03 GMT
- References: <84022@netnews.upenn.edu>
- Sender: news@netnews.upenn.edu
- Organization: University of Pennsylvania
- Lines: 17
- Nntp-Posting-Host: turock.psych.upenn.edu
-
- >We suspect that some of the problems we are having with our PPP connection
- >are due to improper routing. One symptom of the problem is that
- >while rsh client->host works fine, rsh client->client yields
- >a ~75sec delay. Once either connection is established,
- >things work fine.
-
- A kind soul suggested changing the localhost entry in the PPP client (sum):
-
- original: 127.0.0.1 localhost
- new: 127.0.0.1 localhost sum.psych.upenn.edu sum.psych sum
-
- A wonderful hack. This does work, although it creates a few annoyances.
- I'm curious as to why the original localhost entry worked for ethernet,
- but didn't for PPP. Is it because the POINTOPOINT network interface
- type takes precedence over localhost/loopback? If so, is this desirable?
-
- Ross
-