🚀 go-pugleaf

I recently cracked the problem I was experiencing connecting my linux
box to freeserve using kppp and thought others may be experiencing a
similar problem.

I have been connecting linux to demon for some time with no problems.
However when I tried freeserve,the connection appeared to establish ok
(confirmed by the debug output) but the line would hang up as soon as I
tried to actually use it (actually after 4 KBytes or so of data was
exchanged). Searches of the web found other people with similar problems
but no solutions.

I tried the same connection on the same hardware under windows and it
worked fine.  After hunting around I found a windows option to turn on
modem logging, producing the file Modemlog.txt. This revealed the
initialisation AT commands being sent to the modem and a number of
connection time messages being returned which I was not seeing under
linux.  So I copied the AT commands into the kppp modem initialisation
string and bingo, the connection worked.  

For my modem the initialisation string in kppp is now :

        AT&FE0&C1&D2S95=47S0=0S7=60S30=0\N3%C3&K3BN1X4

(Note : this string is unlikely to work for other modems).

The meaning of all this according to the modem manual is :

&F      Load Factory default configuration 0
E0      Commands echo disabled
V1      Text responses
&C1     Turn on CD when remote carrier is present
&D2     Modem hangs up and returns to the Command Mode after DTR toggle
S95=47  Register set - Extended result code options
S0=0    Register set - Auto-answer Ring
S7=60   Register set - Remote carrier wait time
S30=0   Register set - Disconnect timer
\N3     V.42/MNP/Normal auto-mode
%C3     V.42bis/MNP5 data compressions enabled
&K3     Enable RTS/CTS hardware flow control
B       CCITT mode @ 1200 bps
N1      Automatic rate negotiation
X4      All responses and dial tone and busy signal detection

I'm not sure which of these solves the freeserve problem, but kppp
continues to connect to Demon fine.

        Steve P.