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

Add OLSRd gateway selection support #52

Open
areynold opened this issue Oct 18, 2013 · 4 comments
Open

Add OLSRd gateway selection support #52

areynold opened this issue Oct 18, 2013 · 4 comments

Comments

@areynold
Copy link
Collaborator

We already use SmartGateway, so it should be possible to create an interface to allow users to select their gateway based on certain criteria. This would ideally integrate with service advertisements and servald signing, so that we would have more criteria upon which to select than simple ETX.

(Was issue 364 on code.commotionwireless.net)

@seamustuohy
Copy link
Collaborator

Per: opentechinstitute/luci-commotion#85 @jheretic
I will add UCI bindings to add options and values to the /etc/config/network "plug" network. Please let me know what you would like the final options and values named and I will update them in the interface. If we should combine some of these let me know.

  1. for advertising the gateway over the mesh
    option advertised (true/false)
  2. for configuring the way dhcp is handled on the interface
    option configuration (client/host/auto)
  3. for turning on meshing on the interface
    option meshed (true/false)

@jheretic
Copy link
Member

jheretic commented Dec 6, 2013

@elationfoundation Sounds good. I would maybe change the second option to be 'dhcp' rather than 'configuration.' However, this issue is for allowing a node to select a gateway from a list other than the one that OLSRd considers to be the default, not the option that we discussed yesterday. That one is #43

@seamustuohy
Copy link
Collaborator

Darn... woops! I will use those values then.

@jheretic
Copy link
Member

jheretic commented Dec 6, 2013

@elationfoundation Not to hijack this issue further, but there is one further option: client_bridge, which holds the configuration name of the bridge which the plug interface now tries to add itself to when it fails to obtain a lease.

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