You are not logged in.

Pages: 1

#1 2012-01-22 06:54:56

gtpitch
Member
Registered: 2012-01-22
Posts: 6

DHCP issues on wired connection

Hi,

I hope someone can help me.  I'm having issues with my wired connection on a new Arch install.  I used Arch successfully with this setup a few months ago and stopped for a while to switch to another distro.  I'm wanting to install Arch again but hitting a snag. 

When I attempt to connect to the internet through a Linksys router I get this:

dhcpcd

version 5.2.12 starting
eth0: broadcasting for a lease
eth1: wating for carrier
eth0: offered 192.168.1.101 froom 192.168.1.1
timed out
forked to background, child pid 570


I have released DHCP and also deleted the dhcp leases several times and can't seem to get connected.  If I remove the route from the equation and connect directly to cable modem then the internet works just fine.  I've tried setting a static IP as well using the proper gateway and I get nowhere.  I've attempted to set up through netcfg a dhcp connection and I get failed lease attempt.

I'm sure I'm missing something stupid but I've googled and searched these forums and can't find anything.  On previous installs of Arch it seemed to just "work"

Offline

#2 2012-01-22 07:27:40

willbprog127
Member
Registered: 2011-11-09
Posts: 59

Re: DHCP issues on wired connection

You are listing two different network interfaces (eth0 and eth1).  Do you actually have two, or is it possible you've accidentally mistyped one of them, possibly in rc.conf?

Offline

#3 2012-01-22 07:38:31

gtpitch
Member
Registered: 2012-01-22
Posts: 6

Re: DHCP issues on wired connection

Both interfaces are really there, yes. Eth0 is the one that the wired connection is actually plugged into. Rc.conf reflects eth0.  I've also run dhcpcd eth0 and get the same results without the eth1 line. I've also tried switching all of these around and rebooting with the cable in eth1 to no help.

This same setup works fine in linuxmint by the way.

Offline

#4 2012-01-22 08:24:21

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,694

Re: DHCP issues on wired connection

Two things.  First, try using dhclient in lieu of dhcpcd.  Not that it is a solution to your problem, but it may be a work around.  At the least, it will give us another data point.

Also, can you get to the router logs? They might yield some interesting data.

You  typed that dhcpcd message by hand, didn't you?

eth0: offered 192.168.1.101 froom 192.168.1.1

See the typo?

Last edited by ewaller (2012-01-22 08:24:48)

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Offline

#5 2012-01-22 16:51:43

gtpitch
Member
Registered: 2012-01-22
Posts: 6

Re: DHCP issues on wired connection

ewaller wrote:

Two things.  First, try using dhclient in lieu of dhcpcd.  Not that it is a solution to your problem, but it may be a work around.  At the least, it will give us another data point.

Also, can you get to the router logs? They might yield some interesting data.

You  typed that dhcpcd message by hand, didn't you?

eth0: offered 192.168.1.101 froom 192.168.1.1

See the typo?

Ok I'll work on installing dhclient and configuring that to see if it works any better.  I did have to type that information by hand, sorry for the typo.   At the time when I was trying to set this up last night I didn't have a desktop (or even X) installed yet.  I had since connected straight to the cable modem and installed KDE.

Here is the outgoing router log - the incoming log was blank.

