Skip to content

hostapd and dns #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
darkdrgn2k opened this issue Jan 9, 2018 · 4 comments
Open

hostapd and dns #16

darkdrgn2k opened this issue Jan 9, 2018 · 4 comments

Comments

@darkdrgn2k
Copy link
Contributor

Connection to HostAP establishes fine, but no DNS servers are offered over dhcp.
@darkdrgn2k
Copy link
Contributor Author

screenshot_20180108-165320

@benhylau
Copy link
Member

benhylau commented Jan 9, 2018

Confirmed this issue on MacOS

@hamishcoleman
Copy link
Contributor

systemd-networkd has a race condition - the dhcp service is configured before the uplink port is fully setup. Thus the dhcp service does not see any DNS (or NTP) settings when it is first run.

Additionally, the version of systemd-networkd in stretch looks like it will only reconfigure the dhcp server if you restart the whole daemon - which just causes the same race.

Finally, a fix included in systemd v234 could help (see systemd/systemd#6116) by allowing a down/up on the downstream interface to trigger a reconfigure of the dhcp service

@benhylau
Copy link
Member

Let's grab systemd v236 from stretch-backports?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@benhylau @hamishcoleman @darkdrgn2k