Progress to report!
In looking around further, I noticed in /etc/ppp/connect-errors:
sh: my-chat-script: command not found
This caused me to insert the full path prefix in my /etc/ppp/ppp-on script,
(O'Reilly notwithstanding) and lo and behold, running a script now produced
dialtone and connected with my ISP. I am still having some problems,
apparently about authentication
Here is the ifconfig file:
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
ppp0 Link encap:Point-to-Point Protocol
unspec addr:[NONE SET] P-t-P:[NONE SET] Mask:[NONE SET]
POINTOPOINT NOARP MULTICAST MTU:1500 Metric:1
RX packets:7 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
and the chat-log:
Aug 5 21:23:58 debian pppd[442]: pppd 2.3.5 started by root, uid 0
Aug 5 21:23:59 debian chat[443]: send (ATZ^M)
Aug 5 21:23:59 debian chat[443]: expect (OK)
Aug 5 21:23:59 debian chat[443]: ATZ^M^M
Aug 5 21:23:59 debian chat[443]: OK
Aug 5 21:23:59 debian chat[443]: -- got it
Aug 5 21:23:59 debian chat[443]: send (ATDT410-727-0315^M)
Aug 5 21:23:59 debian chat[443]: expect (CONNECT)
Aug 5 21:23:59 debian chat[443]: ^M
Aug 5 21:24:26 debian chat[443]: ATDT410-727-0315^M^M
Aug 5 21:24:26 debian chat[443]: CONNECT
Aug 5 21:24:26 debian chat[443]: -- got it
Aug 5 21:24:26 debian chat[443]: send (^M)
Aug 5 21:24:26 debian chat[443]: expect (ogin:)
Aug 5 21:24:26 debian chat[443]: 36000/ARQ/V90/LAPM/V42BIS^M
Aug 5 21:24:32 debian chat[443]: ^M
Aug 5 21:24:32 debian chat[443]:
Aug 5 21:24:32 debian last message repeated 23 times
Aug 5 21:24:32 debian chat[443]: UQKT2 tnt2.baltimore.md.da.uu.net^M
Aug 5 21:24:32 debian chat[443]: ^M
Aug 5 21:24:32 debian chat[443]: ^M
Aug 5 21:24:32 debian chat[443]: Login:
Aug 5 21:24:32 debian chat[443]: -- got it
Aug 5 21:24:32 debian chat[443]: send (davidturetsky^M)
Aug 5 21:24:32 debian chat[443]: expect (assword:)
Aug 5 21:24:32 debian chat[443]: davidturetsky^M
Aug 5 21:24:32 debian chat[443]: Password:
Aug 5 21:24:32 debian chat[443]: -- got it
Aug 5 21:24:32 debian chat[443]: send ([password removed]^M)
Aug 5 21:24:32 debian pppd[442]: Serial connection established.
Aug 5 21:24:33 debian pppd[442]: Using interface ppp0
Aug 5 21:24:33 debian pppd[442]: Connect: ppp0 <--> /dev/modem
Aug 5 21:24:50 debian pppd[442]: peer refused to authenticate
Aug 5 21:24:50 debian pppd[442]: Connection terminated.
Aug 5 21:24:50 debian pppd[442]: Hangup (SIGHUP)
Aug 5 21:24:50 debian pppd[442]: Exit.
'route -n' produced:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
I also created a .fetchmailrc file
fetchmail --version produced
This is fetchmail release 4.6.4
Linux debian 2.2.12 #2 Thu Aug 26 11:46:26 PDT 1999 i686 unknown
Taking options from command line and /root/.fetchmailrc
Idfile is /root/.fetchids
Fetchmail will forward misaddressed multidrop messages to postmaster.
Options for retrieving from [EMAIL PROTECTED]:
True name of server is email.msn.com.
Protocol is POP3.
Server nonresponse timeout is 300 seconds (default).
Default mailbox selected.
Only new messages will be retrieved (--all off).
Fetched messages will be kept on the server (--keep on).
Old messages will not be flushed before message retrieval (--flush off).
Rewrite of server-local addresses is enabled (--norewrite off).
Carriage-return stripping is disabled (stripcr off).
Carriage-return forcing is disabled (forcecr off).
Interpretation of Content-Transfer-Encoding is enabled (pass8bits off).
MIME decoding is disabled (mimedecode off).
Nonempty Status lines will be kept (dropstatus off)
Messages will be SMTP-forwarded to: localhost (default)
Recognized listener spam block responses are: 571 550 501
Single-drop mode: 1 local name(s) recognized.
No UIDs saved from this host.
When I ran 'fetchmail' I got:
fetchmail: POP3 connection to email.msn.com failed: temporary name server
error
fetchmail: Query status=2
A comparable msg appeared when I used Smtp.email.msn.com
The 'assword' notation did indeed have a colon following
What steps to continue to move forward? Do I need to make changes re
authentication? If the settings are ok, does dialtone automatically follow?
David
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
