Subject: Re: 486 with 56K modem?
To: None <email@example.com>
From: Bruce Anderson <BruceA@SpaceStar.Net>
Date: 11/13/1998 18:26:00
Note -Remove that "call isp"
# pppd call isp
instead to bring the link up.
DX33 with 1.3.2 and Zoom 56K
My /etc/ppp/peers/isp looks like this:
tty00 57600 # modem port and speed
connect '/etc/ppp/chat-script "X-XXX-XXXX" ' # connect script
ipparam "<MY.ISP> XXX,XXX,XXX,XXX,192.168.1.41 <MY.ISP>,home.org"
lock # lock the modem port on connect
modem # use full modem control
crtscts # use hardware flow control
asyncmap 80000000 # represents the character 0x1f or ^_.
defaultroute # add default routing when link comes up
noipdefault # no local defaults for IP addresses
ipcp-accept-local # allow remote to specify our IP address
ipcp-accept-remote # allow remote to specify his IP address
lcp-echo-interval 15 # ping the remote every 15 seconds
lcp-echo-failure 20 # declare link down after 20 pings fail
netmask 255.255.255.0 # netmask for our assigned IP address
domain <my.ISP> # domain name we're connecting into
user <myusername> # account name to use to log onto remote
/etc/ppp/options and options.tty00 are(empty)
On Thu, Nov 12, 1998 9:56 PM, Aidan Cully <mailto:firstname.lastname@example.org> wrote:
> I'm not sure if this is a NetBSD problem, or a 486 problem, or a heavily-
> overloaded VLB problem.. I suspect a combination of the last two. Has
> anyone here had any luck getting a 486 to talk to a 56K modem? I wanted
> this old box to take over the routing for our home network, but whenever
> I start pppd, it looks like the modem drops characters during LCP
> negotiation. Here's some of the output from ppp.log with debugging
> and my /etc/ppp/stuff
> mru 552
> asyncmap 0
> call isp
> name private
> connect "/usr/sbin/chat -f /etc/ppp/scripts/isp"
> which is all the same as on our Linux box, and pppd works fine under
> NetBSD with our internal 288 modem.
> Thanks for any pointers..