LAN IP	Destination URL/IP	Service/Port Number
192.168.1.100	91.189.94.4	123
192.168.1.100	74.125.115.103	www
192.168.1.100	74.125.115.99	www
192.168.1.100	74.125.91.125	5222
192.168.1.100	72.14.204.95	www
192.168.1.100	72.14.204.138	HTTPS
192.168.1.100	199.7.52.190	www
192.168.1.100	199.7.52.190	www
192.168.1.100	72.14.204.120	www
192.168.1.100	74.125.113.99	www
192.168.1.100	74.125.113.103	HTTPS
192.168.1.100	199.7.55.72	www
192.168.1.100	199.7.55.72	www
192.168.1.100	199.7.52.72	www
192.168.1.100	108.59.11.108	www
192.168.1.100	74.125.113.103	www
192.168.1.100	92.242.140.1	www
192.168.1.100	72.14.204.120	HTTPS
192.168.1.100	72.14.204.147	HTTPS
192.168.1.100	74.125.115.104	www
192.168.1.100	74.125.115.104	HTTPS
192.168.1.100	72.14.204.102	HTTPS
192.168.1.100	72.14.204.102	HTTPS
192.168.1.100	75.126.162.205	www
192.168.1.100	75.126.162.205	www
192.168.1.100	75.126.162.205	www
192.168.1.100	173.241.250.2	www
192.168.1.100	75.126.162.205	www
192.168.1.100	208.101.3.245	www
192.168.1.100	204.2.167.100	www
192.168.1.100	173.241.250.2	www
192.168.1.100	75.126.162.205	www
192.168.1.100	204.2.167.100	www
192.168.1.100	96.31.78.174	www
192.168.1.100	109.109.233.74	www
192.168.1.100	72.14.204.113	www
192.168.1.100	75.126.162.205	www
192.168.1.100	96.31.78.174	www
192.168.1.100	67.201.31.128	www
192.168.1.100	72.14.204.113	www
192.168.1.100	74.125.115.104	www
192.168.1.100	209.151.236.22	www
192.168.1.100	72.14.204.154	www
192.168.1.100	209.151.236.22	www
192.168.1.100	72.14.204.113	www
192.168.1.100	72.14.204.113	www

Offline

#6 2012-01-22 17:02:55

gtpitch
Member
Registered: 2012-01-22
Posts: 6

Re: DHCP issues on wired connection

This is what happens using netcfg with dhclient:

[brett@brettarch dhcpcd]$ sudo NETCFG_DEBUG="yes" netcfg mynetwork
DEBUG: Loading profile mynetwork
DEBUG: Configuring interface eth0
:: mynetwork up                                                          [BUSY] DEBUG: status reported to profile_up as: 
DEBUG: Loading profile mynetwork
DEBUG: Configuring interface eth0
DEBUG: ethernet_iproute_up ifup
DEBUG: ethernet_up dhclient -q -e TIMEOUT=10 -pf /run/dhclient-eth0.pid eth0
DEBUG: ethernet_iproute_up hostname brettarch
                                                                         [DONE]

But then I get this:

[brett@brettarch dhcpcd]$ ping -c 3 192.168.1.1
connect: Network is unreachable
[brett@brettarch dhcpcd]$ ping -c 3 www.google.com
ping: unknown host www.google.com

Here are some other outputs (not sure if useful)

