Internet used to work. Then the head of the house changed a bit of the setup. We used to have our modem/router go to another router which then sent cables out to all the PCs (modem/router -> router -> PC). He replaced the router with a switch because it was causing issues with all the other computers (using Windows) in the house (modem/router -> switch -> PC).
I had the nice surprise of losing my internet all together. After playing with the settings for a few days my internet magically came back when the computer started one day (I may have changed a setting the day before and not restarted; but I was so lost I don’t really remember what happened).
Keep in mind that I have duel boot with Windows XP and all the while the internet has worked fine there.
So the internet started working again in Linux but I noticed it was slower than usual; in fact my internet in Linux always seems to be slow. So I started playing with the settings again and now the internet is not working AGAIN! So here I am. I’ve spent far too long messing with this.
What info do y’all need to help me me out? I’m not to good at understanding this internet stuff and I’ve been learning a lot the last couple days but it just doesn’t seem to be enough. i.e. DHCP, DNS, IPs, etc. and how they all interact… I’ve probably completely scrambled all my setting trying to get this to work.
How do I type in a webpage address without the forum turning into a link, like the ones above?
Additional options under the post box, in advanced.
Your network card isn’t up…
So lets try…
First your PC has no ip so it has to get an ip…
So to get an ip it asks whether anyone has an address for it(DHCP)
Now normally the router gives them out, it isn’t always necessary to use DHCP as you can use static.
Now once the router gives out an IP with DHCP it will send info in regards to where it should look up url to IP translation. Google in computer terms is ... this is DNS, now on linux it will store the info in resolv.conf. Many times this will point to the router who will then ask the ISP what Googles number is.
I’ve over simplified but should help you grasp the basics.
Now from the looks of things your network card isn’t up, you want on boot and dhcp, then the rest should work it’s self in…
When you get ifconfig with an eth* and ip you’re the next step in, and should be all that is needed.
Mmm you got me there Akoellh nearly said but not wireless…
@Atomos
That script will help troubleshoot, but I’m hoping with a little more understanding you can get a few steps further in. If you can get the output of the script up it will help a lot more. It isn’t just wireless, but a very good networking troubleshooting script.
As I’m sure you can imagine this is a bit time consuming, as I have to restart each time I do this. So before I try anything else I thought I ought to mention something.
When I go into yast, then into the DSL settings, I add my network card and finish; yet every single time I go back it no longer recognizes my card. Any idea what might cause that. It usually says something like “Unknown device”, even though my network card appears in the drop down menu.
— Which type of your network connection should be tested?
— (1) Wired connection
— (2) Wireless connection (WLAN)
— Please answer with 1-2:1
— What’s the type of networktopology?
— (1) DSL modem <—> LinuxClient
— (2) DSL HW router <—> LinuxClient
— (3) DSL modem <—> LinuxRouter <—> LinuxClient
— (4) DSL HW router <—> LinuxRouter <—> LinuxClient
— Please answer with 1-4:1
— Analyzing system for common network configuration errors…
!!! CND0110E: For the selected connection type there was no active network interface found on your system
!!! CND0310W: Classic network configuration with ifup was detected. Configuration with knetworkmanager is much easier
— Collecting networkconfiguration information …
— Go to Fehlermeldungen/Errormessages | collectNWData.sh Fehlermeldungen to get more detailed instructions about the error/warning messages and how to fix the problems
— If you still don’t have success then post the contents of file collectNWData.txt in your favorite Linux forum. For an alternative read Webseiten für Text- und Bilderuploads/Websites for text and image uploads | collectNWData.sh
It looks like I’m supposed to look up some error codes but I had some other ideas too so if this means anything let me know otherwise I’ll post again with what I find.
Well I suppose this is how it always ends. I feel like a total idiot!
All this stuff seemed to be pointing to my network card so I decided to check it one more time. For some reason (I probably accidentally did this when I was messing with the settings before) the Device Activation option was set to “Never”. I set it to “At Boot Time” and restarted. Now I’m posting this message in Linux. Everything seems to be working and up to speed; except YouTube, that always seems slow, at least when I play the videos on full screen.
ok, now I’m curious (partially because my email app. is now not working).
First, what were you saying about not using the DSL settings? We have a DSL Router, I believe. I don’t think I understood the difference between a modem and a router before but I think I do now. It’s an “Actiontec DSL Modem” w/ wireless gateway (I’m using Ethernet though). It’s description is “a modem with routing capabilities.” So, that’s a little confusing to me. If I still should not use the DSL settings than what should I use?
By the way, the router is then connected to a “Netgear 8 port switch” (where all the cables come and go) which I have been told should not interfere with anything.
Second, that little diagnostic script thingy says I should use knetworkmanager because it’s easier. I did a little search and everyone seems to hate it so I’m sort of at a loss. Any opinions on this?
I feel like I have to get to the bottom of things; working is not enough, I have to understand why it works. and things still seem a bit fishy on my machine.
Just the explanation of the part “Why you should not use DSL settings on the Linux machine even though you have a DSL router?”
The DSL router (or any router) has at least 2 sides. In your case, one side of the router is connecting to the ISP and that side is the DSL part. The other side where your Linux machine is connected to, is a small Ethernet wired switch. (It has got another side too and that is the Etthernet wireless side). So, from the point of view of your Linux machine, it is just connected to a wired Ethernet switch.