additional network interfaces (page)

[seamustuohy]

section text: Additional Network Interfaces
section help text:Commotion's Setup Wizard has detected additional un-configured network interfaces on this device. If desired, you can configure them here.
option text: Internet Gateway
dropdown box: gateway configurations allowed (need list of types for ui text review)
option title: Advertise
checkbox
option help text: Advertise your gateway to the mesh network.
Link to advanced interfaces page: Wireless Interfaces
help text: cbi forms for configuring wireless interfaces on this device
Link to advanced interfaces page: Ethernet Interfaces
help text: cbi forms for configuring wired interfaces on this device

[seamustuohy]

@critzo @georgiamoon worked a few hours on creating a system for adding networks to additional network interfaces. It looks as if, while it is possible, it will be hard enough to warrent being a version 1.1 feature. In fact, since each wireless interface page allows the addition of an arbitrary number of interfaces (post quickstart) it may not be needed at all. We will have to look at user testing to determine this. Gateway configurations will still be implemented though.

TLDR: Should we rename this section to gateway controls? If so I need a new section name

[seamustuohy]

@critzo @georgiamoon

Here is the updated current text. Please review and provide alternatives/feedback for the page

Section text: Internet Gateway
help: "If desired, you can configure your gateway interface here.

title: "Advertise your gateway to the mesh."
checkbox

Title: "Will you be meshing with other Commotion devices over the ethernet interface?"
checkbox

title: "Gateway Configuration"
dropdown
option: Automatically configure gateway on boot."
option: "We have an upstream device that provides DHCP leases"
option: This device should provide DHCP leases to clients."

[seamustuohy]

Page ready for R1. More work needs to be take on for R1.1 to apply these options across all interfaces.

FROM:
opentechinstitute/commotiond#43
opentechinstitute/commotiond#52 (out of band conversation)

"After reflecting on the old notes in this issue, your proposed options in the other issue, which options are mutually exclusive, and our previous conversation, here are my new proposed options. These are actually potentially valid for all three types of interfaces, in that I realized that all the different default functionality for interfaces can be encapsulated by these three options. Also, I realized that a manual switch for 'gateway' is global, and not specific to a given interface. Given the potential for abuse, we should probably hold off of allowing a manual gateway switch until we have #52.

option meshed (true/false) : controls whether this interface passes OLSR traffic. Default off for ap & plug, on for mesh.

option announced (true/false) : controls whether the subnet on this interface is advertised as an HNA. Default true for ap, and for plug acting as a dhcp server, but default false for mesh and for plug acting as a DHCP client.

option dhcp (client, server, none, auto) : client always attempts to get a DHCP lease. Server always attempts to hand one out. None does not attempt to do anything with DHCP; it just attempts to configure the interface. Auto is the current default functionality. Default auto for plug, server for ap, and none for mesh."

[seamustuohy]

closed per enhancement request #133