Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a dual-boot box (Win98 & ubuntu.linux). It's connected by ethernet to a D-Link DI-624 router (Rev. C - Firmware 2.50), behind a Motorola cable modem. All hardware and OS's set up for DHCP.
Booting into Win98 gets me connected, but booting into linux fails to give me an ip address. I assumed the problem was the linux configuration, BUT I find nothing wrong there.
HERE'S THE ODD PART ... if I connect the PC directly to the modem and boot up linux, I get connected. I also have a D-Link bridge that is wirelessly connected to the router. When I plug the PC into the bridge ... bingo ... I am connected.
I suspect the problem is with the router. I've tried all 4 ethernet ports, and have tried turning off mac filters .. and even tried static address instead of dhcp. I called D-Link support, but they claim that they don't offer customer support for linux.
Anyone have any suggestions ? Or, anyone successfully using the same router w/ linux ?
I am new here, so please 'scuse the last post - attempt to quote
I have a di-604, so should work almost the same
According to the cable tech who installed the modem, windows98 makes a lot of assumptions which linux must be told about .
using windows log in to the router as admin, copy down the router's outside ip address, dns server, gateway etc.
try to ping an outside ip, like yahoo.com
if that's ok then log off the router
run winipcfg, record your local ip, dns server, gateway, etc.
in a dos prompt run tracert to a known ip and record the hops.
It's so much easier if you can have a windows machine up at the same time as trying to get linux to work, but ....
In linux set up the network with static ip addresses, like 192.168.0.11 for windows and .22 for linux. Let the router do dhcp if it wants to - it won't hurt.
configure network with gateway of 192.168.0.1, dns as reported by the router, use a dummy domain & host name l(I use drake.stuart, music.stuart etc for different machines)
restart the network, try to ping the router at 192.168.0.1
If that works, try to ping a known ip address such as the outside ip address reported by the router.
if that works then try to ping a known name.
Stuart: Thanks for taking the time to assist me. I followed your advice, but after restarting my network in linux, all ping's ( internal ip address. ISP's address, and google.com) came back with 100% packet loss.
Here are the details:
First, in Win98, I logged onto the router, and it reported the following:
WAN (Outside addresses)
subnet mask 255.255.248.0
subnet mask 255.255.255.0
I pinged the LAN and it was successful. I exited the router, and did "winipcfg" in Win98, and received the following response:
DNS Servers 18.104.22.168
subnet mask 255.255.255.0
Default gateway 192.168.0.1
DHCP Server 192.168.0.1
Windows 98 connects thru the router. I rebooted into linux (it failed to connect, of course), and I set up linux networking as follows:
Static address 192.168.0.22
subnet mask 255.255.255.0
DNS same 7 servers as reported by winipcfg
domain name OurPC
I restarted the network, and all subsequent pings have failed. I am still unable to connect thru the router.
As you think thru the possible root cause, just a reminder that I have successfully connected before under linux ... by connecting directly from PC to the cable modem and also by pugging into a wireless bridge that was downstream from the router. The problem seems to occur when I connect into the router's LAN port.
I'm having the same problem with the same D-Link router. No problems in WinXP (LAN connections, pings, web access). In Linux my connection to the router and other computers on my home LAN are just fine. Connection to anything on the other side of the router fails--only in Linux. I've exhausted the various combinations of attributes that I can think of.
My ethernet adapter: Realtek RTL 8139/810x Family.
I am still a novice with linux, but everything so far looks ok. This is the time I start looking outside the box - like bad cables. Some routers (like my d-link) automatically switch to accommodate straight or crossover cables.
Another thought is network address resolution. The post from dmarsh got me thinking. I also have realtec network cards, I thought the old 3-com unit might be a problem.
But his reference to finding the router and nothing outside indicates a dns problem (or undefined dns) on his machine.
You might want to check the services you have on - if you have a dns server running in linux (but not in windows) that may be enough to confuse things.
I have never even tried to use a local dns server, but that started when I had a peer to peer network and then later added a samba server. I could never get it to find the windows machines consistently, so I gave up and made it just a server, put the machine down on the floor and 'forgot' about it
Try turning off or removing the reference to dhcp server, that may be conflicting with the static ip.
I would suggest also checking what other things, services, etc are significantly different between your win and linux setup.