External Modem Recomendation 3991
In the Usenet newsgroup comp.os.linux.misc, in article
I won't lecture you on the anti-social nature of what you are contemplating... ;-) Here's another idea though, but how well it works...
AT&T knowing nothing is considered news exactly how?
The connection problem is most often due to the brain-dead tool you are attempting to use. Hit this page:
and create a dumb script to get connected. The old 'worldnet.att.net used instead of PAP. Do not attempt to find some wanky old Login: prompt - that concept went out of fashion when microsoft invented the telephone or something, but many Linux application writers haven't gotten the word yet (it's only been ten years now). The above web page will help you figure out what's going on even if you aren't using worldnet.
You'll likely want something along this line:
compton ~$ catusr-local-bin-dialin #!-bin-bash execusr-sbin-pppd connect "-usr-sbin-chat -vfetc-ppp-dialscript" defaultroute lock noipdefault modem nodetachdev-modem 115200 crtscts compton ~$
There must not be anything after the in those two lines.
compton ~$ catetc-ppp-dialscript ABORT BUSY ABORT 'NO CARRIER' AT&F1 OK ATDT2662902 CONNECTd-c compton ~$
Set the fileetc-ppp-chap-secrets (andetc-ppp-pap-secrets just to be safe) with the username and pbuttword in the form
with the obvious suitable corrections. etc-resolv.conf has to have the right nameservers in there. 199.191.144.75 seems to be authoritative for the host you posted from.
I saw a blurb last week saying that broadband penitration in the US has just recently pbutted the 50% mark. There are now slightly more people who have broadband...
Old guy
External Modem Recomendation 3992
Linux groups from Newsgroups