LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   Attaching my linux box to a router. (https://www.linuxquestions.org/questions/linux-networking-3/attaching-my-linux-box-to-a-router-198851/)

mrplatts 06-28-2004 06:59 PM

Attaching my linux box to a router.
 
I am definately a newbie, but am learning all the time. I installed a distro of linux that came free with some magazine on an old computer. I've been playing around with some perl programming & getting the machine to talk to some serial input devices... anyway.

I bought a cheap LAN card & put it in and was pleased that it was detected and seems to be functional.

Now I need some quick advice on how to get it talking to my router.

I'm running a DLINK 614+ router with DCHP enabled. Normally this is the router for my in-home wireless, but it has a hook up for a wired LAN too so I have plugged the network card into there. I set up the Network Configuration to use DCHP and get the error

"Determining IP information for eth0... failed; no link present. Check cable?"

If I give it a static IP i.e. 192.168.0.109 it gives no error, but also isn't able ot be pinged from the router and gets no signal.

Is there an wasy way to just hook up a single machine to the router? Searching the internet is not working, too much networking info.

Thanks,
Richard

dolvmin 06-28-2004 08:17 PM

Two statements:

First, what distribution are you running?
(e.g. Redhat (version), Mandrake (version), Debrian (version), Lindows (version), etc)

Second, the problem sounds like it's your IPTable.

Try doing the following:
Code:

ping 127.0.0.1
My understand is, the reason why you are not getting an error when setting your NIC with a static IP is because, your telling it to do nothing.

Example, running the NIC as a Dynamic requires the NIC to pull an IP address from a DHCP, which would require your NIC to bind an IP from the DHCP DNS server. When the NIC attempts a request, the IPTable disallows the function, returning an error signifying a possibility of which your nic is non-functional. When the NIC is set to a static, the NIC card does not perform any functions, but may not have the IP truly bound to the NIC either. If the IP is not bound to the NIC, this may mean you have a great length of problems. You can test if the IP address is bound by typing the following:
Code:

ping (your Static IP Address)
If your static IP address is bound, but you are unable to communicate outside of your computer, it is because your IPTable is limited to only allowing network traffic to work on the local loop back.

To resolve this issue, you will need to work with the IPTables. Depending on what distribution of Linux you have, this can be as easy as pushing a few buttons or as difficult as working with code.

MS3FGX 06-28-2004 09:07 PM

I would follow what the error message says, check your cable. It is most likely either damaged, or it is a crossover cable.

mrplatts 06-29-2004 08:24 AM

huh... don't I feel sheepish. As usual, the most simple explanation turned out to be correct. Since the cable was brand new I didn't even consider the fact that, as linux suggested, the cable might be faulty. I dug through an old box of computer supplies I had laying around and pulled an ethernet cable out. when I plugged it in it worked perfectly, first time.

Thanks for your responses. I'm sure I will be on here asking dumb questions again.

Thanks a bundle.

R


All times are GMT -5. The time now is 09:07 PM.