populate interface-used with default route #211
Closed
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.
The end goal is for the websocket to loop through the connection interfaces and populate the header with the first interface that works. However, there are still some unknowns as to whether or not getting the interface list from the OS will even work. There are also outstanding questions about priority of which interface to try first, etc.. I think we will learn more if we populate the possible interface list from the os and also retrieve the interface for the default route and just send those back initially.
Just my opinion, though. We don't need to merge this. But currently we are hardcoding "erouter0" for every request which is pretty useless.