PAPA/CHAP again???

Hi guys,

I seem to be lost a bit here with PAP/CHAP and DIALD.
I use Diald Version 1.0 and I had to change ISPs to one that needs PAP or CHAP authentication.

Up to now all worked OK for me but since I changed ISP it does not. I can connect to this new ISP with WVDIAL which means that my /etc/ppp/pap-secrets and /etc/ppp/chap-secrets files work OK.

But when I try to connect with my DIALD it fails. My /etc/diald/internet/connect file contains the line:

pppd-options noipdefault
pppd-options name sv1uy

where sv1uy is my login name to this ISP.

Here is an extract of my /var/log/messages file whenever I try to connect using DIALD.

Could anyone possibly help??? I have read the instructions (RTFM hi hi hi) but I cannot find any answers!!!

-------------------------------------------------------

May 18 19:31:40 nest-0 diald[1253]: connector: send (ATM1^M)
May 18 19:31:40 nest-0 diald[1253]: connector: expect (OK)
May 18 19:31:40 nest-0 diald[1253]: connector: ^M
May 18 19:31:40 nest-0 diald[1253]: connector: ATM1^M^M
May 18 19:31:40 nest-0 diald[1253]: connector: OK
May 18 19:31:40 nest-0 diald[1253]: connector:  -- got it
May 18 19:31:40 nest-0 diald[1253]: connector: send (ATDT8962500000^M)
May 18 19:31:41 nest-0 diald[1253]: connector: timeout set to 60 seconds
May 18 19:31:41 nest-0 diald[1253]: connector: expect (CONNECT)
May 18 19:31:41 nest-0 diald[1253]: connector: ^M
May 18 19:32:06 nest-0 diald[1253]: connector: ATDT8962500000^M^M
May 18 19:32:06 nest-0 diald[1253]: connector: CONNECT
May 18 19:32:06 nest-0 diald[1253]: connector:  -- got it
May 18 19:32:06 nest-0 diald[1253]: connector: abort on (NO CARRIER)
May 18 19:32:06 nest-0 diald[1253]: connector: abort on (NO DIALTONE)
May 18 19:32:06 nest-0 diald[1253]: connector: abort on (NO DIAL TONE)
May 18 19:32:06 nest-0 diald[1253]: connector: abort on (Busy)
May 18 19:32:06 nest-0 diald[1253]: connector: abort on (VOICE)
May 18 19:32:06 nest-0 diald[1253]: connector: abort on (RING\r)
May 18 19:32:06 nest-0 diald[1253]: connector: expect (sername:)
May 18 19:32:06 nest-0 diald[1253]: connector:  49333/ARQ/V90/LAPM/V42BIS^M
May 18 19:32:10 nest-0 diald[1253]: connector: ~^?}#@!}!	} }8}"}&} }*} } 
}#}$@#}%}&}>^UOG}'}"}(}"}2F~~^?}#@!}!
May 18 19:32:12 nest-0 diald[1253]: connector: } }8}"}&} }*} } 
}#}$@#}%}&}>^UOG}'}"}(}"XT~~^?}#@!}!^K} }8}"}&} }*} } }#}$@#}%}&}>^U
May 18 19:32:16 nest-0 diald[1253]: connector: OG}'}"}(}"^Q]~~^?}#@!}!^L} 
}8}"}&} }*} } }#}$@#}%}&}>^UOG}'}"}(}"]x~~^?}#@!}!^M} }8}"}
May 18 19:32:18 nest-0 diald[1253]: connector: &} }*} } 
}#}$@#}%}&}>^UOG}'}"}(}"}4q~~^?}#@!}!^N} }8}"}&} }*} } }#}$@#}%}&}>^UOG}'}"
May 18 19:32:22 nest-0 diald[1253]: connector: }(}"^c~~^?}#@!}!^O} }8}"}&} }*} 
} }#}$@#}%}&}>^UOG}'}"}(}"^Wj~~^?}#@!}!^P} }8}"}&} }*}
May 18 19:32:24 nest-0 diald[1253]: connector:  } 
}#}$@#}%}&}>^UOG}'}"}(}"O}]~~^?}#@!}!^Q} }8}"}&} }*} } 
}#}$@#}%}&}>^UOG}'}"}(}"}&
May 18 19:32:28 nest-0 diald[1253]: connector: t~~^?}#@!}!^R} }8}"}&} }*} } 
}#}$@#}%}&}>^UOG}'}"}(}"Lf~^M
May 18 19:32:28 nest-0 diald[1253]: connector: NO CARRIER
May 18 19:32:28 nest-0 diald[1253]: connector:  -- failed
May 18 19:32:28 nest-0 diald[1253]: connector: Failed (NO CARRIER)
May 18 19:32:28 nest-0 diald[1253]: Connect script failed.
May 18 19:32:29 nest-0 diald[1253]: Delaying 10 seconds before clear to dial.
May 18 19:32:36 nest-0 diald[1253]: FIFO: link down request

-------------------------------------------------------------------------------

I tried to use minicom to connect and see if I get any sort of prompt but I get the same garbage instead of a ligin prompt.

I suspect it has something to do with my configuration since the ISP probably expects something else from me and I am not giving it to him, since my WVDIAL script connects OK every time. I even copied the AT init commands that my WVDIAL script uses and used them to my /usr/share/diald/modem/generic file so that it is not a matter of COMPRESSION ERRORS but no joy.

I would appreciate any help on this one guys!!!

Thanks in advance.

===
73 de Demetre SV1UY

e-mail:      sv1uy at sv1uy.ampr.org
PACKET MAIL: [email protected]

http://www.athnet.ampr.org/~sv1uy

Hi Demetre,

Your new ISP does not require a login before ppp starts. The junk you see in the log (and when dialing with minicom) is the ppp negotiation starting. Edit your connect script so it finishes after receiving CONNECT - remove the lines expecting 'sername:' and 'assword:' and anything else after that.

Mark.

Hi Mark,

Thanks a lot. It works now. I just have this problem of the link not going down after 4 minutes or so due to the multicast packets this ISP sends me every half a minute.

See my previous message please. Any ideas on this please? They are igmp and pim V2 hello packets. DIALD can ignore the igmp but the pim V2 hello are not ognored by DIALD.

===
73 de Demetre SV1UY

e-mail:      sv1uy at sv1uy.ampr.org
PACKET MAIL: [email protected]

http://www.athnet.ampr.org/~sv1uy

Hi Demetre,

Try a rule like this near the top of your filters:

ignore any ip.protocol=pim

Hope that helps!

Mark.

Hi Mark,

It worked straight away. I had already put a rule like "ignore pim any" but DIALD seemed to complain every time I started it. It did like "ignore igmp any" though which seemed peculiar, but nevertheless your idea works fine.

Thanks a lot!!!

===
73 de Demetre SV1UY

e-mail:      sv1uy at sv1uy.ampr.org
PACKET MAIL: [email protected]

http://www.athnet.ampr.org/~sv1uy

Hi guys,

Sorry to bother you again, but I found what was wrong with my configuration. In the /etc/diald/internet/config file I had written the pppd-options in more than one line.

When I included all my pppd-options in ONE line all was OK.

I hadn't realised that until now that I needed to connect to an ISP with PAP authentication!!!

===
73 de Demetre SV1UY

e-mail:      sv1uy at sv1uy.ampr.org
PACKET MAIL: [email protected]

http://www.athnet.ampr.org/~sv1uy