Home network: connecting to a Linksys router for DHCP IP address - no ping
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Originally posted by MS3FGX The problem is that his machine isn't getting an IP from the DHCP server in his router.
The fact that static IP also isn't working suggests that the NIC itself is having some sort of problem.
Now, you show that your NIC is being detected, but what is that ouput from? If you are using "lspci" it can show a device even if there is no module loaded for it.
Check the output of "lsmod" to see if a module has been loaded for your NIC.
I agree that the NIC seems to be trouble .... heres the output from lspci for eth0 (let me know if you want me to post the full log):
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
Originally posted by phats_O quote:The fact that static IP also isn't working suggests that the NIC itself is having some sort of problem.:end quote
Ron, what is the exact message you get when you try to ping the router?
MS3FGX could very well be right about a problem with the nic, but theres still a fundamental difference between getting an ip address from your router, and trying to go through a router to obtain an address from the isp. If you want to get the address from your isp, then you don't need a router, and if you need a router, you dont need to get your ip from your isp.
When I'm using DHCP and eth0 isn't brought up, then I get:
#ping 192.168.1.1
connect: Network is unreachable
When I go back to static IP and eth0 seems to come up ok, I get:
#ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.100 icmp_seq=0 Destination Host Unreachable
From 192.168.1.100 icmp_seq=3 Destination Host Unreachable
From 192.168.1.100 icmp_seq=4 Destination Host Unreachable
Originally posted by n0xvb After you set eth0 with static IP address, did you add routing for that interface as well? DHCP will automatically do this for you, but if you set a static address you'll need to add this as well.
Something like this after ifup eth0 (using your previous example):
Now you can attempt to ping or connect to IP addresses, if you want name resolution
you'll need to add the appropriate line(s) to your resolv.conf file:
Code:
nameserver 192.168.1.1
ok - I just rebooted with the static IP set to 192.168.1.100 (figured I'd keep it well away from the 20 ip's that can be distributed by the router's DHCP, just in case everything starts working all at once ;) ). So my commands were:
Googling for info, I found this info:
The VIA Rhine and Rhine-II chips, via-rhine.c. This chip is used on many OEM boards. The most common branded implementation is the D-Link DFE530-TX. (Note: the DFE530-TX+ uses a RTL8139B chip.) You will need a driver with version 1.07 or higher if you have a VT6102 Rhine-II chip with PCI device ID 3065.
Could you list the relavent part of the "lspci" output to double check that the driver and versions are correct?
Originally posted by phats_O Ron, are you 100% certain that your ethernet cable is good?
That one I'm pretty close to certain on --- when I boot into XP, the network works like a charm and the lights on the router seem to indicate that the connnection is ok for both OSs (i.e. they're on). Let me know if there's a more foolproof way to verify that, though.
ron
ps - I'll post the lspci output that jschiwal requested as soon as I can make it home - hopefully something'll jump out at us (well, more likely you guys than me) at that point... thanks again for the help guys
quote: when I boot into XP, the network works like a charm and the lights on the router seem to indicate that the connnection is ok for both OSs (i.e. they're on). Let me know if there's a more foolproof way to verify that, though.
:endquote
That'll do. If it works, it works.
Originally posted by jschiwal Googling for info, I found this info:
The VIA Rhine and Rhine-II chips, via-rhine.c. This chip is used on many OEM boards. The most common branded implementation is the D-Link DFE530-TX. (Note: the DFE530-TX+ uses a RTL8139B chip.) You will need a driver with version 1.07 or higher if you have a VT6102 Rhine-II chip with PCI device ID 3065.
Could you list the relavent part of the "lspci" output to double check that the driver and versions are correct?
Ok - here's the output from lspci -vvx for the Ethernet Controller. I can attach more of the log if that would be helpful:
When I do a 'dmesg | grep eth0', I get the following (the timeout error repeats ad nauseum):
divert: allocating divert_blk for eth0
eth0: VIA Rhine II at 0xea002000, 00:10:dc:d7:64:ef, IRQ 11.
eth0: MII PHY found at address 1, status 0x786d advertising 01e1 Link 41e1.
eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
eth0: no IPv6 routers present
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
NETDEV WATCHDOG: eth0: transmit timed out
not cool. Also, I don't see any driver version information in the above logs ... have I forgotten to include some output or is there somewhere else I should be looking?
ron
Originally posted by jschiwal Googling for info, I found this info:
The VIA Rhine and Rhine-II chips, via-rhine.c. This chip is used on many OEM boards. The most common branded implementation is the D-Link DFE530-TX. (Note: the DFE530-TX+ uses a RTL8139B chip.) You will need a driver with version 1.07 or higher if you have a VT6102 Rhine-II chip with PCI device ID 3065.
Could you list the relavent part of the "lspci" output to double check that the driver and versions are correct?
Ok - just found the driver info in the dmesg ... looks like I'm running with:
via-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald Becker
He's produced a v1.16 already - any thoughts that it would be worth upgrading to the newest driver?
ron
Originally posted by davcefai I've just solved a very similar problem. Try adding the following to your append line in lilo.conf:
acpi=off noapic
Then run /sbin/lilo and reboot.
ok davcefai ...... what the ??? *everything is working perfectly*. I use grub instead of lilo, so the solution goes something like this.
Modify the /etc/grub.conf file by appending 'acpi=off noapic" to the kernel configuration line, i.e.
BEFORE: kernel /vmlinuz-2.6.9-1.667 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
AFTER: kernel /vmlinuz-2.6.9-1.667 ro root=/dev/VolGroup00/LogVol00 rhgb quiet acpi=off noapic
There's a note in /etc/grub.conf that you don't need to rerun grub after making mods, but I did anyways and that seemed to work fine after the reboot.
Suddenly, there's no more ACPI junk in the system boot logs and *wow* if eth0 isn't brought up like a charm (DHCP, the whole 9 yards)... amazing. If you have a few minutes davcefai, could you explain briefly how you arrived at this configuration - I'll read up on the Advanced Configuration and Power Interface for my own edification, but I'm dying to know what the smoking gun was in your case.
To all you guys who helped me with this - thank you very much --- you're all-stars - I hope I can return the favour some day... in the meantime, I think we all deserve some beer
ron
If you have a few minutes davcefai, could you explain briefly how you arrived at this configuration - I'll read up on the Advanced Configuration and Power Interface for my own edification, but I'm dying to know what the smoking gun was in your case.
How I got there:
Mobo worked OK under Win98 but would not work under Shorewall, Mandrake Security, Mandrake 10.1 or Knoppix.
This is a Socket 370 so we're not talking bleeding edge technology which Linux hasn't caught up with.
Therefore problem was mobo. This is supported by the fact that even disabling the onboard NIC and using plug in cards showed indistinguishable symptoms.
All the suggestions I received did not work.
I googled around and found references to APIC causing problems with some mobos. Apparently the boards mislead Linux into thinking that APIC will work. As this is for SMP systems things go blooey with Interrupt handling doing the wrong things. Note that the REAL problem was APIC, not ACPI.
So I tried removing it!
Took me over a week to get here but I dug my heels in.
Thank you very much! Your solution worked for me as well.
I recently purchased an SY-KT600 Dragon Plus v2.0 motherboard with onboard NIC (uses Rhine-II driver) and was trying to get networking to work with Mandrake 10.1. Same behavior => could not get networking working either with the onboard NIC, or with PCI NICs that work in other systems running Mandrake 10.1. Completely baffled.
This was a dual boot system and no problems with WinXP networking. Knoppix and Suse9.2 bootable CDs also had no problems.
After making the changes to lilo.conf, everything works like a charm. Nice bit of sleuthing to come up with that solution.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
