Buenas,
Más abajo les envío una presentación que hice hace unos años en la lista de
AlterMesh.
Les cuento que actualmente el proyecto tiene instalados 3 routers wdr3600
en 3 instituciones del Barrio Villa Aguirre, Tandil, pero actualmente no se
provee ningún servicio. Estos equipos los instalaron alumnos de la TUPAR en
el marco de un trabajo de la materia Tecnología de Redes 1.
La versión que tienen instalada los equipos es:
lime-tl-wdr3600-v1-r44952-tandillibre-node-factory.bin
lime-tl-wdr3600-v1-r44952-tandillibre-node-sysupgrade.bin
En este momento en una de las instituciones se está instalando un servidor
que hará de portal cautivo y alojará algunos contenidos (wikipedia,
owncloud). El servidor lo están configurando como trabajo final de la
TUPAR.
Estamos teniendo problemas para lograr que el router otorgue como DNS la ip
de servidor.
Pero si te conectas al wifi y le pones manualmente el DNS (10.233.0.55)
funciona perfecto. (video
<https://drive.google.com/open?id=0BzqwAzOcjbGkYVM2V0xyRFpfYTg>)
Si tienen alguna guía de como configurar el equipo para vincularlo al
servidor de DNS del servidor, nos vendría genial.
También me comentaron los chicos que cuando el equipo pierde la corriente
se borra la configuración. ¿Se les ocurre por que puede ser?
Saludos y gracias!
Santiago
---------- Forwarded message ----------
From: Santi Vallazza <rulosanti(a)gmail.com>
Date: 2015-10-05 14:30 GMT-03:00
Subject: Presentación
To: altermesh(a)listas.altermundi.net
Buenas!
Me presento, mi nombre es Santiago Vallazza, vivo en Tandil, Provincia de
Buenos Aires, Argentina y trabajo en la Facultad de Ciencias Exactas
<http://www.exa.unicen.edu.ar/> de la UNICEN <http://unicen.edu.ar/>. En
esta Facultad tenemos varias carreras, las relacionadas con Sistemas son:
Ingeniería de Sistemas, Tecnicatura Universitaria en Programación y
Administración de Redes (TUPAR) y este año arrancó la Tecnicatura
Universitaria en Desarrollo de Aplicaciones Informáticas (TUDAI).
Soy usuario y militante del Software y la Cultura Libre, hace unos años me
metí en redes pero no pude darle mucha continuidad. Ahora tengo ganas de
retomar el tema.
Ahora estamos con un proyecto que propone crear una red inalámbrica de
alcance barrial, que provea contenidos educativos e informativos. La idea
es poder acceder a contenidos que estén en el servidor del proyecto, que
ubicaremos en una sede de la UNICEN, la Universidad Barrial, y en los
servidores de las escuelas que participen (moodle, etc.).
Del proyecto van a participar algunos estudiantes voluntarios y se
trabajará con docentes y cátedras de Comunicación de Datos de la TUPAR de
Ingeniería de Sistemas, y en ese marco algunos estudiantes realizarán
trabajos de cátedra y de final.
Nos gustó el proyecto Altermundi y el alcance territorial que tiene y el
firmware Altermesh, así que intentaremos usarlo como firmware oficial del
proyecto, y si podemos hacer aportes, también lo haremos. Ya he contactado
a algunos miembros de Altermundi por sus correos personales, pero creo que
este será un medio más apropiados.
Eso es todo por ahora, y en otro hilo comienzo con algunas preguntas.
Saludos!
Santiago
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
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
>
hello,
I am trying get on the chef server to work on a local mesh network. I need to download images for a tplink device, as all my downloaded images are for ubiquiti. thanks for any help!
cheers
The last weeks I have been working on a new tool for generating the
LibreMesh firmware images. I hope it makes things easier for those who
want to "cook" their own stuff.
I've just written some documentation, I hope it is understandable enough.
https://github.com/libremesh/lime-sdk
Any correction/modification is welcome via pull-request or issue tracker.
Cheers.
PS: next step is to adapt online Chef web interface
--
./p4u
Sorry I was not very clear in my last message.
I was unable to access chef.altermundi.net from my local network. Now I see that is pointless anyways as chef only creates images for ubnt devices, perhaps chef can be updated to create images for the tplink devices that are stated to be working on the libremesh website(I went and purchased one because I assumed chef would crank out images for it). Since this didn't work I tryed to access the main libremesh release download link link and it is still unavailable, is there a mirror for this?
thanks for any help!On Apr 24, 2017 6:31 PM, Ilario Gelmetti <iochesonome(a)gmail.com> wrote:
>
> On 04/24/2017 08:44 PM, August wrote:
> > I am trying get on the chef server to work on a local mesh network.
>
> If you want yo host the Chef software on a machine of yours, you can but
> this is not needed in order to have a working LibreMesh image.
> Anyway, if you really want to try, follow the instructions here:
> https://github.com/libremesh/alterchef
>
> > I need to download images for a tplink device, as all my downloaded images are for ubiquiti.
> I didn't get this. Are you using chef.altermundi.net ?
> _______________________________________________
> lime-users mailing list
> lime-users(a)lists.libremesh.org
> https://lists.libremesh.org/mailman/listinfo/lime-users
On Friday 21 April 2017 23:43:35 IST you wrote:
> Hi,
> If I assign ip addresses to the wlan0-mesh interfaces in the same c class
> ipv4 range I can ping all the routers in the mesh so they are all
> connected. AFAIK (I think) the mesh routing should be over layer 2, so what
> am I missing in the config setup ... anyone any ideas ?
>
> iw wlan0-mesh mpath dump
> DEST ADDR NEXT HOP IFACE SN METRIC QLEN
> EXPTIME DTIM DRET FLAGS
> 84:16:f9:d9:18:6e 84:16:f9:d9:18:6e wlan0-mesh 2276 141 0 4490
> 0 0 0x15
> 84:16:f9:d9:44:80 84:16:f9:d9:44:80 wlan0-mesh 2330 95 0 4490
> 100 0 0x15
>
>
> Thanks
> Ruairi
>
> On Thursday 20 April 2017 11:10:07 IST Ruairi Hickey wrote:
> > Hi,
> >
> > As per banner below, it's
> >
> > LiMe 16.07 CommunityChaos (16.07 rev.5fbd38f 20160913_2151)
> >
> > Thanks
> >
> > Ruairi
> >
> > _______ ________ __
> >
> > | |.-----.-----.-----.| | | |.----.| |_
> > |
> > | - || _ | -__| || | | || _|| _|
> > |
> > |_______|| __|_____|__|__||________||__| |____|
> > |
> > |__| W I R E L E S S F R E E D O M
> >
> > -----------------------------------------------------
> > CHAOS CALMER (Chaos Calmer, r49403)
> > -----------------------------------------------------
> >
> > * 1 1/2 oz Gin Shake with a glassful
> > * 1/4 oz Triple Sec of broken ice and pour
> > * 3/4 oz Lime Juice unstrained into a goblet.
> > * 1 1/2 oz Orange Juice
> > * 1 tsp. Grenadine Syrup
> >
> > -----------------------------------------------------
> >
> > ___ __ __ _______ __
> >
> > | |_|__| |--.----.-----.| | |-----.-----| |--.
> > | |
> > | | | _ | _| -__|| | -__|__ --| |
> > |
> > |_____|__|_____|__| |_____||__|_|__|_____|_____|__|__|
> >
> > ------------------------------------------------------
> > LiMe 16.07 CommunityChaos (16.07 rev.5fbd38f 20160913_2151)
> > ------------------------------------------------------
> > http://libremesh.org
> > ------------------------------------------------------
> >
> > Ruairi
> >
> > On Thursday 20 April 2017 11:34:09 IST Pau 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
> >
> > _______________________________________________
> > lime-users mailing list
> > lime-users(a)lists.libremesh.org
> > https://lists.libremesh.org/mailman/listinfo/lime-users
Hi,
If I assign ip addresses to the wlan0-mesh interfaces in the same c class
ipv4 range I can ping all the routers in the mesh so they are all connected.
AFAIK (I think) the mesh routing should be over layer 2, so what am I missing
in the config setup ... anyone any ideas ?
iw wlan0-mesh mpath dump
DEST ADDR NEXT HOP IFACE SN METRIC QLEN
EXPTIME DTIM DRET FLAGS
84:16:f9:d9:18:6e 84:16:f9:d9:18:6e wlan0-mesh 2276 141 0 4490
0 0 0x15
84:16:f9:d9:44:80 84:16:f9:d9:44:80 wlan0-mesh 2330 95 0 4490
100 0 0x15
Thanks
Ruairi
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Is there any image cooked by the chef valid for a TL-WR841?
Thanks
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJY97BtAAoJEF2FWO6p8n2epR8QAMGvy9+f9KRP+aR+HRWGB9W3
SC7u2u4zF98qDs6oJE9eGi03TQvfWXLbcCWJN5XOnh0uVF6DGPU+yEUrx8+opHxy
2hJ75sCCMNGcs5WLeObKJKjTrO+mpfaterM99DTfbZAi737MrizY896NGM6gscJO
Kb7L2iUpAFr9VEsb1EKQgohP6/lb+XwfR1zZRgQ+2r6tv+Xe2mOpWCm7rSEYoWas
srKgv61JJGwSvN02XjUKhMMWiw8NfIxB9ZN+Sq6/hr4hZMlmRJEM9E1x1KgxrEJi
gTHAr44UuOexKirtuk7EtTanI71c+ynueoOoI9NsIrAbtQrcwNVpjth5VXmwprWg
2t7m0VqqkSlGgYjy6mOjEHDGyoflq/HSbxzsH71XEr0jUoa5nBJ27RNLopxlXgAK
yZgw8xsz56MogrXmNLRKdaug3FZr7R0DjktUYSIGVOyRXMvrrfadqNXEKORvG/ek
f/8HpA2UCR6Nt98ffeiTF/p0kVm9oHjhDeJAJXtBpCGMRjUQv5NDt3I95/5MhSab
3Ckr5oaSXg2qvrY4oD3r0WVgov+0ZlCjsMqh/EG2OH7MewAX1eUfxMkEiudWdgdF
r5V0WuWImO3aqV2d1EniUqxlMNNdTiyfj118T2+Q/PPIn6n2GER0UmRRWhcLwnFM
9csNA7XKeKVgXrVnHCSO
=mnY7
-----END PGP SIGNATURE-----
On Wednesday 19 April 2017 15:52:08 IST Ruairi Hickey wrote:
> On Wednesday 19 April 2017 16:34:05 IST Pau wrote:
> > list modes 'ap'
> > list modes 'apname'
> > list modes 'ieee80211s'
> > option channel_2ghz '11'
> > option channel_5ghz '48'
>
> Hi,
> That seems to have worked OK.... I have a 3rd box at home which I will
> test as well to try get all 3 on the mesh. The routers are 3 x TPLink TL-
> WR841N.
>
> iw dev wlan0-mesh station dump
> Station 84:16:f9:d9:18:6e (on wlan0-mesh)
> inactive time: 20 ms
> rx bytes: 492473
> rx packets: 7570
> tx bytes: 270
> tx packets: 3
> tx retries: 0
> tx failed: 0
> signal: -19 [-20, -26] dBm
> signal avg: -18 [-20, -22] dBm
> Toffset: -335602982 us
> tx bitrate: 6.5 MBit/s MCS 0
> rx bitrate: 19.5 MBit/s MCS 2
> mesh llid: 7348
> mesh plid: 5441
> mesh plink: ESTAB
> mesh local PS mode: ACTIVE
> mesh peer PS mode: ACTIVE
> mesh non-peer PS mode: ACTIVE
> authorized: yes
> authenticated: yes
> preamble: long
> WMM/WME: yes
> MFP: no
> TDLS peer: no
> connected time: 390 seconds
>
>
> Thanks,
> Ruairi
Hi,
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 connect to the internet / outside via AP d9:44:80. Are
there additional steps required to enable this (it works out of the box on ad-
hoc) ? Apologies if I am asking stupid questions.... this is new to me but
if I can assist in any way please let me know...
Thanks,
Ruairi
