Bug 10869 – More than one dhcp daemon running for wireless interface

Bug 10869 - More than one dhcp daemon running for wireless interface

Summary:

More than one dhcp daemon running for wireless interface

Status:	RESOLVED FIXED

Product:	SB Touch
Classification:	Unclassified
Component:	Setup
Version:	unspecified
Platform:	PC Other

Importance:	-- normal (vote)
Target Milestone:	---
Assigned To:	Felix Mueller

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-01-28 05:14 UTC by Felix Mueller
Modified:	2009-09-08 09:19 UTC (History)
CC List:	1 user (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Felix Mueller 2009-01-28 05:14:07 UTC

From a factory reset switching from ethernet to wireless correctly kills the dhcp daemon for eth0 and starts one for wlan0. After forgetting this wireless network the dhcp daemon for wlan0 is still running (which is not yet an issue), but adding  it back results in two dhcp daemons running.

Every cycle of forgetting and re-adding a wireless network leaves an additional dhcp daemon instance running.

I don't think the dhcp daemon should be killed when forgetting a network since it could be one that is not used at the moment. I rather think we should check before starting a new instance if another is still running.

Comment 1 Felix Mueller 2009-02-02 16:18:59 UTC

Fixed in r4020. This also fixes the entries in the routes table when switching back to ethernet.