Good meshing,
Please do not feel pushed, I am just happily asking things here.
Is there any estimate on when there will be an official captive portal
solution?
In the meantime, is there anything that more or less works with Libremesh?
Sorry to come back again with this topic, we had many emails around
saying different things and I got confused.
Cheers
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
We're going to write on the web a list of tested routers, just for
helping the visitors to have an idea of the supported/recommended
routers without copying and pasting the whole list provided by
OpenWrt/LEDE.
The discussion on this is here:
https://github.com/libremesh/lime-web/pull/14
Please answer with the routers you tried with LibreMesh.
I played with:
TP-Link WDR3600
TP-Link WR1043ND-v1
Ubiquiti NanoBridge M5
Ubiquiti NanoStation M5 XM
Ubiquiti NanoStation LoCo M2
Hi Leonardo
This is to protect those who share their Internet connection with the mesh network from being responsible for other people's traffic. Streisand is amazing and the VPSs available on arubacloud.com only cost 1€ a month, the lowest price we have ever found, with the benefit of being close to us [they're located in Arezzo and we're in Milano] for very low latency and they have of course an IP recognized as Italian in all of the geoIP databases, so that users don't notice any difference when navigating to websites like Google that trace your ip location and adapt the language of their website.
Im getting speeds between 100 and 120mbps down with l2tp+ipsec on my Hex and that makes for a very good amount of bandwidth to be shared with the network.
Nicolas
Sent from Nine
________________________________
From: Leonardo Taborda <leonardotaborda(a)networkbogota.org>
Sent: Feb 16, 2017 23:46
To: lime-users(a)lists.libremesh.org
Subject: Re: [lime-users] VPN
>
> Hello Nicolas and Marvin
>
> This is really interesting, I had no idea about streisand. If you guys
> are setting up this in a mesh network, is it for browsing safely or
> taking advantage of the ease of setting up vpns?
>
> El 16/02/17 a las 10:00, Nicolas North escribió:
> > Hi again!
> >
> > I’m glad you received it this time and are testing it out.
> >
> > I definitely have no windows machines either ;]
> >
> > And actually you don’t need any configuration files for streisand.
> > Once you’ve set up your instance just navigate to your server’s web
> > address and log in with the provided credentials. Then when you see
> > this screen:
> >
> >
> > Select L2TP/IPsec. Then on the next screen press linux, and copy the
> > credentials you find there in the Hex admin page’s configuration in
> > the appropriate fields.
> >
> > That will get you up and running in no time. Remember to select max
> > MTU and RMU to 1280 if you’re getting fragmented packets [I for
> > instance could not access http://speedtest.net before I corrected
> > these values, exactly because of packet fragmentation].
> >
> > Let me know if you need any further help!
> >
> >
> > Nicolas
> >
> >
> > From: Marvin Arnold <marvin(a)unplugged.im> <mailto:marvin@unplugged.im>
> > Reply: libremesh users <lime-users(a)lists.libremesh.org>
> > <mailto:lime-users@lists.libremesh.org>
> > Date: 16 February 2017 at 15:49:26
> > To: lime-users(a)lists.libremesh.org <lime-users(a)lists.libremesh.org>
> > <mailto:lime-users@lists.libremesh.org>
> > Subject: Re: [lime-users] VPN
> >
> >> Thanks for resharing Nicolas, the original never did find my mailbox.
> >>
> >> We tried configuring this setup but hit a wall because we don't have
> >> windows machines. Is there no easy way to take the configuration
> >> files Streisand spits out and upload them directly to the hex?
> >> Alternatively, we're not sure what which settings to copy over from
> >> that file and put into the hex.
> >>
> >>
> >> On 02/15/2017 02:27 AM, Nicolas North wrote:
> >>> Hi Marvin
> >>>
> >>> I’m sorry but I’m having some serious spam issues since i’ve
> >>> migrated my mailserver.
> >>>
> >>> Here is the mail i had sent you. Hope you receive it!
> >>>
> >>> ––––––––––––––––
> >>>
> >>> Hi Marvin
> >>>
> >>> Sorry for the late reply.
> >>>
> >>> We’re using Hexes as vpn-only devices, with the following setup:
> >>>
> >>> ||| ISP Router ||| <=> ||| Hex VPN Router ||| <=> ||| LiMe Router |||
> >>> |
> >>> wifi adhoc
> >>> |
> >>> [other LiMe routers]
> >>>
> >>> This is the guide we’ve been following
> >>> [https://matthewmcclatchey.com/using-private-internet-accesss-vpn-with-mikro…],
> >>> with the exception of the fact that our vpn is lt2p+ipsec, and that
> >>> we’ve had to set max mtu and max mru values to 1280 for some reason
> >>> as packets were getting fragmented with our setup.
> >>>
> >>> If you connect a cable from the ISP’s router’s lan to the Hex’s wan,
> >>> and another cable from the Hex’s lan to the LiMe router’s wan,
> >>> you’ll have all of your internet-bound traffic from inside your mesh
> >>> network sandboxed inside the VPN with no exceptions. The hex has
> >>> some kind of "persistent tunnel” enabled by default, so drops the
> >>> connection if the vpn breaks for some reason, even though it never
> >>> has unless we actually rebooted the remote vpn server for testing
> >>> purposes.
> >>>
> >>> I suggest giving the Hex an address like 172.16.0.1 to avoid
> >>> conflicts with other more common subnets. We set all our ISP routers
> >>> to 192.168.0.1 and LiMe uses 10.13.0.1 etc… so we’re good to go.
> >>> Also, as a bonus, we try to pair all LiMe routers with an openwrt
> >>> “simple AP” router, that takes care of the AP level and lets the
> >>> LiMe router handle only the adhoc meshing level, for maximum
> >>> wireless efficiency.
> >>>
> >>> We give APs static addresses of 10.13.64.1, 2, 3, and so on. They
> >>> must all be different. Try and stay out of the DHCP range which
> >>> starts at 100 I think. This last part [the AP addressing] is all
> >>> trial and error and experimental so it might be wrong, but for us it
> >>> works. We still need to figure out how to scale addressing for APs
> >>> so we’re open to suggestions. While we’re at it:
> >>>
> >>> *TLDR question: what static IPv4 address to give a simple AP
> >>> connected to the lan of a LiMe router? Is 10.13.64.1 - 10.13.64.99 a
> >>> good range? How do we scale beyond that since every AP in the entire
> >>> network must have a different IP?*
> >>>
> >>> Let me know how this works for you. To those answering the question:
> >>> thank you in advance.
> >>>
> >>>
> >>> Nicolas
> >>>
> >>>
> >>>
> >>> From: Marvin Arnold <marvin(a)unplugged.im> <mailto:marvin@unplugged.im>
> >>> Reply: Marvin Arnold <marvin(a)unplugged.im> <mailto:marvin@unplugged.im>
> >>> Date: 14 February 2017 at 02:19:38
> >>> To: pau(a)dabax.net <pau(a)dabax.net> <mailto:pau@dabax.net>, nk(a)os.vu
> >>> <nk(a)os.vu> <mailto:nk@os.vu>
> >>> Subject: Re: [lime-users] VPN
> >>>
> >>>> Hi Pau, Nicolas,
> >>>>
> >>>> Maybe I'm losing my head, but I can't find the original email from
> >>>> Nicolas being quoted. It looks like it may be the additional VPN setup
> >>>> tips we are looking for. I've checked my spam and don't see any hidden
> >>>> messages...
> >>>>
> >>>>
> >>>> On 02/13/2017 06:43 PM, Ilario wrote:
> >>>> > Hi Nicolas!
> >>>> > I think I missed some of your emails in Gmail's spam folder...
> >>>> > Answer inline:
> >>>> >
> >>>> > 2017-02-13 1:51 GMT+01:00 Nicolas North <nk(a)os.vu>:
> >>>> >> Also, as a bonus, we try to
> >>>> >> pair all LiMe routers with an openwrt “simple AP” router, that
> >>>> takes care of
> >>>> >> the AP level and lets the LiMe router handle only the adhoc
> >>>> meshing level,
> >>>> >> for maximum wireless efficiency.
> >>>> > That's really wise :)
> >>>> >
> >>>> >> We give APs static addresses of 10.13.64.1, 2, 3, and so on.
> >>>> They must all
> >>>> >> be different. Try and stay out of the DHCP range which starts at
> >>>> 100 I
> >>>> >> think.
> >>>> > A very interesting question. There's no option for DHCP range in
> >>>> > /etc/config/lime* files (and this is ok).
> >>>> > But I supposed that the range was defined in /etc/config/dhcp, which
> >>>> > on LibreMesh is identical than on OpenWrt/LEDE and contains:
> >>>> > # cat /etc/config/dhcp
> >>>> > [...]
> >>>> > config dhcp 'lan'
> >>>> > option interface 'lan'
> >>>> > option start '100'
> >>>> > option limit '150'
> >>>> > option leasetime '1h'
> >>>> >
> >>>> > But trying to ask for a DHCP lease I received an IPv4 out of the
> >>>> > 10.x.x.100-250 range, looking around I found that the DHCP range for
> >>>> > anygw is hardcoded:
> >>>> >
> >>>> https://github.com/libremesh/lime-packages/commit/3a6596d50b3c0446b988f84d3…
> >>>> > resulting in the whole subnet... No good. @devs?
> >>>> >
> >>>> > Anyway, do you need static IP addresses at the AP routers? You could
> >>>> > also let them take the IP from LiMe (and LiMe would take care of
> >>>> > avoiding collisions).
> >>>> >
> >>>> > Additionally, if you let LiMe routers to autoassign their own IPv4,
> >>>> > they will span over the whole subnet, unless you specify a smaller
> >>>> > "subnet" (not a real subnet, just a range) for auto-assignment, as
> >>>> > explained in /etc/config/lime-example in the comment on the
> >>>> > main_ipv4_address option:
> >>>> >
> >>>> https://github.com/libremesh/lime-packages/blob/2ce5ffa96de5b0b5abb507076b0…
> >>>> >
> >>>> > For example:
> >>>> > # cat /etc/config/lime
> >>>> > config lime 'network'
> >>>> > option main_ipv4_address '10.13.128.0/16/17'
> >>>> >
> >>>> > will limit the autoassignment of IPv4 to the second half of the
> >>>> > broadcast domain.
> >>>> > Bye!
> >>>> > Ilario
> >>>> > _______________________________________________
> >>>> > 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
>
> --
> Cordialmente
>
> Leonardo Taborda Ángel
> leonardotaborda(a)networkbogota.org
> www.networkbogota.org
>
> "When there is a will, there is a way"
>
>
>
Dear all,
As a quick introduction, I have been thinking and talking for many years
about the importance of local applications in community networks, in the
academia before and now somewhere in between research and action through
the non-profit organization http://nethood.org/
My current base is in Zurich, Switzerland but I am working on various
projects in my hometown in Athens including the new community network
James Lewis mentioned in a different thread. For this project I mostly
contribute through a nice roof overlooking the Exarcheia neighbourhood
where the network is being deployed, and an empty apartment in the same
building where I host friends, colleagues, activists, and more.
In addition to offering Internet access to the various refugee squats
that exist in the area, the long-term objective is to offer also a
variety of local services and develop a different model for building
community networks in big cities, anchored in different neighbourhoods
and including open physical spaces for discussions, workshops, training,
residencies, etc.
To make the story short, we were thinking with James to organize a
hands-on workshop perhaps after the battle of the mesh, June 12-15?,
providing free accommodation for 7-8 people and possibly more, and a
small real-life testbed (a short camping retreat in a close to Athens
island is also possible :-))
I thought to share this idea first here, before opening it up to the
battle of the mesh, to get a first feedback since it is mostly with
libremesh that we want to experiment.
What do you think?
Would any of you would be interested to visit us in Athens?
(depending on the prices I might be able to cover also the travel
expenses from Vienna for 2-3 people)
Best,
Panos.
Hi Bruno!
Thank you for your feedback! I still recommend l2tp+ipsec as openvpn in our experience had been very slow [down to half the speed of l2tp] on routers.
In terms of implementation, the GL-INET mini routers we've been playing around with [with amazingly good results with pure olsrd and custom configuration in terms of wireless mesh network nodes] have a custom web ui overlayed onto Luci [as they run openwrt from the factory], and they have a drag-and-drop implementation for openvpn, where you drop a config file and it instantly connects to its server. I don't remember what packages they ship with to make this implementation happen, but I'm sure it's easy to get it running with opkg and the command line on any openwrt router.
If you like the idea of sticking with l2tp, there's also another way of doing that on openwrt, but I still would need to research it.
The fact is that to this day we still haven't found an openwrt compatible wired router [no top notch wireless routers to then only use them for vpn - we want to keep the VPN router separate from the mesh router/ap and from the "simple ap" that provides the ap WiFi network layer] that is powerful enough to handle VPNs with decent speeds [the INET 300n version, which isn't very powerful but isn't too bad either for being a mini router, maxed out at 10mbps on openvpn and 15 with l2tp]. Haven't tested this on a tplink but then again, no need for WiFi on a VPN only router.
If you're able to find a router with such specifications [look for high processing power of course] I'll be happy to buy one to test both openvpn and l2tp onto it.
________________________________
From: bruno vianna <bruno(a)pobox.com>
Sent: Mar 30, 2017 6:22 PM
To: libremesh users
Subject: Re: [lime-users] VPN
>
> nicely done!
>
> nicolas, in the video you recommend lt2p+ipsec for routerOS.
> what would be the recommendation for lede/openwrt/libremesh?
>
> i'm very interested in vpn not only for the security for our networks,
> but also to able to be in the same subnetwork and do some remote
> maintanance.
>
> thanks
> bruno
>
> On Thu, Mar 30, 2017 at 11:45 AM, Nicolas North <nk(a)os.vu> wrote:
> > Yeah sorry I had to re-upload it as it had gotten stuck. Now it’s ready. The
> > url is still the same. Keep in touch!
> >
> >
> > From: Marvin Arnold <marvin(a)geeky.rocks>
> > Reply: libremesh users <lime-users(a)lists.libremesh.org>
> > Date: 30 marzo 2017 at 16:29:51
> > To: libremesh users <lime-users(a)lists.libremesh.org>
> > Subject: Re: [lime-users] VPN
> >
> > Hey Nicolas, great news. But as of now, the video is private. Maybe that
> > will change once its done processing?
> >
> >
> > On 03/30/2017 08:52 AM, Nicolas North wrote:
> >
> > Hi again Marvin
> >
> > I’ve finally been able to do the howto screencast! Here is the link:
> > https://www.youtube.com/watch?v=faGi4mFvcqo [still processing as of right
> > now]
> >
> > It’s my first screencast ever so I hope it makes sense ;]
> >
> > I’ll also make a shorter version for faster setup in the next few days.
> >
> > Let me know if you’re able to get everything up and running.
> >
> >
> > Nk
> >
> >
> > From: Marvin Arnold <marvin(a)geeky.rocks>
> > Reply: libremesh users <lime-users(a)lists.libremesh.org>
> > Date: 24 marzo 2017 at 00:54:20
> > To: libremesh users <lime-users(a)lists.libremesh.org>
> > Subject: Re: [lime-users] VPN
> >
> > Hey Nicolas, ever make any progress on this? I've been dormant but ready to
> > start back up, given a little instruction.
> >
> >
> > On 03/08/2017 04:52 AM, Nk wrote:
> >
> > Hi Marvin
> >
> > Sorry for the late reply
> >
> > I think we’ve solved our spam issues so I hope this mail reaches you
> > correctly now.
> >
> > I have actually just purchased two new hex routers for our network and I’ll
> > set them up tonight or tomorrow night. I’ll document the process as I’m
> > doing it and send you a link to it.
> >
> > Hope we’re still in time ;]
> >
> > On 22 Feb 2017, 04:36 +0100, Marvin Arnold <marvin(a)unplugged.im>, wrote:
> >
> > We have successfully setup the hex to connect to our streisand. But my IP
> > address is still the local one and not the VPN. How do we route the traffic
> > correctly? It didn't automagically work by just plugging it up like you
> > said.
> >
> >
> > On 02/17/2017 10:07 AM, Leonardo Taborda wrote:
> >
> > thanks Nicolas. Now it is more clear.
> > El 17/02/17 a las 04:14, nk(a)os.vu escribió:
> >
> > Hi Leonardo
> >
> > This is to protect those who share their Internet connection with the mesh
> > network from being responsible for other people's traffic. Streisand is
> > amazing and the VPSs available on arubacloud.com only cost 1€ a month, the
> > lowest price we have ever found, with the benefit of being close to us
> > [they're located in Arezzo and we're in Milano] for very low latency and
> > they have of course an IP recognized as Italian in all of the geoIP
> > databases, so that users don't notice any difference when navigating to
> > websites like Google that trace your ip location and adapt the language of
> > their website.
> >
> > Im getting speeds between 100 and 120mbps down with l2tp+ipsec on my Hex and
> > that makes for a very good amount of bandwidth to be shared with the
> > network.
> >
> >
> > Nicolas
> >
> > Sent from Nine
> > ________________________________
> > From: Leonardo Taborda <leonardotaborda(a)networkbogota.org>
> > Sent: Feb 16, 2017 23:46
> > To: lime-users(a)lists.libremesh.org
> > Subject: Re: [lime-users] VPN
> >
> > Hello Nicolas and Marvin
> >
> > This is really interesting, I had no idea about streisand. If you guys
> > are setting up this in a mesh network, is it for browsing safely or
> > taking advantage of the ease of setting up vpns?
> >
> > El 16/02/17 a las 10:00, Nicolas North escribió:
> >
> > Hi again!
> >
> > I’m glad you received it this time and are testing it out.
> >
> > I definitely have no windows machines either ;]
> >
> > And actually you don’t need any configuration files for streisand.
> > Once you’ve set up your instance just navigate to your server’s web
> > address and log in with the provided credentials. Then when you see
> > this screen:
> >
> >
> > Select L2TP/IPsec. Then on the next screen press linux, and copy the
> > credentials you find there in the Hex admin page’s configuration in
> > the appropriate fields.
> >
> > That will get you up and running in no time. Remember to select max
> > MTU and RMU to 1280 if you’re getting fragmented packets [I for
> > instance could not access http://speedtest.net before I corrected
> > these values, exactly because of packet fragmentation].
> >
> > Let me know if you need any further help!
> >
> >
> > Nicolas
> >
> >
> > From: Marvin Arnold <marvin(a)unplugged.im> <mailto:marvin@unplugged.im>
> > Reply: libremesh users <lime-users(a)lists.libremesh.org>
> > <mailto:lime-users@lists.libremesh.org>
> > Date: 16 February 2017 at 15:49:26
> > To: lime-users(a)lists.libremesh.org <lime-users(a)lists.libremesh.org>
> > <mailto:lime-users@lists.libremesh.org>
> > Subject: Re: [lime-users] VPN
> >
> > Thanks for resharing Nicolas, the original never did find my mailbox.
> >
> > We tried configuring this setup but hit a wall because we don't have
> > windows machines. Is there no easy way to take the configuration
> > files Streisand spits out and upload them directly to the hex?
> > Alternatively, we're not sure what which settings to copy over from
> > that file and put into the hex.
> >
> >
> > On 02/15/2017 02:27 AM, Nicolas North wrote:
> >
> > Hi Marvin
> >
> > I’m sorry but I’m having some serious spam issues since i’ve
> > migrated my mailserver.
> >
> > Here is the mail i had sent you. Hope you receive it!
> >
> > ––––––––––––––––
> >
> > Hi Marvin
> >
> > Sorry for the late reply.
> >
> > We’re using Hexes as vpn-only devices, with the following setup:
> >
> > ||| ISP Router ||| <=> ||| Hex VPN Router ||| <=> ||| LiMe Router |||
> > |
> > wifi adhoc
> > |
> > [other LiMe routers]
> >
> > This is the guide we’ve been following
> > [https://matthewmcclatchey.com/using-private-internet-accesss-vpn-with-mikro…],
> > with the exception of the fact that our vpn is lt2p+ipsec, and that
> > we’ve had to set max mtu and max mru values to 1280 for some reason
> > as packets were getting fragmented with our setup.
> >
> > If you connect a cable from the ISP’s router’s lan to the Hex’s wan,
> > and another cable from the Hex’s lan to the LiMe router’s wan,
> > you’ll have all of your internet-bound traffic from inside your mesh
> > network sandboxed inside the VPN with no exceptions. The hex has
> > some kind of "persistent tunnel” enabled by default, so drops the
> > connection if the vpn breaks for some reason, even though it never
> > has unless we actually rebooted the remote vpn server for testing
> > purposes.
> >
> > I suggest giving the Hex an address like 172.16.0.1 to avoid
> > conflicts with other more common subnets. We set all our ISP routers
> > to 192.168.0.1 and LiMe uses 10.13.0.1 etc… so we’re good to go.
> > Also, as a bonus, we try to pair all LiMe routers with an openwrt
> > “simple AP” router, that takes care of the AP level and lets the
> > LiMe router handle only the adhoc meshing level, for maximum
> > wireless efficiency.
> >
> > We give APs static addresses of 10.13.64.1, 2, 3, and so on. They
> > must all be different. Try and stay out of the DHCP range which
> > starts at 100 I think. This last part [the AP addressing] is all
> > trial and error and experimental so it might be wrong, but for us it
> > works. We still need to figure out how to scale addressing for APs
> > so we’re open to suggestions. While we’re at it:
> >
> > *TLDR question: what static IPv4 address to give a simple AP
> > connected to the lan of a LiMe router? Is 10.13.64.1 - 10.13.64.99 a
> > good range? How do we scale beyond that since every AP in the entire
> > network must have a different IP?*
> >
> > Let me know how this works for you. To those answering the question:
> > thank you in advance.
> >
> >
> > Nicolas
> >
> >
> >
> > From: Marvin Arnold <marvin(a)unplugged.im> <mailto:marvin@unplugged.im>
> > Reply: Marvin Arnold <marvin(a)unplugged.im> <mailto:marvin@unplugged.im>
> > Date: 14 February 2017 at 02:19:38
> > To: pau(a)dabax.net <pau(a)dabax.net> <mailto:pau@dabax.net>, nk(a)os.vu
> > <nk(a)os.vu> <mailto:nk@os.vu>
> > Subject: Re: [lime-users] VPN
> >
> > Hi Pau, Nicolas,
> >
> > Maybe I'm losing my head, but I can't find the original email from
> > Nicolas being quoted. It looks like it may be the additional VPN setup
> > tips we are looking for. I've checked my spam and don't see any hidden
> > messages...
> >
> >
> > On 02/13/2017 06:43 PM, Ilario wrote:
> >
> > Hi Nicolas!
> > I think I missed some of your emails in Gmail's spam folder...
> > Answer inline:
> >
> > 2017-02-13 1:51 GMT+01:00 Nicolas North <nk(a)os.vu>:
> >
> > Also, as a bonus, we try to
> > pair all LiMe routers with an openwrt “simple AP” router, that
> >
> > takes care of
> >
> > the AP level and lets the LiMe router handle only the adhoc
> >
> > meshing level,
> >
> > for maximum wireless efficiency.
> >
> > That's really wise :)
> >
> > We give APs static addresses of 10.13.64.1, 2, 3, and so on.
> >
> > They must all
> >
> > be different. Try and stay out of the DHCP range which starts at
> >
> > 100 I
> >
> > think.
> >
> > A very interesting question. There's no option for DHCP range in
> > /etc/config/lime* files (and this is ok).
> > But I supposed that the range was defined in /etc/config/dhcp, which
> > on LibreMesh is identical than on OpenWrt/LEDE and contains:
> > # cat /etc/config/dhcp
> > [...]
> > config dhcp 'lan'
> > option interface 'lan'
> > option start '100'
> > option limit '150'
> > option leasetime '1h'
> >
> > But trying to ask for a DHCP lease I received an IPv4 out of the
> > 10.x.x.100-250 range, looking around I found that the DHCP range for
> > anygw is hardcoded:
> >
> > https://github.com/libremesh/lime-packages/commit/3a6596d50b3c0446b988f84d3…
> >
> > resulting in the whole subnet... No good. @devs?
> >
> > Anyway, do you need static IP addresses at the AP routers? You could
> > also let them take the IP from LiMe (and LiMe would take care of
> > avoiding collisions).
> >
> > Additionally, if you let LiMe routers to autoassign their own IPv4,
> > they will span over the whole subnet, unless you specify a smaller
> > "subnet" (not a real subnet, just a range) for auto-assignment, as
> > explained in /etc/config/lime-example in the comment on the
> > main_ipv4_address option:
> >
> > https://github.com/libremesh/lime-packages/blob/2ce5ffa96de5b0b5abb507076b0…
> >
> > For example:
> > # cat /etc/config/lime
> > config lime 'network'
> > option main_ipv4_address '10.13.128.0/16/17'
> >
> > will limit the autoassignment of IPv4 to the second half of the
> > broadcast domain.
> > Bye!
> > Ilario
> > _______________________________________________
> > 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
> >
> > --
> > Cordialmente
> >
> > Leonardo Taborda Ángel
> > leonardotaborda(a)networkbogota.org
> > www.networkbogota.org
> >
> > "When there is a will, there is a way"
> >
> >
> >
> >
> > _______________________________________________
> > lime-users mailing list
> > lime-users(a)lists.libremesh.org
> > https://lists.libremesh.org/mailman/listinfo/lime-users
> >
> >
> > --
> > Cordialmente
> >
> > Leonardo Taborda Ángel
> > leonardotaborda(a)networkbogota.org
> > www.networkbogota.org
> >
> > "When there is a will, there is a way"
> >
> >
> >
> > _______________________________________________
> > 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
> >
> >
> > _______________________________________________
> > lime-users mailing list
> > lime-users(a)lists.libremesh.org
> > https://lists.libremesh.org/mailman/listinfo/lime-users
>
>
>
> --
>
> bruno(a)pobox.com ▀─█▄██▄▀▄
> http://brunovianna.net ─█▄██▄▀█▀█▄
> skype: randomico▀─█▄██▄▀█▀█▄▌██─█▌█▌
> _______________________________________________
> lime-users mailing list
> lime-users(a)lists.libremesh.org
> https://lists.libremesh.org/mailman/listinfo/lime-users
Cool word game with DR, guys.
Dynamic of course is related to the network topology in a mesh network, and Diversity, "also known as space diversity or spatial diversity, is any one of several wireless diversity schemes that uses two or more antennas to improve the quality and reliability of a wireless link".
I too - like Paul - like the continuity of alphabetical names so that's why I'm sticking with DD or RR as an alternative, but otherwise I like all of the options.
________________________________
From: Paul Spooren <spooren(a)informatik.uni-leipzig.de>
Sent: Mar 29, 2017 01:59
To: libremesh users
Subject: Re: [lime-users] Next LibreMesh release coming, looking for the name
>
> I like the aa bb cc scheme more, what comes after DR? ES?
> Still I like RoutingRevolution best as the new LiMe release will totally revolutionize the whole freifunk/mesh ambitions! Or not ;)?
>
> Anyway, it's just a name, I'm fine with Dayboot Rely as well!
>
>
>
> Am 29. März 2017 00:52:55 WESZ schrieb "Nicolás Echániz" <nicoechaniz(a)altermundi.net>:
> >On 03/28/2017 08:39 PM, Pau wrote:
> >>
> >>
> >> On 29/03/17 01:33, Nicolás Echániz wrote:
> >>> On 03/28/2017 08:09 PM, Pau wrote:
> >>>> I blocked the results at exactly 00:00h.
> >>>>
> >>>> This is the last result: https://framadate.org/ZnBehwGF8COhHmCz
> >>>>
> >>>> Are you sure your time zone is correct? It does not look to me...
> >>>>
> >>>> So we have two winners :S Shall we vote again?
> >>>
> >>> I believe there's no problem voting again.
> >>>
> >>> I propose we have a bit more time to vote this time around.
> >>
> >> I don't really know how to understand the "yellow" votes. If we count
> >> them as "yes" the two winners are "Disruptive Development" and
> >"Routing
> >> Revolution" :/
> >>
> >> So it is definitely a disruptive poll... Maybe voting again with the
> >> three "winners" would be the best.
> >
> >
> >OK. The vote is up again here with the 3 options that got more votes:
> >
> >https://framadate.org/rP6puzFOxcJbaV9U
> >
> >
> >Let's vote until March 31 / 23:59 (UTC)
> >
> >
> >I also want to clarify the "Dayboot Rely" option proposed by some here
> >in the Hackaton. It's wordplay with "Daily Reboot"... we are making a
> >bit of fun with the LEDE release name.
> >
> >We thought using one D and one R is a good transition option, and
> >exchanging word segments is a regular practice for us, so... that's the
> >result :)
> >
> >
> >Cheers!
> >Nico
> >
> >PS: if anyone wants to further clarify their proposals, please do so.
>
>
Last weeks a group of us have been working on LibreMesh to deliver what
will be the next release based on LEDE 17.01. For such purpose some of
us have moved to a rural area of Argentina where exist a Community
Network made of 70 nodes (approx). We are testing the new firmware here,
finding and fixing problems which are only observable when there is real
user data. So we expect this new release to be the most stable and
reliable until now.
Probably this week we will publish the first candidate but we are still
missing something important... the name.
Until now we were trying to follow the name rules used by OpenWRT (AA,
BB, CC, ...), so what we had was:
- BigBang
- CommunityChaos
Then this one should be named DD. But as OpenWRT is kind of abandoned
and now we are using LEDE, maybe we should also change the name rules
(¿maybe?). The LEDE release is named "Reboot". So names related with
Reboot or starting with 'R' would be also an option.
In any case we are open to any idea.
Cheers.
--
./p4u
Ok absolutely I agree. Therefore I just voted myself, since noone else in my team has ever had direct contact with you, let alone the fact that I have just arrived, and have contributed in the amount of zero to your project ;]
That said, since I see that - at least a few hours ago, haven't checked since - one of our proposals was surprisingly among the leading ones, I really don't want that to throw off your ideas about this, as even though I strongly believe in community led decisions [I'm working on our new hacker space here in Milano as I mentioned in the past - that should say it all ;] I really believe that you who have been around for a long time if not from the beginning, have put your heart and soul in the project, and generally have lead it up until this time, should have the definitive say in this decision, also since these inside the voting poll are such small numbers collected over such short time that they might not represent the big picture you have in mind. I don't want a random idea we had this morning to change something this meaningful in your project, even if it's just a name, should it somehow be the top voted [not sure why that would happen anyway ;]
For what it's worth, I really like all of the options in any event, so kudos to all of the proponents and their cool names :)
I hope to be able to actually contribute to your project in the near future.
Nk
________________________________
From: Pau <pau(a)dabax.net>
Sent: Mar 28, 2017 16:25
To: lime-users(a)lists.libremesh.org
Subject: Re: [lime-users] Next LibreMesh release coming, looking for the name
>
> I think the idea is to vote those who are somehow involved with the
> project. However not staying in the ML does not mean not to participate,
> so up to you.
>
> Cheers.
>
> On 28/03/17 10:00, Nk wrote:
> > Hi Pau
> >
> > Nice idea. Are votes welcome from outside the ml [and outside my team of course ;] or members only?
> >
> > Thanks!
> >
> > Nk
> >
> > On 27 mar 2017, 23:15 +0200, Pau <pau(a)dabax.net>, wrote:
> >> I've created a poll on framadate to vote for the name.
> >>
> >> https://framadate.org/ZnBehwGF8COhHmCz
> >>
> >> Let's put Wednesday 29th 00:00 UTC as deadline for voting.
> >> New names only accepted until 28th 12:00 UTC.
> >>
> >> My proposal is maximum two votes per person.
> >>
> >> Please use a name which can be recognized as participant of this mailing
> >> list or the IRC freenode channel.
> >>
> >> Cheers.
> >>
> >> On 27/03/17 16:22, Paul Spooren wrote:
> >>> RoutingRevolution
> >>>
> >>>
> >>> Am 27.03.2017 um 15:38 schrieb Nk:
> >>>> Hi all! Awesome news!
> >>>>
> >>>> All of our team has been on a brainstorming loop over this topic this
> >>>> morning as soon as we read the mail and these are the ideas that have
> >>>> been tossed around ;]
> >>>>
> >>>> With a *D*:
> >>>>
> >>>> *Distributed Dawning* [or *Decentralized* as @Amusa suggested] **
> >>>> *Disruptive Development*
> >>>> *Dynamic Diversity*
> >>>>
> >>>> [*Distributed* as the most extreme level as *decentralization*, also a
> >>>> very cool term as @Amusa pointed out]
> >>>> [I love this definition of *Dawning*: To begin to appear or develop;
> >>>> emerge.]
> >>>> [*Diversity*: Using multiple antennae to reduce interference and
> >>>> improve both transmission and reception of signals.]
> >>>>
> >>>> With an *R*:
> >>>>
> >>>> *Recursive Resonance*
> >>>> *Redundant Rebirth*
> >>>> *Resonant Reboot*
> >>>> *
> >>>> *
> >>>> [*Resonance*: Mechanical resonance is the tendency of a mechanical
> >>>> system to respond at greater amplitude when the frequency of its
> >>>> oscillations matches the system's natural frequency of vibration (its
> >>>> resonance frequency or resonant frequency) than it does at other
> >>>> frequencies.]
> >>>>
> >>>> Some are rather self-ironically nerdy of course, but isn’t that the
> >>>> point? ;]
> >>>>
> >>>>
> >>>> On 27 mar 2017, 15:18 +0200, bruno vianna <bruno(a)pobox.com>, wrote:
> >>>>> we have a winner!
> >>>>>
> >>>>> On Mon, Mar 27, 2017 at 9:42 AM, Amuza <amuza(a)riseup.net> wrote:
> >>>>>> DecentralizedDeity
> >>>>>>
> >>>>>>
> >>>>>> On 26/03/17 18:05, Pau wrote:
> >>>>>>
> >>>>>> Last weeks a group of us have been working on LibreMesh to deliver what
> >>>>>> will be the next release based on LEDE 17.01. For such purpose some of
> >>>>>> us have moved to a rural area of Argentina where exist a Community
> >>>>>> Network made of 70 nodes (approx). We are testing the new firmware
> >>>>>> here,
> >>>>>> finding and fixing problems which are only observable when there is
> >>>>>> real
> >>>>>> user data. So we expect this new release to be the most stable and
> >>>>>> reliable until now.
> >>>>>>
> >>>>>> Probably this week we will publish the first candidate but we are still
> >>>>>> missing something important... the name.
> >>>>>>
> >>>>>> Until now we were trying to follow the name rules used by OpenWRT (AA,
> >>>>>> BB, CC, ...), so what we had was:
> >>>>>>
> >>>>>> - BigBang
> >>>>>> - CommunityChaos
> >>>>>>
> >>>>>> Then this one should be named DD. But as OpenWRT is kind of abandoned
> >>>>>> and now we are using LEDE, maybe we should also change the name rules
> >>>>>> (¿maybe?). The LEDE release is named "Reboot". So names related with
> >>>>>> Reboot or starting with 'R' would be also an option.
> >>>>>>
> >>>>>> In any case we are open to any idea.
> >>>>>>
> >>>>>> Cheers.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> 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
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>>
> >>>>> bruno(a)pobox.com ▀─█▄██▄▀▄
> >>>>> http://brunovianna.net ─█▄██▄▀█▀█▄
> >>>>> skype: randomico▀─█▄██▄▀█▀█▄▌██─█▌█▌
> >>>>> _______________________________________________
> >>>>> 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
> >>
> >> --
> >> ./p4u
> >>
> >>
> >> _______________________________________________
> >> 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
> >
>
> --
> ./p4u
>
>
>
Hi Marvin! Sorry about the delay. I've been very busy on other fronts. I'll do the configuration and the HowTo between tomorrow and Sunday. Thanks for holding tight!
Nicolas
________________________________
From: Marvin Arnold <marvin(a)geeky.rocks>
Sent: Mar 24, 2017 12:54 AM
To: libremesh users
Subject: Re: [lime-users] VPN
>
> Hey Nicolas, ever make any progress on this? I've been dormant but ready
> to start back up, given a little instruction.
>
>
> On 03/08/2017 04:52 AM, Nk wrote:
> > Hi Marvin
> >
> > Sorry for the late reply
> >
> > I think we’ve solved our spam issues so I hope this mail reaches you
> > correctly now.
> >
> > I have actually just purchased two new hex routers for our network and
> > I’ll set them up tonight or tomorrow night. I’ll document the process
> > as I’m doing it and send you a link to it.
> >
> > Hope we’re still in time ;]
> >
> > On 22 Feb 2017, 04:36 +0100, Marvin Arnold <marvin(a)unplugged.im>, wrote:
> >>
> >> We have successfully setup the hex to connect to our streisand. But
> >> my IP address is still the local one and not the VPN. How do we route
> >> the traffic correctly? It didn't automagically work by just plugging
> >> it up like you said.
> >>
> >>
> >> On 02/17/2017 10:07 AM, Leonardo Taborda wrote:
> >>> thanks Nicolas. Now it is more clear.
> >>> El 17/02/17 a las 04:14, nk(a)os.vu escribió:
> >>>> Hi Leonardo
> >>>>
> >>>> This is to protect those who share their Internet connection with the mesh network from being responsible for other people's traffic. Streisand is amazing and the VPSs available on arubacloud.com only cost 1€ a month, the lowest price we have ever found, with the benefit of being close to us [they're located in Arezzo and we're in Milano] for very low latency and they have of course an IP recognized as Italian in all of the geoIP databases, so that users don't notice any difference when navigating to websites like Google that trace your ip location and adapt the language of their website.
> >>>>
> >>>> Im getting speeds between 100 and 120mbps down with l2tp+ipsec on my Hex and that makes for a very good amount of bandwidth to be shared with the network.
> >>>>
> >>>>
> >>>> Nicolas
> >>>>
> >>>> Sent from Nine
> >>>> ________________________________
> >>>> From: Leonardo Taborda <leonardotaborda(a)networkbogota.org>
> >>>> Sent: Feb 16, 2017 23:46
> >>>> To: lime-users(a)lists.libremesh.org
> >>>> Subject: Re: [lime-users] VPN
> >>>>
> >>>>> Hello Nicolas and Marvin
> >>>>>
> >>>>> This is really interesting, I had no idea about streisand. If you guys
> >>>>> are setting up this in a mesh network, is it for browsing safely or
> >>>>> taking advantage of the ease of setting up vpns?
> >>>>>
> >>>>> El 16/02/17 a las 10:00, Nicolas North escribió:
> >>>>>> Hi again!
> >>>>>>
> >>>>>> I’m glad you received it this time and are testing it out.
> >>>>>>
> >>>>>> I definitely have no windows machines either ;]
> >>>>>>
> >>>>>> And actually you don’t need any configuration files for streisand.
> >>>>>> Once you’ve set up your instance just navigate to your server’s web
> >>>>>> address and log in with the provided credentials. Then when you see
> >>>>>> this screen:
> >>>>>>
> >>>>>>
> >>>>>> Select L2TP/IPsec. Then on the next screen press linux, and copy the
> >>>>>> credentials you find there in the Hex admin page’s configuration in
> >>>>>> the appropriate fields.
> >>>>>>
> >>>>>> That will get you up and running in no time. Remember to select max
> >>>>>> MTU and RMU to 1280 if you’re getting fragmented packets [I for
> >>>>>> instance could not access http://speedtest.net before I corrected
> >>>>>> these values, exactly because of packet fragmentation].
> >>>>>>
> >>>>>> Let me know if you need any further help!
> >>>>>>
> >>>>>>
> >>>>>> Nicolas
> >>>>>>
> >>>>>>
> >>>>>> From: Marvin Arnold <marvin(a)unplugged.im> <mailto:marvin@unplugged.im>
> >>>>>> Reply: libremesh users <lime-users(a)lists.libremesh.org>
> >>>>>> <mailto:lime-users@lists.libremesh.org>
> >>>>>> Date: 16 February 2017 at 15:49:26
> >>>>>> To: lime-users(a)lists.libremesh.org <lime-users(a)lists.libremesh.org>
> >>>>>> <mailto:lime-users@lists.libremesh.org>
> >>>>>> Subject: Re: [lime-users] VPN
> >>>>>>
> >>>>>>> Thanks for resharing Nicolas, the original never did find my mailbox.
> >>>>>>>
> >>>>>>> We tried configuring this setup but hit a wall because we don't have
> >>>>>>> windows machines. Is there no easy way to take the configuration
> >>>>>>> files Streisand spits out and upload them directly to the hex?
> >>>>>>> Alternatively, we're not sure what which settings to copy over from
> >>>>>>> that file and put into the hex.
> >>>>>>>
> >>>>>>>
> >>>>>>> On 02/15/2017 02:27 AM, Nicolas North wrote:
> >>>>>>>> Hi Marvin
> >>>>>>>>
> >>>>>>>> I’m sorry but I’m having some serious spam issues since i’ve
> >>>>>>>> migrated my mailserver.
> >>>>>>>>
> >>>>>>>> Here is the mail i had sent you. Hope you receive it!
> >>>>>>>>
> >>>>>>>> ––––––––––––––––
> >>>>>>>>
> >>>>>>>> Hi Marvin
> >>>>>>>>
> >>>>>>>> Sorry for the late reply.
> >>>>>>>>
> >>>>>>>> We’re using Hexes as vpn-only devices, with the following setup:
> >>>>>>>>
> >>>>>>>> ||| ISP Router ||| <=> ||| Hex VPN Router ||| <=> ||| LiMe Router |||
> >>>>>>>> |
> >>>>>>>> wifi adhoc
> >>>>>>>> |
> >>>>>>>> [other LiMe routers]
> >>>>>>>>
> >>>>>>>> This is the guide we’ve been following
> >>>>>>>> [https://matthewmcclatchey.com/using-private-internet-accesss-vpn-with-mikro…],
> >>>>>>>> with the exception of the fact that our vpn is lt2p+ipsec, and that
> >>>>>>>> we’ve had to set max mtu and max mru values to 1280 for some reason
> >>>>>>>> as packets were getting fragmented with our setup.
> >>>>>>>>
> >>>>>>>> If you connect a cable from the ISP’s router’s lan to the Hex’s wan,
> >>>>>>>> and another cable from the Hex’s lan to the LiMe router’s wan,
> >>>>>>>> you’ll have all of your internet-bound traffic from inside your mesh
> >>>>>>>> network sandboxed inside the VPN with no exceptions. The hex has
> >>>>>>>> some kind of "persistent tunnel” enabled by default, so drops the
> >>>>>>>> connection if the vpn breaks for some reason, even though it never
> >>>>>>>> has unless we actually rebooted the remote vpn server for testing
> >>>>>>>> purposes.
> >>>>>>>>
> >>>>>>>> I suggest giving the Hex an address like 172.16.0.1 to avoid
> >>>>>>>> conflicts with other more common subnets. We set all our ISP routers
> >>>>>>>> to 192.168.0.1 and LiMe uses 10.13.0.1 etc… so we’re good to go.
> >>>>>>>> Also, as a bonus, we try to pair all LiMe routers with an openwrt
> >>>>>>>> “simple AP” router, that takes care of the AP level and lets the
> >>>>>>>> LiMe router handle only the adhoc meshing level, for maximum
> >>>>>>>> wireless efficiency.
> >>>>>>>>
> >>>>>>>> We give APs static addresses of 10.13.64.1, 2, 3, and so on. They
> >>>>>>>> must all be different. Try and stay out of the DHCP range which
> >>>>>>>> starts at 100 I think. This last part [the AP addressing] is all
> >>>>>>>> trial and error and experimental so it might be wrong, but for us it
> >>>>>>>> works. We still need to figure out how to scale addressing for APs
> >>>>>>>> so we’re open to suggestions. While we’re at it:
> >>>>>>>>
> >>>>>>>> *TLDR question: what static IPv4 address to give a simple AP
> >>>>>>>> connected to the lan of a LiMe router? Is 10.13.64.1 - 10.13.64.99 a
> >>>>>>>> good range? How do we scale beyond that since every AP in the entire
> >>>>>>>> network must have a different IP?*
> >>>>>>>>
> >>>>>>>> Let me know how this works for you. To those answering the question:
> >>>>>>>> thank you in advance.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Nicolas
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> From: Marvin Arnold <marvin(a)unplugged.im> <mailto:marvin@unplugged.im>
> >>>>>>>> Reply: Marvin Arnold <marvin(a)unplugged.im> <mailto:marvin@unplugged.im>
> >>>>>>>> Date: 14 February 2017 at 02:19:38
> >>>>>>>> To: pau(a)dabax.net <pau(a)dabax.net> <mailto:pau@dabax.net>, nk(a)os.vu
> >>>>>>>> <nk(a)os.vu> <mailto:nk@os.vu>
> >>>>>>>> Subject: Re: [lime-users] VPN
> >>>>>>>>
> >>>>>>>>> Hi Pau, Nicolas,
> >>>>>>>>>
> >>>>>>>>> Maybe I'm losing my head, but I can't find the original email from
> >>>>>>>>> Nicolas being quoted. It looks like it may be the additional VPN setup
> >>>>>>>>> tips we are looking for. I've checked my spam and don't see any hidden
> >>>>>>>>> messages...
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On 02/13/2017 06:43 PM, Ilario wrote:
> >>>>>>>>>> Hi Nicolas!
> >>>>>>>>>> I think I missed some of your emails in Gmail's spam folder...
> >>>>>>>>>> Answer inline:
> >>>>>>>>>>
> >>>>>>>>>> 2017-02-13 1:51 GMT+01:00 Nicolas North <nk(a)os.vu>:
> >>>>>>>>>>> Also, as a bonus, we try to
> >>>>>>>>>>> pair all LiMe routers with an openwrt “simple AP” router, that
> >>>>>>>>> takes care of
> >>>>>>>>>>> the AP level and lets the LiMe router handle only the adhoc
> >>>>>>>>> meshing level,
> >>>>>>>>>>> for maximum wireless efficiency.
> >>>>>>>>>> That's really wise :)
> >>>>>>>>>>
> >>>>>>>>>>> We give APs static addresses of 10.13.64.1, 2, 3, and so on.
> >>>>>>>>> They must all
> >>>>>>>>>>> be different. Try and stay out of the DHCP range which starts at
> >>>>>>>>> 100 I
> >>>>>>>>>>> think.
> >>>>>>>>>> A very interesting question. There's no option for DHCP range in
> >>>>>>>>>> /etc/config/lime* files (and this is ok).
> >>>>>>>>>> But I supposed that the range was defined in /etc/config/dhcp, which
> >>>>>>>>>> on LibreMesh is identical than on OpenWrt/LEDE and contains:
> >>>>>>>>>> # cat /etc/config/dhcp
> >>>>>>>>>> [...]
> >>>>>>>>>> config dhcp 'lan'
> >>>>>>>>>> option interface 'lan'
> >>>>>>>>>> option start '100'
> >>>>>>>>>> option limit '150'
> >>>>>>>>>> option leasetime '1h'
> >>>>>>>>>>
> >>>>>>>>>> But trying to ask for a DHCP lease I received an IPv4 out of the
> >>>>>>>>>> 10.x.x.100-250 range, looking around I found that the DHCP range for
> >>>>>>>>>> anygw is hardcoded:
> >>>>>>>>>>
> >>>>>>>>> https://github.com/libremesh/lime-packages/commit/3a6596d50b3c0446b988f84d3…
> >>>>>>>>>> resulting in the whole subnet... No good. @devs?
> >>>>>>>>>>
> >>>>>>>>>> Anyway, do you need static IP addresses at the AP routers? You could
> >>>>>>>>>> also let them take the IP from LiMe (and LiMe would take care of
> >>>>>>>>>> avoiding collisions).
> >>>>>>>>>>
> >>>>>>>>>> Additionally, if you let LiMe routers to autoassign their own IPv4,
> >>>>>>>>>> they will span over the whole subnet, unless you specify a smaller
> >>>>>>>>>> "subnet" (not a real subnet, just a range) for auto-assignment, as
> >>>>>>>>>> explained in /etc/config/lime-example in the comment on the
> >>>>>>>>>> main_ipv4_address option:
> >>>>>>>>>>
> >>>>>>>>> https://github.com/libremesh/lime-packages/blob/2ce5ffa96de5b0b5abb507076b0…
> >>>>>>>>>> For example:
> >>>>>>>>>> # cat /etc/config/lime
> >>>>>>>>>> config lime 'network'
> >>>>>>>>>> option main_ipv4_address '10.13.128.0/16/17'
> >>>>>>>>>>
> >>>>>>>>>> will limit the autoassignment of IPv4 to the second half of the
> >>>>>>>>>> broadcast domain.
> >>>>>>>>>> Bye!
> >>>>>>>>>> Ilario
> >>>>>>>>>> _______________________________________________
> >>>>>>>>>> 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
> >>>>> --
> >>>>> Cordialmente
> >>>>>
> >>>>> Leonardo Taborda Ángel
> >>>>> leonardotaborda(a)networkbogota.org
> >>>>> www.networkbogota.org
> >>>>>
> >>>>> "When there is a will, there is a way"
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> lime-users mailing list
> >>>>> lime-users(a)lists.libremesh.org
> >>>>> https://lists.libremesh.org/mailman/listinfo/lime-users
> >>>
> >>> --
> >>> Cordialmente
> >>>
> >>> Leonardo Taborda Ángel
> >>> leonardotaborda(a)networkbogota.org
> >>> www.networkbogota.org
> >>>
> >>> "When there is a will, there is a way"
> >>>
> >>>
> >>> _______________________________________________
> >>> 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
>
>
>
