Hi JH, Can you please post the NetJSON config you're using to generate this?
F. On Tue, 20 Dec 2022 at 05:42, J H <[email protected]> wrote: > Ignore the "list ports '*eth0.22*' " typo. VLAN id is not relevant > here - bridge and device work on eth, just not when i want to add wifi to > it. > > On Tuesday, 20 December 2022 at 09:40:24 UTC+1 J H wrote: > >> hi >> >> On OWRT 21.x / 22.x I already have a working cfg, but i wanted to deploy >> it via latest OpenWisp >> >> radio0 (5Ghz) and radio1 (2Ghz) with same SSid and bound to same network >> and bridge vlan 10 on eth0: >> >> config device 'device5' >> option bridge_empty '1' >> option name '*br-iot*' >> list ports '*eth0.10*' >> option type '*bridge*' >> >> config wifi-iface 'wifinet9' >> option device '*radio0*' >> option mode 'ap' >> option network '*lan_iot*' >> option disabled '0' >> option ssid 'iot' >> >> config wifi-iface 'wifinet10' >> option device '*radio1*' >> option mode 'ap' >> option network '*lan_iot*' >> option disabled '0' >> option ssid 'iot' >> >> config interface '*lan_iot*' >> option proto 'none' >> option device '*br-iot*' >> >> >> When i try to this this via OpenWisp i get this config which does not >> work: >> >> config device 'device_lan_iot' >> option name '*br_iot*' >> list ports '*eth0.22*' >> option type 'bridge' >> >> config interface 'lan_iot' >> option auto '1' >> option bridge_empty '1' >> option device '*br_iot*' >> option enabled '1' >> option proto 'none' >> >> config device 'device_lan_iot' >> option mtu '1500' >> option name '*iot5*' >> >> config interface 'lan_iot' >> option auto '1' >> option device '*iot5*' >> option enabled '1' >> option proto 'none' >> >> config device 'device_lan_iot' >> option mtu '1500' >> option name '*iot2*' >> >> config interface 'lan_iot' >> option auto '1' >> option device '*iot2*' >> option enabled '1' >> option proto 'none' >> >> package wireless >> >> config wifi-device 'radio0' >> option disabled '0' >> >> config wifi-device 'radio1' >> option disabled '0' >> >> config wifi-iface 'wifi_iot5' >> option device 'radio0' >> option disabled '0' >> *option ifname 'iot5'* >> option mode 'ap' >> option network '*lan_iot*' >> option ssid 'iot' >> >> config wifi-iface 'wifi_iot2' >> option device 'radio1' >> option disabled '0' >> >> *option ifname 'iot2'* option mode 'ap' >> option network '*lan_iot*' >> option ssid 'iot' >> >> >> Why are ifname used and devices built that are not used ? If i add iot2 >> or iot5 interfaces as bridge members then deployment also fails. >> Is it possible to built a cfg w/o ifnames and those interfaces ? Because >> that config works - just use network in wifi-ifaces. >> >> thank you >> >> >> -- > You received this message because you are subscribed to the Google Groups > "OpenWISP" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web, visit > https://groups.google.com/d/msgid/openwisp/f9c4d66c-2ab4-40f6-9e4a-c1353fde7da7n%40googlegroups.com > <https://groups.google.com/d/msgid/openwisp/f9c4d66c-2ab4-40f6-9e4a-c1353fde7da7n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/openwisp/CAAGgX6Jqo7wVNo3mUr%3DR54mMazPUg372Q29Epz2qPwgAWD2D3A%40mail.gmail.com.
