Reinstalling Suse I face this problem. Before this operation yast sucessfully detected all parameters and internet appeared at first boot.
Now it doesn’t work .
I connect through D-link network(switch-“свич” :))
Here there is I faced:
eth0 Link encap:Ethernet HWaddr 00:1F:C6:53:AC:CC
inet6 addr: fe80::21f:c6ff:fe53:accc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:16 Base address:0xcc00
I configured with Yast using my settings (which I have taken from windows ipocnfig) and adresses like 192. etc.
Nothing helped.
I found advice to use PPPoE. I have created it. But connection failed.
dsl0 Link encap: Point-to-Point Protocol
inet addr:10.64.64.64 P-t-P:10.112.112.112 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:1 errors:0 dropped:7 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:0 (0.0 b) TX bytes:55 (55.0 b)
I can’t say I can pinpoint the culprit exactly, what I can do, however, is list all the settings I find a little “suspect”, which may hopefully point you in the right direction:
1.png - ifup never worked for me; I always use NetworkManager
3.png - there’s no use in having the same DNS server as primary and secondary; it would be advisable moreover to enable “getting DNS via DHCP” if your Internet provider has that service (most ISPs do).
5. png - when troubleshooting network, the first thing to do is temporarily disable firewall altogether.
10.png - you have configured your connection to start manually. It may be better to enable start on cable connection.
15.png - the ifup, ifdown, ifstatus commands need your network interface as argument; in your case it should be eth0, if I see correctly. So: ifup eth0 (or ifstatus eth0).
I set up Network Manager as default.I set the connection to activate on hotplug. I deactivate firewall. I used “Update DNS VIA DHCP” but nothing helped.
At the last screen (ifconfig and ifup) I used not to configure, but to show information about connections.
Of course, I use ifup dsl0.
Also kIntenet connects through dsl0 (which I set with Yast), but not through eth0.
But I don’y sure this is correct.
I’d follow swerdna’s wise advice. By editing resolv.conf you may have messed up things additionally. In SuSE, YAST is the tool to use. I see you added a nameserver
nameserver 192.168.0.201
which means you have a DNS server on your internal network (LAN). On the other hand, you say you’re connecting through a switch which most certainly doesn’t have DNS capabilities. This may be a routing problem. How is your LAN configured if you have one? If I see correctly, you do manage to connect to your ISP, right? eth0 and dsl0 are both up and running, right?
I’ve done it!
The trable occured because of network cabel. I have bought longer one (than I have got) but some another (a man of techsupport said something about crossover - I don’t know what is it).
Inetresting detail is that Windows XP (I have 2 OS) succesfully worked with it on the same machine (driver sent traffic through this cable without noticing what it is), but Suse didn’t work.
So I thought that bug is in Suse, in it’s configs.
But I solve this problem. It costs me a killed partition of my data (music+soft) by 10 attempts to reinstall the system with automatic settings and without.
Thank you very much. This was the one forum, where members helped me all this time (Russian main forum about Linux stopped to help on 5th post).
>:(
Next day my situation repeated.
It seems that suse want a new cabel every day.
I have bought 3 new cabel and os (after two or three restarts) stopped working with it!
I have solved problem.
I think I must tell you because it is unbelieveable!
Using Suse I noticed that if a bulb of D-Link is switched off during boot there will be no internet.
Using windows it doesn’t depend, because it driver can “activate” it but how I didn’t know.
Also I noticed that if I install Suse (also I tried with mandriva, but it the same) internet will be, but after booting after windows it will be disappeared.
I supposed that this two things are connected.
I thought that problem can be in windows’s driver, not in linux. I suspected driver in “preventing network card working in Suse”.
It sounds crazy, but I had no other ideals.
To deceided to check my version. I used to reset computer after working windows, not proper shutdowning it.
And the result was the internet in suse appeared!
I was mainly shocked not because it appeared, but my version seems to be true. But how a driver of non-working system can make troubles for working???
Later I found answer. The driver used the so called “Wake up WLAN on boot” but deseabled it. That is my my network card waked up after windows driver is loaded and suse didn’t work.
The paradox is that problem of linux was solved using Windows Device manager (enable the option).
I am very suprised.
I remember now – we used to get lots of posts like this one recommending unplugging the power entirely after using windows before Linux. Asus M2n-e Onboard Nic - openSUSE Forums
