Datum: Mon, 05 Mar 2012 01:48:14 +0100
Von: Philippe Vouters<philippe.vouters@xxxxxxxxxxx>
An: Ludwig Gebauer<ludwiggebauer@xxxxxxx>
CC: junker@xxxxxxxxxxxxxxxxxxx, olivares14031@xxxxxxxxx, discuss@xxxxxxxxxxxxx, goldberg@xxxxxxxxxxxxxxxxxxxx
Betreff: Re: pppd and DNS [WAS:Driver for 536ep-Modem does not compile]
Dear Ludwig,
Read chapter 11.4. Starting the BIND Name Server at
http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.dns.html
This documentation and chapter matches your openSUSE version and problem.
As far as I understand it, you should set 127.0.0.1 as your nameserver
in /etc/resolv.conf and keep NETCONFIG_DNS_POLICY as auto as you already
have. You ought to not be able to get the correct DNS servers for your
DHCP connection if you otherwise proceed with /etc/resolv.conf. Again
this way to proceed is very special to openSUSE and has no
correspondance on Fedora.
Yours truly,
Philippe
Le 05/03/2012 01:15, Ludwig Gebauer a écrit :
Hello Philippe,
in openSUSE 10.3 (where everything works well), in the
/etc/sysconfig/network/config file exists the simple and interesting option:
## Type: yesno
## Default: yes
# There are some services (ppp, ippp, dhcp-client, pcmcia, hotplug) that
have to
# change the /etc/resolv.conf dynamically at certain times. E.g. if
ppp/ippp
# establishes a connection and is supplied by the peer with a list of
# nameservers. Or pcmcia needs to set the correct nameserver for the
choosen
# configuration scheme. If you don't like these services to change
# /etc/resolv.conf at all, then set this variable to "no".
# If unsure, leave it at the default (which is "yes").
#
MODIFY_RESOLV_CONF_DYNAMICALLY="yes"
in openSUSE 11.4 (where the problems with resolv.conf arise), I find
instead the following DNS relatet options:
NETCONFIG_DNS_POLICY="auto"
NETCONFIG_DNS_FORWARDER="resolver"
NETCONFIG_DNS_FORWARDER_FALLBACK="yes"
NETCONFIG_DNS_STATIC_SEARCHLIST=""
NETCONFIG_DNS_STATIC_SERVERS=""
NETCONFIG_DNS_RANKING="auto"
Please, give me some time to read (and hopefully, unterstand) the
related man pages. Of course I would appreciate to get some hints :-)
In SuSE, the default dialer is Kinternet/Qinternet, not kppp. I have no
experience with kppp, am a bit short of time, so I ask for your
understanding that I will not tune into this issue.
Regard
Ludwig
-------- Original-Nachricht --------
Datum: Fri, 02 Mar 2012 16:33:34 +0100
Von: Philippe Vouters<philippe.vouters@xxxxxxxxxxx>
An: Wolfgang Junker<junker@xxxxxxxxxxxxxxxxxxx>, Ludwig
Gebauer<ludwiggebauer@xxxxxxx>
CC: Jacques Goldberg<goldberg@xxxxxxxxxxxxxxxxxxxx>,
discuss@xxxxxxxxxxxxx, olivares14031@xxxxxxxxx
Betreff: Re: pppd and DNS [WAS:Driver for 536ep-Modem does not
compile]
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.
--
Philippe Vouters (Fontainebleau/France)
URL: http://vouters.dyndns.org/
--
Philippe Vouters (Fontainebleau/France)
URL: http://vouters.dyndns.org/
