Bug 46543 – udhcpc does not work with multiple routers

Bug 46543 - udhcpc does not work with multiple routers


Summary:	udhcpc does not work with multiple routers

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	DHCP
Version:	UCS 4.3
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-03-08 11:43 CET by Philipp Hahn
Modified:	2021-05-14 16:34 CEST (History)
CC List:	0 users

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	6: Setup Problem: Issue for the setup process
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.069
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Allow multiple routers (1.62 KB, patch) 2018-03-08 11:43 CET, Philipp Hahn	Details \| Diff
View All 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 Philipp Hahn

2018-03-08 11:43:19 CET

Created attachment 9449 [details]
Allow multiple routers

During the Debian setup process "udhcpc" from "busybox" is used.
It fails "silently" if multiple routers are configures via a "DHCP routing" policy.

Running the following command by hand shows the error:
  udhcpc -i ens3 -V d-i -T 1 -t 59 -O router -f
...
  ip: an inet address is expected rather than "192.168.10.13 192.168.10.14"

The bug is in "/etc/udhcpc/default.script:72", where "$router" is quoted prefenting IFS splitting.

<https://udhcp.busybox.net/README.udhcpc>

Upstream-Bug
No regression

Comment 1 Ingo Steuwer

2021-05-14 15:41:40 CEST

This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.