onemarcfifty / luci-proto-batman-adv

OpenWrt LuCI support for the batman-adv protocol
Apache License 2.0
17 stars 6 forks source link

Using bat VLANs causes luci rendering issues preventing config #1

Open slogen opened 2 years ago

slogen commented 2 years ago

First, thanks for the luci interfaces to batman!

I have added some interfaces and devices that use batman VLANs (bat0.xxx). This seems to crash the edit of interfaces luci (22.:

image

image

I found this related issue on openwrt: https://forum.openwrt.org/t/missing-js-files-for-luci/63298, which may be involved. When luci renders the edit boxes for interfaces, it asks for a "batadv_vlan.js": https://10.160.0.1/luci-static/resources/protocol/batadv_vlan.js?v=git-22.167.28394-8a4486a, resulting in [HTTP/1.1 404 Not Found 46ms]. This could be what is causing devices to not be set?

Openwrt version: Powered by LuCI openwrt-22.03 branch (git-22.167.28394-8a4486a) / OpenWrt 22.03.0-rc5 r19523-bfd070e7fa

root@ap6:/www/luci-static/resources/protocol# opkg list-installed
base-files - 1485-r19523-bfd070e7fa
batctl-full - 2022.0-3
batctl-tiny - 2022.0-3
busybox - 1.35.0-3
ca-bundle - 20211016-1
cgi-io - 2021-09-08-98cef9dd-20
dnsmasq - 2.86-13
dropbear - 2022.82-2
firewall4 - 2022-06-17-15c38317-1
fstools - 2022-06-02-93369be0-1
fwtool - 2019-11-12-8f7fe925-1
getrandom - 2021-08-03-205defb5-2
hostapd-common - 2022-01-16-cff80b4f-9
iperf3 - 3.11-1
iw - 5.16-1
iwinfo - 2022-04-26-dc6847eb-1
jansson4 - 2.13.1-2
jshn - 2022-05-15-d2223ef9-1
jsonfilter - 2018-02-04-c7e938d6-1
kernel - 5.10.127-1-cc11c9333c8f4322e054499edd5bc57a
kmod-batman-adv - 5.10.127+2022.0-4
kmod-cfg80211 - 5.10.127+5.15.33-1-1
kmod-crypto-aead - 5.10.127-1
kmod-crypto-ccm - 5.10.127-1
kmod-crypto-cmac - 5.10.127-1
kmod-crypto-crc32c - 5.10.127-1
kmod-crypto-ctr - 5.10.127-1
kmod-crypto-gcm - 5.10.127-1
kmod-crypto-gf128 - 5.10.127-1
kmod-crypto-ghash - 5.10.127-1
kmod-crypto-hash - 5.10.127-1
kmod-crypto-hmac - 5.10.127-1
kmod-crypto-manager - 5.10.127-1
kmod-crypto-null - 5.10.127-1
kmod-crypto-rng - 5.10.127-1
kmod-crypto-seqiv - 5.10.127-1
kmod-crypto-sha256 - 5.10.127-1
kmod-gpio-button-hotplug - 5.10.127-3
kmod-hwmon-core - 5.10.127-1
kmod-leds-gpio - 5.10.127-1
kmod-lib-crc-ccitt - 5.10.127-1
kmod-lib-crc16 - 5.10.127-1
kmod-lib-crc32c - 5.10.127-1
kmod-mac80211 - 5.10.127+5.15.33-1-1
kmod-mt76-connac - 5.10.127+2022-07-03-93e3fce9-4
kmod-mt76-core - 5.10.127+2022-07-03-93e3fce9-4
kmod-mt7615-common - 5.10.127+2022-07-03-93e3fce9-4
kmod-mt7615-firmware - 5.10.127+2022-07-03-93e3fce9-4
kmod-mt7615e - 5.10.127+2022-07-03-93e3fce9-4
kmod-mt7915e - 5.10.127+2022-07-03-93e3fce9-4
kmod-nf-conntrack - 5.10.127-1
kmod-nf-conntrack6 - 5.10.127-1
kmod-nf-flow - 5.10.127-1
kmod-nf-log - 5.10.127-1
kmod-nf-log6 - 5.10.127-1
kmod-nf-nat - 5.10.127-1
kmod-nf-nat6 - 5.10.127-1
kmod-nf-reject - 5.10.127-1
kmod-nf-reject6 - 5.10.127-1
kmod-nfnetlink - 5.10.127-1
kmod-nft-core - 5.10.127-1
kmod-nft-fib - 5.10.127-1
kmod-nft-nat - 5.10.127-1
kmod-nft-nat6 - 5.10.127-1
kmod-nft-offload - 5.10.127-1
kmod-nls-base - 5.10.127-1
kmod-ppp - 5.10.127-1
kmod-pppoe - 5.10.127-1
kmod-pppox - 5.10.127-1
kmod-slhc - 5.10.127-1
kmod-thermal - 5.10.127-1
kmod-usb-core - 5.10.127-1
kmod-usb-xhci-hcd - 5.10.127-1
kmod-usb3 - 5.10.127-1
libblobmsg-json20220515 - 2022-05-15-d2223ef9-1
libc - 1.2.3-4
libevent2-core7 - 2.1.12-1
libgcc1 - 11.2.0-4
libiwinfo-data - 2022-04-26-dc6847eb-1
libiwinfo-lua - 2022-04-26-dc6847eb-1
libiwinfo20210430 - 2022-04-26-dc6847eb-1
libjson-c5 - 0.15-2
libjson-script20220515 - 2022-05-15-d2223ef9-1
liblua5.1.5 - 5.1.5-10
liblucihttp-lua - 2022-02-13-cc851838-1
liblucihttp0 - 2022-02-13-cc851838-1
libmnl0 - 1.0.5-1
libncurses6 - 6.3-1
libnftnl11 - 1.2.1-1
libnl-tiny1 - 2021-11-21-8e0555fb-1
libpcap1 - 1.10.1-2
libpthread - 1.2.3-4
librt - 1.2.3-4
libubox20220515 - 2022-05-15-d2223ef9-1
libubus-lua - 2022-06-01-2bebf93c-1
libubus20220601 - 2022-06-01-2bebf93c-1
libuci20130104 - 2021-10-22-f84f49f0-6
libuclient20201210 - 2021-05-14-6a6011df-1
libucode20220322 - 2022-06-01-b211ca0e-1
libustream-wolfssl20201210 - 2022-01-16-868fd881-1
libwolfssl5.3.0.ee39414e - 5.3.0-stable-6
logd - 2021-08-03-205defb5-2
lua - 5.1.5-10
luci - git-20.074.84698-ead5e81
luci-app-firewall - git-22.089.67563-7e3c1b4
luci-app-opkg - git-22.154.41881-28e92e3
luci-base - git-22.167.28394-8a4486a
luci-lib-base - git-20.232.39649-1f6dc29
luci-lib-ip - git-20.250.76529-62505bd
luci-lib-jsonc - git-22.097.61921-7513345
luci-lib-nixio - git-20.234.06894-c4a4e43
luci-mod-admin-full - git-19.253.48496-3f93650
luci-mod-network - git-22.172.78921-28d70ba
luci-mod-status - git-22.140.66206-3886866
luci-mod-system - git-22.140.66206-02913be
luci-proto-batman-adv - git-22.104.47289-0a762fd
luci-proto-ipv6 - git-21.148.48881-79947af
luci-proto-ppp - git-21.158.38888-88b9d84
luci-ssl - git-20.244.36115-e10f954
luci-theme-bootstrap - git-22.141.59265-d8ecf48
mtd - 26
netifd - 2022-06-01-39ef9fe1-1
nftables-json - 1.0.2-2
odhcp6c - 2021-12-05-39b584bc-18
odhcpd-ipv6only - 2021-08-11-01b4e604-1
openwrt-keyring - 2022-03-25-62471e69-3
opkg - 2022-01-09-2edcfad1-1
ppp - 2.4.9.git-2021-01-04-3
ppp-mod-pppoe - 2.4.9.git-2021-01-04-3
procd - 2022-06-01-7a009685-1
procd-seccomp - 2022-06-01-7a009685-1
procd-ujail - 2022-06-01-7a009685-1
px5g-wolfssl - 4
rpcd - 2022-02-07-909f2a04-1
rpcd-mod-file - 2022-02-07-909f2a04-1
rpcd-mod-iwinfo - 2022-02-07-909f2a04-1
rpcd-mod-luci - 20210614
rpcd-mod-rrdns - 20170710
tcpdump - 4.9.3-4
terminfo - 6.3-1
tmux - 3.2a-1
ubi-utils - 2.1.4-1
uboot-envtools - 2022.01-27
ubox - 2021-08-03-205defb5-2
ubus - 2022-06-01-2bebf93c-1
ubusd - 2022-06-01-2bebf93c-1
uci - 2021-10-22-f84f49f0-6
uclient-fetch - 2021-05-14-6a6011df-1
ucode - 2022-06-01-b211ca0e-1
ucode-mod-fs - 2022-06-01-b211ca0e-1
ucode-mod-ubus - 2022-06-01-b211ca0e-1
ucode-mod-uci - 2022-06-01-b211ca0e-1
uhttpd - 2022-02-07-2f8b1360-1
uhttpd-mod-ubus - 2022-02-07-2f8b1360-1
urandom-seed - 3
urngd - 2020-01-21-c7f7b6b6-1
usign - 2020-05-23-f1f65026-1
wireless-regdb - 2022.06.06-1
wpad-wolfssl - 2022-01-16-cff80b4f-9
slogen commented 2 years ago

It seems like the issue is not provoked by having VLAN tagged bat interfaces. Possibly by assigning two nets to a single bat interface? (in my case I did it with a wired VLAN and a wireless interface)

slogen commented 2 years ago

Validated that this "issue" was closed by assigning two nets to a single bat interface. It is still an issue, but only triggered with "improper" configuration

lorenzofiamingo commented 3 months ago

same here

lu-zero commented 2 months ago

I have the same issue apparently but only on the dhcp/dns section.