Can ping router, but not internet

fatallyhuman · 2010-08-26 18:36:23

I've searched the forums and I can't seem to figure this out. I can ping the router (192.168.1.0), but I can't get out to the internet. Pinging a domain name results in "unknown host" and pinging an outside IP address results in "Network is unreachable." I've tried both static IP and DHCP (even though I'm pretty sure that DHCP correct). The namservers are being created by Network Manager, but I can't ping the namservers it's using due to the "Network is unreachable" problem. When I enter dhcpcd eth0, I get the following:

dhcpcd[3742]: version 5.2.5 starting
dhcpcd[3742]: eth0: broadcasting for a lease
dhcpcd[3742]: eth0: offered 192.168.1.72 from 192.168.1.0
dhcpcd[3742]: eth0: acknowledged 192.168.1.72 from 192.168.1.0
dhcpcd[3742]: eth0: checking for 192.168.1.72
dhcpcd[3742]: eth0: leased 192.168.1.72 for 600 seconds
dhcpcd[3742]: eth0: add_route: Invalid argument
dhcpcd[3742]: forked to background, child pid 3763

Any ideas? Let me know if I need to provide any further info. Thanks!

karol · 2010-08-26 18:49:15

dhcpcd[3742]: eth0: leased 192.168.1.72 for 600 seconds

A bit short ...

dhcpcd[3742]: eth0: add_route: Invalid argument

Do you have any settings with add_route?

lagagnon · 2010-08-26 18:50:33

Show us the output to the following commands run as root in a terminal:

ifconfig
cat /etc/resolv.conf
cat /etc/rc.conf
hostname

karol · 2010-08-26 18:51:44

https://bbs.archlinux.org/viewtopic.php … 59#p703659

fatallyhuman · 2010-08-26 20:29:35

@karol How can I change the IP lease length? Also, I couldn't find any add_route settings in the /etc/rc.conf file. Is there somewhere else I should check?

@lagagnon Here are the outputs...

ifconfig

eth0      Link encap:Ethernet  HWaddr 00:22:15:59:61:F4  
          inet addr:192.168.1.72  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::222:15ff:fe59:61f4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6878 errors:0 dropped:0 overruns:0 frame:0
          TX packets:130 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:599314 (585.2 Kb)  TX bytes:22581 (22.0 Kb)
          Interrupt:27 Base address:0x4000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:42 errors:0 dropped:0 overruns:0 frame:0
          TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:2100 (2.0 Kb)  TX bytes:2100 (2.0 Kb)

cat /etc/resolv.conf

# Generated by dhcpcd from eth0
# /etc/resolv.conf.head can replace this line
nameserver 69.145.248.50
nameserver 69.145.232.4
# /etc/resolv.conf.tail can replace this line

cat /etc/rc.conf

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
#   in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.UTF-8"
HARDWARECLOCK="localtime"
TIMEZONE="America/Los_Angeles"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(vboxdrv !snd_pcsp !pcspkr)

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="c3arch"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
# 
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#

#Static IP example
eth0="eth0 192.168.0.99 netmask 255.255.255.0 broadcast 192.168.0.255"
#eth0="dhcp"
INTERFACES=(eth0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
 
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng hal networkmanager netfs crond alsa kdm httpd mysqld)

hostname: c3arch

Last edited by fatallyhuman (2010-08-26 20:51:59)

karol · 2010-08-26 20:31:06

*Please* use [code ] tags.

I meant that such short lease times are not normal, but *you* can't change them - dhcp can.
I have no idea what add_route does, that's why I asked you.

Edit: Just a thought, does it has sth to do w/ VirtualBox?

Last edited by karol (2010-08-26 20:47:59)

hokasch · 2010-08-26 20:53:24

Check the routes with "route". You can add the gateway manually with

route add default gw 192.168.1.0

Next update your system, dhcpcd is currently on 5.2.7, maybe you are lucky and its fixed

edit: ip typo

Last edited by hokasch (2010-08-26 20:54:11)

madeye · 2010-08-26 20:57:18

"Unknown host" is an indication that you don't get an answer from the DNS.

"Unreachable network" indicates that the route to the external network is disabled or wrong.

You can check you default gateway by issuing

route

at the prompt

Mine reads

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.111.0   *               255.255.255.0   U     202    0        0 eth0
default         192.168.111.254  0.0.0.0         UG    202    0        0 eth0

If you use a static IP address, then the line

ROUTES=(!gateway)

should be

ROUTES=(gateway)

EDIT: Seems someone beat me to it

Last edited by madeye (2010-08-26 20:59:54)

fatallyhuman · 2010-08-26 21:05:46

Sorry about that. I'm new to the forums. I just went back and added code tags now. I have VirtualBox installed in Arch, but Arch is installed directly on the machine, so I doubt that add_route has to do with it.

fukawi2 · 2010-08-26 23:14:10

fatallyhuman wrote:

dhcpcd[3742]: version 5.2.5 starting
dhcpcd[3742]: eth0: broadcasting for a lease
dhcpcd[3742]: eth0: offered 192.168.1.72 from 192.168.1.0
dhcpcd[3742]: eth0: acknowledged 192.168.1.72 from 192.168.1.0
dhcpcd[3742]: eth0: checking for 192.168.1.72
dhcpcd[3742]: eth0: leased 192.168.1.72 for 600 seconds
dhcpcd[3742]: eth0: add_route: Invalid argument
dhcpcd[3742]: forked to background, child pid 3763
Any ideas? Let me know if I need to provide any further info. Thanks!

What is giving you DHCP leases? 192.168.1.0 is NOT a valid address in the 192.168.1.0/24 network which is what you're using as indicated by the output of your ifconfig. It looks like you have invalid configuration on the DHCP server.

A lease time of 600 seconds is short, but perfectly fine so I wouldn't worry about "fixing" that until you work out the rest.

Sjoden · 2010-08-28 00:40:55

fukawi2 wrote:

fatallyhuman wrote:
dhcpcd[3742]: version 5.2.5 starting
dhcpcd[3742]: eth0: broadcasting for a lease
dhcpcd[3742]: eth0: offered 192.168.1.72 from 192.168.1.0
dhcpcd[3742]: eth0: acknowledged 192.168.1.72 from 192.168.1.0
dhcpcd[3742]: eth0: checking for 192.168.1.72
dhcpcd[3742]: eth0: leased 192.168.1.72 for 600 seconds
dhcpcd[3742]: eth0: add_route: Invalid argument <-- this
dhcpcd[3742]: forked to background, child pid 3763
Any ideas? Let me know if I need to provide any further info. Thanks!
What is giving you DHCP leases? 192.168.1.0 is NOT a valid address in the 192.168.1.0/24 network which is what you're using as indicated by the output of your ifconfig. It looks like you have invalid configuration on the DHCP server.
A lease time of 600 seconds is short, but perfectly fine so I wouldn't worry about "fixing" that until you work out the rest.

^ What fukawi2 said. ^

Also, that last bolded line is probably dhcpcd telling you that the route it recieved, and tried to add to its list of routes, is bad. You probably can just set the IP Address of your DHCP server(router) to 192.168.2.1, and try to get a new lease.

Last edited by Sjoden (2010-08-28 00:44:34)

Arch Linux

#1 2010-08-26 18:36:23

Can ping router, but not internet

#2 2010-08-26 18:49:15

Re: Can ping router, but not internet

#3 2010-08-26 18:50:33

Re: Can ping router, but not internet

#4 2010-08-26 18:51:44

Re: Can ping router, but not internet

#5 2010-08-26 20:29:35

Re: Can ping router, but not internet

#6 2010-08-26 20:31:06

Re: Can ping router, but not internet

#7 2010-08-26 20:53:24

Re: Can ping router, but not internet

#8 2010-08-26 20:57:18

Re: Can ping router, but not internet

#9 2010-08-26 21:05:46

Re: Can ping router, but not internet

#10 2010-08-26 23:14:10

Re: Can ping router, but not internet

#11 2010-08-28 00:40:55

Re: Can ping router, but not internet

Board footer