On 3/22/20 9:40 PM, pmauro(a)posteo.net wrote: Heeeeelo and welcome!! Ah hem... 18.06 is not an existing LibreMesh release, the latest release is 17.06 but most of the new installations use the development code compiled on top of OpenWrt 18.06 (which is considered to be stable enough to make a release, still has not been packaged as a release yet). I suggest to compile the development code using the instructions here [1] on "Compiling LibreMesh from source code". Linksys E2000 [2,3] have Broadcom wireless chipset, so it does not support multiAP (multiAP means that each radio can only have one interface, including mesh, but not mesh+AP+AP as we do by default in LibreMesh). For example, a meaningful configuration would be to use 2.4 GHz radio for AP and 5 GHz radio for mesh. For doing so, with development code, you'll need the following /etc/config/lime-node: ----------------------------------------------------------------------- config lime system # empty section means: take config from lime-community or lime-defaults config lime network # empty section means: take config from lime-community or lime-defaults config lime wifi list modes 'ap_2ghz' list modes 'ieee80211s_5ghz' ----------------------------------------------------------------------- then apply the LibreMesh configuration to OpenWrt configuration with "lime-config" command and reboot. The two lines I specified are documented in /docs/lime-example [4]. Some more documentation is on the website [5]. realized Yes, the development code is using lime-app. In my opinion it lacks some features for being a great and simpler replacement of the default LuCI, between those also the upload firmware one. Please contribute to the discussion here [6]. For uploading a new firmware, I usually use the "sysupgrade -n /tmp/blabla.bin" command. If you really need LuCI classical web interface, you can select it in the menuconfig during compilation (or install it via command line using opkg) and then open it with http://thisnode.info/cgi-bin/luci/ (as the default http://thisnode.info is now pointing to lime-app location). wifi? See above. Nope, it's automagic! Perfect! I Yeah! Thanks to the whole community :) Hugs, Ilario [1] https://libremesh.org/development.html [2] https://openwrt.org/toh/linksys/wrt320n [3] https://openwrt.org/toh/hwdata/linksys/linksys_e2000_v1 [4] https://github.com/libremesh/lime-packages/blob/master/packages/lime-docs/f… [5] https://libremesh.org/docs/index.html [6] https://github.com/libremesh/lime-packages/issues/327 -- Ilario iochesonome(a)gmail.com ilario(a)sindominio.net

Good afternoon again! I tried the proposed configuration on /etc/config/lime-node, done `lime-config` and `restart`. But, unfortunately, wifi is not working. Based on the output of the `lime-config` and `wifi status` command, and reading the documentation, I wonder if what I must do is create another radio and configure the mesh there. Also, I rollbacked the lime-node file changes, and checked the output of `wifi status`. Both APs and the mesh are configured on a single radio. Is that correct? So.. on a router like the TP-Link with 2 antennas, only one works? I mean, radio==antenna? Next is the output of `lime-config` and `wifi status`, with the suggested changes on lime-node: ---------------------------------------------------------------- root@LiMe-d64151:~# lime-config Clearing wireless config... Clearing network config... Disabling odhcpd sh: /etc/init.d/odhcpd: not found Cleaning dnsmasq Disabling 6relayd... No wan interface detected lime.proto.babeld.configure(...) Use fallback value for network.babeld_over_librenet6: false lime.proto.babeld.setup_interface(...)    wlan0-apname    ignored lime.proto.babeld.setup_interface(...)    wlan0-ap    ignored lime.proto.babeld.setup_interface(...)    eth0 Configuring system... Let uhttpd listen on IPv4/IPv6 ---------------------------------------------------------------- ---------------------------------------------------------------- root@LiMe-d64151:~# wifi status {     "radio0": {         "up": false,         "pending": false,         "autostart": true,         "disabled": false,         "retry_setup_failed": true,         "config": {             "channel": "11",             "hwmode": "11g",             "path": "bcma0:1",             "distance": 100,             "noscan": "1",             "noscan": true,             "disabled": false         },         "interfaces": [             {                 "section": "lm_wlan0_ap_radio0",                 "config": {                     "mode": "ap",                     "ifname": "wlan0-ap",                     "ssid": "LibreMesh.org",                     "mode": "ap",                     "network": [                         "lan"                     ]                 }             },             {                 "section": "lm_wlan0_apname_radio0",                 "config": {                     "mode": "ap",                     "ifname": "wlan0-apname",                     "ssid": "LibreMesh.org\/LiMe-d64151",                     "mode": "ap",                     "network": [                         "lan"                     ]                 }             }         ]     } } ---------------------------------------------------------------- Again, thanks in advance for your patience and help. Kind regards, Pedro. On 25.03.2020 05:57, Pedro Mauro wrote: _______________________________________________ lime-users mailing list lime-users(a)lists.libremesh.org https://lists.libremesh.org/mailman/listinfo/lime-users

