luci-app-mwan3: add rt_table_lookup option
Make list option rt_table_lookup configurable in luci. With this option we could define additional routing tables which get scanned by mwan3 and then get added to the connected ipset. The entries will be treated as connected network and will not get mangeld by mwan3. Signed-off-by: Florian Eckert <fe@dev.tdt.de>
This commit is contained in:
parent
8517a25a80
commit
6ec540c46d
1 changed files with 10 additions and 1 deletions
|
@ -3,7 +3,7 @@
|
|||
|
||||
local net = require "luci.model.network".init()
|
||||
|
||||
local s, m, local_source, mask, rtmon
|
||||
local s, m, local_source, mask, rtmon, rtlookup
|
||||
|
||||
m = Map("mwan3", translate("MWAN - Globals"))
|
||||
|
||||
|
@ -43,4 +43,13 @@ rtmon:value("5", translatef("%d seconds", 5))
|
|||
rtmon:value("7", translatef("%d seconds", 7))
|
||||
rtmon:value("10", translatef("%d seconds", 10))
|
||||
|
||||
rtlookup = s:option(DynamicList,
|
||||
"rt_table_lookup",
|
||||
translate("Routing table lookup"),
|
||||
translate("Also scan this Routing table for connected networks"))
|
||||
rtlookup.datatype = "integer"
|
||||
rtlookup:value("1", translatef("Routing table %d", 1))
|
||||
rtlookup:value("2", translatef("Routing table %d", 2))
|
||||
rtlookup:value("220", translatef("Routing table %d", 220))
|
||||
|
||||
return m
|
||||
|
|
Loading…
Reference in a new issue