Re: [lime-dev] Pad of LiMeCat2016q3

On 08/07/2016 01:12 PM, Ilario Gelmetti wrote: It was an amazing weekend :D I copy-pasted here the pad contents for continuing the discussion here. The content of the pad is just a part of what was discussed and done, check out the commits for having a deeper inspection of the changes done https://github.com/libre-mesh/lime-packages/commits/develop https://github.com/libre-mesh/lime-build/commits/16.07 waiting for the release of version 16.07 which is quite there! You can already use the "16.07" branch of lime-build for testing. === LiMeCat 2016q3 - La Talaia, Valldoreix, 20160806 === Canal IRC: #libre-mesh en freenode.net Idioma: lo que quereis usar està bien. Index: Do we want firewall package? Do we want /etc/lime-rc.d? Do we want nodogsplash? (v2?) builds.libre-mesh.org will be down until september clarify manual vs lime-build ways to compile the firmware express support LEDE project Let's switch now from adhoc to 802.11s? fix auto ip assignment for mac address producing ip ending with 0 seems safe to include named wifi interfaces which value for adhoc_ssid? anygw or thisnode.info Random errors which channel for 5GHz? libre-mesh, Libre-Mesh, libremesh or LibreMesh? ESSID ap, ap-named, adhoc? NAT by default on every WAN? How to add ethernet interface to batman-adv using "specific" settings in lime Changing options in wifi section in /etc/config/lime Let's eliminate /etc/lime directory WE HAVE STIKERS removed dependency from luabitop suggest to reboot after issuing lime-config in the web interface == Do we want firewall package? == Gio: the fact that the package is installed, even if disabled, is annoying Gui: LiMe has to work both with firewall or without Gio: by default no dependence by it Pau: disabled by default better to not allow the user to use the firewall otherwise it will break things, if he really wants to use it he can install it manually == Do we want /etc/lime-rc.d? == Exeryone except Pau: no, two dirs with the same function Pau: a directory for all the LiMe daemons firewall rules for LiMe will be moved from /etc/lime-rc.d to /etc/init.d and renamed to firewall-user or firewall-mini Decision: we will move content of /etc/lime-rc.d to /etc/init.d and rename to firewall-user. This file will be moved from lime-system to lime-eb-ip-tables == Do we want nodogsplash? == No, decided some time ago (?) == builds.libre-mesh.org will be down until september == shall we remove it temporarly for the website? do we have another server for it? the same server == clarify manual vs lime-build ways to compile the firmware == http://libre-mesh.org/getit.html https://github.com/libre-mesh/lime-packages/blob/develop/README.md - When trying to compile, the "Get it" page offers two options. The "Compile Using the Tool lime-build" option is the recommended one for newbies -like me. So this is the only option to study today. - We are just trying for Ubuntu/Debian - If you can install OpenWRT in your router, you should be able to install LiMe. There's no need to check RAM, Flash, CPU... But it seems a good idea to find the page of your router at https://openwrt.org/ to check how easy -or difficult- will be to flash your router. Some can be tricky. - First of all, you need at least 7GB of free disk space to compile the firmware of your router (If you were to coock every available model with Chef, you would need 14GB of free disk space) - git clone https://github.com/libre-mesh/lime-build.git - sudo apt-get install git subversion zlib1g-dev gawk flex unzip bzip2 gettext build-essential libncurses5-dev libncursesw5-dev libssl-dev binutils cpp psmisc docbook-to-man - cd lime-build/ - You can see the list of officialy supported targets and profiles by typing: make info The output will be something like this: Using LiMe Git repository git://github.com/libre-mesh/lime-packages.git (T)ARGETS -> ar71xx ar71xx-mini x86 (P)ROFILES -> generic basic freifunk chef custom bmx7olsr1 T is the target related to the hardware type. P is the profile related to the software combination of packets. You will have to go to your router's page at https://openwrt.org/ and check at Hardware -> System-On-Chip if the architecture of your router is one of the supported ones. - ar71xx is one of the supported router architectures (this one is used for routers with at least 8MB of flash - you can check that in your router's page at https://openwrt.org/) - ar71xx-mini is one of the supported router architectures (this one is used for routers with only 4MB of Flash - you can check that in your router's page at https://openwrt.org/) - x86 is one of the supported router architectures (Intel architecture) For the Profiles (P), you will normally have to choose generic, but if your router only has 4MB of Flash, you better choose basic To compile a target/profile just execute (example): make T=ar71xx P=generic The default branch is always the last stable release. You will find the binaries ready to install in output directory. PR for lime-build readme https://github.com/libre-mesh/lime-build/pull/12 PR for lime-package readme https://github.com/libre-mesh/lime-packages/pull/65 there are broken links in lime-packages readme solved == announce the support LEDE project == where do we put the announcement? changed the meetings page to news page in the website draft of endorsement: 2016-08-06 - Endorsement to LEDE project We endorse the LEDE project and we plan to start basing Libre-Mesh releases on Linux Embedded Development Environment (LEDE) as soon as it will have a stable release. http://libre-mesh.org/news.html == odhcpd or not? == Pau & Gio: no, to have it is a problem Gui: if the package is broken tell this to OpenWrt people, better to not diverge from OpenWrt if not needed No == Let's switch now from adhoc to 802.11s? == not this release, but yes for the next one! == fix auto ip assignment for mac address producing ip ending with 0 == we will try https://github.com/libre-mesh/lime-packages/issues/34 done == seems safe to include named wifi interfaces == https://github.com/libre-mesh/lime-packages/issues/50 make it as a lime-mode package, we can put it already in the coming release the alternative is specify a mac address when connecting to the ap, with network-manager is not working via terminal commands is doable: # iwconfig wlan0 essid Libre-Mesh.org # iwconfig wlan0 ap 12:32:ad:ad:ad:ad apname inserted in lime-system https://github.com/libre-mesh/lime-packages/blob/develop/packages/lime-syst… == which value for adhoc_ssid? == Pau: hostname (as already is) Gui: "libre-mesh.org" LiMe == can we avoid the conditional dependency bug? == https://github.com/libre-mesh/lime-packages/pull/41 https://dev.openwrt.org/ticket/22226 reverted the commit which inserted the conditional dependency == anygw or thisnode.info == they do exactly the same but anygw doesn't work in firefox we will keep both but just document thisnode.info, anygw is useful just for saving keyboard use... == Random errors == On a WDR3600 dmesg [...] [ 105.030000] ip6_tunnel: bmxOut_android xmit: Local address not yet configured! [ 320.250000] ip6_tunnel: bmxOut_android: Path to destination invalid or inactive! [ 320.250000] ip6_tunnel: bmxOut_android: Path to destination invalid or inactive! [ 320.260000] ip6_tunnel: bmxOut_android: Path to destination invalid or inactive! [ 1128.740000] ip6_tunnel: bmxOut_android xmit: Local address not yet configured! root@LiMe-f9c237:/# batctl o Warning - mac already known (changing name from 'LiMe-fd17fa_anygw' to 'LiMe-f9c237_anygw'): aa:aa:aa:aa:aa:aa Warning - mac already known (changing name from 'LiMe-f9c237_anygw' to 'TalaiaNS-0f6374_anygw'): aa:aa:aa:aa:aa:aa Warning - mac already known (changing name from 'TalaiaNS-0f6374_anygw' to 'TallerTalaia_anygw'): aa:aa:aa:aa:aa:aa Warning - mac already known (changing name from 'TallerTalaia_anygw' to 'LiMe-fc3312_anygw'): aa:aa:aa:aa:aa:aa [B.A.T.M.A.N. adv 2016.1, MainIF/MAC: dummy0/aa:e9:84:f9:c2:37 (bat0 BATMAN_IV)] [...] These last warnings are because alfred shares /tmp/bat-hosts with duplicated mac address from anygw (which has always the same mac address) This part of Alfred was written by Gui, he could implement a check == which channel for 5GHz? == 48 is allowed for indoor 157 is allowed just for low powers in Europe but is just allowed in many other places 36 problems with 40 MHz width 48 == libre-mesh, Libre-Mesh, libremesh or LibreMesh? == Pau: libre-mesh Gui: LibreMesh Ilario: libremesh but is a very bad idea to change it now, too late we're not going to change the name of the project, we can consider to stop paying for the domain name without dash == ESSID ap, ap-named, adhoc? == ap: Libre-Mesh.org (that will be customized for each community) ap-named: Libre-Mesh.org-AABBCC (append the last part of MAC address to ap essid) adhoc: ??? Gui: adhoc no with mac address because too many useless networks seen by laptop user, better "Libre-Mesh.org" Gio: let's leave adhoc as hostname (LiMe-AABBCC) Ilario: Libre-Mesh.org-adhoc Decision for adhoc: LiMe https://github.com/libre-mesh/lime-packages/pull/67 Pau, Gui: ap-named Libre-Mesh.org/%H Gio: Libre-Mesh.org-%H Ilario: Libre-Mesh.org_%H Decision for ap-named: Libre-Mesh.org/%H and redirect on the homepage for every 404 in our website https://github.com/libre-mesh/lime-packages/pull/68 404 redirection still to do == NAT by default on every WAN? == Gui: yes Pau: not needed but doable in lime-firewall When someone plugs something in a WAN port he expects to have a NAT there This allows you to access captive portals if your router is plugged to it Also in case of malfunctioning of the modem, this way you can access the modem == How to add ethernet interface to batman-adv using "specific" settings in lime == It works as expected: putting something like (but the name of the new section can't contain neither dashes -) config net 'ethbat' option linux_name 'eth0.1' list protocols 'adhoc' list protocols 'lan' list protocols 'anygw' list protocols 'batadv:%N1' list protocols 'bmx6:13' list protocols 'olsr:14' list protocols 'olsr6:15' list protocols 'olsr2:16' == Changing options in wifi section in /etc/config/lime == works. == Let's eliminate /etc/lime directory == Gui: It's confusing and makes too easy to throw stuff there instead of looking for the proper OpenWrt place Ilario: Let's delete it! Gio: could be needed == WE HAVE STIKERS == We have stickers!!!! Ask Pau for having some. == removed dependency from luabitop == just this == suggest to reboot after issuing lime-config in the web interface == done by Pau