Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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 post this from my Linux RedHat 8.0 box...
THis thread is not about a hardware incompatibility concern. My ethernet card worked well with MS Windows and I was able to connect the internet through my LAN from my laptop. The mess came when I decided to experiment with RedHat Linux 8.0 on that laptop. But now it's OK.
Indeed I had TWO ethernet cards I think, "eth0" and "eth1".
I decided to delete "eth0" and only kept "eth1" wich I configured like under MS. I give you here the details of what I did to access the internet through my LAN using an ethernet card.
THE FOLLOWING ARE DETAILS UNDER TABS OF THE NETWORK TOOL TO CONFIGURE (Start\System Tools\Peripheric Control\ Then click on configure if it is the right NIC (read all this post) that is selected. Highlight the NIC to configure ("eth1" for this case) and then "modify" as follows :
Set to run automatically at boot
Static : IP, MASK (255.255.255.0), GATEWAY (on my case the gateway was the comp directly connected to the internet and it has its own IP I chose myself 192.168.x.x)
Was also configured using the same details
"Sticked" with the right MAC address (detect) so activate here
THAT'S FOR THE NIC ITSELF.
FOR OTHERS DETAILS :
HERE, NAME OF THE BOX TO CONNECT TO THE LAN
localhost. localdomain localhost
HERE, NAME OF THE BOX TO CONNECT TO THE LAN
PUT THEN THE DNS (1,2,3) YOUR ISP USES (they are the same you used probably under your MS box directly connected to the NET
For troubleshooting, you may verify firewall is not running (someone told me that RedHat 8.0 had a bug and indicates the highest security even if firewall is disabled). When problem solved the firewall must be in use for your security!
Verify the "eth1" is really ACTIVATED. If impossible to activate it, then retry from the beginning, or simply add it manually.
That's all folks. Oh and what I would suggest (some people suggested me that here in this thread : thanks!) is to ping from the terminal (Start\System Tools\Terminal) and as a root -type su- 127.0.0.1 AND the static IP you gave your NIC (in this case there is no DHCP) AND of course the gateway in order to determine what exactly is going on. The "ifconfig" command (from the terminal is also useful of course for outputs you can post then).
You never really said what your problem is, just that it was similar, however, the original post said "unable to resolve www.google.com" and you seem to be able to do that. I did notice you have eth0 setup for 2 separate networks:
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
You are getting an IP. Ping works, nslookup works, dig works. But you say you can't get on the internet?
I looked around the browser settings, didn't see that option, any idea where it is? A guy on a different forum recommended I try Lynx to see if its a problem with the browser, thing is though update programs and the like can't connect either so getting Lynx on there seems like it might be a waste of time. Am I wrong?
192.168.1.2 must be the server that I am directly connected up to. It only takes me 1 hop to get to it. I should maybe explain my setup. I'm on a network at college, I have an ethernet drop in my room, then that goes out to the servers so I don't have physical access to the servers or routers.
I don't really think it would make a difference, but on this network there are cetain things that are blocked. UDP and FTP specifically. I really don't think this would have anything to do with it since HTTP works fine on XP through the same drop on the same machine with the same settings, but who knows. I'm a Linux newbie, quite the newbie to networking too, thats why I'm here, haha.
I agree this probably this isn't the problem if other programs don't work but it doesn't hurt to check:
In mozilla check:
Edit -> Preferences -> Advanced -> Proxies
And the check box "Direct connection to Internet" should be checked.
For Konqueror it is:
Settings -> Configure Konqueror -> Proxy
And make sure the box "Use Proxy" in UN-checked.
Try this and post any interesting results:
nmap -sP 192.168.1.0/24
nmap -sP 169.254.0.0/24
You could also do a port scan of the gateway device.
I had the same problem on my box, RH9 (upgraded from kernel 2.4.whatever to 2.6.3) where i could resolve ip addresses from domain names but I couldn't connect to the web sites. I had enabled ethernet congestion notification in the networking part of the kernel and built and installed a new kernel with that. My router, a cheep quest rental, any many others do not support that part of the protocol so I couldn't get any where on the web. I disabled it by using the runtime config for the new kernel to turn it off and the internet worked perfectly after that. To permanetly set that option to off I added a line to the /etc/sysctl.conf file. This fix probably only will work if you compiled your own kernel and turned on this option. Runtime config is only availible in 2.6 (maybe 2.5, not familiar with that dev kernel). If you didn't build your own kernel then you probably dont have this situation and I am sorry I couldnt be of more help.
quick fix for my problem: # /sbin/sysctl -w net.ipv4.tcp_ecn=0
permenent fix: add net.ipv4.tcp_ecn = 0 to the /etc/sysctl.conf file or recompile the kernel without this option enabled not needed if this is the only thing wrong with the build.
Load up one of the kernel config editors with your current config file used to build your current kernel to check if you did infact enable this option.