[brett@brettarch dhcpcd]$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:24:1d:2d:2c:55 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::224:1dff:fe2d:2c55/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 00:1f:d0:81:68:b0 brd ff:ff:ff:ff:ff:ff
[brett@brettarch dhcpcd]$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500  metric 1
        inet6 fe80::224:1dff:fe2d:2c55  prefixlen 64  scopeid 0x20<link>
        ether 00:24:1d:2d:2c:55  txqueuelen 1000  (Ethernet)
        RX packets 558541  bytes 121643919 (116.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 98761  bytes 8369132 (7.9 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 46  base 0x2000  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 16436  metric 1
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 868  bytes 72456 (70.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 868  bytes 72456 (70.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[brett@brettarch dhcpcd]$ route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

And here is the same information plugged straight into my cable modem:

[brett@brettarch dhcpcd]$ sudo netcfg -a
:: mynetwork down                                                        [DONE] 
[brett@brettarch dhcpcd]$ sudo NETCFG_DEBUG="yes" netcfg mynetwork
DEBUG: Loading profile mynetwork
DEBUG: Configuring interface eth0
:: mynetwork up                                                          [BUSY] DEBUG: status reported to profile_up as: 
DEBUG: Loading profile mynetwork
DEBUG: Configuring interface eth0
DEBUG: ethernet_iproute_up ifup
DEBUG: ethernet_up dhclient -q -e TIMEOUT=10 -pf /run/dhclient-eth0.pid eth0
DEBUG: ethernet_iproute_up hostname brettarch
                                                                         [DONE]

And same outputs with internet working:

[brett@brettarch dhcpcd]$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:24:1d:2d:2c:55 brd ff:ff:ff:ff:ff:ff
    inet 69.81.133.8/26 brd 255.255.255.255 scope global eth0
    inet6 fe80::224:1dff:fe2d:2c55/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 00:1f:d0:81:68:b0 brd ff:ff:ff:ff:ff:ff
[brett@brettarch dhcpcd]$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500  metric 1
        inet 69.81.133.8  netmask 255.255.255.192  broadcast 255.255.255.255
        inet6 fe80::224:1dff:fe2d:2c55  prefixlen 64  scopeid 0x20<link>
        ether 00:24:1d:2d:2c:55  txqueuelen 1000  (Ethernet)
        RX packets 558912  bytes 121674332 (116.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 98830  bytes 8377858 (7.9 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 46  base 0x2000  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 16436  metric 1
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 1028  bytes 85912 (83.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1028  bytes 85912 (83.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[brett@brettarch dhcpcd]$ route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         user-12l3181.ca 0.0.0.0         UG    0      0        0 eth0
69.81.133.0     *               255.255.255.192 U     0      0        0 eth0

And finally here is the profile for 'mynetwork'

CONNECTION='ethernet'
DESCRIPTION='A basic dhcp ethernet connection using iproute'
INTERFACE='eth0'
IP='dhcp'
DHCLIENT=yes
## for DHCPv6
#IP6='dhcp'
## for IPv6 autoconfiguration
#IP6='stateless'

Hopefully this helps.

Last edited by gtpitch (2012-01-22 17:14:52)

Offline

#7 2012-01-22 17:48:12

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,694

Re: DHCP issues on wired connection

Odd.  Any chance you've a bad cable? 
You said it worked when you plugged straight into the cable modem.  Did you unplug the cable from the router and plug it into your system?  Or did you unplug the router from the modem and use the cable from your computer into the modem?

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Offline

#8 2012-01-22 17:53:54

gtpitch
Member
Registered: 2012-01-22
Posts: 6

Re: DHCP issues on wired connection

ewaller wrote:

Odd.  Any chance you've a bad cable? 
You said it worked when you plugged straight into the cable modem.  Did you unplug the cable from the router and plug it into your system?  Or did you unplug the router from the modem and use the cable from your computer into the modem?

Just to be sure I did switch the cables around and it didn't help.

This exact same setup works on Mint without any issues so it has to be some setting that isn't getting set right.  I can look at Mint config files to see but I'm not sure which ones I should look at.

Offline

#9 2012-01-22 19:31:34

gtpitch
Member
Registered: 2012-01-22
Posts: 6

Re: DHCP issues on wired connection

Ok so I found a fix that works for now.  Yesterday I had tried loading it as a static IP address and couldn't get it to work but I think I had the DNS servers wrong.  Today I loaded a static IP through:

CCONNECTION='ethernet'
DESCRIPTION='A basic static ethernet connection using iproute'
INTERFACE='eth0'
IP='static'
ADDR='192.168.1.101'
ROUTES=('192.168.1.1')
GATEWAY='192.168.1.1'
DNS=('207.69.188.186')

## For IPv6 autoconfiguration
#IP6=stateless

## For IPv6 static address configuration
#IP6='static'
#ADDR6=('1234:5678:9abc:def::1/64' '1234:3456::123/96')
#ROUTES6=('abcd::1234')
#GATEWAY6='1234:0:123::abcd'

and the internet seems to work fine.  I still don't understand why DHCP won't work however I'm satisfied that I can at least connect to the internet through the router and have wireless on my laptop at the same time.

Offline

Pages: 1

Board footer

Powered by FluxBB