Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have confugured my usb wireless stick using modeswitch.
It appears to be working OK, but I have a problem connecting to the internet.
When I run wvdial, ( my ISP is Bob.at in Austria )
The modem responds, it starts ppp and it waits for a carrier, It connects at 3600000, but then when it get to "Script /etc/ppp/ip-up run successful", then I get the Nameserver error.
I have looked at other threads on the forum, but none really answer my question. ie what do I do now ?
Thanks, both of you.
I should have mentioned I use Suse 11.4 and have tried unsuccessfully to use Yast to configure.
As far as I know the provider DNS is 194.48.124.185, there is also a secondary number there,´.200
In wvdail I have a line saying " Auto DNS = 1 " , is this the same as "ON" ?
resolv.conf file as far as I can see is just a comment file telling me to go and screw around with /etc/sysconfig/network/config file, so I have been doing just that.
I have tried putting in the DNS No. that I have into this under NETCONGIG_DNS_STATIC_SEARCHLIST and NETCONFIG_DNS_STATIC_SERVERS and also NETCONFIG_DNS_FORWARDER.
.. again, I am not really too sure what I am doing here
What I believe is supposed to happen is once you've made a connection (dialed, connected, authorized) then the PPP server should be giving you an IP address and the nameservers via DHCP. It sounds like something in that chain is failing. You should be using DHCP (Instead of static config) via PPP.
I wish I could be of more help, but I would Google the heck out of "wvdial", "dhcp", "ppp", "nameserver" and "dns" in various combinations.
As far as I know the provider DNS is 194.48.124.185, there is also a secondary number there,´.200
So you are saying that you know that the ISP has DNS servers at 194.48.124.185 and 194.48.124.200?
Do you get the chance to ping either of those addresses, or are saying that the connection auto-closes once the DNS error has happened?
And, while the connection is up, can you cat /etc/resolv.conf as....
Quote:
Originally Posted by EPS
resolv.conf file as far as I can see is just a comment file telling me to go and screw around with /etc/sysconfig/network/config file, so I have been doing just that.
That should not be the case: in the particular case of SUSE, Yast has had a reputation of making things a little more confusing when things go wrong, by putting settings back to what it thinks they should be, if you go around changing settings behind its back.
What I think is happening here is that Yast is using the setting in /etc/sysconfig/network/config to configure networking, but (in this particular respect) resolv.conf is what really causes changes to system operation. Where this really gets important is that other things change resolv.conf, too. So you may start up with some default settings in resolv.conf, Yast (and associated scripts) may then change those settings, and then DHCP or PPP may change them again, as networking actually starts up. This can be confusing, particularly if it is not what you were expecting.
Usually, the first step, if you think that DNS is not being correctly configured correctly, is to see if you do something with the IP address directly (thereby side-stepping the issue of whether DNS works, DNS not being needed in that particular case). So, if, for example:
ping w.x.y.z works, and the associated
ping www.somethingoranother.com doesn't, then it is usually the case that you can be sure that there is a DNS configuration error.
A worthwhile thing to remember is that Google have public nameservers at 8.8.8.8 and 8.8.4.4, at least one of those is a memorable address, and they do work (unlike some ISP nameservers, which can be, err, a bit intermittent, and not to be relied upon during debugging, because it adds an extra random factor, which can really mess you about, if they go wrong at a bad time).
Again, thank you for your replies.
I have not been able to "Ping" anything at all.
netstat -rn gives me:
destination 127.0.0.0 ; Gateway 0.0.0.0 ; Genmask 255.0.0.0
Can you tell me how to edit the resolv.conf file, as I think this may be where the conflict lies.
at present it looks like this, it's all just commentary:
### /etc/resolv.conf file autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
# NETCONFIG_DNS_STATIC_SEARCHLIST
# NETCONFIG_DNS_STATIC_SERVERS
# NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
# NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
# Note: Manual change of this file disables netconfig too, but
# may get lost when this file contains comments or empty lines
# only, the netconfig settings are same with settings in this
# file and in case of a "netconfig update -f" call.
#
### at least remove this warning if you change anything.
Here also is my wvdial dialog
Running as Root:
# wvdial bob
-->wvDial: Internet dialer version 1.60
-->Cannot get information for serial port
-->Initialising modem
-->Sending ATZ
ATZ
OK
-->Sending AT+CGDCONT=4,"IP","bob.at"
AT+CGDCONT=4,"IP","bob.at"
OK
-->Modem initialised
-->Sending: ATDT *99***1#
ATDT *99***1#
CONNECT 3600000
-->Carrier detected. Starting ppp immediately.
-->Starting pppd:2933
-->Using Interface ppp0
-->pppd:§§[06][08]§§[06][08]
-->pppd:§§[06][08]§§[06][08]
-->pppd:§§[06][08]§§[06][08]
-->pppd:§§[06][08]§§[06][08]
-->pppd:§§[06][08]§§[06][08]
-->local IP address 10.61.86.251
-->pppd:§§[06][08]§§[06][08]
-->remote IP address 10.64.64.64
-->pppd:§§[06][08]§§[06][08]
-->primary DNS address 194.48.124.202
-->pppd:§§[06][08]§§[06][08]
-->secondary DNS address 194.48.124.200
-->pppd:§§[06][08]§§[06][08]
-->Script /etc/ppp/ip-up run successful
-->Default route Ok
-->warning, no nameserver found '/etc/resolv.conf/'
-->Nameserver DNS failure, the connection may not work.
-->Connected ... Press Crtl-C to disconnect
I then press ctrl-C to terminate. That is where I stand at present.
Hello Repo, Thanks for the tip.
Sorry, but no help. I added the code as you suggested, but I still cannot make a connection.
So I still cannot ping anything either.
As indicated at the top of my /etc/resolv.conf file
"#/etc/resolv.conf file is autogenerated by netconfig! ", I am sure that this needs to be part of the problem, because anything I add to resolv.conf is just being overwritten.
However, I have went over the netconfig file several times and I cannot see where to insert a nameserver DNS.
It also say that manually changing this file ( ie the resolv.conf ), will automatically disable Netconfig. But I don't know if that is so ?
My latin is at an end now, and I cannot see any way forward, so I will gladly try any other thoughts.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.