[v2] hostapd: IAPP: Set SO_REUSEADDR on listening socket #242
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
LGTM. 1 minor nit, following https://wiki.openwrt.org/doc/devel/patches#naming_patches the patch name should start with 1xx. |
|
Hadn't noticed that, thanks, will change it |
This patch makes it possible to use the Inter-Access Point Protocol implementation of hostapd in one of the most common scenarios -- when having more than one interface or BSS. Upstream tracking: https://patchwork.ozlabs.org/patch/656818/ Signed-off-by: Petko Bordjukov <bordjukov@gmail.com>
|
Pushed a hostapd update to my staging tree |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch makes it possible to use the Inter-Access Point Protocol
implementation of hostapd in one of the most common scenarios -- when
having more than one interface or BSS.
Upstream tracking: https://patchwork.ozlabs.org/patch/656818/
As a side note, the upstream patch comes as a follow-up to https://patchwork.ozlabs.org/patch/542556/, which wasn't merged because there were concerns about
SO_REUSEPORT's compatibility.