My laptop receives an IP via DHCP, but can't ping router or outside IP's!
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.
My laptop receives an IP via DHCP, but can't ping router or outside IP's!
Hi all. New here, and new to Linux in general. Nice looking place though, looks like there is a ton of helpful folks around.
So a while back I made the move to Linux from Win, on my home comp, and I'm very happy. Linux is pretty damn cool. Gaim for instance, and many more examples of course. The whole open-source and GNU thing is very cool to my mind. Anyhow, Fedora Core 2 installed really slick, no problems. My machine sits behind a Linksys router, and has a fixed IP. No connection problems at all.
Now. I wanted to take a stab at getting my laptop cooking with Linux as well. IT's a Toshiba Satellite Pro 4600. Old laptop, not really enough room for the dual boot thing, although that is what I'm doing now. I'm just not really a dual boot sort of guy. If Linux is going to be my os, then it's going to be my os. All or nothing right?
So under Fedora Core 2 everything is pretty good, except for a few things. The winmodem of course. Almost got it going with Smartlink's AMR modules, but whatever. Thing is a little unstable. Don't really need the modem anyhow. Audio is not working, I'll tackle it later though. The big thing is my NIC is not really working right. Well I think it is, but my network settings must be wrong or something.
The thing is, the card (Intel 100/Pro VE) is recognized and the e100 module loaded, it receives an ip via DHCP, but i can't ping out anything. Not the router, not my other Linux box, not an external ip either(aka the internet!)
So I think the driver(module?) works, the hardware works, because I don't believe it would get an ip if it didn't. Tried it with a static ip, like my other Linux machine, and my winblows box which sits on the same network. No dice.
Got frustrated, tried SuSE 9.1. This distro hangs at boot, right around the 'starting pcmcia' message, but tried passing the no pcmcia commands, no acpi, etc.. at boot with no success. It will however boot in 'failsafe' mode, and surprise of surprises, the same card was detected, same module loaded, and bang, it works. In failsafe i guess maybe the video card is handled a little differently, perhaps with a generic driver, cause the max resolution was 780 or whatever. Not so good anyhow.
I figure FC2 is the way to go, as I will probably need the pcmcia at some point, if i ever want to get a modem running(on the road a lot w. work), and I'd like to get a wireless nic going one day as well.
I've tried installing the latest driver from Intel's site, no success, but again I think that card and driver are working cause of the successful DHCP request.
Thought maybe it was a firewall/iptables problem, although there was no such trouble with my home comp, so I disabled the firewall in config-network or whatever the FC2/Gnome GUI tool is called. Maybe it was the Preferences/Security menu. Dunno. Anyway, still no success.
Googled my brains out for weeks now, literally, and no deal. The closest I've gotten was to read that maybe it was "the old IPV6 fedora problem"(?). So I read on, disabled it with "alias net-pf-10 off" (without quotes) in modprobe.conf. Again, nadda.
Any ideas folks? I'm desperate over here. Without the internet connection I can't troubleshoot and learn how to fix my audio problems, etc... any the comp is basically a boat anchor without the internet, as we all know...hehehe.
Oh, I get the same problems trying to connect from hotels I stay at with work, where I also successfully get an assigned ip, etc... I can connect with winblows from the hotels no prob. Same deal there i suppose, a router, dhcp, and so on.
I will of course be very happy to post any logs or iptables -L outputs or whatever is required!
Anyhow, TIA for any help people. Jeez, thats a novel up there! My memoirs would be shorter...
I have the same problem and have tried many of the same things. I am not that knowledgeable about hardware and networking, but it does appear to be a problem with FC2. FC1 was on the laptop before I did a fresh install, and it worked fine with the same setup.
A possibly related issue: what is the mysterious 169.254.0.0 entry in the route listing? I noticed you have that as well.
Any help anyone can provide would be appreciated by me as well.
modprobe.conf essentially replaces modules.conf. Syntax is similar enough. I missed it the first time too (Mandrake 10 had both, or maybe I just made it. ;) Plus, this suse 9 has modprobe (uses modprobe.conf) and modprobe.old (uses modules.conf, conf.modules). YMMV.
the 184.108.40.206 in the route table may come from a failed DHCP client (Sets it to a private address until it can get a real address.).
There doesn't seem to be any errors from your ethernet driver (dmesg|grep eth0 or dmesg|grep e100). I don't know if it is a hardware issue.
Is 192.168.0.101 the same IP address you get under windows? Is 192.168.0.1 the router (default gateway)?
Make sure you don't have dhcpd installed (this is the DHCP server), dhclient or dhcpcd (DHCP client daemon) is OK.
Lets try to bring up the interface manually (# are comments):
# bring down the interface
# Make sure no dhcp agents are running (I thing fedora uses isc dhcp)
# Please post if you get anything here (execpt matching the grep itself)
ps -ef|grep dhc
# Check the interface, Only should have lo, no eth0
# Reload the module
modprobe -r e100
# Here you could add the module params at the end. The first time
# don't (cause we want to see what mii-tool comes up with "naturally")
# Not everybody has a 100mib switch.
# "activate" the device, no configuration.
ifconfig eth0 up
# see what ethernet settings we negotiated (post the results)
# Now run packet sniffing to see what is happening
# capture on eth0, the whole packet, write to /home/root/file1.tcp
# run in background. Remember to kill this off later.
tcpdump -i eth0 -s0 -w ~/file1.tcp &
# Now setup the interface
ifconfig eth0 192.168.0.101 netmask 255.255.255.0
# We won't worry about routing yet.
# see if we can talk to our gateway
# Ctrl-C to exit
# Did it work?
# Let's try dhcp "manually"
# I don't know what fedora uses, so this may fail
# check config
# test again
# Kill off tcpdump
# see which job it was
# The only thing you can't copy and paste
# Take a look at our packet capture
# This should be around 10-20 lines
tcpdump -vn -r ~/file1.tcp | less
# Post the results if either ping fails.
Not sure why I'm being so verbose today. But hopefully one of these commands will show us why it isn't working.