Arch Linux

STiAT

Member

From: Vienna, Austria

Registered: 2004-12-23

Posts: 606

wvdialer and my problems

Hey guys,

First of all - yes, my connection is up and running ;D.

There still are some glitches:
- Running wvdial as a normal user
- DNS Servers won't show up in /etc/resolv.conf

$ ls -la /dev/ttyUSB0
l rwxrwxrwx 1 root root 8 2007-07-02 21:11 /dev/ttyUSB0 -> tss/USB0
$ ls -la /dev/tts/USB0
c rw-rw---- 1 root tty 188, 0 2007-07-02 21:12 /dev/tts/USB0
$ groups
root bin sys adm tty disk wheel log dbus hal network video audio optical storage camera users

Running wvdial:

WvDial<*1>: WvDial: Internet dialer version 1.56 (root@laptop)
WvDial<Err>: Cannot open /dev/ttyUSB0: Device or resource busy
WvDial<Err>: Cannot open /dev/ttyUSB0: Device or resource busy
WvDial<Err>: Cannot open /dev/ttyUSB0: Device or resource busy

Good, so i need to start wvdial as root - why so?

Also a problem seems - the resolv.conf isn't updated. Is there any way so i don't have to set it manually?

Yours,
Georg

---

Ability is nothing without opportunity.

PenguinFlavored

Member

From: Chicago, IL, USA

Registered: 2006-06-06

Posts: 66

Website

Re: wvdialer and my problems

What are your permissions on resolv.conf? Can you edit it as the non-root user.

---

penguinflavored.com

STiAT

Member

From: Vienna, Austria

Registered: 2004-12-23

Posts: 606

Re: wvdialer and my problems

666 is the permission on the file.

Wouldn't  help anyway, since i don't seem to have permission on the device, what would be my first problem in this case.

Last edited by STiAT (2007-07-03 15:55:23)

---

Ability is nothing without opportunity.

gradgrind

Member

From: Germany

Registered: 2005-10-06

Posts: 921

Re: wvdialer and my problems

I tried the various ppp connectors a few months ago (about four or five of them). A couple I couldn't get to work at all, then there were wvdialer and chestnut-dialer which I did get to work after fiddling around a bit and scouring through the docs. I remember the problem with resolv.conf - but stupidly I did not write down how to get around it. Could it be that it creates its 'own' resolv.conf in /etc/ppp (or was that one of the other programs ...)?
Generally these programs need to be run as (suid) root - primarily because of /etc/resolv.conf I think. If I remember correctly chestnut-dialer will work as a normal user - if you change the permissions on resolv.conf. I believe the device permissions can be handled by putting the user in the appropriate group.
In the end, I settled for kppp - in spite of the kde dependencies - because it has always worked out-of-the-box (for me).

---

larch: http://larch.berlios.de