SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
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 recently installed ndiswrapper on opensuse 10.2. Everything was working ok until i rebooted. The Ndiswrapper module is loaded, and the network is up, but all the internet browsers can't get to the internet. I tried pinging the opensuse server and got a reply. Does anybody know how to rename interfaces, the system renamed wlan0 to wlan1 and i think that's the problem.
ok, i tried to recreate the interface, but at boot, it always renames it to wlan1 instaed of wlan0. the same thing happened to eth0, it was renmaed eth3
but I don't think the interface number has anything to do with browsers not being able to connect to the internet...they're just going to go to the protocol interface, and the protocol interface should be connected through the kernel to the interface or something like that.
ok, i tried to recreate the interface, but at boot, it always renames it to wlan1 instaed of wlan0. the same thing happened to eth0, it was renmaed eth3
Wouldn't this indicate that some other device or device set is taking wlan0 and eth0 ?
What is the content of /etc/resolv.conf? About the interface name problem, you need to edit the /etc/udev/rules.d/30-net_persistent_names.rules file and delete any duplicate entries and rename the interfaces as you wish.
ok, i tried to use the wired connection, but that one doesn't work either, it used to work before it was renamed. and when i tried again to redo the interface, it completly stopped working. now i can't even ping a server. also here is the content from /etc/resolv.conf
nameserver 192.168.11.1
search triad.rr.com
the devices were all working fine and properly named until i rebooted
I had a problem with LAN port numbers going up on each reboot. Here was that solution...
PROBLEM: On Each Reboot of your SuSE 10.2 Linux computer, the ETHx port assignment increments one adapter higher. (Exp. At Start you are eth0, then next it is eth1 and so forth)
WHY: The problem is related to how udev handles the hardware naming, incrementing it up each time your restart Linux.
SOLUTION: Remark out a rule setting and remove all previous ethx entries.
Here is the solution:
Start a terminal session and enter su and your password. Then use the VI text editor to modify two configuration files.
#vi /etc/udev/rules.d/31-network.rules //Load “31-network.rules” config file into VI
# comment out the first SUBSYSTEM== //add a # to comment out the first SUBSYSTEM rule
#wq // write modified file back to disk
#vi /etc/udev/rules.d/30-net_persistent_names.rules //Load “30-net_persistent_names.rules” config file into VI
#dd // Use the VI dd command to remove ALL ethx entries so that you will use eth0 on reboot.
#wq //Save modified file
You are done with the rule changes. Reboot your computer and then use Yast Network to reenter your network card using eth0 and the driver forcedeth. In my case, no network card appears in the list. You add a new network card with the default of device 0, static-0 and the forcedeth driver. Save your entries and reboot your computer. You should find that the network entry works and continues to be eth0 on each reboot.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.