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