25 Dec
2014
25 Dec
'14
9:49 p.m.
Hi all!
I have just pushed the feature/ground-routing branch to our git repo, the good
news is that it is already usable and working, the bad news is that it seems
that openwrt doesn't offer a way to know who switch%d is so it could arbitrary
be eth0 or eth1 depending on the model and seems there is no way to determine
it from software side -_-
what I have done now is assume in the code that swtich$i will be mapped to
eth$i and although it is not true it works on all device i have and on device
we use the most like tl-wdr3x00
what openwrt do is ship a spefic confing for each different device, this config is
manually written by the person who write the support for that device so plain
old boring manual human work...
what we can do is
1) leave stuff as is, so users with "unusual" devices have do do some adjust
after lime-config
2) Introduce some kind of very very hardware specific module like the unpopular
lime-hwd-tl-wdr3600 we had this summer for each device with a "switch map"
readeable by a program
3) Push openwrt developers to implement some kind of mechanism to make switch
map readeable from software side
7 Jan
7 Jan
11:28 a.m.
Can you please make two cents about what do you mean for ground routing?
Thanks Gio!
On 25/12/14 22:49, Gioacchino Mazzurco wrote:
Hi all!
I have just pushed the feature/ground-routing branch to our git repo, the good
news is that it is already usable and working, the bad news is that it seems
that openwrt doesn't offer a way to know who switch%d is so it could arbitrary
be eth0 or eth1 depending on the model and seems there is no way to determine
it from software side -_-
what I have done now is assume in the code that swtich$i will be mapped to
eth$i and although it is not true it works on all device i have and on device
we use the most like tl-wdr3x00
what openwrt do is ship a spefic confing for each different device, this config is
manually written by the person who write the support for that device so plain
old boring manual human work...
what we can do is
1) leave stuff as is, so users with "unusual" devices have do do some adjust
after lime-config
2) Introduce some kind of very very hardware specific module like the unpopular
lime-hwd-tl-wdr3600 we had this summer for each device with a "switch map"
readeable by a program
3) Push openwrt developers to implement some kind of mechanism to make switch
map readeable from software side
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
--
./p4u
3:37 p.m.
New subject: Ground routing
On Wednesday, January 07, 2015 12:28:20 PM Pau wrote:
Can you please make two cents about what do you mean
for ground routing?
Yep!
Ground routing is a way of building supernodes developed by ninux community
network, in practice because they was experiencing bugs in openwrt drivers and
their links were mostly AP-STA they started to separate routing from the radio
layer, so on the roof you have CPE that only do radio stuff either with openwrt
or fabric firmware, while the router is inside your house, there are two
variants, one in which an ethernet cable run from each CPE to the router and
one in witch you have a gigabit siwtch on the roof where all CPE are connected
and only one gigait ethernet cable run to your ground router, lime actually
supports both modes, first mode have the advantage that doesn't needs 802.1q
tagged vlan support (on both GR and CPE) while have the disadvantage that you
have to run one cable for each CPE, the second mode have the advantage that
you can run just one gigabit ethernet cable from your roof switch to your GR
but needs that both GR and CPEs have 802.1q tagged vlan support to avoid L2
loop, i believe it have some similaruty with guifi hibrid mode, but using open
source router, having now libre-mesh supporting GR it means that supernode
configuracion is quite simpler having most of them automatically generated by
lime :)
A tipical topology with gigabit switch on the roof
=== ethernet link
------- wireless link
In the house 1 on the roof 1
<lime GR 1>======<GbEth switch>||=====<CPE1.1>------
_||=====<CPE1.2>----
_||=====<CPE1.3>----
on the roof 2 In the house 2
--------<CPE2.1>====||<GbEth switch>====<lime GR2>
--------<CPE2.3>====||
--------<CPE2.7>====||
--------<CPE2.x>====||
on the roof 3 In the house 2
--------<CPE3.1>====||<GbEth switch>====<lime GR2>
--------<CPE3.2>====||
--------<CPE3.y>====||
The usage of tagged 802.1q vlans avoid L2 loop
Here you can find more informations about GR
https://docs.google.com/document/d/1tEp4rFNDis4RAwwo4wwg6xDMdqeJKAi8FVYh_Fs…
3645
days inactive
3658
days old
2 comments
2 participants
participants (2)
-
Gioacchino Mazzurco -
Pau