Hello Pedro! The output you posted shows that both wlan0-ap and wlan0-apname are present. This should not happen if the configuration in /etc/config/lime-node is only what I suggested as the default modes list should have been replaced by only "ap_2ghz" and "ieee80211s_5ghz". Weird. The presence of both "ap" and "apname" interfaces is clearly an issue as Broadcom does not support more than one AP on the same radio. And for this reason I think that what SAn suggested should not work as both an AP and a mesh are set on the same radio [1]. For confirming this fact, please post the output of the commands, the relevant part is the "valid interface combinations" sections: iw phy phy0 info iw phy phy1 info the second command could say that there is no radio: according to the device characteristics page on OpenWrt website this device has two radios [2] (each radio is likely connected to both antennas, the number does not need to be the same, I believe) BUT according to dd-wrt wiki, the 2.4 GHz and 5 GHz cannot be used at the same time [3]! This means that on this router you'll be able to use only AP or only mesh. Not both. So this device is not very useful and should be paired to another device connected by cable (e.g. one Linksys E2000 does AP and is connected on the LAN ethernet port to another Linksys E2000 doing mesh). The alternative option to build the mesh with AP-sta backbone connections [4] does not improve by much the situation. For having only AP function, try having the following content in /etc/config/lime-node (and run lime-config and reboot): config lime system config lime network config lime wifi list modes 'ap' I suppose that it will default to use only 2.4 GHz. If this does not work please post the /etc/config/wireless file here. Analogously, for having only mesh try with a lime-config with: config lime system config lime network config lime wifi list modes 'ieee80211s' Again, if it does not work please post the /etc/config/wireless file here. As you say, it's a good idea to use interface specific configuration [5] but should not be needed. Ciao! Ilario [1] https://openwrt.org/docs/techref/hardware/soc/soc.broadcom.bcm47xx#b43 [2] https://openwrt.org/toh/hwdata/linksys/linksys_e2000_v1 [3] https://wiki.dd-wrt.com/wiki/index.php/Linksys_E2000 [4] https://github.com/libremesh/lime-packages/blob/master/packages/lime-docs/f… [5] https://github.com/libremesh/lime-packages/blob/master/packages/lime-docs/f… On 3/27/20 4:56 AM, SAn via lime-users wrote: > Hi Pedro! > > It seems that you device only have one radio, and as Ilario says if it > only supports one AP interface (I dont have experience with this > routers) then your lime-node should have: > > config lime wifi > list modes 'ap_2ghz' > list modes 'ieee80211s_2ghz' > > > Best! > SAn > > > On 3/26/20 8:23 PM, pmauro(a)posteo.net wrote: >> Good afternoon again! >> >> I tried the proposed configuration on /etc/config/lime-node, done >> `lime-config` and `restart`. >> But, unfortunately, wifi is not working. >> >> Based on the output of the `lime-config` and `wifi status` command, >> and reading the documentation, I wonder if what I must do is create >> another radio and configure the mesh there. >> >> Also, I rollbacked the lime-node file changes, and checked the output >> of `wifi status`. Both APs and the mesh are configured on a single >> radio. Is that correct? So.. on a router like the TP-Link with 2 >> antennas, only one works? I mean, radio==antenna? >> >> Next is the output of `lime-config` and `wifi status`, with the >> suggested changes on lime-node: >> ---------------------------------------------------------------- >> root@LiMe-d64151:~# lime-config >> Clearing wireless config... >> Clearing network config... >> Disabling odhcpd >> sh: /etc/init.d/odhcpd: not found >> Cleaning dnsmasq >> Disabling 6relayd... >> No wan interface detected >> lime.proto.babeld.configure(...) >> Use fallback value for network.babeld_over_librenet6: false >> lime.proto.babeld.setup_interface(...)    wlan0-apname    ignored >> lime.proto.babeld.setup_interface(...)    wlan0-ap    ignored >> lime.proto.babeld.setup_interface(...)    eth0 >> Configuring system... >> Let uhttpd listen on IPv4/IPv6 >> ---------------------------------------------------------------- >> >> ---------------------------------------------------------------- >> root@LiMe-d64151:~# wifi status >> { >>     "radio0": { >>         "up": false, >>         "pending": false, >>         "autostart": true, >>         "disabled": false, >>         "retry_setup_failed": true, >>         "config": { >>             "channel": "11", >>             "hwmode": "11g", >>             "path": "bcma0:1", >>             "distance": 100, >>             "noscan": "1", >>             "noscan": true, >>             "disabled": false >>         }, >>         "interfaces": [ >>             { >>                 "section": "lm_wlan0_ap_radio0", >>                 "config": { >>                     "mode": "ap", >>                     "ifname": "wlan0-ap", >>                     "ssid": "LibreMesh.org", >>                     "mode": "ap", >>                     "network": [ >>                         "lan" >>                     ] >>                 } >>             }, >>             { >>                 "section": "lm_wlan0_apname_radio0", >>                 "config": { >>                     "mode": "ap", >>                     "ifname": "wlan0-apname", >>                     "ssid": "LibreMesh.org\/LiMe-d64151", >>                     "mode": "ap", >>                     "network": [ >>                         "lan" >>                     ] >>                 } >>             } >>         ] >>     } >> } >> ---------------------------------------------------------------- >> >> Again, thanks in advance for your patience and help. >> >> Kind regards, Pedro. >> >> >> >> On 25.03.2020 05:57, Pedro Mauro wrote: >>> Hey Ilario, I'm very thankful for your detailed reply. >>> >>> I'll try to connect the Linksys router using those lines in the >>> config >>> and more documentation reading. I'm going very slow with it, because >>> a >>> lot of the terminology is new for me. >>> >>> Will be back with some news of the progress. >>> Kind regards, Pedro. >>> >>> El 23 de marzo de 2020 8:59:51 ART, Ilario Gelmetti >>> <iochesonome(a)gmail.com> escribió: >>> >>>> On 3/22/20 9:40 PM, pmauro(a)posteo.net wrote: >>>>> Good afternoon people! >>>> >>>> Heeeeelo and welcome!! >>>> >>>>> TLDR: on lime 17.x there was a Luci web interface (at >>>>> thisnode.info) >>>>> with a lot of configurations, and an option to upgrade the >>>>> router's >>>>> firmware. What happened to that in version 18.06? >>>> >>>> Ah hem... 18.06 is not an existing LibreMesh release, the latest >>>> release >>>> is 17.06 but most of the new installations use the development code >>>> compiled on top of OpenWrt 18.06 (which is considered to be stable >>>> enough to make a release, still has not been packaged as a release >>>> yet). >>>> I suggest to compile the development code using the instructions >>>> here >>>> [1] on "Compiling LibreMesh from source code". >>>> >>>>> I have now two routers to test: a TP-Link TL-WR842ND and a Linksys >>>>> E2000, both with version 18.06. >>>>> The TP-Link router works great! but in the Linksys I have no >>>>> wifi... >>>>> (now trying to see why) >>>> >>>> Linksys E2000 [2,3] have Broadcom wireless chipset, so it does not >>>> support multiAP (multiAP means that each radio can only have one >>>> interface, including mesh, but not mesh+AP+AP as we do by default >>>> in >>>> LibreMesh). >>>> >>>> For example, a meaningful configuration would be to use 2.4 GHz >>>> radio >>>> for AP and 5 GHz radio for mesh. >>>> For doing so, with development code, you'll need the following >>>> /etc/config/lime-node: >>>> ------------------------- >>>> config lime system >>>> # empty section means: take config from lime-community or >>>> lime-defaults >>>> >>>> config lime network >>>> # empty section means: take config from lime-community or >>>> lime-defaults >>>> >>>> config lime wifi >>>> list modes 'ap_2ghz' >>>> list modes 'ieee80211s_5ghz' >>>> ------------------------- >>>> then apply the LibreMesh configuration to OpenWrt configuration >>>> with >>>> "lime-config" command and reboot. >>>> The two lines I specified are documented in /docs/lime-example [4]. >>>> Some more documentation is on the website [5]. >>>> >>>>> While trying to test a "vanilla" OpenWRT .bin on the Linksys, I >>>>> realized >>>>> that the web interface for updating the firmware (among other >>>>> things) >>>>> that was present in some 17.x relase was no longer there, instead >>>>> replaced by another web app. Is that correct? >>>> >>>> Yes, the development code is using lime-app. >>>> In my opinion it lacks some features for being a great and simpler >>>> replacement of the default LuCI, between those also the upload >>>> firmware >>>> one. Please contribute to the discussion here [6]. >>>> For uploading a new firmware, I usually use the >>>> "sysupgrade -n /tmp/blabla.bin" command. >>>> If you really need LuCI classical web interface, you can select it >>>> in >>>> the menuconfig during compilation (or install it via command line >>>> using >>>> opkg) and then open it with http://thisnode.info/cgi-bin/luci/ [1] >>>> (as the >>>> default http://thisnode.info [2] is now pointing to lime-app >>>> location). >>>> >>>>> Also, do you know where I can look to know why the router has no >>>>> wifi? >>>>> (I can connect to it via ethernet). >>>> >>>> See above. >>>> >>>>> Also, I will need to make something >>>>> specific so that the two routers can build a mesh? >>>> >>>> Nope, it's automagic! >>>> >>>>> (I'm following the >>>>> instructions on the section "Compiling LibreMesh from source >>>>> code") >>>> >>>> Perfect! >>>> >>>>> Thanks to you all for the great work! >>>>> The simple fact of sending a mail to you It's a pleasure for me >>>>> haha, I >>>>> greatly admire this project :) >>>> >>>> Yeah! Thanks to the whole community :) >>>> Hugs, >>>> Ilario >>>> >>>> [1] https://libremesh.org/development.html [3] >>>> [2] https://openwrt.org/toh/linksys/wrt320n [4] >>>> [3] https://openwrt.org/toh/hwdata/linksys/linksys_e2000_v1 [5] >>>> [4] >>>> >>> https://github.com/libremesh/lime-packages/blob/master/packages/lime-docs/f… >>>> [6] >>>> [5] https://libremesh.org/docs/index.html [7] >>>> [6] https://github.com/libremesh/lime-packages/issues/327 [8] >>> >>> -- >>> Enviado desde mi dispositivo Android con K-9 Mail. Por favor, >>> disculpa >>> mi brevedad. >>> >>> Links: >>> ------ >>> [1] http://thisnode.info/cgi-bin/luci/ >>> [2] http://thisnode.info >>> [3] https://libremesh.org/development.html >>> [4] https://openwrt.org/toh/linksys/wrt320n >>> [5] https://openwrt.org/toh/hwdata/linksys/linksys_e2000_v1 >>> [6] >>> https://github.com/libremesh/lime-packages/blob/master/packages/lime-docs/f… >>> [7] https://libremesh.org/docs/index.html >>> [8] https://github.com/libremesh/lime-packages/issues/327 >> _______________________________________________ >> lime-users mailing list >> lime-users(a)lists.libremesh.org >> https://lists.libremesh.org/mailman/listinfo/lime-users > _______________________________________________ > lime-users mailing list > lime-users(a)lists.libremesh.org > https://lists.libremesh.org/mailman/listinfo/lime-users >