Awesome mate, I'm now sorted. Worked through the ppp setup docs you
refered me to and yep, I think it was the password that was holding up the
show. Have no idea how that got set wrong - I didn't even know the
pap.secrets file existed. I've no idea why I had all these issues compared
to last time when after upgrading to Ubuntu 5.10 my modem just suddenly
starting working. Ah well, we got there :o) Wikid! Cheers for you help.
That was really starting to frustrate me!

Thanks
Matt


> I'd say that the password is the first thing to get fixed. Are you
> absolutely certain that the contents of /etc/ppp/pap.secrets is correct?
> The relevant line has the format
>
> "[EMAIL PROTECTED]" * "password"
>
> Quotes are not necessary, but handy.
>
> Steve
>
> On Sat, 11 Mar 2006 11:09:08 +1300 (NZDT)
> Matthew Whiting <[EMAIL PROTECTED]> wrote:
>
>> I tried using your options file but didn't have any luck. Contents of my
>> options file:
>>
>> asyncmap 0
>> noauth
>> crtscts
>> lock
>> hide-password
>> modem
>> debug
>> proxyarp
>> lcp-echo-interval 30
>> lcp-echo-failure 4
>> noipx
>>
>> Logging with debug on now:
>> Mar 11 10:57:32 localhost pppd[9361]: pppd 2.4.3 started by matthew, uid
>> 1000
>> Mar 11 10:57:32 localhost pppd[9361]: using channel 4
>> Mar 11 10:57:32 localhost pppd[9361]: Using interface ppp0
>> Mar 11 10:57:32 localhost pppd[9361]: Connect: ppp0 <--> /dev/ttyLTM0
>> Mar 11 10:57:32 localhost pppd[9361]: sent [LCP ConfReq id=0x1 <asyncmap
>> 0x0> <magic 0xeb970738> <pcomp> <accomp>]
>> Mar 11 10:57:32 localhost pppd[9361]: rcvd [LCP ConfAck id=0x1 <asyncmap
>> 0x0> <magic 0xeb970738> <pcomp> <accomp>]
>> Mar 11 10:57:35 localhost pppd[9361]: rcvd [LCP ConfReq id=0x2 <asyncmap
>> 0xa0000> <auth pap> <magic 0x19ed2af7> <pcomp> <accomp>]
>> Mar 11 10:57:35 localhost pppd[9361]: sent [LCP ConfAck id=0x2 <asyncmap
>> 0xa0000> <auth pap> <magic 0x19ed2af7> <pcomp> <accomp>]
>> Mar 11 10:57:35 localhost pppd[9361]: sent [LCP EchoReq id=0x0
>> magic=0xeb970738]
>> Mar 11 10:57:35 localhost pppd[9361]: sent [PAP AuthReq id=0x1
>> user="mdub"
>> password=<hidden>]
>> Mar 11 10:57:35 localhost pppd[9361]: rcvd [LCP EchoRep id=0x0
>> magic=0x19ed2af7]
>> Mar 11 10:57:35 localhost pppd[9361]: rcvd [PAP AuthNak id=0x1 "Username
>> \"mdub\" using incorrect password\nUsername \"mdub\" using incorrect
>> password\n"]
>> Mar 11 10:57:35 localhost pppd[9361]: Remote message: Username "mdub"
>> using incorrect password^JUsername "mdub" using incorrect password^J
>> Mar 11 10:57:35 localhost pppd[9361]: PAP authentication failed
>> Mar 11 10:57:35 localhost pppd[9361]: sent [LCP TermReq id=0x2 "Failed
>> to
>> authenticate ourselves to peer"]
>> Mar 11 10:57:35 localhost pppd[9361]: rcvd [LCP TermReq id=0x3]
>> Mar 11 10:57:35 localhost pppd[9361]: sent [LCP TermAck id=0x3]
>> Mar 11 10:57:35 localhost pppd[9361]: rcvd [LCP TermAck id=0x2]
>> Mar 11 10:57:35 localhost pppd[9361]: Connection terminated.
>> Mar 11 10:57:35 localhost pppd[9361]: Exit.
>> Mar 11 10:57:55 localhost pppd[9309]: Connect script failed
>>
>> Rather perplexed about that incorrect password. Its the same as what I'm
>> using to connect on this laptop and also gnome-ppp and .wvdial.conf have
>> correct password specified.
>>
>> Cheers
>> Matt
>>
>> > On Fri, 10 Mar 2006 21:15, Matthew Whiting wrote:
>> >
>> >> syslog:
>> >> Mar 10 20:08:31 localhost pppd[11336]: pppd 2.4.3 started by matthew,
>> >> uid
>> >> 1000
>> >> Mar 10 20:08:31 localhost pppd[11336]: Using interface ppp0
>> >> Mar 10 20:08:31 localhost pppd[11336]: Connect: ppp0 <-->
>> /dev/ttyLTM0
>> >> Mar 10 20:08:58 localhost pppd[11336]: Modem hangup
>> >> Mar 10 20:08:58 localhost pppd[11336]: Connection terminated.
>> >> Mar 10 20:08:58 localhost pppd[11336]: Exit.
>> >>
>> >  Here is the contents of my  /etc/ppp/options  file;
>> >
>> > lock
>> > noauth
>> > noipdefault
>> > usepeerdns
>> > debug
>> >
>> > Is yours any different?
>> >
>> > I would recomend that you at least add the 'debug' line to your
>> options
>> > file
>> > and you should see more information in the syslog file next time it
>> > crashes.
>> >
>> > Cheers Ross Drummond
>> >
>>
>>
>


Reply via email to