[thedude]

Get this every time I try to start dhcpd on 3.6 Ideas? Flames?

puffy# dhcpd xl0
user "_dhcp" not found
exiting.

[bmw]

I bet they reimplemented this with privilege separation. The online manpage doesn't mention it, but says that OpenBSD reworked it. Try creating a low-priv user called _dhcp and see what happens ...

[elmore]

http://www.openbsd.org/plus36.html


New _dhcp user and group for, funnily enough, the DHCP programs.


Looks like you need to add a _dhcp user. Did you upgrade?

[thedude]

Yep, upgraded. Wasted your guy's time with somethign simple. Addign the user worked just fine though I note it didn't fall back the user nobody though as stated on the OpenBSD site.

[bmw]

I'd say it's a bug (worth reporting). The rlse notes mention that dhclient will use nobody if there's no _dhcp, but no mention of dhcpd doing this, and you discovered that indeed it doesn't. That's inconsistent.

Also, the upgrade process should install all req'd privsep users, like _dhcp.

So two bugs unearthed today by thedude. Watcha gonna do for an encore? :-)

[thedude]

For an encore I'd like to figure out why my Macs and Windows/SUSE desktop can't ping each other. My Mac can ping a linux laptop, the linux laptop can ping the desktop and vice versa but no Max/desktop interaction. No personal firewalls turned, on just weird. See the Networking Forum if you have any ideas.

I submitted the bug. I will post here any responses/flames :D

[thedude]

And here's my response from joshATopenbsd.org

http://www.openbsd.org/faq/upgrade-minifaq.html#3.5.2

[thedude]

From: deraadtATcvs.openbsd.org
Subject: Re: dhcpd bug?
Date: November 7, 2004 5:00:52 PM PST
To: baxATshepfam.net
Cc: bugsATopenbsd.org

Upgraded from 3.5 to 3.6. DHCPD would not start and gave me the error
puffy# dhcpd xl0
user "_dhcp" not found
exiting.


Adding the user _dhcp fixed this. Shouldn't the dhcpd daemon have
defaulted to the user "nobody?"

No, it should not have. Sharing uids inside and outside jails is bad.

[cod3fr3ak]

good job bug hunter!