-------- Message original --------
Sujet: Re: pppd and DNS [WAS:Driver for 536ep-Modem does not compile]
Date : Sun, 04 Mar 2012 22:12:39 +0100 (CET)
De : Wolfgang Junker <junker@xxxxxxxxxxxxxxxxxxx>
Pour : Philippe Vouters <philippe.vouters@xxxxxxxxxxx>
Copie à : Jacques Goldberg <goldberg@xxxxxxxxxxxxxxxxxxxx>, Ludwig
Gebauer <ludwiggebauer@xxxxxxx>, discuss@linmodems.orgame,
olivares14031@xxxxxxxxx
Dear Philippe and Jacques,
kppp is a mess...
I don't even see a well-defined behaviour:
Case 1) kppp says "modem ready", then "modem doesn't answer".
No connection, no log-output. Perhaps some lock-file, but I don't
know where? It has nothing to do with AT-commands because:
Case 2) kppp connects with my internet provider, the connection
is stable, but no throughput, because DNS-names cannot be
resolved, i.e. the same DNS-issue as we had before, although kppp
uses the same /etc/resolv.conf file as wvdial and modifies it
with the same DNS-adresses as wvdial.
(But I don't have a second wvdial.conf file in my system.)
I don't have a clue when case 1) and when case 2) happens. And
wvdial works all the way.
Today I managed to setup the modem for sending faxes with
Hylafax, and everything seems to work fine as far as I can say
after one test. So for my part I am quite happy that I can send
faxes and connect to the internet with wvdial if this should be
necessary. I can live without kppp. But if you insist on
resolving this issue I am ready to follow your advices. I
couldn't make anything out of strace because it output thousands
of lines on my shell and I didn't know what to look for...
Sincerely
Wolfgang
On Sun, 4 Mar 2012, Philippe Vouters wrote:
Jacques, Wolfgang, Ludwig,
An excellent way to troubleshoot kppp with what Jacques states is to run
strace over kppp and to analyze each open to get the device/file name kppp
attempts to open.
To run strace, refer to:
http://vouters.dyndns.org/tima/Unix-OpenVMS-Tracing_system_calls.html
Philippe
Le 04/03/2012 08:44, Jacques Goldberg a écrit :
Friends,
Excuse me for a trivial check which you perhaps did not yet hear about.
Actually as far as I remember KPPP works using wvdial behind the scene
with a configuration file wvdial.conf hidden elsewhere than the regular
place. A sudo updatedb followed by a sudo locate wvdial.conf will reveal
if there is such a file and probably show as /dev/modem as device in
that file.
A trick is needed with kppp, and I forgot which, to make kppp know the
name of the driver device. If I remember well kppp tries /dev/modem and
allows the user, through the configuration menu. to use /dev/ttyS1
through /dev/ttyS4 and abandons if no modem found. I think but I am not
sure that the trick is to place the right device name in the hidden
wvdial.conf.
It is of course tempting to think of a link of the actual driver device
to /dev/modem but it must be re-created after the port creation at each
boot because the port (the udev thus the /dev) isn't there yet !
I must add that I have not had any experience with SuSE which, again,may
well have its own way to do this thing.
Regards - Jacques
On 03/03/2012 11:13 PM, Philippe Vouters wrote
Wolfgang,
Run minicom and issue ATI AT commands to check whether the modem is
responding. Your "modem doesn't answer" with kppp tells me the modem
is not responding to ATI AT commands.
[philippe@victor ~]$ minicom
Device /dev/modem access failed: No such file or directory.
[philippe@victor ~]$ cat .minirc.536ep
# Fichier généré automatiquement - utilisez le menu de configuration de
# minicom pour changer les paramètres.
pr port /dev/536ep
pu minit ^M~AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0^M~
pu mdropdtr 1
pu hasdcd Yes
pu rtscts Yes
[philippe@victor ~]$ cd intel-536-537/
[philippe@victor intel-536-537]$ make 536
cd coredrv; make clean
make[1]: Entering directory `/home/philippe/intel-536-537/coredrv'
rm -f *.ko .*.o.cmd *.mod.c .*.ko.cmd *.o *~ core Module.* modules.*
rm -rf .tmp_versions
make[1]: Leaving directory `/home/philippe/intel-536-537/coredrv'
rm -f *.o *.ko
Module precompile check
Current running kernel is: 3.2.7-1.fc16.i686
/lib/modules... autoconf.h exists
diff: /boot/vmlinuz.autoconf.h: No such file or directory
autoconf.h matches running kernel
diff: /boot/vmlinuz.version.h: No such file or directory
version.h matches running kernel
make[1]: Entering directory `/home/philippe/intel-536-537'
3.2.7-1.fc16.i686
make[2]: Entering directory `/home/philippe/intel-536-537/coredrv'
make -C /lib/modules/3.2.7-1.fc16.i686/build
M=/home/philippe/intel-536-537/coredrv modules
make[3]: Entering directory `/usr/src/kernels/3.2.7-1.fc16.i686'
CC [M] /home/philippe/intel-536-537/coredrv/coredrv.o
CC [M] /home/philippe/intel-536-537/coredrv/clmmain.o
CC [M] /home/philippe/intel-536-537/coredrv/rts.o
CC [M] /home/philippe/intel-536-537/coredrv/task.o
CC [M] /home/philippe/intel-536-537/coredrv/uart.o
CC [M] /home/philippe/intel-536-537/coredrv/wwh_dflt.o
CC [M] /home/philippe/intel-536-537/coredrv/locks.o
CC [M] /home/philippe/intel-536-537/coredrv/softserial_io.o
CC [M] /home/philippe/intel-536-537/coredrv/softserial_ioctl.o
CC [M] /home/philippe/intel-536-537/coredrv/softserial.o
LD [M] /home/philippe/intel-536-537/coredrv/Intel536.o
Building modules, stage 2.
MODPOST 1 modules
CC /home/philippe/intel-536-537/coredrv/Intel536.mod.o
LD [M] /home/philippe/intel-536-537/coredrv/Intel536.ko
make[3]: Leaving directory `/usr/src/kernels/3.2.7-1.fc16.i686'
make[2]: Leaving directory `/home/philippe/intel-536-537/coredrv'
make[1]: Leaving directory `/home/philippe/intel-536-537'
[philippe@victor intel-536-537]$ sudo make install
make[1]: Entering directory `/home/philippe/intel-536-537'
rm -f /etc/hamregistry.bin
bash Intel536_inst
running kernel 3.2.7-1.fc16.i686
installing hamregistry, used for persistant storage
installing Intel536 driver
install REDHAT Intel536 boot script and links
starting module and utilities
hamregistry: no process found
done
make[1]: Leaving directory `/home/philippe/intel-536-537'
Minicom screen:
---------------
Welcome to minicom 2.5
OPTIONS: I18n
Compiled on Apr 6 2011, 07:59:01.
Port /dev/modem
Press CTRL-A Z for help on special keys
AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
OK
ATI
OK
ATI0
OK
ATI1
Intel V92 Data Fax Voice
OK
ATI2
Intel Corporation
OK
ATI3
536EP
OK
ATI4
536EP Release 4.69 - Jul 09 2004 - 18:19:48
OK
ATI5
V.92 Capable Modem
Host I/F: PCI
OK
ATI6
DSP Patch Level:09.82
OK
CTRL-A Z to get the help.
Yours truly,
Philippe
Le 03/03/2012 19:12, Philippe Vouters a écrit :
Dear Wolfgang,
Any news from you with kppp ? Did you progess on this topic ?
Dear Ludwig,
As far as I can guess and possibly thanks to mails exchanges with
Wolfgang, you should now have a working wvdial/pppd connection.
Would it happen you would also be interested with kppp ? Please let
everyone know.
Grüsse aus Fontainebleau/Frankreich,
Philippe
Le 02/03/2012 16:33, Philippe Vouters a écrit :
Wolfgang, Ludwig,
Would such information be of some help for you to configure kppp ?
http://www.nairaland.com/nigeria/topic-259411.0.html
Regards,
Philippe
Le 01/03/2012 00:02, Wolfgang Junker a écrit :
Dear Philippe,
I think your hint to
https://bugzilla.novell.com/show_bug.cgi?id=465679
really solves the problem:
I didn't understand what they were saying but I have put
NETCONFIG_DNS_POLICY="STATIC_FALLBACK ppp0 NetworkManager"
into my /etc/sysconfig/network/config (or equivalently into the
mask of
the editor of YAST for the Network-configuration under
/etc/sysconfig).
Now if I plug off the ethernet cable and do $wvdial I get a working
internet connection and ppp's DNS-address is dynamically added to
/etc/resolv.conf:
search localdomain site
nameserver 195.50.140.248
nameserver 145.253.2.203
nameserver 192.168.0.1
I still couldn't make kppp work (it says "modem doesn't answer") but I
hope to resolve this issue also.
Many thanks for your help!
Wolfgang
On Wed, 29 Feb 2012, Philippe Vouters wrote:
Hello Ludwig, Wolfgang,
Have a look at this openSUSE bugzilla :
https://bugzilla.novell.com/show_bug.cgi?id=465679
I think this can indeed help you. This is very openSUSE specific
Kind regards to both.
Philippe
Le 29/02/2012 21:50, Ludwig Gebauer a écrit :
Hello all,
DHCP is installed, the system accepts to get adresses from a router
with DHCP server.
Added usepeerdns to /etc/ppp/options. As described in man pppd, the
following files were created:
/var/run/ppp_resolv.conf.ppp0
nameserver 195.129.111.50
nameserver 195.129.111.49
/var/run/ppp_resolv.conf.dsl0
nameserver 217.0.43.1
nameserver 217.0.43.193
...but apparently not passed to pppd ("ppp 2.4.5-5.1-i586 from
vendor
openSUSE"). Browsing via dial-up modem failed. The nameserver
addresses are correct.
My DSL device is new, but rather old fashioned. It is merely a
modem,
not a router. It does nothing else than convert IP-packages to DSL
format and vice versa. It can not be configured, it gets the
internet
access data every time it is startet from pppd resp. smpppd.
Regards
Ludwig
-------- Original-Nachricht --------
Datum: Wed, 29 Feb 2012 15:05:38 +0200
Von: Jacques Goldberg<goldberg@xxxxxxxxxxxxxxxxxxxx>
An: Ludwig Gebauer<ludwiggebauer@xxxxxxx>
CC: Philippe Vouters<philippe.vouters@xxxxxxxxxxx>,
junker@xxxxxxxxxxxxxxxxxxx, olivares14031@xxxxxxxxx,
discuss@xxxxxxxxxxxxx
Betreff: Re: pppd and DNS [WAS:Driver for 536ep-Modem does not
compile]
Dear Ludwig,
Please forgive me to remind here, since I do not know you, that
wvdial/wdialconf are not programs that operate the communication
but
rather friendly utilities that prepare the parameters (data) for
the
real program which does the work, pppd.
Now please can you tell us if there is or not a line usepeerdns in
your file /etc/ppp/options
If there is not, please add that line.
Then please try to connect to your analog modem ISP with wvdial and
Auto
DNS = yes, do not worry for what there is or not in
/etc/resolv.conf
because in this case pppd should NOT use /etc/resolv.conf,
disconnect
the cable from DSL to PC to make sure that you use the analog
modem,
and
try to surf the Web, like Google or others. Does it work?
If it works (it should), reconnect your DSL, make it work by adding
the
DSL DNS in /etc/resolv.conf if necessary (see Note) and give the
following commands in a separate window as superuser (the first
takes
time), while wvdial (pppd) is still running: updatedb ,then this
long
composite command for f in `locate resolv.conf* `;do echo $f;cat
$f;done so that you can see the contents of the various
resolv.conf present on your computer.
Note: if your DSL box is not old, and I am sure you were given a
brand
new one since DSL is new in your place, configure your PC
(Linux) for
the DSL connection to take DNS's from the DSL box (do not define
/etc/resolv.conf and make it clear in the network s\manager
definitions, no local name server, no local DNS). Your DSL box
normally
comes configured such that the DSL box takes itself
automatically the
DNS addresses from the network. You may want,and even need, to
check
that your DSL box is configured like that. That way you should not
hear
of DNS's any more once you have usepeerdns in your /etc/ppp/options
.
Regards
Jacques
n 02/29/012 02:00 PM, Ludwig Gebauer wroteresolv.conf
With "Auto DNS = yes" in wvdial.conf, DNS addresses show up in the
wvdial protocol, when running wvdial (ISP: www.yooline.de ),
whether
network manager is activated or not. wi And whether network
manager is
activated or not, I have to edit resolv.conf manually. Since a few
weeks, DSL exists here in my village, 12 km afar from Brunswick (so
much
about the highly industrialisated etc. country Germany), and
with my
DSL
_modem_ (not a modem _router_!) I have the same effect: DNS
addresses
must be transferred manually to resolv.conf. Seems to be an
openSUSE
11.4 issue.
