On Fri, 27 Feb 1998, Bill Studenmund wrote:

> You need to set up the modem to do all the right things and save the
> settings. Compression's ok if you have transfer rates & flow control set
> right. You also need to get the modem's idea of the flow control saved, so
> that you don't have to talk to it each time it powers up.

	Unfortunately I've lost my modem manuals and can't remember any of
the AT commands besides the standard ones like at&f1, atz, ath,
atdt,ats0=n, etc. And, I've searched the global village web site for an
online manual or something... no luck 8-( What are the standard AT strings
to set and then save settings to a modem? Right now the modem is
defaulting to m1s0=1 I think (it waits for a call by ddefault and the
soundd is on. I don't know what else it's doing, so that might be part of
the problem.

> Decide if you want/can hang up the modem by dropping DTR. Advantage: you
> can hang up cleanly. Disadvantage: With mac serial ports, you can't
> simultaniously shut the modem up w/ flow control and also be able to hang
> up. Both functions use DTR. If you don't need to throttle the modem, use
> DTR to drop the connection. Then you can use crtscts flow control (we'll
> stop sending if the modme asks by dropping CTS). If you need to throttle
> the modem, use cdtrcts flow control. CTS will get us to hush as above, and
> DTR will get the modem to hush.
> 
> For cdtrcts (dtrcts in /etc/ttys), you'll need to make sure your modem
> will either use DTR for flow control, or it will use RTS and your modem
> cable links the two. Also, the modem should NOT drop carrier on loss of
> DTR. :-)
> 
> > 
> > 	So, right now the client can ping all 3 other hosts on the
> > network. The client can lookup names, so it is talking to the domain name
> > server, which is also the ppp server. But, TCP and UDP tests (via MacTCP
> > Watcher) fail, and I cannot telnet to the ppp server, or my IIcx.
> 
> Wait. If the client can ping hosts, ppp is up quite well. Are you
> telnetting by IP address or name? Try IP address. If that doesn't work
> when pinging does, your telnet client is broken.
> 

	I've tried both names and IP's. Actually, I fire up MacTCP WAtcher
and it recognizes itselff as ppp0.woo.org, which is the name I have set
for the IP I allocate it in my named configs. So, it's getting domain and
ICMP, but no TCP or UDP. It can traceroute too... but when I do a TCP ping
or UDP ping in MacTCP WAtcher it fails, and telnets to the ppp server fail
as well.

	Netstat shows that the client has an entry... though I haven't
tried pinging it from any of the other machines. And, I think the telnet
client works because I'm using it right now ;-) I've got the laptop in my
room hooked up to the ethernet atm and everything works just fine. And, I
AM changing my TCP configs over to a PPP setting when I am trying this.
I'm prety sure that my Mac-side configuration is fine...

> > 	It still sounds to me like the client isn't getting told its
> > defaultroute. And, as it is impossible to manually configure that with
> > FreePPP/PPP/MacPPP.... the client NEEDS to get the routing information. I
> > remember that MacTCP always had the gateway field... I don't remember if
> > it would let you change it if you were getting your IP from the server...
> > 	
> > 	Any ideas on either topic? I am totally stumped. If PPP works
> > (except for the routing), I don't see why a dialup shell shouldn't be
> > working too, and I've gone over the pppd man page 20 times so far, looking
> > or options which will set the router... and there IS one if you're using
> > IPX, but not one for regular IP 8-(
> 
> How is pppd getting fired up on the host computer?

	I have a subdirectory of /etc/ppp called dialup-ppp with an
options file and a ppp server startup script. You've seen the options in
the options file, here is the startup script:

#
# This will setup pppd and ready it for our dialup
#

/usr/sbin/pppd file /etc/ppp/dialup-ppp/options 192.168.1.1:192.168.2.1
/dev/tty00 57600

	The above is on the same line though. I've tried giving the client
an IP on the 192.168.1 network, like 192.168.1.5, but I get the same
result, that a ping works and a telnet, etc. does not.

	Should I try setting a different speed? Or, am I missing an option
or something?

	Thanks.

	Ryan

-----
HELO... my name is rewt... you have SIGKILLed my father... prepare to vi!