[Ping sktsee] Re: Agere WinModem 56k on Thinkpad - Working!

[sktsee]

On 07/09/2011 01:17 PM, NoOp wrote:
> On 07/09/2011 09:47 AM, sktsee wrote:
> ....
>>
>> At first glance, it looks to be a script problem with the dial string
>> being sent as a response to remote's sign-on prompt, however I'm not
>> familiar enough with wvdial or gnome-ppp to assess whether that's the
>> case. I've always used pppconfig to setup dial-up networking. It also
>> uses pppd and chatscript, but maintains separate dialing profiles from
>> that of wvdial or gnome-ppp. However, to begin troubleshooting I would
>> start by ruling out whether the modem or modem driver is responsible for
>> the auth issue. To do that, install the Minicom terminal communications
>> program and set a dialing entry for your ISP. Dial it and see if you can
>> establish a terminal session with your ISP remote access server. If it
>> connects, you should be to manually enter your username and password
>> when prompted causing the remote access server to start a PPP session
>> (though just in minicom, pppd won't see it). This will test that the
>> modem, its driver, and your username and password are correct, and the
>> problem is most likely in the dialing script or in pppd's configuration
>> (/etc/ppp/options may need some tweaking).
>>
>> As I mentioned above, I used pppconfig to setup dial-up networking. It's
>> menu driven and uses pon/poff scripts which don't require root
>> privileges to start/stop sessions . I'd recommend using it to setup your
>> dial-up networking ISP profile and see if that solves the authentication
>> issue.
>>
>
> Got it working! Had to run gnome-ppp as root (gksu) and put in stupid
> mode (Ignore terminal strings (stupid mode))&  it now connects:
>

Cool!

> Now I need to sort out why I need to use 'gksu' and then on to figuring
> out hylafax or similar so that I can finally get rid of my old fax
> machine :-)
>
>

You might try adding you user account to the "dip" group and possibly 
changing the martian modem daemon command line to use "--group=dip" 
instead of "--group=dialout"  I think I used dialout because the udev 
rule for the old ltserial and ltmodem device files did. But pppd is 
setuid and owned by the dip group so it really makes more sense to have 
ttySM0 created with the dip group permission.

Also concerning permissions, apparently wvdial needs write permission to 
those {pap,chap}-secrets files. To get rid of those PAP/CHAP warnings, 
just add read/write perms for the "dip" group to those files and 
hopefully you won't need to run gnome-ppp with root privs.

-- 
sktsee