20 May
2017
20 May
'17
9:55 p.m.
Cooking went flawlessly but output has been a vanilla Lede firmware.
Did I overlook something?
21 May
21 May
9:42 a.m.
On 05/20/2017 11:55 PM, Juergen Kimmel wrote:
Cooking went flawlessly but output has been a vanilla
Lede firmware.
Did I overlook something?
Can you post the cooker command you used?
I tried to replicate using:
./cooker -c ramips/mt7620 --flavor=lime_default --profile=zbt-ape522ii
--update-feeds
and I got:
ls output/ramips/mt7620/zbt-ape522ii/lime_default/
lede-17.01.1-libremesh-ramips-mt7620-device-zbt-ape522ii.manifest
lede-17.01.1-libremesh-ramips-mt7620-zbt-ape522ii-squashfs-sysupgrade.bin
sha256sums
I can't verify if the image works but I can say it contains many
LibreMesh related files, using:
binwalk -e
lede-17.01.1-libremesh-ramips-mt7620-zbt-ape522ii-squashfs-sysupgrade.bin
Did you use a different lime-sdk command?
Can you check the firmware image content with binwalk (is there any
other way)?
Bye!
Ilario
9:30 p.m.
Hi Ilario you got me. Has been a typo - minus instead of underscore -.
So this time output ok.
But also this firmware ends in a bootloop triggered by traffic.
Still waiting for daniel golle's efforts on mt7620 drivers
Cheers
Ilario Gelmetti <iochesonome(a)gmail.com> schrieb am So., 21. Mai 2017 um
11:42 Uhr:
On 05/20/2017 11:55 PM, Juergen Kimmel wrote:
Cooking went flawlessly but output has been a
vanilla Lede firmware.
Did I overlook something?
Can you post the cooker command you used?
I tried to replicate using:
./cooker -c ramips/mt7620 --flavor=lime_default --profile=zbt-ape522ii
--update-feeds
and I got:
ls output/ramips/mt7620/zbt-ape522ii/lime_default/
lede-17.01.1-libremesh-ramips-mt7620-device-zbt-ape522ii.manifest
lede-17.01.1-libremesh-ramips-mt7620-zbt-ape522ii-squashfs-sysupgrade.bin
sha256sums
I can't verify if the image works but I can say it contains many
LibreMesh related files, using:
binwalk -e
lede-17.01.1-libremesh-ramips-mt7620-zbt-ape522ii-squashfs-sysupgrade.bin
Did you use a different lime-sdk command?
Can you check the firmware image content with binwalk (is there any
other way)?
Bye!
Ilario
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users 
22 May
22 May
9:15 a.m.
On 21/05/17 23:30, Juergen Kimmel wrote:
Hi Ilario you got me. Has been a typo - minus instead
of underscore -.
So this time output ok.
But also this firmware ends in a bootloop triggered by traffic.
Still waiting for daniel golle's efforts on mt7620 drivers
Cheers
Hi Jurgen.
There is a patch which may fix some stuff related with 802.11s, but it
is not applied automatically. Please, make sure you are using the last
lime-sdk (execute git pull).
You have to manually execute a script snippet like this:
bash snippets/patch_sdk_mac80211.sh
Then recompile the packages:
./cooker -b ramips/mt7620
And finally cook the firmware
./cooker -c ramips/mt7620 --flavor=lime_default --profile=zbt-ape522ii
Recently I added a way to enable 11s by default (instead of adhoc) in
the firmware, you have to use a community profile like this:
./cooker -c ramips/mt7620 --flavor=lime_default --profile=zbt-ape522ii
--community=libremesh/11s
** the communities profiles are listed here:
https://github.com/libremesh/network-profiles
** read the README.md of lime-sdk to understand what a community profile is.
You can also download precompiled binaries with the patch and 11s
enabled from here:
http://repo.libremesh.org/lime-17.04/targets/ramips/mt7620/zbt-ape522ii/lim…
Please, let us know if it works for you. I don't have this hardware and
I cannot test by myself.
Cheers.
Ilario Gelmetti <iochesonome(a)gmail.com> schrieb am So., 21. Mai 2017 um
11:42 Uhr:
--
./p4u
On 05/20/2017 11:55 PM, Juergen Kimmel wrote:
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
Cooking went flawlessly but output has been a
vanilla Lede firmware.
Did I overlook something?
Can you post the cooker command you used?
I tried to replicate using:
./cooker -c ramips/mt7620 --flavor=lime_default --profile=zbt-ape522ii
--update-feeds
and I got:
ls output/ramips/mt7620/zbt-ape522ii/lime_default/
lede-17.01.1-libremesh-ramips-mt7620-device-zbt-ape522ii.manifest
lede-17.01.1-libremesh-ramips-mt7620-zbt-ape522ii-squashfs-sysupgrade.bin
sha256sums
I can't verify if the image works but I can say it contains many
LibreMesh related files, using:
binwalk -e
lede-17.01.1-libremesh-ramips-mt7620-zbt-ape522ii-squashfs-sysupgrade.bin
Did you use a different lime-sdk command?
Can you check the firmware image content with binwalk (is there any
other way)?
Bye!
Ilario
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
6:25 p.m.
Hi all,
flashed the precompiled binary.
Interface WAN does not come up WAN6 does. So I can't test stability in
concern of internet traffic.
Minor flaw: Meshpoint SSID isn't set as usual.
About every 10 sec dmesg: br-lan: received packet on bat0 with own address
as source address
Devices mesh as expected.
Cheers
Pau <pau(a)dabax.net> schrieb am Mo., 22. Mai 2017 um 11:15 Uhr:
On 21/05/17 23:30, Juergen Kimmel wrote:
--
./p4u
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
Hi Ilario you got me. Has been a typo - minus
instead of underscore -.
So this time output ok.
But also this firmware ends in a bootloop triggered by traffic.
Still waiting for daniel golle's efforts on mt7620 drivers
Cheers
Hi Jurgen.
There is a patch which may fix some stuff related with 802.11s, but it
is not applied automatically. Please, make sure you are using the last
lime-sdk (execute git pull).
You have to manually execute a script snippet like this:
bash snippets/patch_sdk_mac80211.sh
Then recompile the packages:
./cooker -b ramips/mt7620
And finally cook the firmware
./cooker -c ramips/mt7620 --flavor=lime_default --profile=zbt-ape522ii
Recently I added a way to enable 11s by default (instead of adhoc) in
the firmware, you have to use a community profile like this:
./cooker -c ramips/mt7620 --flavor=lime_default --profile=zbt-ape522ii
--community=libremesh/11s
** the communities profiles are listed here:
https://github.com/libremesh/network-profiles
** read the README.md of lime-sdk to understand what a community profile
is.
You can also download precompiled binaries with the patch and 11s
enabled from here:
http://repo.libremesh.org/lime-17.04/targets/ramips/mt7620/zbt-ape522ii/lim…
Please, let us know if it works for you. I don't have this hardware and
I cannot test by myself.
Cheers.
Ilario Gelmetti <iochesonome(a)gmail.com> schrieb am So., 21. Mai 2017 um
11:42 Uhr:
> On 05/20/2017 11:55 PM, Juergen Kimmel wrote:
>> Cooking went flawlessly but output has been a vanilla Lede firmware.
>> Did I overlook something?
>
> Can you post the cooker command you used?
> I tried to replicate using:
> ./cooker -c ramips/mt7620 --flavor=lime_default --profile=zbt-ape522ii
> --update-feeds
>
> and I got:
> ls output/ramips/mt7620/zbt-ape522ii/lime_default/
> lede-17.01.1-libremesh-ramips-mt7620-device-zbt-ape522ii.manifest
>
lede-17.01.1-libremesh-ramips-mt7620-zbt-ape522ii-squashfs-sysupgrade.bin
> sha256sums
>
> I can't verify if the image works but I can say it contains many
> LibreMesh related files, using:
> binwalk -e
>
lede-17.01.1-libremesh-ramips-mt7620-zbt-ape522ii-squashfs-sysupgrade.bin
Did you use a different lime-sdk command?
Can you check the firmware image content with binwalk (is there any
other way)?
Bye!
Ilario
_______________________________________________
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
23 May
23 May
2:24 a.m.
Maybe this clarifies:
[ 23.650087] batman_adv: bat0: Changing gw mode from: off to: client
[ 23.703459] batman_adv: bat0: multicast_mode: Changing from: enabled to:
disabled
[ 23.742264] batman_adv: The newly added mac address (78:a3:51:16:d9:e9)
already exists on: eth0-2_29
[ 23.751672] batman_adv: It is strongly recommended to keep mac addresses
unique to avoid problems!
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Mo., 22. Mai 2017 um
20:25 Uhr:
Hi all,
flashed the precompiled binary.
Interface WAN does not come up WAN6 does. So I can't test stability in
concern of internet traffic.
Minor flaw: Meshpoint SSID isn't set as usual.
About every 10 sec dmesg: br-lan: received packet on bat0 with own
address as source address
Devices mesh as expected.
Cheers
Pau <pau(a)dabax.net> schrieb am Mo., 22. Mai 2017 um 11:15 Uhr:
On 21/05/17 23:30, Juergen Kimmel wrote:
--
./p4u
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
Hi Ilario you got me. Has been a typo - minus
instead of underscore -.
So this time output ok.
But also this firmware ends in a bootloop triggered by traffic.
Still waiting for daniel golle's efforts on mt7620 drivers
Cheers
Hi Jurgen.
There is a patch which may fix some stuff related with 802.11s, but it
is not applied automatically. Please, make sure you are using the last
lime-sdk (execute git pull).
You have to manually execute a script snippet like this:
bash snippets/patch_sdk_mac80211.sh
Then recompile the packages:
./cooker -b ramips/mt7620
And finally cook the firmware
./cooker -c ramips/mt7620 --flavor=lime_default --profile=zbt-ape522ii
Recently I added a way to enable 11s by default (instead of adhoc) in
the firmware, you have to use a community profile like this:
./cooker -c ramips/mt7620 --flavor=lime_default --profile=zbt-ape522ii
--community=libremesh/11s
** the communities profiles are listed here:
https://github.com/libremesh/network-profiles
** read the README.md of lime-sdk to understand what a community profile
is.
You can also download precompiled binaries with the patch and 11s
enabled from here:
http://repo.libremesh.org/lime-17.04/targets/ramips/mt7620/zbt-ape522ii/lim…
Please, let us know if it works for you. I don't have this hardware and
I cannot test by myself.
Cheers.
Ilario Gelmetti <iochesonome(a)gmail.com> schrieb am So., 21. Mai 2017 um
11:42 Uhr:
> On 05/20/2017 11:55 PM, Juergen Kimmel wrote:
>> Cooking went flawlessly but output has been a vanilla Lede firmware.
>> Did I overlook something?
>
> Can you post the cooker command you used?
> I tried to replicate using:
> ./cooker -c ramips/mt7620 --flavor=lime_default --profile=zbt-ape522ii
> --update-feeds
>
> and I got:
> ls output/ramips/mt7620/zbt-ape522ii/lime_default/
> lede-17.01.1-libremesh-ramips-mt7620-device-zbt-ape522ii.manifest
>
lede-17.01.1-libremesh-ramips-mt7620-zbt-ape522ii-squashfs-sysupgrade.bin
> sha256sums
>
> I can't verify if the image works but I can say it contains many
> LibreMesh related files, using:
> binwalk -e
>
lede-17.01.1-libremesh-ramips-mt7620-zbt-ape522ii-squashfs-sysupgrade.bin
Did you use a different lime-sdk command?
Can you check the firmware image content with binwalk (is there any
other way)?
Bye!
Ilario
_______________________________________________
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
11:16 a.m.
On 23/05/17 04:24, Juergen Kimmel wrote:
--
./p4u
Maybe this clarifies:
[ 23.650087] batman_adv: bat0: Changing gw mode from: off to: client
[ 23.703459] batman_adv: bat0: multicast_mode: Changing from: enabled to:
disabled
[ 23.742264] batman_adv: The newly added mac address (78:a3:51:16:d9:e9)
already exists on: eth0-2_29
[ 23.751672] batman_adv: It is strongly recommended to keep mac addresses
unique to avoid problems!
That should not be a real problem, just annoying.
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb
am Mo., 22. Mai 2017 um
20:25 Uhr:
> Hi all,
> flashed the precompiled binary.
>
> Interface WAN does not come up WAN6 does. So I can't test stability in
> concern of internet traffic.
Does the system recognizes the eth1 device? (ip link show)
Can you paste the output of "uci show network" and "uci show lime" ?
Thanks.
Minor flaw:
Meshpoint SSID isn't set as usual.
About every 10 sec dmesg: br-lan: received packet on bat0 with own
address as source address
Devices mesh as expected.
Cheers
Pau <pau(a)dabax.net> schrieb am Mo., 22. Mai 2017 um 11:15 Uhr:
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
On 21/05/17 23:30, Juergen Kimmel wrote:
Hi Ilario you got me. Has been a typo - minus
instead of underscore -.
So this time output ok.
But also this firmware ends in a bootloop triggered by traffic.
Still waiting for daniel golle's efforts on mt7620 drivers
Cheers
Hi Jurgen.
There is a patch which may fix some stuff related with 802.11s, but it
is not applied automatically. Please, make sure you are using the last
lime-sdk (execute git pull).
You have to manually execute a script snippet like this:
bash snippets/patch_sdk_mac80211.sh
Then recompile the packages:
./cooker -b ramips/mt7620
And finally cook the firmware
./cooker -c ramips/mt7620 --flavor=lime_default --profile=zbt-ape522ii
Recently I added a way to enable 11s by default (instead of adhoc) in
the firmware, you have to use a community profile like this:
./cooker -c ramips/mt7620 --flavor=lime_default --profile=zbt-ape522ii
--community=libremesh/11s
** the communities profiles are listed here:
https://github.com/libremesh/network-profiles
** read the README.md of lime-sdk to understand what a community profile
is.
You can also download precompiled binaries with the patch and 11s
enabled from here:
http://repo.libremesh.org/lime-17.04/targets/ramips/mt7620/zbt-ape522ii/lim…
Please, let us know if it works for you. I don't have this hardware and
I cannot test by myself.
Cheers.
Ilario Gelmetti <iochesonome(a)gmail.com> schrieb am So., 21. Mai 2017 um
11:42 Uhr:
> On 05/20/2017 11:55 PM, Juergen Kimmel wrote:
>> Cooking went flawlessly but output has been a vanilla Lede firmware.
>> Did I overlook something?
>
> Can you post the cooker command you used?
> I tried to replicate using:
> ./cooker -c ramips/mt7620 --flavor=lime_default --profile=zbt-ape522ii
> --update-feeds
>
> and I got:
> ls output/ramips/mt7620/zbt-ape522ii/lime_default/
> lede-17.01.1-libremesh-ramips-mt7620-device-zbt-ape522ii.manifest
>
lede-17.01.1-libremesh-ramips-mt7620-zbt-ape522ii-squashfs-sysupgrade.bin
> sha256sums
>
> I can't verify if the image works but I can say it contains many
> LibreMesh related files, using:
> binwalk -e
>
lede-17.01.1-libremesh-ramips-mt7620-zbt-ape522ii-squashfs-sysupgrade.bin
>
> Did you use a different lime-sdk command?
> Can you check the firmware image content with binwalk (is there any
> other way)?
> Bye!
> Ilario
>
>
> _______________________________________________
> 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
--
./p4u
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
24 May
24 May
1:43 a.m.
Here come the data:
login as: root
root(a)10.13.0.1's password:
BusyBox v1.25.1 () built-in shell (ash)
_________
/ /\ _ ___ ___ ___
/ LE / \ | | | __| \| __|
/ DE / \ | |__| _|| |) | _|
/________/ LE \ |____|___|___/|___|
lede-project.org
\ \ DE /
\ LE \ /
-----------------------------------------------------------
\ DE \ / Reboot (17.01.1, r3316-7eb58cf109)
\________\/
-----------------------------------------------------------
___ __ __ _______ __
| |_|__| |--.----.-----.| | |-----.-----| |--.
| | | _ | _| -__|| | -__|__ --| |
|_____|__|_____|__| |_____||__|_|__|_____|_____|__|__|
------------------------------------------------------
LiMe 0.0 development (develop rev.6ded289 20170522_1204)
------------------------------------------------------
http://libremesh.org
------------------------------------------------------
=== System Notes =====================================
======================================================
root@LiMe-16d9e8:~# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state
UNKNOWN mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e8 brd ff:ff:ff:ff:ff:ff
3: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN mode DEFAULT group
default qlen 1
link/tunnel6 :: brd ::
4: dummy0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue master bat0
state UNKNOWN mode DEFAULT group default qlen 1000
link/ether aa:a3:51:16:d9:e8 brd ff:ff:ff:ff:ff:ff
7: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e8 brd ff:ff:ff:ff:ff:ff
8: eth0.1@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
master br-lan state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e8 brd ff:ff:ff:ff:ff:ff
9: anygw@br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UNKNOWN mode DEFAULT group default qlen 1
link/ether aa:aa:aa:0d:fe:aa brd ff:ff:ff:ff:ff:ff
10: eth0-1_13(a)eth0.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1398 qdisc
noqueue state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e8 brd ff:ff:ff:ff:ff:ff
11: eth0.2@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e9 brd ff:ff:ff:ff:ff:ff
12: eth0-2_13(a)eth0.2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1398 qdisc
noqueue state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e9 brd ff:ff:ff:ff:ff:ff
13: eth0-2_29(a)eth0.2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
noqueue master bat0 state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e9 brd ff:ff:ff:ff:ff:ff
14: eth0_13@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1398 qdisc noqueue
state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e8 brd ff:ff:ff:ff:ff:ff
15: bat0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master
br-lan state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 16:f1:88:98:5f:0b brd ff:ff:ff:ff:ff:ff
16: bmxmain@NONE: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1452 qdisc noqueue
state UNKNOWN mode DEFAULT group default qlen 1
link/tunnel6 fd66:66:66:a:7aa3:51ff:fe16:d9e8 peer
fd66:66:66:ff00:7aa3:51ff:fe16:d9e8
17: wlan1-mesh: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1536 qdisc mq state
UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e8 brd ff:ff:ff:ff:ff:ff
18: wlan0-mesh: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1536 qdisc noqueue
state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e9 brd ff:ff:ff:ff:ff:ff
19: wlan1-ap: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master
br-lan state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e9 brd ff:ff:ff:ff:ff:ff
20: wlan0-ap: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
master br-lan state UP mode DEFAULT group default qlen 1000
link/ether 7a:a3:51:16:d9:e9 brd ff:ff:ff:ff:ff:ff
21: wlan0-apname: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
master br-lan state UP mode DEFAULT group default qlen 1000
link/ether 7e:a3:51:16:d9:e9 brd ff:ff:ff:ff:ff:ff
22: wlan1-apname: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq
master br-lan state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:ea brd ff:ff:ff:ff:ff:ff
23: wlan1-mesh_13@wlan1-mesh: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1398
qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e8 brd ff:ff:ff:ff:ff:ff
24: wlan1-mesh_29@wlan1-mesh: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1532
qdisc noqueue master bat0 state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e8 brd ff:ff:ff:ff:ff:ff
25: wlan0-mesh_13@wlan0-mesh: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1398
qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e9 brd ff:ff:ff:ff:ff:ff
26: wlan0-mesh_29@wlan0-mesh: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1532
qdisc noqueue master bat0 state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e9 brd ff:ff:ff:ff:ff:ff
27: bmxC4main: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc
fq_codel state UNKNOWN mode DEFAULT group default qlen 500
link/none
28: bmxC6main: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc
fq_codel state UNKNOWN mode DEFAULT group default qlen 500
link/none
root@LiMe-16d9e8:~# uci show network
network.loopback=interface
network.loopback.ifname='lo'
network.loopback.proto='static'
network.loopback.ipaddr='127.0.0.1'
network.loopback.netmask='255.0.0.0'
network.globals=globals
network.lan=interface
network.lan.type='bridge'
network.lan.proto='static'
network.lan.ip6assign='60'
network.lan.ip6addr='2a00:1508:a0d:fe00::16:d9e8/64'
network.lan.ipaddr='10.13.217.232'
network.lan.netmask='255.255.0.0'
network.lan.mtu='1500'
network.lan.ifname='bat0' 'eth0.1'
network.lan_dev=device
network.lan_dev.name='eth0.1'
network.lan_dev.macaddr='78:a3:51:16:d9:e8'
network.wan=interface
network.wan.ifname='eth0.2'
network.wan.proto='dhcp'
network.wan_dev=device
network.wan_dev.name='eth0.2'
network.wan_dev.macaddr='78:a3:51:16:d9:e9'
network.wan6=interface
network.wan6.ifname='eth0.2'
network.wan6.proto='none'
network.@switch[0]=switch
network.(a)switch[0].name='switch0'
network.(a)switch[0].reset='1'
network.(a)switch[0].enable_vlan='1'
network.@switch_vlan[0]=switch_vlan
network.(a)switch_vlan[0].device='switch0'
network.(a)switch_vlan[0].vlan='1'
network.(a)switch_vlan[0].ports='0 1 2 3 6t'
network.@switch_vlan[1]=switch_vlan
network.(a)switch_vlan[1].device='switch0'
network.(a)switch_vlan[1].vlan='2'
network.(a)switch_vlan[1].ports='4 6t'
network.lm_net_br_lan_anygw_dev=device
network.lm_net_br_lan_anygw_dev.type='macvlan'
network.lm_net_br_lan_anygw_dev.name='anygw'
network.lm_net_br_lan_anygw_dev.ifname='br-lan'
network.lm_net_br_lan_anygw_dev.macaddr='aa:aa:aa:0d:fe:aa'
network.lm_net_br_lan_anygw_if=interface
network.lm_net_br_lan_anygw_if.ifname='anygw'
network.lm_net_br_lan_anygw_if.auto='1'
network.lm_net_br_lan_anygw_if.netmask='255.255.0.0'
network.lm_net_br_lan_anygw_if.proto='static'
network.lm_net_br_lan_anygw_if.ipaddr='10.13.0.1'
network.lm_net_br_lan_anygw_if.ip6addr='2a00:1508:a0d:fe00::1/64'
network.lm_net_anygw_rule6=rule6
network.lm_net_anygw_rule6.src='2a00:1508:a0d:fe00::1/128'
network.lm_net_anygw_rule6.lookup='170'
network.lm_net_anygw_route6=route6
network.lm_net_anygw_route6.interface='lm_net_br_lan_anygw_if'
network.lm_net_anygw_route6.target='2a00:1508:a0d:fe00::/64'
network.lm_net_anygw_route6.table='170'
network.lm_net_anygw_rule4=rule
network.lm_net_anygw_rule4.src='10.13.0.1/32'
network.lm_net_anygw_rule4.lookup='170'
network.lm_net_anygw_route4=route
network.lm_net_anygw_route4.interface='lm_net_br_lan_anygw_if'
network.lm_net_anygw_route4.target='10.13.0.0'
network.lm_net_anygw_route4.netmask='255.255.0.0'
network.lm_net_anygw_route4.table='170'
network.lm_net_batadv_dummy_if=interface
network.lm_net_batadv_dummy_if.ifname='dummy0'
network.lm_net_batadv_dummy_if.macaddr='aa:a3:51:16:d9:e8'
network.lm_net_batadv_dummy_if.proto='batadv'
network.lm_net_batadv_dummy_if.mesh='bat0'
network.lm_net_eth0_1_bmx6_dev=device
network.lm_net_eth0_1_bmx6_dev.type='8021ad'
network.lm_net_eth0_1_bmx6_dev.name='eth0-1_13'
network.lm_net_eth0_1_bmx6_dev.ifname='eth0.1'
network.lm_net_eth0_1_bmx6_dev.vid='13'
network.lm_net_eth0_1_bmx6_dev.mtu='1398'
network.lm_net_eth0_1_bmx6_if=interface
network.lm_net_eth0_1_bmx6_if.proto='none'
network.lm_net_eth0_1_bmx6_if.auto='1'
network.lm_net_eth0_1_bmx6_if.ifname='eth0-1_13'
network.lm_net_wlan0_mesh_batadv_dev=device
network.lm_net_wlan0_mesh_batadv_dev.type='8021ad'
network.lm_net_wlan0_mesh_batadv_dev.name='wlan0-mesh_29'
network.lm_net_wlan0_mesh_batadv_dev.ifname='@lm_net_wlan0_mesh'
network.lm_net_wlan0_mesh_batadv_dev.vid='29'
network.lm_net_wlan0_mesh_batadv_dev.mtu='1532'
network.lm_net_wlan0_mesh_batadv_if=interface
network.lm_net_wlan0_mesh_batadv_if.auto='1'
network.lm_net_wlan0_mesh_batadv_if.ifname='wlan0-mesh_29'
network.lm_net_wlan0_mesh_batadv_if.proto='batadv'
network.lm_net_wlan0_mesh_batadv_if.mesh='bat0'
network.lm_net_wlan0_mesh_bmx6_dev=device
network.lm_net_wlan0_mesh_bmx6_dev.type='8021ad'
network.lm_net_wlan0_mesh_bmx6_dev.name='wlan0-mesh_13'
network.lm_net_wlan0_mesh_bmx6_dev.ifname='@lm_net_wlan0_mesh'
network.lm_net_wlan0_mesh_bmx6_dev.vid='13'
network.lm_net_wlan0_mesh_bmx6_dev.mtu='1398'
network.lm_net_wlan0_mesh_bmx6_if=interface
network.lm_net_wlan0_mesh_bmx6_if.auto='1'
network.lm_net_wlan0_mesh_bmx6_if.ifname='wlan0-mesh_13'
network.lm_net_wlan0_mesh_bmx6_if.proto='static'
network.lm_net_wlan0_mesh_bmx6_if.ipaddr='169.254.217.233'
network.lm_net_wlan0_mesh_bmx6_if.netmask='255.255.255.255'
network.lm_net_wlan0_mesh=interface
network.lm_net_wlan0_mesh.proto='none'
network.lm_net_wlan0_mesh.mtu='1536'
network.lm_net_wlan0_mesh.auto='1'
network.lm_net_wlan1_mesh_batadv_dev=device
network.lm_net_wlan1_mesh_batadv_dev.type='8021ad'
network.lm_net_wlan1_mesh_batadv_dev.name='wlan1-mesh_29'
network.lm_net_wlan1_mesh_batadv_dev.ifname='@lm_net_wlan1_mesh'
network.lm_net_wlan1_mesh_batadv_dev.vid='29'
network.lm_net_wlan1_mesh_batadv_dev.mtu='1532'
network.lm_net_wlan1_mesh_batadv_if=interface
network.lm_net_wlan1_mesh_batadv_if.auto='1'
network.lm_net_wlan1_mesh_batadv_if.ifname='wlan1-mesh_29'
network.lm_net_wlan1_mesh_batadv_if.proto='batadv'
network.lm_net_wlan1_mesh_batadv_if.mesh='bat0'
network.lm_net_wlan1_mesh_bmx6_dev=device
network.lm_net_wlan1_mesh_bmx6_dev.type='8021ad'
network.lm_net_wlan1_mesh_bmx6_dev.name='wlan1-mesh_13'
network.lm_net_wlan1_mesh_bmx6_dev.ifname='@lm_net_wlan1_mesh'
network.lm_net_wlan1_mesh_bmx6_dev.vid='13'
network.lm_net_wlan1_mesh_bmx6_dev.mtu='1398'
network.lm_net_wlan1_mesh_bmx6_if=interface
network.lm_net_wlan1_mesh_bmx6_if.auto='1'
network.lm_net_wlan1_mesh_bmx6_if.ifname='wlan1-mesh_13'
network.lm_net_wlan1_mesh_bmx6_if.proto='static'
network.lm_net_wlan1_mesh_bmx6_if.ipaddr='169.254.217.232'
network.lm_net_wlan1_mesh_bmx6_if.netmask='255.255.255.255'
network.lm_net_wlan1_mesh=interface
network.lm_net_wlan1_mesh.proto='none'
network.lm_net_wlan1_mesh.mtu='1536'
network.lm_net_wlan1_mesh.auto='1'
network.lm_net_eth0_bmx6_dev=device
network.lm_net_eth0_bmx6_dev.type='8021ad'
network.lm_net_eth0_bmx6_dev.name='eth0_13'
network.lm_net_eth0_bmx6_dev.ifname='eth0'
network.lm_net_eth0_bmx6_dev.vid='13'
network.lm_net_eth0_bmx6_dev.mtu='1398'
network.lm_net_eth0_bmx6_if=interface
network.lm_net_eth0_bmx6_if.proto='none'
network.lm_net_eth0_bmx6_if.auto='1'
network.lm_net_eth0_bmx6_if.ifname='eth0_13'
network.lm_net_eth0_2_batadv_dev=device
network.lm_net_eth0_2_batadv_dev.type='8021ad'
network.lm_net_eth0_2_batadv_dev.name='eth0-2_29'
network.lm_net_eth0_2_batadv_dev.ifname='eth0.2'
network.lm_net_eth0_2_batadv_dev.vid='29'
network.lm_net_eth0_2_batadv_dev.mtu='1532'
network.lm_net_eth0_2_batadv_if=interface
network.lm_net_eth0_2_batadv_if.auto='1'
network.lm_net_eth0_2_batadv_if.ifname='eth0-2_29'
network.lm_net_eth0_2_batadv_if.proto='batadv'
network.lm_net_eth0_2_batadv_if.mesh='bat0'
network.lm_net_eth0_2_bmx6_dev=device
network.lm_net_eth0_2_bmx6_dev.type='8021ad'
network.lm_net_eth0_2_bmx6_dev.name='eth0-2_13'
network.lm_net_eth0_2_bmx6_dev.ifname='eth0.2'
network.lm_net_eth0_2_bmx6_dev.vid='13'
network.lm_net_eth0_2_bmx6_dev.mtu='1398'
network.lm_net_eth0_2_bmx6_if=interface
network.lm_net_eth0_2_bmx6_if.proto='none'
network.lm_net_eth0_2_bmx6_if.auto='1'
network.lm_net_eth0_2_bmx6_if.ifname='eth0-2_13'
root@LiMe-16d9e8:~# uci show lime
lime.system=lime
lime.network=lime
lime.wifi=lime
lime.lm_hwd_openwrt_wan=net
lime.lm_hwd_openwrt_wan.autogenerated='true'
lime.lm_hwd_openwrt_wan.protocols='anygw' 'batadv:%N1'
'bmx6:13' 'olsr:14'
'olsr6:15' 'olsr2:16' 'ieee80211s' 'wan'
lime.lm_hwd_openwrt_wan.linux_name='eth0.2'
root@LiMe-16d9e8:~#
Pau <pau(a)dabax.net> schrieb am Di., 23. Mai 2017 um 13:17 Uhr:
On 23/05/17 04:24, Juergen Kimmel wrote:
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
--
./p4u
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
Maybe this clarifies:
[ 23.650087] batman_adv: bat0: Changing gw mode from: off to: client
[ 23.703459] batman_adv: bat0: multicast_mode: Changing from: enabled
to:
disabled
[ 23.742264] batman_adv: The newly added mac address
(78:a3:51:16:d9:e9)
already exists on: eth0-2_29
[ 23.751672] batman_adv: It is strongly recommended to keep mac
addresses
unique to avoid problems!
That should not be a real problem, just annoying.
Juergen Kimmel <juergenkimmel(a)gmail.com>
schrieb am Mo., 22. Mai 2017 um
20:25 Uhr:
> Hi all,
> flashed the precompiled binary.
>
> Interface WAN does not come up WAN6 does. So I can't test stability in
> concern of internet traffic.
Does the system recognizes the eth1 device? (ip link show)
Can you paste the output of "uci show network" and "uci show lime" ?
Thanks.
> Minor flaw: Meshpoint SSID isn't set as
usual.
> About every 10 sec dmesg: br-lan: received packet on bat0 with own
> address as source address
> Devices mesh as expected.
>
> Cheers
>
> Pau <pau(a)dabax.net> schrieb am Mo., 22. Mai 2017 um 11:15 Uhr:
>
>>
>>
>> On 21/05/17 23:30, Juergen Kimmel wrote:
>>> Hi Ilario you got me. Has been a typo - minus instead of underscore -.
>>> So this time output ok.
>>> But also this firmware ends in a bootloop triggered by traffic.
>>> Still waiting for daniel golle's efforts on mt7620 drivers
>>>
>>> Cheers
>>
>> Hi Jurgen.
>>
>> There is a patch which may fix some stuff related with 802.11s, but it
>> is not applied automatically. Please, make sure you are using the last
>> lime-sdk (execute git pull).
>>
>> You have to manually execute a script snippet like this:
>>
>> bash snippets/patch_sdk_mac80211.sh
>>
>> Then recompile the packages:
>>
>> ./cooker -b ramips/mt7620
>>
>> And finally cook the firmware
>>
>> ./cooker -c ramips/mt7620 --flavor=lime_default --profile=zbt-ape522ii
>>
>> Recently I added a way to enable 11s by default (instead of adhoc) in
>> the firmware, you have to use a community profile like this:
>>
>> ./cooker -c ramips/mt7620 --flavor=lime_default --profile=zbt-ape522ii
>> --community=libremesh/11s
>>
>> ** the communities profiles are listed here:
>> https://github.com/libremesh/network-profiles
>>
>> ** read the README.md of lime-sdk to understand what a community
profile
>> is.
>>
>> You can also download precompiled binaries with the patch and 11s
>> enabled from here:
>>
>>
>>
http://repo.libremesh.org/lime-17.04/targets/ramips/mt7620/zbt-ape522ii/lim…
>>
>> Please, let us know if it works for you. I don't have this hardware and
>> I cannot test by myself.
>>
>> Cheers.
>>
>>>
>>> Ilario Gelmetti <iochesonome(a)gmail.com> schrieb am So., 21. Mai 2017
um
>>> 11:42 Uhr:
>>>
>>>> On 05/20/2017 11:55 PM, Juergen Kimmel wrote:
>>>>> Cooking went flawlessly but output has been a vanilla Lede
firmware.
>>>>> Did I overlook something?
>>>>
>>>> Can you post the cooker command you used?
>>>> I tried to replicate using:
>>>> ./cooker -c ramips/mt7620 --flavor=lime_default
--profile=zbt-ape522ii
>>>> --update-feeds
>>>>
>>>> and I got:
>>>> ls output/ramips/mt7620/zbt-ape522ii/lime_default/
>>>> lede-17.01.1-libremesh-ramips-mt7620-device-zbt-ape522ii.manifest
>>>>
>>
lede-17.01.1-libremesh-ramips-mt7620-zbt-ape522ii-squashfs-sysupgrade.bin
>>>> sha256sums
>>>>
>>>> I can't verify if the image works but I can say it contains many
>>>> LibreMesh related files, using:
>>>> binwalk -e
>>>>
>>
lede-17.01.1-libremesh-ramips-mt7620-zbt-ape522ii-squashfs-sysupgrade.bin
>>
>> Did you use a different lime-sdk command?
>> Can you check the firmware image content with binwalk (is there any
>> other way)?
>> Bye!
>> Ilario
>>
>>
>> _______________________________________________
>> 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
>
--
./p4u
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
12:38 p.m.
Everything looks correct to me.
If the internal switch is configured correctly by LEDE. eth0.1 should be
LAN and eth0.2 should be wan. So, unless there is some problem with the
internal switch management, it should work.
You can try to execute manually a dhcp client call after connecting the
WAN port to an Internet router with dhcp server: udhcpc -i eth0.2
You can also try a manual IP configuration (depending on the IP range):
ip addr add 192.168.1.2/24 dev eth0.2
ip route add default via 192.168.1.1
Hope it helps.
On 24/05/17 03:43, Juergen Kimmel wrote:
Here come the data:
login as: root
root(a)10.13.0.1's password:
BusyBox v1.25.1 () built-in shell (ash)
_________
/ /\ _ ___ ___ ___
/ LE / \ | | | __| \| __|
/ DE / \ | |__| _|| |) | _|
/________/ LE \ |____|___|___/|___|
lede-project.org
\ \ DE /
\ LE \ /
-----------------------------------------------------------
\ DE \ / Reboot (17.01.1, r3316-7eb58cf109)
\________\/
-----------------------------------------------------------
___ __ __ _______ __
| |_|__| |--.----.-----.| | |-----.-----| |--.
| | | _ | _| -__|| | -__|__ --| |
|_____|__|_____|__| |_____||__|_|__|_____|_____|__|__|
------------------------------------------------------
LiMe 0.0 development (develop rev.6ded289 20170522_1204)
------------------------------------------------------
http://libremesh.org
------------------------------------------------------
=== System Notes =====================================
======================================================
root@LiMe-16d9e8:~# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state
UNKNOWN mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e8 brd ff:ff:ff:ff:ff:ff
3: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN mode DEFAULT group
default qlen 1
link/tunnel6 :: brd ::
4: dummy0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue master bat0
state UNKNOWN mode DEFAULT group default qlen 1000
link/ether aa:a3:51:16:d9:e8 brd ff:ff:ff:ff:ff:ff
7: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e8 brd ff:ff:ff:ff:ff:ff
8: eth0.1@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
master br-lan state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e8 brd ff:ff:ff:ff:ff:ff
9: anygw@br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UNKNOWN mode DEFAULT group default qlen 1
link/ether aa:aa:aa:0d:fe:aa brd ff:ff:ff:ff:ff:ff
10: eth0-1_13(a)eth0.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1398 qdisc
noqueue state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e8 brd ff:ff:ff:ff:ff:ff
11: eth0.2@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e9 brd ff:ff:ff:ff:ff:ff
12: eth0-2_13(a)eth0.2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1398 qdisc
noqueue state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e9 brd ff:ff:ff:ff:ff:ff
13: eth0-2_29(a)eth0.2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
noqueue master bat0 state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e9 brd ff:ff:ff:ff:ff:ff
14: eth0_13@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1398 qdisc noqueue
state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e8 brd ff:ff:ff:ff:ff:ff
15: bat0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master
br-lan state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 16:f1:88:98:5f:0b brd ff:ff:ff:ff:ff:ff
16: bmxmain@NONE: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1452 qdisc noqueue
state UNKNOWN mode DEFAULT group default qlen 1
link/tunnel6 fd66:66:66:a:7aa3:51ff:fe16:d9e8 peer
fd66:66:66:ff00:7aa3:51ff:fe16:d9e8
17: wlan1-mesh: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1536 qdisc mq state
UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e8 brd ff:ff:ff:ff:ff:ff
18: wlan0-mesh: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1536 qdisc noqueue
state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e9 brd ff:ff:ff:ff:ff:ff
19: wlan1-ap: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master
br-lan state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e9 brd ff:ff:ff:ff:ff:ff
20: wlan0-ap: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
master br-lan state UP mode DEFAULT group default qlen 1000
link/ether 7a:a3:51:16:d9:e9 brd ff:ff:ff:ff:ff:ff
21: wlan0-apname: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
master br-lan state UP mode DEFAULT group default qlen 1000
link/ether 7e:a3:51:16:d9:e9 brd ff:ff:ff:ff:ff:ff
22: wlan1-apname: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq
master br-lan state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:ea brd ff:ff:ff:ff:ff:ff
23: wlan1-mesh_13@wlan1-mesh: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1398
qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e8 brd ff:ff:ff:ff:ff:ff
24: wlan1-mesh_29@wlan1-mesh: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1532
qdisc noqueue master bat0 state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e8 brd ff:ff:ff:ff:ff:ff
25: wlan0-mesh_13@wlan0-mesh: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1398
qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e9 brd ff:ff:ff:ff:ff:ff
26: wlan0-mesh_29@wlan0-mesh: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1532
qdisc noqueue master bat0 state UP mode DEFAULT group default qlen 1000
link/ether 78:a3:51:16:d9:e9 brd ff:ff:ff:ff:ff:ff
27: bmxC4main: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc
fq_codel state UNKNOWN mode DEFAULT group default qlen 500
link/none
28: bmxC6main: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc
fq_codel state UNKNOWN mode DEFAULT group default qlen 500
link/none
root@LiMe-16d9e8:~# uci show network
network.loopback=interface
network.loopback.ifname='lo'
network.loopback.proto='static'
network.loopback.ipaddr='127.0.0.1'
network.loopback.netmask='255.0.0.0'
network.globals=globals
network.lan=interface
network.lan.type='bridge'
network.lan.proto='static'
network.lan.ip6assign='60'
network.lan.ip6addr='2a00:1508:a0d:fe00::16:d9e8/64'
network.lan.ipaddr='10.13.217.232'
network.lan.netmask='255.255.0.0'
network.lan.mtu='1500'
network.lan.ifname='bat0' 'eth0.1'
network.lan_dev=device
network.lan_dev.name='eth0.1'
network.lan_dev.macaddr='78:a3:51:16:d9:e8'
network.wan=interface
network.wan.ifname='eth0.2'
network.wan.proto='dhcp'
network.wan_dev=device
network.wan_dev.name='eth0.2'
network.wan_dev.macaddr='78:a3:51:16:d9:e9'
network.wan6=interface
network.wan6.ifname='eth0.2'
network.wan6.proto='none'
network.@switch[0]=switch
network.(a)switch[0].name='switch0'
network.(a)switch[0].reset='1'
network.(a)switch[0].enable_vlan='1'
network.@switch_vlan[0]=switch_vlan
network.(a)switch_vlan[0].device='switch0'
network.(a)switch_vlan[0].vlan='1'
network.(a)switch_vlan[0].ports='0 1 2 3 6t'
network.@switch_vlan[1]=switch_vlan
network.(a)switch_vlan[1].device='switch0'
network.(a)switch_vlan[1].vlan='2'
network.(a)switch_vlan[1].ports='4 6t'
network.lm_net_br_lan_anygw_dev=device
network.lm_net_br_lan_anygw_dev.type='macvlan'
network.lm_net_br_lan_anygw_dev.name='anygw'
network.lm_net_br_lan_anygw_dev.ifname='br-lan'
network.lm_net_br_lan_anygw_dev.macaddr='aa:aa:aa:0d:fe:aa'
network.lm_net_br_lan_anygw_if=interface
network.lm_net_br_lan_anygw_if.ifname='anygw'
network.lm_net_br_lan_anygw_if.auto='1'
network.lm_net_br_lan_anygw_if.netmask='255.255.0.0'
network.lm_net_br_lan_anygw_if.proto='static'
network.lm_net_br_lan_anygw_if.ipaddr='10.13.0.1'
network.lm_net_br_lan_anygw_if.ip6addr='2a00:1508:a0d:fe00::1/64'
network.lm_net_anygw_rule6=rule6
network.lm_net_anygw_rule6.src='2a00:1508:a0d:fe00::1/128'
network.lm_net_anygw_rule6.lookup='170'
network.lm_net_anygw_route6=route6
network.lm_net_anygw_route6.interface='lm_net_br_lan_anygw_if'
network.lm_net_anygw_route6.target='2a00:1508:a0d:fe00::/64'
network.lm_net_anygw_route6.table='170'
network.lm_net_anygw_rule4=rule
network.lm_net_anygw_rule4.src='10.13.0.1/32'
network.lm_net_anygw_rule4.lookup='170'
network.lm_net_anygw_route4=route
network.lm_net_anygw_route4.interface='lm_net_br_lan_anygw_if'
network.lm_net_anygw_route4.target='10.13.0.0'
network.lm_net_anygw_route4.netmask='255.255.0.0'
network.lm_net_anygw_route4.table='170'
network.lm_net_batadv_dummy_if=interface
network.lm_net_batadv_dummy_if.ifname='dummy0'
network.lm_net_batadv_dummy_if.macaddr='aa:a3:51:16:d9:e8'
network.lm_net_batadv_dummy_if.proto='batadv'
network.lm_net_batadv_dummy_if.mesh='bat0'
network.lm_net_eth0_1_bmx6_dev=device
network.lm_net_eth0_1_bmx6_dev.type='8021ad'
network.lm_net_eth0_1_bmx6_dev.name='eth0-1_13'
network.lm_net_eth0_1_bmx6_dev.ifname='eth0.1'
network.lm_net_eth0_1_bmx6_dev.vid='13'
network.lm_net_eth0_1_bmx6_dev.mtu='1398'
network.lm_net_eth0_1_bmx6_if=interface
network.lm_net_eth0_1_bmx6_if.proto='none'
network.lm_net_eth0_1_bmx6_if.auto='1'
network.lm_net_eth0_1_bmx6_if.ifname='eth0-1_13'
network.lm_net_wlan0_mesh_batadv_dev=device
network.lm_net_wlan0_mesh_batadv_dev.type='8021ad'
network.lm_net_wlan0_mesh_batadv_dev.name='wlan0-mesh_29'
network.lm_net_wlan0_mesh_batadv_dev.ifname='@lm_net_wlan0_mesh'
network.lm_net_wlan0_mesh_batadv_dev.vid='29'
network.lm_net_wlan0_mesh_batadv_dev.mtu='1532'
network.lm_net_wlan0_mesh_batadv_if=interface
network.lm_net_wlan0_mesh_batadv_if.auto='1'
network.lm_net_wlan0_mesh_batadv_if.ifname='wlan0-mesh_29'
network.lm_net_wlan0_mesh_batadv_if.proto='batadv'
network.lm_net_wlan0_mesh_batadv_if.mesh='bat0'
network.lm_net_wlan0_mesh_bmx6_dev=device
network.lm_net_wlan0_mesh_bmx6_dev.type='8021ad'
network.lm_net_wlan0_mesh_bmx6_dev.name='wlan0-mesh_13'
network.lm_net_wlan0_mesh_bmx6_dev.ifname='@lm_net_wlan0_mesh'
network.lm_net_wlan0_mesh_bmx6_dev.vid='13'
network.lm_net_wlan0_mesh_bmx6_dev.mtu='1398'
network.lm_net_wlan0_mesh_bmx6_if=interface
network.lm_net_wlan0_mesh_bmx6_if.auto='1'
network.lm_net_wlan0_mesh_bmx6_if.ifname='wlan0-mesh_13'
network.lm_net_wlan0_mesh_bmx6_if.proto='static'
network.lm_net_wlan0_mesh_bmx6_if.ipaddr='169.254.217.233'
network.lm_net_wlan0_mesh_bmx6_if.netmask='255.255.255.255'
network.lm_net_wlan0_mesh=interface
network.lm_net_wlan0_mesh.proto='none'
network.lm_net_wlan0_mesh.mtu='1536'
network.lm_net_wlan0_mesh.auto='1'
network.lm_net_wlan1_mesh_batadv_dev=device
network.lm_net_wlan1_mesh_batadv_dev.type='8021ad'
network.lm_net_wlan1_mesh_batadv_dev.name='wlan1-mesh_29'
network.lm_net_wlan1_mesh_batadv_dev.ifname='@lm_net_wlan1_mesh'
network.lm_net_wlan1_mesh_batadv_dev.vid='29'
network.lm_net_wlan1_mesh_batadv_dev.mtu='1532'
network.lm_net_wlan1_mesh_batadv_if=interface
network.lm_net_wlan1_mesh_batadv_if.auto='1'
network.lm_net_wlan1_mesh_batadv_if.ifname='wlan1-mesh_29'
network.lm_net_wlan1_mesh_batadv_if.proto='batadv'
network.lm_net_wlan1_mesh_batadv_if.mesh='bat0'
network.lm_net_wlan1_mesh_bmx6_dev=device
network.lm_net_wlan1_mesh_bmx6_dev.type='8021ad'
network.lm_net_wlan1_mesh_bmx6_dev.name='wlan1-mesh_13'
network.lm_net_wlan1_mesh_bmx6_dev.ifname='@lm_net_wlan1_mesh'
network.lm_net_wlan1_mesh_bmx6_dev.vid='13'
network.lm_net_wlan1_mesh_bmx6_dev.mtu='1398'
network.lm_net_wlan1_mesh_bmx6_if=interface
network.lm_net_wlan1_mesh_bmx6_if.auto='1'
network.lm_net_wlan1_mesh_bmx6_if.ifname='wlan1-mesh_13'
network.lm_net_wlan1_mesh_bmx6_if.proto='static'
network.lm_net_wlan1_mesh_bmx6_if.ipaddr='169.254.217.232'
network.lm_net_wlan1_mesh_bmx6_if.netmask='255.255.255.255'
network.lm_net_wlan1_mesh=interface
network.lm_net_wlan1_mesh.proto='none'
network.lm_net_wlan1_mesh.mtu='1536'
network.lm_net_wlan1_mesh.auto='1'
network.lm_net_eth0_bmx6_dev=device
network.lm_net_eth0_bmx6_dev.type='8021ad'
network.lm_net_eth0_bmx6_dev.name='eth0_13'
network.lm_net_eth0_bmx6_dev.ifname='eth0'
network.lm_net_eth0_bmx6_dev.vid='13'
network.lm_net_eth0_bmx6_dev.mtu='1398'
network.lm_net_eth0_bmx6_if=interface
network.lm_net_eth0_bmx6_if.proto='none'
network.lm_net_eth0_bmx6_if.auto='1'
network.lm_net_eth0_bmx6_if.ifname='eth0_13'
network.lm_net_eth0_2_batadv_dev=device
network.lm_net_eth0_2_batadv_dev.type='8021ad'
network.lm_net_eth0_2_batadv_dev.name='eth0-2_29'
network.lm_net_eth0_2_batadv_dev.ifname='eth0.2'
network.lm_net_eth0_2_batadv_dev.vid='29'
network.lm_net_eth0_2_batadv_dev.mtu='1532'
network.lm_net_eth0_2_batadv_if=interface
network.lm_net_eth0_2_batadv_if.auto='1'
network.lm_net_eth0_2_batadv_if.ifname='eth0-2_29'
network.lm_net_eth0_2_batadv_if.proto='batadv'
network.lm_net_eth0_2_batadv_if.mesh='bat0'
network.lm_net_eth0_2_bmx6_dev=device
network.lm_net_eth0_2_bmx6_dev.type='8021ad'
network.lm_net_eth0_2_bmx6_dev.name='eth0-2_13'
network.lm_net_eth0_2_bmx6_dev.ifname='eth0.2'
network.lm_net_eth0_2_bmx6_dev.vid='13'
network.lm_net_eth0_2_bmx6_dev.mtu='1398'
network.lm_net_eth0_2_bmx6_if=interface
network.lm_net_eth0_2_bmx6_if.proto='none'
network.lm_net_eth0_2_bmx6_if.auto='1'
network.lm_net_eth0_2_bmx6_if.ifname='eth0-2_13'
root@LiMe-16d9e8:~# uci show lime
lime.system=lime
lime.network=lime
lime.wifi=lime
lime.lm_hwd_openwrt_wan=net
lime.lm_hwd_openwrt_wan.autogenerated='true'
lime.lm_hwd_openwrt_wan.protocols='anygw' 'batadv:%N1'
'bmx6:13' 'olsr:14'
'olsr6:15' 'olsr2:16' 'ieee80211s' 'wan'
lime.lm_hwd_openwrt_wan.linux_name='eth0.2'
root@LiMe-16d9e8:~#
Pau <pau(a)dabax.net> schrieb am Di., 23. Mai 2017 um 13:17 Uhr:
--
./p4u
On 23/05/17 04:24, Juergen Kimmel wrote:
--
./p4u
_______________________________________________
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
Maybe this clarifies:
[ 23.650087] batman_adv: bat0: Changing gw mode from: off to: client
[ 23.703459] batman_adv: bat0: multicast_mode: Changing from: enabled
to:
disabled
[ 23.742264] batman_adv: The newly added mac address
(78:a3:51:16:d9:e9)
already exists on: eth0-2_29
[ 23.751672] batman_adv: It is strongly recommended to keep mac
addresses
unique to avoid problems!
That should not be a real problem, just annoying.
Juergen Kimmel <juergenkimmel(a)gmail.com>
schrieb am Mo., 22. Mai 2017 um
20:25 Uhr:
> Hi all,
> flashed the precompiled binary.
>
> Interface WAN does not come up WAN6 does. So I can't test stability in
> concern of internet traffic.
Does the system recognizes the eth1 device? (ip link show)
Can you paste the output of "uci show network" and "uci show lime" ?
Thanks.
> Minor flaw: Meshpoint SSID isn't set as
usual.
> About every 10 sec dmesg: br-lan: received packet on bat0 with own
> address as source address
> Devices mesh as expected.
>
> Cheers
>
> Pau <pau(a)dabax.net> schrieb am Mo., 22. Mai 2017 um 11:15 Uhr:
>
>>
>>
>> On 21/05/17 23:30, Juergen Kimmel wrote:
>>> Hi Ilario you got me. Has been a typo - minus instead of underscore -.
>>> So this time output ok.
>>> But also this firmware ends in a bootloop triggered by traffic.
>>> Still waiting for daniel golle's efforts on mt7620 drivers
>>>
>>> Cheers
>>
>> Hi Jurgen.
>>
>> There is a patch which may fix some stuff related with 802.11s, but it
>> is not applied automatically. Please, make sure you are using the last
>> lime-sdk (execute git pull).
>>
>> You have to manually execute a script snippet like this:
>>
>> bash snippets/patch_sdk_mac80211.sh
>>
>> Then recompile the packages:
>>
>> ./cooker -b ramips/mt7620
>>
>> And finally cook the firmware
>>
>> ./cooker -c ramips/mt7620 --flavor=lime_default --profile=zbt-ape522ii
>>
>> Recently I added a way to enable 11s by default (instead of adhoc) in
>> the firmware, you have to use a community profile like this:
>>
>> ./cooker -c ramips/mt7620 --flavor=lime_default --profile=zbt-ape522ii
>> --community=libremesh/11s
>>
>> ** the communities profiles are listed here:
>> https://github.com/libremesh/network-profiles
>>
>> ** read the README.md of lime-sdk to understand what a community
profile
>> is.
>>
>> You can also download precompiled binaries with the patch and 11s
>> enabled from here:
>>
>>
>>
http://repo.libremesh.org/lime-17.04/targets/ramips/mt7620/zbt-ape522ii/lim…
>>
>> Please, let us know if it works for you. I don't have this hardware and
>> I cannot test by myself.
>>
>> Cheers.
>>
>>>
>>> Ilario Gelmetti <iochesonome(a)gmail.com> schrieb am So., 21. Mai 2017
um
>>> 11:42 Uhr:
>>>
>>>> On 05/20/2017 11:55 PM, Juergen Kimmel wrote:
>>>>> Cooking went flawlessly but output has been a vanilla Lede
firmware.
>>>>> Did I overlook something?
>>>>
>>>> Can you post the cooker command you used?
>>>> I tried to replicate using:
>>>> ./cooker -c ramips/mt7620 --flavor=lime_default
--profile=zbt-ape522ii
>>>> --update-feeds
>>>>
>>>> and I got:
>>>> ls output/ramips/mt7620/zbt-ape522ii/lime_default/
>>>> lede-17.01.1-libremesh-ramips-mt7620-device-zbt-ape522ii.manifest
>>>>
>>
lede-17.01.1-libremesh-ramips-mt7620-zbt-ape522ii-squashfs-sysupgrade.bin
>>>> sha256sums
>>>>
>>>> I can't verify if the image works but I can say it contains many
>>>> LibreMesh related files, using:
>>>> binwalk -e
>>>>
>>
lede-17.01.1-libremesh-ramips-mt7620-zbt-ape522ii-squashfs-sysupgrade.bin
>>>
>>> Did you use a different lime-sdk command?
>>> Can you check the firmware image content with binwalk (is there any
>>> other way)?
>>> Bye!
>>> Ilario
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>
> --
> ./p4u
>
> _______________________________________________
> 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
2531
days inactive
2535
days old
lime-users@lists.libremesh.org
8 comments
3 participants
participants (3)
-
Ilario Gelmetti -
Juergen Kimmel -
Pau