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.
Hello,
I'm trying to get my ethernet to work with my router. Running FC2. I am able to get online at work using DHCP but at home, I cannot. At home, my linux computer is connected to a linksys router which is connected to a modem and to a computer running the PPPoE protocol (DSL connection) and set to assign DHCP.
I know the driver configuration is fine, since network connectivity is fine at work.
I can't seem to ping the router but I can ping myself. Using the GUI, I get an error message telling me to check the cable. All connections have been checked and the cable has been checked as well. The computer (when booted to windows) can connect via the network cable.
I have run ifconfig and dhcpd and present it below. I've been working on this for some time, and hopefully someone can point me in the right direction. It seems like this problem is fundamental since I can't even seem to ping the router. Thanks in advance.
[root@localhost zzoltani]# /sbin/ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:0F:1F:1F:52:F0
inet6 addr: fe80::20f:1fff:fe1f:52f0/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
[root@localhost zzoltani]# ping 192.168.1.1
connect: Network is unreachable
[root@localhost zzoltani]# /sbin/dhclient
Internet Software Consortium DHCP Client V3.0.1rc12
Copyright 1995-2002 Internet Software Consortium.
All rights reserved.
sit0: unknown hardware address type 776
/sbin/dhclient-script: configuration for sit0 not found.
sit0: unknown hardware address type 776
Listening on LPF/eth0/00:0f:1f:1f:52:f0
Sending on LPF/eth0/00:0f:1f:1f:52:f0
Listening on LPF/sit0/
Sending on LPF/sit0/
Listening on LPF/lo/
Sending on LPF/lo/
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on sit0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on sit0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on sit0 to 25²•.255.255.255 port 67 interval 15
DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on sit0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on sit0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on sit0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
[root@localhost zzoltani]# /sbin/route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
169.254.0.0 * 255.255.0.0 U 0 0 0 lo
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
Are you sure there is a working dhcp server?
Log into the router and view the leases to see if the eth0 MAC address has an ip allocated..
Turn iptables off, do /etc/init.d/iptables stop and then do ifdown eth0 and ifup eth0..
and as a last resort..
do ifdown eth0 and ifconfig eth0 192.168.1.2 and try pinging 192.168.1.1
Peter,
Thanks for your thoughts. Unfortunately, I'm not able to log onto the router in the way that you describe. The router is a linksys which has a web based interface that is used to perform all setup and diagnostic tests.
I tried to do: ifdown eth0 and ifconfig eth0 192.168.1.2 and try pinging 192.168.1.1.
I get the message "Destination Host Unreachable."
I know that DHCP is working, because it is enabled on the router and my computer runing on Windows can successfully get an IP. Perhaps there is something else I could try?
The computer I'm trying to connect is just a computer on the LAN and so it shouldn't be connecting via PPPoE which is what I believe adsl-setup would do. The router is indeed connected through the PPPoE protocol. Is this correct? Any ideas why the same machine under windows can pick up an IP via DHCP but linux can't?
u can try basic stuff, when u boot up with windows ipconfig and check the router ip addy. U could also try linksys website to see if there is anything on there about linux drivers. Like I say basic but u never know. If ur cables are working ok then it can only be ur configuration set up. have u got any output in /var/log/ that may give u more info.....sometimes it can be just something really simple that u may have missed
ps check in ur bios pnp it maybe that windoze recognises ur set up but it may not be enabled in bios...just a thought
I think I'm fighting the same problem--except I;m working with a motorola WR850G wireless/wired/broadband router. If I read your posting correctly you have access to the GUI stuff coming out of your router but it's not connecting to the net. I'm not sure why yet--actually that was what I was researching when I came across your question--but I got net access after I dumped using DHCP to get the IP address and assigned a static IP address. That might be iffy if you're running a mixed network with computers that are getting their addresses through DHCP but if you know the base address your router will start from then add all the connection's (computers) that may be on the LAN then you should be able to pick a status IP address above the highest that the router will choose. I have up to 5 computers on the LAN with a base assignment of 192.168.0.2 so I picked 192.168.0.20 for my static address in the Linux Box.
I'm still hoping to get the DHCP angle up and running and will keep you informed if you'd like. Also if you come up with anything helpful I'd appriciate hearing about it.
Turns out rebooting the computer, turning the router off and on again, and swithching the port the cable was connected to resolved the issue. I had tried this previously but it worked this time around. Thanks for the other notes and ideas.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.