I manage to get my mobile broadband working (connected, I mean) in both root & user account. However, my web browser, IM etc only work in root account. In user, knetworkmanager does show that my Huawei E160G is working fine, connected but I still can’t surf the net & chat. I’ve included the dialout & uucp group for user account but that still doesn’t resolve the problem
I had the same problem with a Huawei E 620.
It got better through setting in yast under editor of /etc/sysconfig under “network” - “general” - “DNS_policy” the value STATIC_FALLBACK ppp NetworkManager*
Curiously I still have problems (especially if the suspend mode was on, because the modem does not wake up). But if it does connect fine.
If not, I do the following: I disconnect, then I open Yast, go to network - modem - open the modem values with modify, and without modifying anything I click all to the end with OK.
The modem is rewritten and magically now connects. Annoying but I did not find any hint on how not to have the issue.
sorry for the late reply
here’s the output for cat /etc/resolv.conf when running in user account.
yoda@linux-nor4:~ # cat /etc/resolv.conf
### /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.
#
### Please remove (at least) this line when you modify the file!
yoda@linux-nor4:~ #
this is the output when running in root account:
linux-nor4:~ # cat /etc/resolv.conf
### /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.
#
### Please remove (at least) this line when you modify the file!
nameserver 203.82.64.41
nameserver 203.82.64.67
linux-nor4:~ #
it seems that DNS entries are not updated when running in user account. how can I make it updated?
pdc_2,
I logout from user account & login to root account. right click on the network manager icon on systray & click on the mobile broadband profile to activate it. the same thing i did on user account.
I had a similar problem after an update to network manager 0.7.1. I changed the dns values by hand into /etc/resolve.conf
My modem does connect now, but I did not check up to now if the other means (wlan/cable) connect correctly (and have no way to do so right now).
Cheers.
Unfortunately, I can see a lot of threads related to this issue - “DNS entries are not updated”. Most users just shout that the Internet is not working in oS11.2! We cant blame them because in a lot of cases, it was working under oS11.1 and now, they got the new version and it stopped working!!
I am not 100% sure that this issue is fully solved even with the latest networkmanager. Also, I am not sure if the issue really lies with the networkmanager or something else. I am saying this because in one case, the networkmanager was showing the correct DNS entries (comes up in the tooltip text of the connection), but the /etc/resolv.conf was not updated!
I set NET_CONFIG_DNS=“auto” in /etc/sysconfig/network/config file, removed /etc/resolv.conf file and did a “rcnetwork restart” but the DNS were still not updated. However, it got updated after a reboot!!
I cannot confirm this. I have 11.1 and KDE3.5 and only trouble all the way through. It simply worked for me in 11.0. Same hardware and provider.
I can confirm this. I do not think either this is only a problem of networkmanager, the whole thing seems severely troubled. I have curious behaviors (like networkmanager would not dial - but it DOES dial if you open beforehand yast and do a modem recognition by hand).
I can confirm this behavior also in 0.7 and KDE3.5. It would work in one session…and then not anymore. I also removed /etc/resolve conf.
However at the end I did use the dns policy:
NETCONFIG_DNS_POLICY=“STATIC_FALLBACK ppp* NetworkManager“ and then I told Netconfig in /etc/sysconfig to search statically only for the DNS numbers that I did previously saved (during one of these “grace periods” when all was working).
Now it seems stable (if stable is that you have to open yast to do modem recognition and only then are able to dial).
In the program previsions for KDE 4.3.4 (Schedules/KDE4/4.4 Feature Plan - KDE TechBase) you find a commitment that they are going to update it with stable and working code …and it is signed already as DONE (so at least for you there is hope) - I remember an article in news that explained about the whereabouts of the delay. Still, it is curious that in a world where laptops, nettops, netbooks and portatile linux devices gain ever-growing performance it had to come to this point.
If anybody is around and knows how to get rid of the necessity to open yast in order to dial out with my umts-huawei-pcmcia modem I would be greatful (registered as /dev/ttyUSB0).
I tried also to join me to the tty group but did not help. I can live with it, but it is quite annoying.
switch133 wrote:
> Is there any workaround for this?
please, do not log into KDE, Gnome, XFCE or any other GUI as root…
there is no end to the trouble that may be caused by doing so…
i do not know why you have trouble connecting to the net…but i am
sure that logging into a desktop environment is much more likely to be
a problem maker than a solution, or even part of the solution…
matter of fact, it might be that logging in as root can and did cause the problem…
everything that needs root powers to be accomplished can be done
without logging into the desktop environment as root.
here are four (of thousands) of posts and web articles on this subject:
I notice an improvement after updating the networkmanager, deleting resolv.conf & running rcnetwork restart. DNS is auto updated (user account) now. however, the only problem is I still can’t browse the internet although the wireless broadband connection is active. when running nslookup, the error message mentions that it couldn’t reach the server. I’m still working on the solution for this problem. thanks for sharing some workaround although it didn’t work for me.
well yeah, I admit. running root account in any desktop environment does posses great security risk. but if that’s the only way I could get connected, perhaps I should try to live with it (till I manage to get my user account connection working).
I do not think you did get the point of not logging into a GUI as root. The security problem is only one aspect. The real problem are the file permissions. The root does alter the permissions inside your home. Little by little your user account gets totally screwed up (owner of hidden files and permissions will be root) so this is, as far as I did understand it, the real big problem of running a GUI as root.
then I ran wvdial to see the output. an error message appeared stated that no DNS in resolv.conf. using firefox, I still can’t browse the internet. so I edited /etc/resolv.conf to become like this:
# Generated by NetworkManager
nameserver 203.82.64.41
nameserver 203.82.64.67
dialled using KInternet & there you go…I got my connection working fine. web browser & IM client are fully functioning now.
I no longer need to login to root GUI to surf & chat. Thanks everyone for your help & advice.
I did it before but using Knetworkmanager, I still couldn’t get connected (for user account). Only after I decided to change to KInternet, it works fine.