13 Jun
2017
13 Jun
'17
9:01 p.m.
On Mon, Jun 12, 2017 at 12:14:46AM +0200, Pau wrote:
I review your commits and they look good. Thank you.
Things were deployed today and a small initial mesh went into
production. There are about 8 more of TL-WR841Nv11 waiting in
a box...
Topology:
Vodafone
VDSL2
|
TL-W8970B TL-WR841Nv11
| TL-WR841Nv11
| |
+-----------(Ethernet wire)------------------------------------+
All three devices got ath9k radios and were setup with a simply
community profile containing only /etc/config/lime-defaults:
config lime system
option hostname 'LiMe-%M4%M5%M6'
option domain 'funkenteile'
config lime network
option primary_interface eth0
option main_ipv4_address '10.%N1.0.0/16'
option main_ipv6_address '2a00:1508:0a%N1:%N200::/64'
list protocols adhoc
list protocols lan
list protocols anygw
list protocols batadv:%N1
list protocols bmx6:13
list resolvers 4.2.2.2 # b.resolvers.Level3.net
list resolvers 141.1.1.1 # cns1.cw.net
# list resolvers 2001:470:20::2 # ordns.he.net
config lime wifi
option channel_2ghz '1'
option channel_5ghz '40'
option country 'DE'
option distance '2000'
option htmode_5ghz 'HT40'
option htmode_2ghz 'HT40'
list modes 'ap'
list modes 'ieee80211s'
option ap_ssid 'Funkenteile'
option ap_encryption 'psk2'
option ap_key 'xxxxxxxxx'
option ieee80211s_mesh_fwding '0'
option ieee80211s_mesh_id 'LiMe'
---
Let's start with the good side, the things that worked:
* I mananged to configure VDSL2 and PPPoE on the TDW8970B!
This is officially my first non-ar71xx LiMe node and it workes great!
* 802.11s interfaces came up and got neighbours, AP+mesh mode works
out-of-the-box on LEDE 17.01.2
* most other things worked as expected, which is great!
Now to the non-working things (read: issues to be discussed):
* watchping needs to be converted to procd so it gets the pppoe
interface name when it actually comes up. Otherwise the gateway isn't
detected (for obvious reasons)
I can do that and will file a PR later tonight.
* lm_net_wlan0_mesh was not created
Despite being used a couple of times as an alias in /etc/config/network
the 'config interface lm_net_wlan0_mesh' section wasn't created and
hence all child vlan-interfaces also never came up.
It was easy to fix it by adding
config interface lm_net_wlan0_mesh
option proto 'none'
to /etc/config/network, after a subsequent network restart the VLANs
got created and both bmx6 and batman-adv started meshing on top of the
802.11s mesh interface!
To me the whole lime-system stuff is very intransparent and hard to
wrap my head around, it also doesn't exactly have a lot of comments,
so I'm totally in the dark why this section doesn't get created in
first place.
Fixing this is really important, but I couldn't do it (yet). Maybe
someone who wrote the Lua code of lime-system can fix it...?
* batman-adv and bmx6 vlans for wired interfaces
I never quite understood how to connect two LiMe nodes over Ethernet
in a way that they would exchange routing information, at least via
bmx6 (I do understand that this nasty BLA bug prevents us from
running batman-adv and a bare bridge-link and hence batman-adv-over-
Ethernet doesn't work right now). Even worse: On the TL-WR841N
devices the batman-adv and bmx6 VLANs were created only on the WAN
interface (eth1). On the TDW8970 (which got only LAN Ethernet ports)
the VLAN sections were created correctly, as 8021ad-type VLANs on
top of the raw Ethernet device which is hooked into the br-lan bridge.
I tried to build an image without the lime-hwd-openwrt-wan but didn't
succeed, it somehow always ended up being installed :(
Maybe there is a misunderstanding, but once again I'm failing to
grasp how to debug lime-config, as (obviously) running it a second
time after firstboot won't work :(
Ok, that's it for the (obvious) bugs.
In the long run it could be interesting to port the ciphers needed for
SAE to be included in wpa_supplicant rather than needing OpenSSL for
that. Then we could probably have something like a lime-zero-variant
with encrypted mesh (but without webUI) which could be an intersting
USE-case as well.
However, I'd rather see bmx7 getting ready and allow using IPSec for
bmx-created tun-interfaces :)
Sidenote: Never, really never ever buy CCA (copper-coted-aluminum)
wires. It's produced directly for the bin and not worth the effort
even cutting, mounting and terminating it. Random link failures,
some switches work, some don't, some just endup with a 10MB/s link,
it's a hell you don't want to get in. I didn't even know that such
bad things are sold, for now I always bought the cheapest Cat.6
cable and it always worked, this time was different :(
I hope to hear from you and get things fixed up, so we'll have an
awesome next LiMe release!
Cheers
Daniel