Udhcpc fails on interface that starts with MAC of 00:00:00:00:00:00

Bug #567977 reported by blaisegassend
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
udhcp (Ubuntu)
New
Undecided
Unassigned

Bug Description

I have a wireless USB card (Ralink 2770 based) that reports a MAC address of 00:00:00:00:00:00 until it is first brought up. If I start udhcpc before the the interface is first brought up, and then bring up the interface, udhcpc will never manage to get a lease (doing a SIGUSR1 causes it to try, but it consistently fails). I suspect that udhcpc is caching the MAC address the interface had when it was first started, and hence failing to communicate even after the MAC address gets set. I think that it would be appropriate for udhcpc to re-read the MAC address each time it starts trying to get a lease, as the performance hit would be trivial.

pr2@ta105:~$ lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10

pr2@ta105:~$ apt-cache policy udhcpc
udhcpc:
  Installed: 0.9.8cvs20050303-2.1
  Candidate: 0.9.8cvs20050303-2.1
  Version table:
 *** 0.9.8cvs20050303-2.1 0
        500 http://aptproxy.willowgarage.com karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
Architecture: i386
Date: Wed Apr 21 09:52:27 2010
DistroRelease: Ubuntu 9.10
Package: udhcpc 0.9.8cvs20050303-2.1
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: udhcp
Uname: Linux 2.6.31-14-generic i686
XsessionErrors:
 (gnome-settings-daemon:1547): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1547): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:1587): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:1604): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
blaisegassend (blaise-gassend-launchpad) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.