You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/backends/airos.rst
+36-3Lines changed: 36 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -141,7 +141,7 @@ AirOS supports the following types of interfaces
141
141
* **wirelesss interfaces**: must be of type ``wireless``
142
142
* **bridge interfaces**: must be of type ``bridge``
143
143
144
-
A network interface can be designed to be the management interfaces by setting the ``managed`` key to ``True`` on the address chosen.
144
+
A network interface can be designed to be the management interfaces by setting the ``role`` key to ``mlan`` on the address chosen.
145
145
146
146
As an example here is a snippet that set the vlan ``eth0.2`` to be the management interface on the address ``192.168.1.20``
147
147
@@ -156,7 +156,7 @@ As an example here is a snippet that set the vlan ``eth0.2`` to be the managemen
156
156
{
157
157
"address": "192.168.1.20",
158
158
"family": "ipv4",
159
-
"managed": true,
159
+
"role": "mlan",
160
160
"mask": 24,
161
161
"proto": "static"
162
162
}
@@ -188,7 +188,40 @@ As an example here is a snippet that enables both auto-negotiation and flow cont
188
188
Role
189
189
^^^^
190
190
191
-
Interfaces can be assigned a ``role`` to mimic the web interfaces features. As an example setting the ``management`` property of an address to ``true`` will add the role ``mlan`` to the interface configuration. If not set the management interface will be selected as the (first) one providing a gateway in one of it's addresses.
191
+
Interfaces can be assigned a ``role`` to mimic the web interfaces features.
192
+
193
+
As an example setting the ``role`` property of an address to ``mlan`` will add the role ``mlan`` to the interface configuration.
194
+
195
+
Here is the snippet to set the role to ``mlan``
196
+
197
+
.. code-block:: json
198
+
199
+
{
200
+
"interfaces": [
201
+
{
202
+
"type": "ethernet",
203
+
"name": "eth0",
204
+
"addresses": [
205
+
{
206
+
"family": "ipv4",
207
+
"proto": "static",
208
+
"address": "192.168.1.1",
209
+
"role": "mlan"
210
+
}
211
+
]
212
+
}
213
+
]
214
+
}
215
+
216
+
217
+
This is the list of roles available for a device in ``bridge`` mode:
218
+
219
+
* ``mlan`` for the management interface
220
+
221
+
This is the list of roles available for a device in ``router`` mode:
0 commit comments