lime May 2017

lime-users@lists.libremesh.org

14 participants
21 discussions

[lime-users] Fwd: [Telecommons] WIFI4EU : Common letter open for signature

by Ilario Gelmetti

We already decided to subscribe, right? -------- Forwarded Message -------- Subject: [Telecommons] WIFI4EU : Common letter open for signature Date: Thu, 18 May 2017 12:39:22 +0200 From: Christopher Talib <ct(a)laquadrature.net> To: telecommons(a)laquadrature.net Dear all, As we discussed earlier this month, we are going to send a common letter from community networks to EU institutions concerning the WIFI4EU regulation. WIFI4EU (https://ec.europa.eu/digital-single-market/en/wifi4eu-free-wi-fi-europeans ) is an initiative announced last year by President Juncker in his "State of the Union" speech in Strasbourg. To deliver on this promise "to equip every European village and every city with free wireless Internet access around the main centres of public life by 2020", the EU will unleash 120 million between by 2017-2019 to roll out WiFi hotspots in at least 6,000 to 8,000 local communities. This initiative is laudable however, big telco companies want to ensure their monopolies through by leave smaller actors apart of it. Plus, few amendements are might open breaches of privacy by allowing the use of personal data of users using those networks. ***This letter is open for signatures untill Sunday 21 May midnight***. We will send it on Monday 22 May, few days before the trialogue meetings that will take place on the 29. The letter is here : https://pad.lqdn.fr/p/wifi4eu-netcommons-letter Do not hesitate to add or comment anything that looks unclear to you. Best, Chris -- Christopher Talib Chargé de Campagne Campaign Manager 0033 (0)6 34 16 81 89 GPG: 74C7 C656 A7C1 D900 E6F3 508C 2EFD 84D7 5FF7 74CB Keep updated about La Quadrature du Net: * https://wiki.laquadrature.net/Listes_de_discussion * https://lqdn.fr/chat _______________________________________________ Telecommons mailing list Telecommons(a)laquadrature.net https://lists.laquadrature.net/cgi-bin/mailman/listinfo/telecommons

6 years, 11 months

[lime-users] sdk git

by bruno vianna

hey, i just used the sdk cooker for the first time- it's brilliant. i created 6 new files in the fumaçaonline cmmunity (spelled fuma-aonline). Can you merge the to the repository the so I can try compiling? thanks bruno -- bruno(a)pobox.com ▀─█▄██▄▀▄ http://brunovianna.net ─█▄██▄▀█▀█▄ skype: randomico▀─█▄██▄▀█▀█▄▌██─█▌█▌

6 years, 11 months

[lime-users] back to vpn

by bruno vianna

so, as i had mentioned to nicolas some time ago, i'd like to encrypt and tunnel the whole traffic of a local network and would like to try do it in a raspi. i actually tried this configuration and it works really well. i made a post in portuguese [1], based on this [2]. all traffic routed to the raspi is sent over to a openvpn server. i actually changed the dhcp server on a openwrt router to give out the raspi address as gateway to all clients in the network, making the whole thing transparent to the users. now the question is, of course, how to get this working in libre-mesh? simply changing the /etc/config/dhcp didn't work, since alfred seems to be the one filling dhcp requests. also, there seems to be two approaches: this first one would be to change the gateway in the clients when they receive the dhcp lease. the other would be to keep the localnode gateways (x.x.0.1) and route the traffic from them to the raspi. then there is also the issue of having more than one exits to the internet. right now the raspi is hardwired to the actual exit gateway (outside libre-mesh). but it could be automagically updated to use the best exit. it also nice to have the raspi physically close to the exit, so that that less internal bandwidth is wasted. any thoughts? thanks! bruno [1]http://www.brunovianna.net/documenta/?p=93 [2]https://gist.github.com/superjamie/ac55b6d2c080582a3e64 -- bruno(a)pobox.com ▀─█▄██▄▀▄ http://brunovianna.net ─█▄██▄▀█▀█▄ skype: randomico▀─█▄██▄▀█▀█▄▌██─█▌█▌

6 years, 11 months

[lime-users] setting one mesh device as gateway? (and nanostation M2 update)

by James Lewis

Hi all, Thanks for previous help getting nanostation M2 working. It worked great downgrading first to AirOS 5.5.11 then installing the nano factory firmware. I have two M2's, and they have automatically meshed and we can connect two devices to their ethernet ports, the devices both get IP address and we can ping between the connected devices! All good! (Except there is no gateway IP issued - is that expected?) Now the quesiton is: how do we set one of the mesh devices to _take_ DHCP through the LAN port rather than give it, and to be the 'gateway' device on the mesh network, and then what will happen with devices that subsequently connect to the mesh? How will they get their gateway set? Thanks for help! Sorry if this is a bit of a newb question, it's not immediately clear from the configuration docs, any rtfm answer pointing to speciifc documentation also appreciated. James

6 years, 11 months

Re: [lime-users] 802.11s config

by Ruairi Hickey

Hi, I downloaded the patch from Daniel below and applied to the latest lime-build tree however when I build this with a make v=S T=ar71xx-mini P=basic the images dont include a specific image for the tlink tl-wr841n - is there a specific image I should use instead ? Thanks, Ruairi On Tuesday 9 May 2017 16:41:29 IST Daniel Golle wrote: > Hi Pau, > > sorry for the late reply. See my comment below. > > On Fri, May 05, 2017 at 03:21:36PM +0200, Pau wrote: > > Hi Again. > > > > I've been testing 802.11s support on LibreMesh develop branch. These are > > the conclusions: > > > > 1) I fixed a bug related to the network configuration: > > > > https://github.com/libremesh/lime-packages/commit/3163e6ed15079e2c760824c6 > > d1f81837345e2093 > > > > This is already comited and soon the binaries available on > > http://repo.libremesh.org will have this patch applied (the compilation > > process is already running). > > > > 2) Good news are that I managed to create a mesh network using 802.11s. > > In addition to `mode ieee80211s` also `proto ieee80211s` must be enabled > > in the configuration file. > > > > This is my /etc/config/lime > > > > config lime network > > > > list protocols ieee80211s > > list protocols lan > > list protocols anygw > > list protocols batadv:%N1 > > list protocols bmx6:13 > > > > config lime wifi > > > > list modes ieee80211s > > > > Then run: lime-config && lime-apply > > > > This configuration works for me and the two routers are connected. > > > > 3) Bad news is that, for some point I don't understand, if "AP" is > > enabled in addition to 80211s, the mesh point is not enabled and it does > > not work. > > > > So the right configuration (to mesh and AP at same time) would be: > > > > config lime wifi > > > > list modes ieee80211s > > list modes ap > > list modes apname > > > > But it does not work. > > > > According to "iw list" information, Mesh point + AP is possible, but I > > think there is something wrong on LEDE. So I'll investigate a bit more > > and talk with LEDE developers if it is an actual LEDE bug. > > > > PS: add Daniel as CC, maybe he can add some extra information for the > > resolution of this problem. > > I've been in touch with neoraider and he made a fix for this: > https://git.lede-project.org/?p=lede/neoraider/staging.git;a=commit;h=6db7dc > d74aaf23865ff19b515daf8c534414adaf > > I also updated the ticket on github, just in case you missed that. > > > Cheers > > > Daniel > > > On 20/04/17 20:04, Ruairi Hickey wrote: > > > On Thursday 20 April 2017 11:34:09 IST you wrote: > > >> On 19/04/17 20:46, Ruairi Hickey wrote: > > >>> On Wednesday 19 April 2017 19:29:59 IST Ilario Gelmetti wrote: > > >>>> On 04/19/2017 05:25 PM, Ruairi Hickey wrote: > > >>>>> While the mesh appears to be up and the stations can see each other > > >>>>> there is no ip connectivity - if a client is connected to the > > >>>>> libremesh.org > > >>>>> via AP node d9:18:6e it can not connect to the internet / outside > > >>>>> via AP > > >>>>> d9:44:80. > > >>>> > > >>>> Hi Ruairi! > > >>>> Have you plugged an internet connection to a WAN port of your router? > > >>>> If your router doesn't have a WAN port you will have to configure > > >>>> another one as WAN (check out /etc/config/lime-example and > > >>>> http://libremesh.org/docs/changing_network_behavior.html ). > > >>>> If this doesn't work: can you post the content of /etc/config/network > > >>>> on > > >>>> your LibreMesh router? > > >>>> And the output of the "ip address show" commend. > > >>>> > > >>>>> Are there additional steps required to enable this (it works > > >>>>> out of the box on ad- hoc) ? > > >>>> > > >>>> No, it should automagically work when you plug the WAN port of the > > >>>> LiMe > > >>>> router into a LAN port of a router offering a DHCP server and a

6 years, 11 months

Re: [lime-users] VPN

by Marvin Arnold

Hey Nicolas, I tried sending you this email directly, but it bounced back. I can't tell if your domain thinks mine is spam, or vice-versa. My speed test results are below and might be interesting to others anyways. Thanks, Marvin On 04/12/2017 12:10 AM, Marvin Arnold wrote: > > Hey, just did some thorough tests. There's a huge drop in download > speed starting at the hex. Upload speed is almost constant. > > https://nolime.sandcats.io/shared/Q2guq9wOIl-l0Yt4Dou-nkqfR_kNqH1wf4DIwHg9Z… > > The tests also made me realize something weird is going on where I'm > unable to connect directly to the lime node which is also the only > node with internet access. I have to restart the router whenever I > re-enter the network. > > > On 04/10/2017 04:54 AM, Nicolas North wrote: >> Awesome very happy to hear that. Can I ask you out of curiosity what >> speed: >> >> 1] your pure ISP connection is >> 2] your vpn is delivering >> 3] you get from a device connected to a non-exit node [so not the one >> connected to the hex]? >> >> I’m having real problems getting steady speeds out of LiMe in >> general, and really high latencies, compared to OLSR which always >> delivers, although not very fast. >> >> Thank you >> >> >> From: Marvin Arnold via lime-users <lime-users(a)lists.libremesh.org> >> <mailto:lime-users@lists.libremesh.org> >> Reply: Marvin Arnold <marvin(a)geeky.rocks> >> <mailto:marvin@geeky.rocks>, libremesh users >> <lime-users(a)lists.libremesh.org> <mailto:lime-users@lists.libremesh.org> >> Date: 8 aprile 2017 at 03:26:52 >> To: lime-users(a)lists.libremesh.org <lime-users(a)lists.libremesh.org> >> <mailto:lime-users@lists.libremesh.org> >> Subject: Re: [lime-users] VPN >> >>> 1 alone didn't fix it. 1+2 did. Switching MTU from 1280 to 1350 >>> immediately resolved the issue. >>> >>> So I think it's all set now. I have three lime nodes forming a mesh >>> around my house. One of the lime nodes is connected over ethernet to >>> the hex. >>> >>> I'll report back any issues and successes. Now that this is working, >>> we'll start setting up more clusters, all using the same exit node. >>> I suppose we'll eventually want to figure out how to connect using a >>> lime node only without a hex. I don't think it will be cost >>> effective to have a hex at every node that connects to the Internet. >>> We almost had that working before. >>> >>> >>> On 04/06/2017 09:54 PM, Nk wrote: >>>> Ok so I think it’s one of two problems if not both here: >>>> >>>> 1] DNS >>>> 2] MTU >>>> >>>> In the first case, which seems more likely, your Hex isn’t >>>> providing DNS correctly. See the last part of this video and follow >>>> just the DNS settings >>>> part: https://www.youtube.com/watch?v=SW6AZ33go5U [this is the >>>> video I followed for my howto in the first place with the exception >>>> of a few things such as L2TP instead of PPTP of course. >>>> >>>> In the second case, your MTU might be wrong. Have you followed the >>>> MTU section of my video? If not [*likely you made the right choice >>>> as mine was a simple empirical one-time experience*] why not? Have >>>> you set it to 1350 or have you left it default? See this link for a >>>> packet fragmentation ping test >>>> guide: http://www.tp-link.com/us/FAQ-190.html. >>>> >>>> Let me know how it works out >>>> >>>> On 7 apr 2017, 02:56 +0200, Marvin Arnold <marvin(a)geeky.rocks>, wrote: >>>>> >>>>> That's weird. Sending that last email worked even though I am >>>>> still connected via ethernet. Websites still won't load. >>>>> >>>>> >>>>> On 04/06/2017 07:43 PM, Marvin Arnold wrote: >>>>>> >>>>>> Hey there, really appreciate the help. Responses below. >>>>>> >>>>>> >>>>>> On 04/06/2017 07:26 PM, Nk wrote: >>>>>>> How are you connecting via wifi to the hex? You have a simple >>>>>>> access point connected on the lan side of the hex that does no >>>>>>> routing at all, I assume, is this correct? >>>>>> - ISP Router: out the first internet port <ethernet> hex: into >>>>>> internet/first port >>>>>> - hex: out the second port <ethernet> LiMe wdr4300: into internet >>>>>> port >>>>>> - hex: out the fourth port <ethernet> into computer >>>>>>> >>>>>>> In any event, it looks like your computer is hard-set [meaning >>>>>>> in system options or via ifconfig/ipconfig] to use itself as the >>>>>>> DNS server [strange config btw, is this a server?] when using >>>>>>> the wifi interface [127.0.0.1] whereas it’s not hard-set to a >>>>>>> specific DNS server when using the wired interface. >>>>>> >>>>>> Its Ubuntu 16.04 x64. I use a lot of virtualization (virtualbox, >>>>>> lxc) so the bare-metal I'm running from should be fairly close to >>>>>> a stock ubuntu install. >>>>>> >>>>>>> >>>>>>> Is your computer getting an IP automatically from the HEX when >>>>>>> connecting to it via ethernet? Could you post the result of >>>>>>> command *ifconfig* >>>>>> enp0s31f6 Link encap:Ethernet HWaddr xx:xx:xx:xx >>>>>> inet addr:172.16.0.252 Bcast:172.31.255.255 >>>>>> Mask:255.240.0.0 >>>>>> inet6 addr: fe80::6e3d:818b:4805:dee0/64 Scope:Link >>>>>> UP BROADCAST RUNNING MULTICAST MTU:1350 Metric:1 >>>>>> RX packets:92402 errors:0 dropped:668 overruns:0 frame:0 >>>>>> TX packets:93032 errors:0 dropped:0 overruns:0 carrier:0 >>>>>> collisions:0 txqueuelen:1000 >>>>>> RX bytes:64456103 (64.4 MB) TX bytes:22227903 (22.2 MB) >>>>>> Interrupt:16 Memory:c5700000-c5720000 >>>>>> >>>>>> lo Link encap:Local Loopback >>>>>> inet addr:127.0.0.1 Mask:255.0.0.0 >>>>>> inet6 addr: ::1/128 Scope:Host >>>>>> UP LOOPBACK RUNNING MTU:65536 Metric:1 >>>>>> RX packets:155595 errors:0 dropped:0 overruns:0 frame:0 >>>>>> TX packets:155595 errors:0 dropped:0 overruns:0 carrier:0 >>>>>> collisions:0 txqueuelen:1 >>>>>> RX bytes:34758916 (34.7 MB) TX bytes:34758916 (34.7 MB) >>>>>> >>>>>>> Secondly, could you try [always via ethernet] to *nslookup >>>>>>> wikipedia.org 172.16.0.1* >>>>>> $ nslookup wikipedia.org 172.16.0.1 >>>>>> Server: 172.16.0.1 >>>>>> Address: 172.16.0.1#53 >>>>>> >>>>>> ** server can't find wikipedia.org: SERVFAIL >>>>>> >>>>>>> and *nslookup wikipedia.org 8.8.8.8* ? >>>>>> Server: 8.8.8.8 >>>>>> Address: 8.8.8.8#53 >>>>>> >>>>>> Non-authoritative answer: >>>>>> Name: wikipedia.org >>>>>> Address: 198.35.26.96 >>>>>> >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> On 7 apr 2017, 01:43 +0200, Marvin Arnold <marvin(a)geeky.rocks>, >>>>>>> wrote: >>>>>>>> >>>>>>>> Hey, I'm replying with two sets of commands. The first is >>>>>>>> always using WIFI which is working fine. The second is >>>>>>>> connecting my computer to the hex via ethernet, which does not >>>>>>>> work well. >>>>>>>> >>>>>>>> I'm pretty sure its not my computer's ethernet. I've also tried >>>>>>>> connecting my computer directly into the isp router via >>>>>>>> ethernet and that works fine. >>>>>>>> >>>>>>>> Working version using hex<WIFI>computer: >>>>>>>> >>>>>>>>> *ping 8.8.8.8* [reply with output] >>>>>>>> $ ping 8.8.8.8 >>>>>>>> PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. >>>>>>>> 64 bytes from 8.8.8.8: icmp_seq=1 ttl=43 time=63.6 ms >>>>>>>> >>>>>>>>> *curl ipinfo.io* [reply with output] >>>>>>>> $ curl ipinfo.io >>>>>>>> { >>>>>>>> "ip": "X.X.X.X", >>>>>>>> "hostname": "XX.net", >>>>>>>> "city": "Washington", >>>>>>>> "region": "District of Columbia", >>>>>>>> "country": "US", >>>>>>>> "loc": "LAT,LONG", >>>>>>>> "org": "ORG", >>>>>>>> "postal": "XXXXX" >>>>>>>> } >>>>>>>> >>>>>>>>> *nslookup wikipedia.org* [reply with output] >>>>>>>> >>>>>>>> $ nslookup wikipedia.org >>>>>>>> Server: 127.0.1.1 >>>>>>>> Address: 127.0.1.1#53 >>>>>>>> >>>>>>>> Non-authoritative answer: >>>>>>>> Name: wikipedia.org >>>>>>>> >>>>>>>> ---------------------------- KEEP SCROLLING >>>>>>>> ------------------------------------ >>>>>>>> >>>>>>>> Broken version using hex<ethernet>: >>>>>>>> >>>>>>>>> *ping 8.8.8.8* [reply with output] >>>>>>>> $ ping 8.8.8.8 >>>>>>>> PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. >>>>>>>> 64 bytes from 8.8.8.8: icmp_seq=1 ttl=44 time=64.2 ms >>>>>>>> >>>>>>>>> *curl ipinfo.io* [reply with output] >>>>>>>> $ curl ipinfo.io >>>>>>>> curl: (6) Could not resolve host: ipinfo.io >>>>>>>> >>>>>>>> >>>>>>>>> *nslookup wikipedia.org* [reply with output] >>>>>>>> >>>>>>>> $ nslookup wikipedia.org >>>>>>>> ;; connection timed out; no servers could be reached >>>>>>>> >>>>>>>> Non-authoritative answer: >>>>>>>> Name: wikipedia.org >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>> >>>> >>>> _______________________________________________ >>>> 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 >

6 years, 11 months

[lime-users] Throttling bandwidth

by Marvin Arnold

What's the best way for nodes giving Internet access to control how much bandwidth they will share? Preferably depending on the day of the week and time? We found nodogsplash but the lime fork doesn't seem to be maintained. https://github.com/libremesh/openwrt-routing-packages/tree/master/nodogspla…

6 years, 11 months

[lime-users] Fwd: openwrt and lede - remerge proposal

by Ilario Gelmetti

YAY! Follow full discussion on this thread: http://lists.infradead.org/pipermail/lede-dev/2017-May/007336.html -------- Forwarded Message -------- Subject: [LEDE-DEV] openwrt and lede - remerge proposal Date: Mon, 8 May 2017 15:19:40 +0200 From: John Crispin <john(a)phrozen.org> To: openwrt-devel(a)lists.openwrt.org, LEDE Development List <lede-dev(a)lists.infradead.org>, LEDE Project Administration <lede-adm(a)lists.infradead.org>, OpenWrt Internal Developer List <openwrt-hackers(a)lists.openwrt.org> Hi, Felix, Imre and myself had 2 calls last week lasting several hours and discussed the following proposal of conditions for a remerge that we would like to propose and have people vote on. *) branding - the owrt side sees no option of using the lede brand - a (minor) majority voted for openwrt as a name over lede whilst most people said they did not care - as the last vote had a 100% ACK for a remerge using the owrt brand is the only feasible option *) domain - transfer owner ship to SPI for openwrt.org and lede-project.org - add them to the pool of urls at digital ocean - post remerge build a setup where we have several DNS servers in various locations - point git.openwrt.org at the lede git server - point bugs.openwrt.org to the lede flyspray instance - keep both wikis and forums as is (we should decide post remerge how to proceed to avoid these issues blocking the progress) - update the lede domain entries for build/download/rsync/... servers so that the openwrt domain also points at them *) SPI - TBD post remerge *) github - stop pushing to lede-project organisation - start pushing to the openwrt organisation - cleanup the list of owners in the openwrt organisation - obsolete all issues on the openwrt organisation and close the issue tracker - go through the open openwrt and lede PRs, pickup whats useful and close the rest, asking people to repost (things wont be rebasable anyhow) - close the lede PR tracker - keep the lede organisation in its current state so that forked trees dont get obsoleted - obsolete the lede github org after a grace period of 3-6 months *) landing page - update the lede landing page to represent the openwrt name - update the landing page to have the same look & feel as the current openwrt landing page - point openwrt.org at the lede landing page *) trac - trac is already readonly, keep content so that search engines can still find the it - edit the trac html templates, adding a note pointing at the bug.openwrt.org instance *) email accounts - currently there are around ~20 active openwrt.org mail accounts - turn all the webmaster@, hostmaster@, ... accounts into aliases that anyone with voting rights can be subscribed to - ask those people that are no longer active to voluntarily give up their accounts - mail addresses may under no conditions be used for any personal business, consultancy, applying for jobs, ... purposes - any mail sent from an openwrt.org account needs to adhere the trademark policy and should only be used for FOSS purposes *) wiki / forum - TBD - asking in either forum/wiki will get a biased vote so keep them both around - start a separate discussion regarding these post remerge *) LF - find out what doubts folks have about LF - find out benefits - we would have their hosting and sponsorship ?! - start a separate discussion regarding these post remerge *) git trees - rebrand the lede tree to openwrt - work out what has happened inside the openwrt tree since the reboot and pick up the useful bits (zoltan has done some prior work on this already) *) mailing list - ask david to add the openwrt-adm and openwrt lists - announce the switch to the infradead serves, asking people to unsubscribe if they have privacy issues with this - import the user DB from the current openwrt and lede ML into the 2 new mailing lists - find out if we can redirect/auto-reply the existing lists to the new ones *) trademark/sponsorship policy - review/ack imres trademark policy - review/ack jows sponsorship policy *) timeline - refine / vote / agree on the proposal withing the next 2 week - work on the action items in the 4 weeks after that John _______________________________________________ Lede-dev mailing list Lede-dev(a)lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev

6 years, 11 months

[lime-users] network-profiles write access

by Nk

Hi p4u and all I’ve just come across https://github.com/libremesh/lime-sdk thanks to Marvin and I think this is exactly what we need to generate images for routers not available in Chef. I’d like to request write access to https://github.com/libremesh/network-profiles in order to create our community as specified here: https://github.com/libremesh/lime-sdk#communities. If anyone could enlighten us as to how to transition from our Chef custom configs to this, that would be amazing. Thank you so much in advance Nk

6 years, 11 months

[lime-users] Fwd: Re: 802.11s config

by Ruairi Hickey

---------- Forwarded Message ---------- Subject: Re: [lime-users] 802.11s config Date: Tuesday 2 May 2017, 21:48:57 IST From: Ruairi Hickey <ruairi.hickey-mesh(a)collon.ie> To: lime-users(a)lists.libremesh.org On Wednesday 26 April 2017 12:47:04 IST you wrote: > I'll try to setup a testbed for testing 802.11s at my place and let you > know the results. > > In any case, it would be better if you can use the last pre-release for > libremesh: http://repo.libremesh.org/lime-17.04 > > Cheers. > > On 20/04/17 20:04, Ruairi Hickey wrote: > > On Thursday 20 April 2017 11:34:09 IST you wrote: > >> On 19/04/17 20:46, Ruairi Hickey wrote: > >>> On Wednesday 19 April 2017 19:29:59 IST Ilario Gelmetti wrote: > >>>> On 04/19/2017 05:25 PM, Ruairi Hickey wrote: > >>>>> While the mesh appears to be up and the stations can see each other > >>>>> there is no ip connectivity - if a client is connected to the > >>>>> libremesh.org > >>>>> via AP node d9:18:6e it can not connect to the internet / outside via > >>>>> AP > >>>>> d9:44:80. > >>>> > >>>> Hi Ruairi! > >>>> Have you plugged an internet connection to a WAN port of your router? > >>>> If your router doesn't have a WAN port you will have to configure > >>>> another one as WAN (check out /etc/config/lime-example and > >>>> http://libremesh.org/docs/changing_network_behavior.html ). > >>>> If this doesn't work: can you post the content of /etc/config/network > >>>> on > >>>> your LibreMesh router? > >>>> And the output of the "ip address show" commend. > >>>> > >>>>> Are there additional steps required to enable this (it works > >>>>> out of the box on ad- hoc) ? > >>>> > >>>> No, it should automagically work when you plug the WAN port of the LiMe > >>>> router into a LAN port of a router offering a DHCP server and a gateway > >>>> to the internet. > >>>> Let us know! > >>>> Ilario > >>> > >>> Hi Ilario, > >>> > >>> The WAN port is connected to the switch and if that is the only > >>> router in > >>> > >>> up / or if I connect to that when connecting to SSID libremesh.org I can > >>> connect to the internet. > >>> > >>> If I connect to either of the other 2 nodes I cannot connect to the > >>> > >>> Internet... > >> > >> The link layer seems to work fine in your setup, so the problem is > >> proably in the mac or ip layer. Please, run the next test and attach the > >> output: > >> > >> Run "bmx6 -c originators" to see all nodes in the network. > >> > >> Run "bmx6 -c links" to see the one-hop nodes > >> > >> Run "batctl o" to see the layer2 nodes > >> > >> Run "bmx6 -cp" on the node with Internet connection to see if the tunIn > >> for sharing Internet is enabled (inet4). > >> > >> Cheers. > >> > >>> I've attached 2 text files (one for each router with the file contents) > >>> router connected to switch (WAN port) / Internet > >>> router-d94040.txt > >>> > >>> router in mesh > >>> router-d94480.txt > >>> > >>> Thanks, > >>> > >>> Ruairi > >>> > >>> (if the attachments get stripped I'll resend with the contents inline..) > >>> > >>> > >>> > >>> _______________________________________________ > >>> lime-users mailing list > >>> lime-users(a)lists.libremesh.org > >>> https://lists.libremesh.org/mailman/listinfo/lime-users > > > > Hi, > > > > If it would be of assistance I can give you ssh access to the router > > ... I > > > > have it behind a static IP, just need to open up the firewall. > > > > Ruairi Hi, Apologies, I missed one of your emails last week ... thought it was a duplicate send....I will run the bmx6 commands etc when the I manage to resolve the issue below.... I have installed the image from 26.04 on the routers last night but there is an error bringing up the wlan0-mesh interface Thu Apr 27 13:54:26 2017 kern.info kernel: [ 20.659483] IPv6: ADDRCONF(NETDEV_UP): wlan0-mesh: link is not ready Thu Apr 27 13:54:26 2017 daemon.notice netifd: radio0 (913): command failed: Resource busy (-16) Thu Apr 27 13:54:26 2017 daemon.notice netifd: radio0 (913): command failed: Link has been severed (-67) Thanks, Ruairi -----------------------------------------

6 years, 11 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

lime May 2017