Ethernet/Wi-Fi - Hostapd prevents Ethernet from getting DHCP address
Jouni Malinen
j
Sat Apr 18 00:00:32 PDT 2015
On Fri, Apr 17, 2015 at 05:08:04PM -0500, Don Lawrence wrote:
> I have a custom build project using an Intel NUC with a wirless card and
> ethernet port as a AP for clients to connect to. The ethernet is just a
> connection to the machine and the two are not bridged.
> I had to compile hostapd from source since it isn't in the CentOS 7 repo. I
> had few problems getting the system setup. After I rebooted, I found the
> ethernet port didn't have a DHCP address and I couldn't get it to snag
> one. I thought because I was running dhcdp locally but that wasn't it.
> Once I stopped hostapd I was able to get an IP on the ethernet port.
I don't think there is anything in hostapd that would do that especially
when the netdevs are independent and not bridged together.
> I am wondering if I could get a point in the right direction as to why and
> how to get around it if possible. I could make the hostapd a manual start
> after the device starts up but I'd rather not.
So how does hostapd get started for the case where DHCP does not work?
I'd assume those startup scripts would be behind the changes that affect
DHCP.
--
Jouni Malinen PGP id EFC895FA
More information about the Hostap
mailing list