Skip to content
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.

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

FS#1451 - Access points should not run a DHCP server after installation #6414

Open
openwrt-bot opened this issue Mar 20, 2018 · 2 comments
Open
Labels

Comments

@openwrt-bot
Copy link

whitequark:

Take an UniFi AP or UniFi AC AP and deploy OpenWRT to it. It'll come up as an authoritative DHCP server, which is (a) completely unexpected, as no reasonable network will have authoritative DHCP servers running on access points, and (b) disruptive.

I think that default configuration for access points should be any of, in the order decreasing preference:

  • DHCP client with fallback to static configuration
  • Just DHCP client
  • Static configuration
@openwrt-bot
Copy link
Author

lleachii:

The OpenWRT software runs on all types of machines. What you describe appears to be OpenWRT's default configuration. Have you tried compiling a custom firmware?

The images are not built to differentiate between the OEM's originally intended use of a device.

The device could also be used as a Wireless router with no LAN ports.

Why is this config disruptive...it actually follows the OpenWRT user's manual?

@openwrt-bot
Copy link
Author

whitequark:

Have you tried compiling a custom firmware?

I am able to, and would much rather not do it.

The images are not built to differentiate between the OEM's originally intended use of a device.

Yes, this is what I consider the issue in this case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant