When I use wvdial, I can't auth with server with pap/chap auth - auth failed (with terminal auth is OK) After failed connection /etc/ppp/*-secrets are empty (should have line with user and secret) If I edit by hand /etc/ppp/pap-secrets and write username-secret pair, wvdial connects without any problems I use root account, wvdial has permissions to write /etc/ppp/*-secrets Conclusion: wvdial doesn't write user-secret pair from /etc/wvdial.conf to /etc/ppp/pap-secrets, /etc/ppp/chap-secrets Additional info: root@dell pawelj # which wvdial /usr/bin/wvdial root@dell pawelj # strings /usr/bin/wvdial | grep pap-secrets root@dell pawelj # Strange? root@dell pawelj # emerge -pv wvdial These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] net-dialup/wvdial-1.53-r1 Reproducible: Always Steps to Reproduce: 1.emerge wvdial, wvdialconf, edit /etc/wvdial.conf 2. connect using wvdial with pap/chap auth (dumb mode) 3.connect with wvdial Actual Results: auth fail Expected Results: auth OK Portage 2.0.49-r20 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.4.22) ================================================================= System uname: 2.4.22 i686 Mobile Intel(R) Pentium(R) 4 - M CPU 1.70GHz Gentoo Base System version 1.4.3.10 ccache version 2.3 [enabled] ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=pentium4 -Os -pipe -DNDEBUG -DG_DISABLE_ASSERT -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=pentium4 -Os -pipe -DNDEBUG -DG_DISABLE_ASSERT -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://212.219.247.14/sites/www.ibiblio.org/gentoo/ http://212.219.247.12/sites/www.ibiblio.org/gentoo/ http://212.219.247.17/sites/www.ibiblio.org/gentoo/ http://mirrors.sec.informatik.tu-darmstadt.de/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X alsa apm arts avi berkdb crypt cups encode esd foomaticdb gdbm gif gnome gpm gtk gtk2 imlib java jpeg kde libg++ libwww mad mikmod motif mozilla mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl slang spell sse ssl svga tcpd truetype x86 xml2 xmms xv zlib linguas_pl_PL"
I dug through the 1.53 source code. In order to write to /etc/ppp/{pap, chap}-secrets, the wvdial program calls the function WvPapChap::put_secret. After checking the source tree, this function is only called in two places, the first is papchaptest.cc (which is just a test program, not part of the wvdial program) and wvdialer.cc (which is commented out!). Secondly, the program doesn't seem to be reading it's own configuration files (at least as far as the username/password is concerned). The documentation says that this program reads from /etc/wvdial.conf (which contains a Username and Password field) and automagically updates {pap,chap}-secrets on its own (and indeed the functionality is there in the program, just never called). So, for the time being it seems that this version of wvdial only works if you already set the contents of /etc/ppp/pap-secrets and/or /etc/ppp/chap-sercrets. Should this problem be thrown upstream to the wvdial maintainers?
Ok, just found the source for the new version of wvdial on their website. Source code says: // PP - Put this back in, since we're not using passwordfd unless we're // SuSE... how did this work without this? WvPapChap papchap; papchap.put_secret( options.login, options.password, options.remote ); Looks like this is a known issue, and is fixed in 1.54. Basically, wvdial is borked until you upgrade to version 1.54 (or you manually edit {pap,chap}-secrets yourself).
So to resolve bug we should upgrade wvdial to 1.54 (current 1.53) and wvstream (needed by wvdial) (current 1.70) to 1.74. I try do it, but wvstream 1.74 I can't compile :-( (db related error)
Did you try to compile the source yourself or did you use the ebuild in portage for wvstreams? I did: emerge sync ACCEPT_KEYWORDS="~x86" emerge wvstreams And it built just fine. If you had trouble building the wvstreams package using emerge you should file a seperate bug report.
this is fixed in 1.54.0
