Linux Modem Server - Frequently Asked Questions v1.0

Q: Why does every connection come up as CONNECT 2400 in the log?

A: Most modems return the connect string before it raises DCD.
   Because Linux Blocks on DCD (Ie, waits for DCD to to come high)
   it will miss the connect string. Some modems (Ie the NetComm's and
   Avtek modems, in later firmware revisions had a command switch
   that would make the modem return the connect string after is raises
   DCD. Your modem may have a similar switch. There is another way to make
   it work, but it's messy as it requires you to have an RS232 patch
   box, or to hack up your cable. Basically, you unhook the DCD line on the
   cable, and hook the DSR line across there instead.. This should work
   for most modems, as the Hayes Spec states, that DSR must come high
   before the connect message (And indeed, this is the behavoir of Hayes
   modems).

Q: People log in, I see the connect message in the log, but then they just
   get garbage.

A: No doubt, you either have a Locked modem without the 'LOCKED' setting,
   or you have a 'Variable Speed' modem, WITH the 'LOCKED' setting.
   If your modem can stay at the same speed, even after connection
   regardless of the connect speed, you should set the 'LOCKED' setting
   in that modems configuration line. 
   Most intellegent modems have this option.
   Most older 2400 modems don't, and thus you cannot set the 'LOCKED' option.

Q: Why should I set AT&D3 ?

A: Because MDM has no way of knowing when a client program (who has temporarily
   taken over the line), has exited. But.. one thing definately happens, and
   that is the DTR line is toggled. AT&D3 sets the option to reload the 
   stored defaults (like an ATZ) when DTR is toggled. That way, the modem
   is restored back to the state where MDM had control of the modem before
   the client took over (Ie UUCP/XC/SEYON/Minicom etc)


