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

Improve broadcast address handling #4149

Open
lucasdemarchi opened this issue May 17, 2016 · 1 comment
Open

Improve broadcast address handling #4149

lucasdemarchi opened this issue May 17, 2016 · 1 comment
Assignees

Comments

@lucasdemarchi
Copy link
Contributor

Issue details

The bcast flag in ardupilot is primitive: it still needs the user to pass a valid broadcast address and doesn't work without one.

This makes it harder for writing an init unit file since you need to know what's the IP of the drone when you are configuring it. Even on scenarios where you are configuring Linux to act as an Access Point, depending on the right interface/address is bad for integrators and distro creators.

Proposal here is to use netlink which is the way Linux exports this information. With the Poller interface it's very easy to query the list of interfaces and dynamically adapt to it. Ideally we should be able to have a "no setup fee" for people installing ardupilot on a Linux board.

@rmackay9
Copy link
Contributor

that sounds useful!

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

No branches or pull requests

3 participants