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
---------- 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
-----------------------------------------
Hi all
I’m back working with LiMe after several months and I’m looking to achieve the best possible speeds that are technically possible with wifi tech.
I’m getting extremely variable results over 2.4GHz [varying from 45mbps to 3mbps speedtest.net over 1 mesh hop - meaning connected via ethernet to the node not connected to wan, which in turn has a line-of-sight, 3m distance, wireless mesh connection to the router connected to a 120mbps down / 30mbps up wan]. All tests being done with two TL Archer C7s with base LiMe 1607.
I assume the speed variations are due to interference, since nothing else is changing between tests? I had posted a question about this back in the day, but I don’t remember any answers having come back.
Therefore I’m looking into 5GHz AC as an option. I’m thinking 5GHz non-AC could already be an improvement due to less interference, but of course AC would be the best.
I know there is a lot of hardware out there, but very little of it is supported by owrt/lede with full 5GHz AC speeds, let alone by LiMe, am I correct?
I’m looking for outdoor AP that has 5GHz AC and is supported not only by owrt/lede but also by lime. Does anyone know of any such model?
Obviously if it were a dual band device it would be even better. In such case would LiMe choose how to mesh with other devices on the most appropriate band on an individual basis?
And last question: do we have any LiMe support for the TL WBS210/510? It is not currently supported in a stable way by owrt but it is by lede: https://lede-project.org/toh/hwdata/tp-link/tp-link_wbs210.
This question interconnects with the one about 802.11s I posted just a few minutes ago.
Thank you all so much for sticking with me throughout the way of my ever-more-detailed questions ;]
Nk
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-----
