I am a complete newbie. I cannot connect to the Internet under Linux using a 4-port adsl router (D-Link 504T, its internal modem handles the connection and passowrd, etc.).

It works fine under windows and has been already configured through firefox/windows calling the router IP number.

All the distro's I've tried see the eth0 port. If I set it to auto DHCP, nothing happens. When I set it to fixed IP, they all require some specification of IP address, Subnet and gateway.

I have tried some numbers that were specified in the router documentation (it says its IP address is 192.168.1.1, it also says the subnet is 255.255.255.0). There is no mention of "gateway". Nothing seems to work.

Am I missing something? Is there something else that needs to be specified? Its the same problem on FC1, Ubuntu 5.04 and Mandriva LE.

Any suggestions are greatly appreciated - cheers, Buzzgrowl

for the static configuration (non dhcp):

The gateway is the IP address of the modem (e.g. 192.168.1.1)
The subnet is 255.255.255.0
Your IP address should be something other than .1 in the 192.168.1.0/24 range
The DNS will be your modem IP address too.

buzzgrowl,
Welcome to LQ. Glad you have managed to make a start!
If your modem is already set up, it should be easy to get it working with linux.
Easiest is to use DHCP:
Plug in the modem's ethernet cable.

Open a terminal.
Become root:
su -
Give your password.
Give the following commands:
ifdown eth0
Will bring the interface down, in case anything else was using it.
dhclient eth0
Should set up your connection if your modem provides a DHCP server (most seem to).

If this works, put the dhclient eth0 command at the end of the file /etc/rc.d/rc.local, and you will be connected at every boot time.
If this does not work, post the output of ifconfig eth0 for us to take a look at.

Static IP addressing is not that much more complicated, but DHCP is really easy.

HTH

Edit: Path to rc.local

Dear all,
Thanks *very*! much for the advice, will try it tonight + get back tomorrow on if/how it worked.
big cheers - Buzzgrowl

Check the DNS Server numbers in the network configuration. Are they specified correctly? (Notice: I am extremely allergic to this, because they have caused my woe and frustration in the past, so it's the FIRST thing I always check when the internet isn't working). If you don't know what they should be, go back to windows and check or contact your ISP. Hope this helps..

-A

Hi Ahmed,
My ISP says that if the DNS does not resolve automatically I should try these:

ns1.sunrise.ch : 193.192.227.3
ns2.sunrise.ch : 194.158.230.53
ns3.sunrise.ch : 195.141.56.5
ns4.sunrise.ch : 194.230.1.5

I will do this tomorrow and see. Is there some reason why the router resolves ok with windows on top, but not with linux? Is this an issue at/with the ISP, or in my box?

cheers -Buzzgrowl

If you don't use DHCP, Linux won't be able to figure out your name servers automatically, you can just add them to /etc/resolv.conf by adding the following lines to the file

It works now.
Here is a rundown -

FC1 didn't work, it kept asking to delete and add NIC on reboot after changes were made and then failed to connect all the same. It could not see the router on its IP address from a browser.

Mandriva LE didn't work - It took ages to accept changes in NIC setting as well as to activate them, and then still did not see the router.

Ubuntu 5.10 for AMD64 worked (!!!) - The router was visible through the browser immediately after installation. It accepted the ISP's DNS servers when set up to a fixed IP (I chose 192.168.1.5) but only after the router IP was deleted from the DNS list. It finally started working when the actual browser was set to "auto detect proxy" (instead of the default "direct connection to internet").

However Ubuntu has an issue with screen resolutions and the fix is a manual edit of the /etc/X11/xorg.conf file. As a total newbie I managed this but was very careful.

Once again, thanks to everyone here on the forum!
Buzzgrowl

from a newbie to other,

Once I had this problem. It was the second day of using Suse.
The day before when I installed Suse everything was fine and Internet connection was functioning correctly.

On the second day before starting my Suse, I started my Windows and find out my router (4 port DSL router) is down ... (because of some unknown reasons this happends often with my provider - german T-online) ... so I reset the router and could get internet on my windows, however, now my Suse wouldnt start networking services and as a result no Internet to surf on.

Solution: I deleted my network interface card (in Suse you can do it in Yast control center) and then added the same card with the necessery parameters for my DSL connection as I had done by first time installation of Suse ... zim-zalla-bim ... everything OK again.

Conclusion: everytime you reset your dsl router, remove and set up your network interface card to avoid such problem. (I think the reason for this is that by a router reset, dns servers information need to be renewed)