Linux networking question

Clockwork

I'm a linux newbie, so bear with me if I'm missing any details.

I'm trying to network my linux box into my LAN. I've connected it via ethernet to a Linksys WRT54G router.

I am able to:

Obtain an IP via DHCP
Ping the router
Ping other computers on the network
Ping websites
Get the router to recognize the computer

I am unable to:

Bring up web sites in any sort of web browser
Connect to any of my other computers (macintoshes all)
Ping my ISP

The router claims the computer runs at the IP 192.168.1.101, but the linux box says it's running at 192.168.1.104

My ifconfig command returns the following:

eth1
Link encap:Ethernet  HWaddr 00:11:95:1D:87:99
inet addr:192.168.1.104  Bcast:192.168.1.255  Mask:255.255.255.0
inet6 addr:fe80::211::95ff:feid:8799/64  Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:970  errors:743  dropped:0  overruns:0  frame:0
TX packets:1471  errors:0  dropped:0  overruns:0  carrier:0  
collisions:0  Txqueuelen:1000
RX bytes:105604  (103.1 KiB) TX bytes:143912  (140.5 KiB)
Interrupt:11  Base address:0x8c00

I'm running Fedora Core 5 with a D-Link RTL8139 PCI Ethernet card.

Any help would be appreciated greatly.

Thrax

I have no answers for you, because I'm a Linux noob, but your avatar is profoundly amusing.

primesuspect

so wait - you can ping websites in a terminal, such as:

ping google.com

and you'll get name resolution? (as in - it will know that google.com is 64.233.x.x whatever)? but when you go to use a browser, the page times out?

We need to narrow it down to see if it's a DNS problem or what..

drasnor

See if the file /etc/resolv.conf exists and has some valid DNS servers in it. If it doesn't, there may be a problem with your DHCP client configuration and using the DHCP server-specified DNS server addresses.

-drasnor

Clockwork

New situation (Sorry to change up to fast). My brother was over with his son (my nephew), who thinks he's the almighty god of computers. Stupidly, I left the Linux PC running on root as I was trying to jimmy the network into working. Being the kid he is, he opened up a terminal, and started screwing around... Bad stuff happened, and I ended up having to reinstall (Linux wouldn't boot).

SO... I redid the networking, and thankfully only one thing changed... I can't get the router to recognize the computer.

The contents of the /etc/resolv.conf are:

; generated by /sbin/dhclient-script
search wi.rr.com
nameserver 24.94.163.100
nameserver 24.92.163.101

I think the DNS servers are valid, however (.100 returns nothing when pinged, .101 returns all packets when pinged). I'm getting this sinking suspicion that it's my network card that's bad... If that does end up being the case, how would I go about setting up a Kingston KNE111TX with the tulip driver on Fedora Core 5?

Thanks for the help so far, despite what it looks like, the ideas have helped a lot.

--Clockwork

jhenry

Well, put .101 first since it responds, and remove the other one. Find another DNS server to place in resolv.conf

If a server responds, then your network card is fine. It's your config that is screwed up.

209.218.44.6 and 209.218.76.2 are my DNS servers. They're pretty quick.

Thrax

I might be able to help in this case:

I use 4.2.2.3 and 4.2.2.4 for my DNS servers -- they're the top level US DNS servers, and they're very quick. Never had a problem with 'em.

Park_7677

jhenry wrote:

209.218.44.6 and 209.218.76.2 are my DNS servers. They're pretty quick.

Just a note.. Most ISPs will only serve DNS requests of its customers. It's unlikely that using other DNS servers other than the ones provided by your ISP will work. If you're having trouble with one or both of yours, contact your ISP for support.

EDIT:// The IPs Thrax posted will work, they're public servers. You could use them or contact your ISP.

BTW, what do you mean exactly when you say "I can't get the router to recognize the computer."? Routers aren't aware of devices connected to them (with exceptions, but a SOHO router isn't one). You probably mean the DHCP server doesn't have it listed, which means it's not getting a proper request to send out IP information.

Clockwork

Ah, yes, I meant that I cannot get it to show up on the table of clients provided by the DHCP server.

I'll try those DNS servers and see if I get a response...

drasnor

Clockwork wrote:

The contents of the /etc/resolv.conf are:

; generated by /sbin/dhclient-script

...how would I go about setting up a Kingston KNE111TX with the tulip driver on Fedora Core 5?

As it says, your resolv.conf is generated anytime your network interface is started by dhclient so any changes you make won't stick. If you want to edit it manually you'll need to tell dhclient not to generate a resolv.conf file. I use Gentoo so I would just man dhclient.conf and figure out what options need to be changed and edit /etc/conf.d/dhclient.conf. However, I'm pretty sure Fedora has a GUI tool that can do this but you'll need to explore for yourself. However, if you've got one valid DNS server in your list and you can perform DNS lookups then that isn't your problem. I haven't ever really seen this sort of behavior before.

I had a KNE111TX for awhile, if my memory serves me it's supported under the tulip driver (just like most other cheap 10/100 cards from D-Link, Linksys, and Netgear). If Fedora doesn't automagically load the correct module, just modprobe tulip after you boot up.

-drasnor