Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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 just installed Suse Linux 9.2, it's looks great and I'm really looking forward to operating without viruses, spyware and the rest of that nonsense.
There's just one thing: I don't seem to be on-line and it's not clear what I should do about it. I followed the instructions to set up a DSL connection on the root, but nothing seems to be happening. I was a little surprised that it didn't ask for details of the modem (a Voyager 105). Should it have done? Where else might the problem lie? Can anyone please help?!
Have you had the modem online before, or is this the first time the modem is being used? Most DSL modems have to be setup in the modem itself to make a connection to your ISP, you will need to put the username and password supplied to you by your ISP.
You will also need to either configure it with either a static or DHCP assigned IP address. If you have that information available, you can usually access your DSL modem via your web browser, most default to either http://192.168.0.1 or http://192.168.1. And will have as the default login
username: admin
password: admin
If your modem has been working before, you just might need to enable the DHCP server in the modem to give your machine an IP address to connect to modem. All though most modems default with DHCP server enable.
In the end I've gone out and bought an ethernet router to replace the USB modem, since so many other people have reported problems with them. But I can't get it to work either! All the manuals tell me different things I ought or ought not to set up for it, while some other postings on this forum have said you don't really need to set anything up at all.
Now I'm completely confused. Following what seemed to be authoritative advice, I changed some of the net card settings to what appeared to be correct. Maybe I should have left well alone?
On the Suse/Novell forum on this site I have requested advice on configuring DHCP, but I'm no longer sure that's what I need. But I don't know where else to begin.
Anyone got any advice how I can begin to unscramble the situation?!
First, look in the router's manual to determine if its "inside" network (your side) is set to 192.168.0.x or 192.168.1.x. Assuming it is 192.168.0.x, issue the following commands on your SuSE box:
ifconfig eth0 192.168.0.10 netmask 255.255.255.0
route add default gw 192.168.0.1
That's all you need to do for the SuSE box's network connection.
Now you can bring up a web browser, enter http://192.168.0.1 for the address, and configure your router so that it will set up your ADSL connection through the modem. You will probably want to configure a PPPoE connection, using the username and password set up by your ISP. Instructions for this should be in the router's manual.
I've entered the two lines of commands you gave. There was no visible response to either of them; the shell just moved on to the next # prompt. Is that as it should be?
I then entered http://192.168.0.1 on the Konqueror browser and it said:
An error occurred while loading http://192.168.0.1:
Could not connect to host 192.168.0.1.
Yes, that is as it should be. To check to see if the commands "took", you can type:
ifconfig
route
and that will display your network configuration and routing table, respectively.
"Any suggestions what I should do next?"
What does your router manual say about the "inside" network? Is it 192.168.0.x or 192.168.1.x? I have a Linksys, and it defaults to .1.x, but many others default to .0.x; which is yours?
The Netgear's default is 192.168.0.x. That's why I typed that into the browser.
I've found the network configuration and routing table, as you suggested. The latter shows "inet addr:127.0.0.1" and "Mask:255.0.0.0". Is either of them at all significant?
I happened upon your other thread, and it seems you have two network interfaces. I assume the Centrino is for a wireless connection, so we should be working with the other one (hooked up with a cable), yes? Anyway, the output of your ifconfig and route commands should look like this:
nld1:/etc # route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
default 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
nld1:/etc #
Note that your "wired" interface may actually be eth1 instead of eth0, so you may have to adjust your commands accordingly. How does this compare with what you have now?
RX packets: 0 tells me you're not hooked up to anything on the eth0 interface. Let's figure out what kind of hardware you have installed. Type
dmesg | grep eth
and post the results. We need to figure out which hardware your kernel is detecting for eth0.
Me again! I have done what you suggested, and dmesg | grep eth produced these results:
eth0: Broadcom 4400 10/100BaseT Ethernet 00:c0:9f:35:5b:bf
eth1: Using hotplug firmware load.
eth1: Radio is disabled by RF switch
eth1: Bound to 0000:02:04.0
b44: eth0: Link is down.
b44: eth0: Link is up at 100 Mbps, full duplex.
b44: eth0: Flow control is off for TX and off for RX.
eth0: no IPV6 routers present
SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.0.2 DST=192.168.0.1 LEN=52 TOS=0X08 PREC=0x00 TTL=64 ID=41820 DF PROTO=TCP SPT=1039 DPT=80 WINDOW=1930 RES=0x00 ACK FIN URGP=0 OPT (0101080AEB590002230A)
The final line with all the capitals came up nine times. It's identical each time, except that all but the first have "PSH" between "ACK" and "FIN", and the number AEB59000 (in the middle of the long string in brackets at the end) is different in every case.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
