Re: [lime-users] APE522II strange behaviour

Here are some excerpts from syslog which look suspicious to me: Tue Oct 27 22:03:09 2020 daemon.err babeld[1491]: Warning: keyword "wired" is deprecated -- please use "type" instead. Tue Oct 27 22:03:09 2020 daemon.err babeld[1491]: Warning: keyword "wired" is deprecated -- please use "type" instead. Tue Oct 27 22:03:09 2020 daemon.err babeld[1491]: Warning: couldn't determine channel of interface eth0-1_17. Tue Oct 27 22:03:09 2020 user.notice mac80211: Failed command: iw phy phy1 set antenna 0xffffffff 0xffffffff Tue Oct 27 22:03:09 2020 daemon.notice netifd: radio1 (1153): command failed: Not supported (-122) Tue Oct 27 22:03:10 2020 user.notice mac80211: Failed command: iw phy phy1 set distance 100 Tue Oct 27 22:03:15 2020 user.notice ucitrack: Setting up /etc/config/firewall reload dependency on /etc/config/miniupnpd Tue Oct 27 22:03:15 2020 daemon.crit dnsmasq[2005]: directory /tmp/resolv.conf.d/resolv.conf.auto for resolv-file is missing, cannot poll Tue Oct 27 22:03:15 2020 daemon.crit dnsmasq[2005]: FAILED to start up Tue Oct 27 22:03:15 2020 daemon.info procd: Instance dnsmasq::cfg01411c s in a crash loop 6 crashes, 0 seconds since last crash Tue Oct 27 22:03:20 2020 daemon.notice procd: /etc/rc.d/S90batmand: uci: Entry not found Tue Oct 27 22:03:21 2020 daemon.err hostapd: Using interface wlan0-ap with hwaddr 7a:a3:51:16:da:89 and ssid "MarinaMalgrats" Tue Oct 27 22:03:22 2020 kern.warn kernel: [ 45.557225] ieee80211 phy1: rt2800_config_channel: Warning - Using incomplete support for external PA Tue Oct 27 22:03:25 2020 daemon.err babeld[1491]: Warning: couldn't determine channel of interface wlan0-mesh_17. Tue Oct 27 22:03:26 2020 daemon.err babeld[1491]: Warning: couldn't determine channel of interface wlan1-mesh_17. Tue Oct 27 22:03:26 2020 daemon.err babeld[1491]: send: Address not available Tue Oct 27 22:03:26 2020 daemon.err babeld[1491]: send: Address not available Tue Oct 27 22:03:26 2020 daemon.err babeld[1491]: send: Operation not permitted Wed Oct 28 08:32:56 2020 daemon.crit dnsmasq[3050]: directory /tmp/resolv.conf.d/resolv.conf.auto for resolv-file is missing, cannot poll Wed Oct 28 08:32:56 2020 daemon.crit dnsmasq[3050]: FAILED to start up Regards Jürgen Am Mi., 28. Okt. 2020 um 09:49 Uhr schrieb Juergen Kimmel < juergenkimmel(a)gmail.com&gt;gt;: > *Juergen do you have the lime-proto-wan selected * > Yes > > Am Di., 27. Okt. 2020 um 21:44 Uhr schrieb Daniel Golle < > daniel(a)makrotopia.org&gt;gt;: > >> On Tue, Oct 27, 2020 at 05:25:32PM -0300, SAn via lime-users wrote: >> > Hi! >> > >> > On 10/27/20 5:14 PM, Daniel Golle wrote: >> > > On Mon, Oct 26, 2020 at 12:07:24PM +0100, Juergen Kimmel wrote: >> > >> I learned from the config.buildinfo that firewall has not been >> selected >> > >> The settings of the switches are identical. >> > >> May disabling the firewall have been the culprit? >> > >> I flashed the same device again there is no error and client has >> internet. >> > > >> > > Ah, of course, without any firewall installed there is also no >> > > NAT / masquerading happening, so if you want that, you do need >> > > something to configure that (such as OpenWrt's 'firewall' package'). >> > >> > AFAIK we recommend in the docs to use the package lime-hwd-openwrt-wan >> that selects lime-proto-wan. >> > This package provides the NATing rules without the need of the >> firewall package. >> >> It never matched my requirements and I never saw a reason not to use >> OpenWrt's firewall package. I've heard some vague myths about OpenWrt's >> firewall not working well with some of the routing protocols used in >> libremesh, but all attempts to reproduce that or inquire what the >> problem was or is remained without substancial results. >> I guess there are some historic reasons for some people to still >> hestitate using OpenWrt's firewall (ie. fw3 nowadays), maybe some bug >> which has long been resolved or simply not (auto-)adding the rules >> needed to also run routing protocols on the WAN interface (which I've >> fixed some years ago). >> >> > >> > Daniel maybe you are not using lime-proto-wan in your deploys? Juergen >> do you have the lime-proto-wan selected? >> > Maybe the automatic selection that is donde by lime-hwd-openwrt-wan is >> not working in this device? >> > >> > Best! >> > SAn >> > _______________________________________________ >> > 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 > >