Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#8848 - dhcpcd 3.1.7-2 cannot get a lease when using the ethernet interface

Attached to Project: Arch Linux
Opened by João M. S. Silva (jmss) - Thursday, 06 December 2007, 02:05 GMT
Last edited by Greg (dolby) - Saturday, 24 May 2008, 09:03 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture i686
Severity High
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

dhcpcd cannot get a lease from the DHCP server (cable modem) when using the ethernet interface:

Dec 6 01:53:48 steklov dhcpcd[8527]: eth0: dhcpcd 3.1.7 starting
Dec 6 01:53:48 steklov dhcpcd[8527]: eth0: hardware address = (...)
Dec 6 01:53:48 steklov dhcpcd[8527]: eth0: broadcasting for a lease
Dec 6 01:54:18 steklov dhcpcd[8527]: eth0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-eth0.info'
Dec 6 01:54:18 steklov dhcpcd[8527]: eth0: checking (...) is available on attached networks
Dec 6 01:54:19 steklov dhcpcd[8527]: eth0: adding IP address (...)
Dec 6 01:54:19 steklov dhcpcd[8527]: eth0: exiting
Dec 6 01:54:24 steklov dhcpcd[8530]: eth0: broadcasting for a lease
Dec 6 01:54:54 steklov dhcpcd[8530]: eth0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-eth0.info'
Dec 6 01:54:54 steklov dhcpcd[8530]: eth0: checking (...) is available on attached networks
Dec 6 01:54:55 steklov dhcpcd[8530]: eth0: adding IP address (...)
Dec 6 01:55:00 steklov dhcpcd[8530]: eth0: broadcasting for a lease

It keeps repeating. There is no Internet connection. On the other hand, when starting the network through the USB interface:

Dec 6 01:57:09 steklov dhcpcd[8585]: eth2: dhcpcd 3.1.7 starting
Dec 6 01:57:09 steklov dhcpcd[8585]: eth2: hardware address = (...)
Dec 6 01:57:09 steklov dhcpcd[8585]: eth2: broadcasting for a lease
Dec 6 01:57:09 steklov dhcpcd[8585]: eth2: offered (...) from (...)
Dec 6 01:57:09 steklov dhcpcd[8585]: eth2: checking (...) is available on attached networks
Dec 6 01:57:11 steklov dhcpcd[8585]: eth2: leased (...) for 7200 seconds
Dec 6 01:57:11 steklov dhcpcd[8585]: eth2: adding IP address (...)
Dec 6 01:57:11 steklov dhcpcd[8585]: eth2: adding default route via (...) metric 0
Dec 6 01:57:11 steklov dhcpcd[8585]: eth2: exiting

Internet connection works.

Additional info:
* package version(s)

dhcpcd 3.1.7-2

* config and/or log files etc.

Both network profiles are configured only with IFOPTS="dhcp".

Steps to reproduce:

1. pacman -Sy dhcpcd
2. start ethernet interface with DHCP
This task depends upon

Closed by  Greg (dolby)
Saturday, 24 May 2008, 09:03 GMT
Reason for closing:  Not a bug
Comment by Jan de Groot (JGC) - Thursday, 06 December 2007, 10:57 GMT
It looks like you're getting a 30s timeout there.
Does this also happen with dhclient?

When I hear the word "cable modem", I'm always thinking about the fact that quite some modems need the power cord plugged before they will connect with a different network card.
Comment by João M. S. Silva (jmss) - Thursday, 06 December 2007, 11:50 GMT
I don't know how to use dhclient instead of dhcpcd. I tried to remove dhcpcd and then restart the network, but it seems that dhcpcd is hardcoded in the netcfg script that belongs to initscripts. Is there a place where I can configure dhclient instead of dhcpcd?

I will try the power off/on suggestion tonight.

Thanks.
Comment by Jan de Groot (JGC) - Thursday, 06 December 2007, 11:59 GMT
Just start "dhclient eth0" as root and it should try to get a DHCP lease for eth0.
Comment by Tobias Powalowski (tpowa) - Friday, 07 December 2007, 20:50 GMT
status on dhcpcd 3.1.8 from testing?
Comment by João M. S. Silva (jmss) - Saturday, 08 December 2007, 00:19 GMT
Hi,

I just tried what Jan de Groot suggested and it worked. So it probably is a modem problem. The modem is a Motorola SBV5120.

Additionally, I tried dhcpcd 3.1.8-1 and it also works.

Thanks for your help.
Comment by João M. S. Silva (jmss) - Saturday, 08 December 2007, 00:52 GMT
Hi again,

I made some more experiments. I switched the network connection between two laptops that I have. Whenever I did that I was unable to reconnect unless I powered down the modem.

Then I installed dhcpcd 3.1.8-1 on both laptops and I can now switch the laptops without any problems. It looks like the correction in 3.1.8-1 is working well (equivalent to powering down the modem).

Thanks.
Comment by João M. S. Silva (jmss) - Tuesday, 11 December 2007, 17:47 GMT
Even using dhcpcd 3.1.8 I still had to power off/on the modem for getting a lease with an USB interface.

Is this possible?
Comment by Jan de Groot (JGC) - Thursday, 27 December 2007, 12:22 GMT
This is by design. Your modem learns a MAC address and sets up bridging to that device. Whenever you switch your network card, your modem has to re-initialize its bridge settomgs. I've had several modems here (Motorola Surfboard 4200, 5100 and the Arris TouchStone TM502B) that require you to power off the modem to re-initialize the bridge settings.

Loading...