6 Apr
2017
6 Apr
'17
8:41 a.m.
I am pretty inexperienced in compiling
I have managed to compile the master branch but not 17.02
"git clone -b 17.02 git: //github.com/libremesh/lime-build"
and
"make T = mt7620 V = s"
led to the error
"rule for checkout failed (makefile line 168)"
where is the problem?
Tx
Jürgen Kimmel
6 Apr
6 Apr
11:40 a.m.
Hi Jurgen.
I've been working on a new tool to build firmwares. Instead of using
standard buildroot it uses the LEDE SDK and ImageBuilder. It means less
compilation time (and problems) and better integration with official
LEDE releases.
To use it:
git clone https://github.com/libremesh/lime-sdk
# Download SDK and IB from LEDE
./cooker -d ar71xx/generic
# List the hardware profiles and find your own
./cooker --profiles=ar71xx/generic
# Cook the firmware for your profile using lime_default flavor
./cooker -c ar71xx/generic --flavor=lime_default --profile=tl-wdr3500-v1
The current master branch points to LEDE 17.01.0. If you want to use the
snapshot branch of LEDE checkout "development" branch of lime-sdk.
This is a new tool, I'm still working on it. Please, let me know if you
have problems.
Cheers.
On 06/04/17 10:41, Juergen Kimmel wrote:
I am pretty inexperienced in compiling
I have managed to compile the master branch but not 17.02
"git clone -b 17.02 git: //github.com/libremesh/lime-build"
and
"make T = mt7620 V = s"
led to the error
"rule for checkout failed (makefile line 168)"
where is the problem?
Tx
Jürgen Kimmel
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
--
./p4u
3:20 p.m.
Many thanks Pau,
but 'I need further instructons.
I cloned lime-sdk and lede-sdk and downloaded
lede-imagebuilder-ramips-mt7620.Linux-x86_64 so I have three folders.
Whats next?
2017-04-06 12:40 GMT+01:00 Pau <pau(a)dabax.net>et>:
Hi Jurgen.
I've been working on a new tool to build firmwares. Instead of using
standard buildroot it uses the LEDE SDK and ImageBuilder. It means less
compilation time (and problems) and better integration with official
LEDE releases.
To use it:
git clone https://github.com/libremesh/lime-sdk
# Download SDK and IB from LEDE
./cooker -d ar71xx/generic
# List the hardware profiles and find your own
./cooker --profiles=ar71xx/generic
# Cook the firmware for your profile using lime_default flavor
./cooker -c ar71xx/generic --flavor=lime_default --profile=tl-wdr3500-v1
The current master branch points to LEDE 17.01.0. If you want to use the
snapshot branch of LEDE checkout "development" branch of lime-sdk.
This is a new tool, I'm still working on it. Please, let me know if you
have problems.
Cheers.
On 06/04/17 10:41, Juergen Kimmel wrote:
--
Mit freundlichen Grüssen
Jürgen Kimmel
I am pretty inexperienced in compiling
I have managed to compile the master branch but not 17.02
"git clone -b 17.02 git: //github.com/libremesh/lime-build"
and
"make T = mt7620 V = s"
led to the error
"rule for checkout failed (makefile line 168)"
where is the problem?
Tx
Jürgen Kimmel
_______________________________________________
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
3:32 p.m.
On 06/04/17 17:20, Juergen Kimmel wrote:
Many thanks Pau,
but 'I need further instructons.
I cloned lime-sdk and lede-sdk and downloaded
lede-imagebuilder-ramips-mt7620.Linux-x86_64 so I have three folders.
Whats next?
I think you misunderstood me. The lime-sdk makes everything for you, you
don't actually need to manually download anything else than lime-sdk.
The comments (starting with # in my previous mail) where to explain what
is the command doing.
Here the clean list of commands you might execute to compile for target
ramips/mt7620.
git clone https://github.com/libremesh/lime-sdk
cd lime-sdk
./cooker --profiles=ramips/mt7620
# Find the name of your hardware profile on this list
./cooker -c ramips/mt7620 --flavor=lime_default --profile=YOUR_PROFILE
That is all, once it finishes you'll find the firmware in the output/
directory.
Please, run "git pull" if you are not cloning a new lime-sdk but using
and old cloned one.
Also, I just implemented support for --remote so you don't need to
compile the SDK (all libremesh packages will be also downloaded instead
of localy compiled).
For using such feature, execute the cooker like this:
./cooker -c ramips/mt7620 --remote --flavor=lime_default
--profile=YOUR_PROFILE
Lastly, you can also use the current precompiled (using the cooker)
binaries at http://repo.libremesh.org (not yet official).
Cheers.
2017-04-06 12:40 GMT+01:00 Pau <pau(a)dabax.net>et>:
--
./p4u
Hi Jurgen.
I've been working on a new tool to build firmwares. Instead of using
standard buildroot it uses the LEDE SDK and ImageBuilder. It means less
compilation time (and problems) and better integration with official
LEDE releases.
To use it:
git clone https://github.com/libremesh/lime-sdk
# Download SDK and IB from LEDE
./cooker -d ar71xx/generic
# List the hardware profiles and find your own
./cooker --profiles=ar71xx/generic
# Cook the firmware for your profile using lime_default flavor
./cooker -c ar71xx/generic --flavor=lime_default --profile=tl-wdr3500-v1
The current master branch points to LEDE 17.01.0. If you want to use the
snapshot branch of LEDE checkout "development" branch of lime-sdk.
This is a new tool, I'm still working on it. Please, let me know if you
have problems.
Cheers.
On 06/04/17 10:41, Juergen Kimmel wrote:
I am pretty inexperienced in compiling
I have managed to compile the master branch but not 17.02
"git clone -b 17.02 git: //github.com/libremesh/lime-build"
and
"make T = mt7620 V = s"
led to the error
"rule for checkout failed (makefile line 168)"
where is the problem?
Tx
Jürgen Kimmel
_______________________________________________
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
7 Apr
7 Apr
3:26 a.m.
Thankk you again Pau,
I used the option precompiled binaries.
Here I got stuck that the clients don't get internet despite the fact that
network diagnostics on the node runs fine.
Regards
Pau <pau(a)dabax.net> schrieb am Do., 6. Apr. 2017 um 17:32 Uhr:
On 06/04/17 17:20, Juergen Kimmel wrote:
Many thanks Pau,
but 'I need further instructons.
I cloned lime-sdk and lede-sdk and downloaded
lede-imagebuilder-ramips-mt7620.Linux-x86_64 so I have three folders.
Whats next?
I think you misunderstood me. The lime-sdk makes everything for you, you
don't actually need to manually download anything else than lime-sdk.
The comments (starting with # in my previous mail) where to explain what
is the command doing.
Here the clean list of commands you might execute to compile for target
ramips/mt7620.
git clone https://github.com/libremesh/lime-sdk
cd lime-sdk
./cooker --profiles=ramips/mt7620
# Find the name of your hardware profile on this list
./cooker -c ramips/mt7620 --flavor=lime_default --profile=YOUR_PROFILE
That is all, once it finishes you'll find the firmware in the output/
directory.
Please, run "git pull" if you are not cloning a new lime-sdk but using
and old cloned one.
Also, I just implemented support for --remote so you don't need to
compile the SDK (all libremesh packages will be also downloaded instead
of localy compiled).
For using such feature, execute the cooker like this:
./cooker -c ramips/mt7620 --remote --flavor=lime_default
--profile=YOUR_PROFILE
Lastly, you can also use the current precompiled (using the cooker)
binaries at http://repo.libremesh.org (not yet official).
Cheers.
2017-04-06 12:40 GMT+01:00 Pau
<pau(a)dabax.net>et>:
--
./p4u
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users Hi Jurgen.
I've been working on a new tool to build firmwares. Instead of using
standard buildroot it uses the LEDE SDK and ImageBuilder. It means less
compilation time (and problems) and better integration with official
LEDE releases.
To use it:
git clone https://github.com/libremesh/lime-sdk
# Download SDK and IB from LEDE
./cooker -d ar71xx/generic
# List the hardware profiles and find your own
./cooker --profiles=ar71xx/generic
# Cook the firmware for your profile using lime_default flavor
./cooker -c ar71xx/generic --flavor=lime_default --profile=tl-wdr3500-v1
The current master branch points to LEDE 17.01.0. If you want to use the
snapshot branch of LEDE checkout "development" branch of lime-sdk.
This is a new tool, I'm still working on it. Please, let me know if you
have problems.
Cheers.
On 06/04/17 10:41, Juergen Kimmel wrote:
I am pretty inexperienced in compiling
I have managed to compile the master branch but not 17.02
"git clone -b 17.02 git: //github.com/libremesh/lime-build"
and
"make T = mt7620 V = s"
led to the error
"rule for checkout failed (makefile line 168)"
where is the problem?
Tx
Jürgen Kimmel
_______________________________________________
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
4:28 a.m.
edit:
"the clients of *gateway *nodes don't get internet ( no ping response) even
after having changed wan proto to dhcp. So wan connects to the internet
router"
Having read that adhoc does not work properly in mt7620 I changed to
802.11s but here is no meshing.
I changed lan interface static address to avoid problems with my lan
(192.168.1.0) but nevertheless the gateway node tangles my lan makes it
slow if not unusable.
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Fr., 7. Apr. 2017 um
05:26 Uhr:
Thankk you again Pau,
I used the option precompiled binaries.
Here I got stuck that the clients don't get internet despite the fact that
network diagnostics on the node runs fine.
Regards
Pau <pau(a)dabax.net> schrieb am Do., 6. Apr. 2017 um 17:32 Uhr:
On 06/04/17 17:20, Juergen Kimmel wrote:
Many thanks Pau,
but 'I need further instructons.
I cloned lime-sdk and lede-sdk and downloaded
lede-imagebuilder-ramips-mt7620.Linux-x86_64 so I have three folders.
Whats next?
I think you misunderstood me. The lime-sdk makes everything for you, you
don't actually need to manually download anything else than lime-sdk.
The comments (starting with # in my previous mail) where to explain what
is the command doing.
Here the clean list of commands you might execute to compile for target
ramips/mt7620.
git clone https://github.com/libremesh/lime-sdk
cd lime-sdk
./cooker --profiles=ramips/mt7620
# Find the name of your hardware profile on this list
./cooker -c ramips/mt7620 --flavor=lime_default --profile=YOUR_PROFILE
That is all, once it finishes you'll find the firmware in the output/
directory.
Please, run "git pull" if you are not cloning a new lime-sdk but using
and old cloned one.
Also, I just implemented support for --remote so you don't need to
compile the SDK (all libremesh packages will be also downloaded instead
of localy compiled).
For using such feature, execute the cooker like this:
./cooker -c ramips/mt7620 --remote --flavor=lime_default
--profile=YOUR_PROFILE
Lastly, you can also use the current precompiled (using the cooker)
binaries at http://repo.libremesh.org (not yet official).
Cheers.
2017-04-06 12:40 GMT+01:00 Pau
<pau(a)dabax.net>et>:
--
./p4u
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
Hi Jurgen.
I've been working on a new tool to build firmwares. Instead of using
standard buildroot it uses the LEDE SDK and ImageBuilder. It means less
compilation time (and problems) and better integration with official
LEDE releases.
To use it:
git clone https://github.com/libremesh/lime-sdk
# Download SDK and IB from LEDE
./cooker -d ar71xx/generic
# List the hardware profiles and find your own
./cooker --profiles=ar71xx/generic
# Cook the firmware for your profile using lime_default flavor
./cooker -c ar71xx/generic --flavor=lime_default --profile=tl-wdr3500-v1
The current master branch points to LEDE 17.01.0. If you want to use the
snapshot branch of LEDE checkout "development" branch of lime-sdk.
This is a new tool, I'm still working on it. Please, let me know if you
have problems.
Cheers.
On 06/04/17 10:41, Juergen Kimmel wrote:
I am pretty inexperienced in compiling
I have managed to compile the master branch but not 17.02
"git clone -b 17.02 git: //github.com/libremesh/lime-build"
and
"make T = mt7620 V = s"
led to the error
"rule for checkout failed (makefile line 168)"
where is the problem?
Tx
Jürgen Kimmel
_______________________________________________
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
8 Apr
8 Apr
12:24 a.m.
There is no channel assigned to the meshing radio1
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Fr., 7. Apr. 2017 um
06:28 Uhr:
edit:
"the clients of *gateway *nodes don't get internet ( no ping response)
even after having changed wan proto to dhcp. So wan connects to the
internet router"
Having read that adhoc does not work properly in mt7620 I changed to
802.11s but here is no meshing.
I changed lan interface static address to avoid problems with my lan
(192.168.1.0) but nevertheless the gateway node tangles my lan makes it
slow if not unusable.
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Fr., 7. Apr. 2017 um
05:26 Uhr:
Thankk you again Pau,
I used the option precompiled binaries.
Here I got stuck that the clients don't get internet despite the fact that
network diagnostics on the node runs fine.
Regards
Pau <pau(a)dabax.net> schrieb am Do., 6. Apr. 2017 um 17:32 Uhr:
On 06/04/17 17:20, Juergen Kimmel wrote:
Many thanks Pau,
but 'I need further instructons.
I cloned lime-sdk and lede-sdk and downloaded
lede-imagebuilder-ramips-mt7620.Linux-x86_64 so I have three folders.
Whats next?
I think you misunderstood me. The lime-sdk makes everything for you, you
don't actually need to manually download anything else than lime-sdk.
The comments (starting with # in my previous mail) where to explain what
is the command doing.
Here the clean list of commands you might execute to compile for target
ramips/mt7620.
git clone https://github.com/libremesh/lime-sdk
cd lime-sdk
./cooker --profiles=ramips/mt7620
# Find the name of your hardware profile on this list
./cooker -c ramips/mt7620 --flavor=lime_default --profile=YOUR_PROFILE
That is all, once it finishes you'll find the firmware in the output/
directory.
Please, run "git pull" if you are not cloning a new lime-sdk but using
and old cloned one.
Also, I just implemented support for --remote so you don't need to
compile the SDK (all libremesh packages will be also downloaded instead
of localy compiled).
For using such feature, execute the cooker like this:
./cooker -c ramips/mt7620 --remote --flavor=lime_default
--profile=YOUR_PROFILE
Lastly, you can also use the current precompiled (using the cooker)
binaries at http://repo.libremesh.org (not yet official).
Cheers.
2017-04-06 12:40 GMT+01:00 Pau
<pau(a)dabax.net>et>:
--
./p4u
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
Hi Jurgen.
I've been working on a new tool to build firmwares. Instead of using
standard buildroot it uses the LEDE SDK and ImageBuilder. It means less
compilation time (and problems) and better integration with official
LEDE releases.
To use it:
git clone https://github.com/libremesh/lime-sdk
# Download SDK and IB from LEDE
./cooker -d ar71xx/generic
# List the hardware profiles and find your own
./cooker --profiles=ar71xx/generic
# Cook the firmware for your profile using lime_default flavor
./cooker -c ar71xx/generic --flavor=lime_default --profile=tl-wdr3500-v1
The current master branch points to LEDE 17.01.0. If you want to use the
snapshot branch of LEDE checkout "development" branch of lime-sdk.
This is a new tool, I'm still working on it. Please, let me know if you
have problems.
Cheers.
On 06/04/17 10:41, Juergen Kimmel wrote:
I am pretty inexperienced in compiling
I have managed to compile the master branch but not 17.02
"git clone -b 17.02 git: //github.com/libremesh/lime-build"
and
"make T = mt7620 V = s"
led to the error
"rule for checkout failed (makefile line 168)"
where is the problem?
Tx
Jürgen Kimmel
_______________________________________________
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:33 a.m.
Status overview reports wlano-adhoc nodes but no mesh nodes
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Sa., 8. Apr. 2017 um
02:24 Uhr:
There is no channel assigned to the meshing radio1
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Fr., 7. Apr. 2017 um
06:28 Uhr:
edit:
"the clients of *gateway *nodes don't get internet ( no ping response)
even after having changed wan proto to dhcp. So wan connects to the
internet router"
Having read that adhoc does not work properly in mt7620 I changed to
802.11s but here is no meshing.
I changed lan interface static address to avoid problems with my lan
(192.168.1.0) but nevertheless the gateway node tangles my lan makes it
slow if not unusable.
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Fr., 7. Apr. 2017 um
05:26 Uhr:
Thankk you again Pau,
I used the option precompiled binaries.
Here I got stuck that the clients don't get internet despite the fact that
network diagnostics on the node runs fine.
Regards
Pau <pau(a)dabax.net> schrieb am Do., 6. Apr. 2017 um 17:32 Uhr:
On 06/04/17 17:20, Juergen Kimmel wrote:
Many thanks Pau,
but 'I need further instructons.
I cloned lime-sdk and lede-sdk and downloaded
lede-imagebuilder-ramips-mt7620.Linux-x86_64 so I have three folders.
Whats next?
I think you misunderstood me. The lime-sdk makes everything for you, you
don't actually need to manually download anything else than lime-sdk.
The comments (starting with # in my previous mail) where to explain what
is the command doing.
Here the clean list of commands you might execute to compile for target
ramips/mt7620.
git clone https://github.com/libremesh/lime-sdk
cd lime-sdk
./cooker --profiles=ramips/mt7620
# Find the name of your hardware profile on this list
./cooker -c ramips/mt7620 --flavor=lime_default --profile=YOUR_PROFILE
That is all, once it finishes you'll find the firmware in the output/
directory.
Please, run "git pull" if you are not cloning a new lime-sdk but using
and old cloned one.
Also, I just implemented support for --remote so you don't need to
compile the SDK (all libremesh packages will be also downloaded instead
of localy compiled).
For using such feature, execute the cooker like this:
./cooker -c ramips/mt7620 --remote --flavor=lime_default
--profile=YOUR_PROFILE
Lastly, you can also use the current precompiled (using the cooker)
binaries at http://repo.libremesh.org (not yet official).
Cheers.
2017-04-06 12:40 GMT+01:00 Pau
<pau(a)dabax.net>et>:
--
./p4u
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
Hi Jurgen.
I've been working on a new tool to build firmwares. Instead of using
standard buildroot it uses the LEDE SDK and ImageBuilder. It means less
compilation time (and problems) and better integration with official
LEDE releases.
To use it:
git clone https://github.com/libremesh/lime-sdk
# Download SDK and IB from LEDE
./cooker -d ar71xx/generic
# List the hardware profiles and find your own
./cooker --profiles=ar71xx/generic
# Cook the firmware for your profile using lime_default flavor
./cooker -c ar71xx/generic --flavor=lime_default --profile=tl-wdr3500-v1
The current master branch points to LEDE 17.01.0. If you want to use the
snapshot branch of LEDE checkout "development" branch of lime-sdk.
This is a new tool, I'm still working on it. Please, let me know if you
have problems.
Cheers.
On 06/04/17 10:41, Juergen Kimmel wrote:
I am pretty inexperienced in compiling
I have managed to compile the master branch but not 17.02
"git clone -b 17.02 git: //github.com/libremesh/lime-build"
and
"make T = mt7620 V = s"
led to the error
"rule for checkout failed (makefile line 168)"
where is the problem?
Tx
Jürgen Kimmel
_______________________________________________
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
8:36 a.m.
Digging just a bit deeper there is no automagically libremesh configuration
at all.
Only three interfaces created (lan, wan, wan6)
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Sa., 8. Apr. 2017 um
02:33 Uhr:
Status overview reports wlano-adhoc nodes but no mesh
nodes
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Sa., 8. Apr. 2017 um
02:24 Uhr:
There is no channel assigned to the meshing radio1
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Fr., 7. Apr. 2017 um
06:28 Uhr:
edit:
"the clients of *gateway *nodes don't get internet ( no ping response)
even after having changed wan proto to dhcp. So wan connects to the
internet router"
Having read that adhoc does not work properly in mt7620 I changed to
802.11s but here is no meshing.
I changed lan interface static address to avoid problems with my lan
(192.168.1.0) but nevertheless the gateway node tangles my lan makes it
slow if not unusable.
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Fr., 7. Apr. 2017 um
05:26 Uhr:
Thankk you again Pau,
I used the option precompiled binaries.
Here I got stuck that the clients don't get internet despite the fact that
network diagnostics on the node runs fine.
Regards
Pau <pau(a)dabax.net> schrieb am Do., 6. Apr. 2017 um 17:32 Uhr:
On 06/04/17 17:20, Juergen Kimmel wrote:
Many thanks Pau,
but 'I need further instructons.
I cloned lime-sdk and lede-sdk and downloaded
lede-imagebuilder-ramips-mt7620.Linux-x86_64 so I have three folders.
Whats next?
I think you misunderstood me. The lime-sdk makes everything for you, you
don't actually need to manually download anything else than lime-sdk.
The comments (starting with # in my previous mail) where to explain what
is the command doing.
Here the clean list of commands you might execute to compile for target
ramips/mt7620.
git clone https://github.com/libremesh/lime-sdk
cd lime-sdk
./cooker --profiles=ramips/mt7620
# Find the name of your hardware profile on this list
./cooker -c ramips/mt7620 --flavor=lime_default --profile=YOUR_PROFILE
That is all, once it finishes you'll find the firmware in the output/
directory.
Please, run "git pull" if you are not cloning a new lime-sdk but using
and old cloned one.
Also, I just implemented support for --remote so you don't need to
compile the SDK (all libremesh packages will be also downloaded instead
of localy compiled).
For using such feature, execute the cooker like this:
./cooker -c ramips/mt7620 --remote --flavor=lime_default
--profile=YOUR_PROFILE
Lastly, you can also use the current precompiled (using the cooker)
binaries at http://repo.libremesh.org (not yet official).
Cheers.
2017-04-06 12:40 GMT+01:00 Pau
<pau(a)dabax.net>et>:
--
./p4u
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
Hi Jurgen.
I've been working on a new tool to build firmwares. Instead of using
standard buildroot it uses the LEDE SDK and ImageBuilder. It means less
compilation time (and problems) and better integration with official
LEDE releases.
To use it:
git clone https://github.com/libremesh/lime-sdk
# Download SDK and IB from LEDE
./cooker -d ar71xx/generic
# List the hardware profiles and find your own
./cooker --profiles=ar71xx/generic
# Cook the firmware for your profile using lime_default flavor
./cooker -c ar71xx/generic --flavor=lime_default --profile=tl-wdr3500-v1
The current master branch points to LEDE 17.01.0. If you want to use the
snapshot branch of LEDE checkout "development" branch of lime-sdk.
This is a new tool, I'm still working on it. Please, let me know if you
have problems.
Cheers.
On 06/04/17 10:41, Juergen Kimmel wrote:
I am pretty inexperienced in compiling
I have managed to compile the master branch but not 17.02
"git clone -b 17.02 git: //github.com/libremesh/lime-build"
and
"make T = mt7620 V = s"
led to the error
"rule for checkout failed (makefile line 168)"
where is the problem?
Tx
Jürgen Kimmel
_______________________________________________
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 Apr
12 Apr
11:25 a.m.
That looks like a crash during the configuration process.
Can you run "lime-config" manually on a SSH session?
On 08/04/17 10:36, Juergen Kimmel wrote:
Digging just a bit deeper there is no automagically
libremesh configuration
at all.
Only three interfaces created (lan, wan, wan6)
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Sa., 8. Apr. 2017 um
02:33 Uhr:
--
./p4u
Status overview reports wlano-adhoc nodes but no
mesh nodes
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Sa., 8. Apr. 2017 um
02:24 Uhr:
There is no channel assigned to the meshing radio1
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Fr., 7. Apr. 2017 um
06:28 Uhr:
edit:
"the clients of *gateway *nodes don't get internet ( no ping response)
even after having changed wan proto to dhcp. So wan connects to the
internet router"
Having read that adhoc does not work properly in mt7620 I changed to
802.11s but here is no meshing.
I changed lan interface static address to avoid problems with my lan
(192.168.1.0) but nevertheless the gateway node tangles my lan makes it
slow if not unusable.
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Fr., 7. Apr. 2017 um
05:26 Uhr:
Thankk you again Pau,
I used the option precompiled binaries.
Here I got stuck that the clients don't get internet despite the fact that
network diagnostics on the node runs fine.
Regards
Pau <pau(a)dabax.net> schrieb am Do., 6. Apr. 2017 um 17:32 Uhr:
On 06/04/17 17:20, Juergen Kimmel wrote:
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
Many thanks Pau,
but 'I need further instructons.
I cloned lime-sdk and lede-sdk and downloaded
lede-imagebuilder-ramips-mt7620.Linux-x86_64 so I have three folders.
Whats next?
I think you misunderstood me. The lime-sdk makes everything for you, you
don't actually need to manually download anything else than lime-sdk.
The comments (starting with # in my previous mail) where to explain what
is the command doing.
Here the clean list of commands you might execute to compile for target
ramips/mt7620.
git clone https://github.com/libremesh/lime-sdk
cd lime-sdk
./cooker --profiles=ramips/mt7620
# Find the name of your hardware profile on this list
./cooker -c ramips/mt7620 --flavor=lime_default --profile=YOUR_PROFILE
That is all, once it finishes you'll find the firmware in the output/
directory.
Please, run "git pull" if you are not cloning a new lime-sdk but using
and old cloned one.
Also, I just implemented support for --remote so you don't need to
compile the SDK (all libremesh packages will be also downloaded instead
of localy compiled).
For using such feature, execute the cooker like this:
./cooker -c ramips/mt7620 --remote --flavor=lime_default
--profile=YOUR_PROFILE
Lastly, you can also use the current precompiled (using the cooker)
binaries at http://repo.libremesh.org (not yet official).
Cheers.
2017-04-06 12:40 GMT+01:00 Pau
<pau(a)dabax.net>et>:
--
./p4u
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
Hi Jurgen.
I've been working on a new tool to build firmwares. Instead of using
standard buildroot it uses the LEDE SDK and ImageBuilder. It means less
compilation time (and problems) and better integration with official
LEDE releases.
To use it:
git clone https://github.com/libremesh/lime-sdk
# Download SDK and IB from LEDE
./cooker -d ar71xx/generic
# List the hardware profiles and find your own
./cooker --profiles=ar71xx/generic
# Cook the firmware for your profile using lime_default flavor
./cooker -c ar71xx/generic --flavor=lime_default --profile=tl-wdr3500-v1
The current master branch points to LEDE 17.01.0. If you want to use the
snapshot branch of LEDE checkout "development" branch of lime-sdk.
This is a new tool, I'm still working on it. Please, let me know if you
have problems.
Cheers.
On 06/04/17 10:41, Juergen Kimmel wrote:
> I am pretty inexperienced in compiling
> I have managed to compile the master branch but not 17.02
> "git clone -b 17.02 git: //github.com/libremesh/lime-build"
> and
> "make T = mt7620 V = s"
> led to the error
> "rule for checkout failed (makefile line 168)"
>
> where is the problem?
>
> Tx
> Jürgen Kimmel
> _______________________________________________
> 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
4:36 p.m.
This is the outcome of lime-config:
root@LiMe-16da88:~# lime-config
Clearing wireless config...
Clearing network config...
Disabling odhcpd
Cleaning dnsmasq
Disabling 6relayd...
/usr/lib/lua/lime/network.lua:155: attempt to index local 'dev' (a nil value)
stack traceback:
/usr/bin/lime-config:45: in function </usr/bin/lime-config:45>
[C]: in function 'foreach'
/usr/lib/lua/lime/network.lua:192: in function 'scandevices'
/usr/lib/lua/lime/network.lua:217: in function
</usr/lib/lua/lime/network.lua:208>
[C]: in function 'xpcall'
/usr/bin/lime-config:45: in function 'main'
/usr/bin/lime-config:65: in main chunk
[C]: ?
Configuring system...
Let uhttpd listen on IPv4/IPv6
So not working at all.
Cheers
2017-04-12 13:25 GMT+02:00 Pau <pau(a)dabax.net>et>:
That looks like a crash during the configuration
process.
Can you run "lime-config" manually on a SSH session?
On 08/04/17 10:36, Juergen Kimmel wrote:
--
Mit freundlichen Grüssen
Jürgen Kimmel
Digging just a bit deeper there is no
automagically libremesh configuration
at all.
Only three interfaces created (lan, wan, wan6)
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Sa., 8. Apr. 2017 um
02:33 Uhr:
--
./p4u
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users Status overview reports wlano-adhoc nodes but no
mesh nodes
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Sa., 8. Apr. 2017 um
02:24 Uhr:
There is no channel assigned to the meshing radio1
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Fr., 7. Apr. 2017 um
06:28 Uhr:
edit:
"the clients of *gateway *nodes don't get internet ( no ping response)
even after having changed wan proto to dhcp. So wan connects to the
internet router"
Having read that adhoc does not work properly in mt7620 I changed to
802.11s but here is no meshing.
I changed lan interface static address to avoid problems with my lan
(192.168.1.0) but nevertheless the gateway node tangles my lan makes it
slow if not unusable.
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Fr., 7. Apr. 2017 um
05:26 Uhr:
Thankk you again Pau,
I used the option precompiled binaries.
Here I got stuck that the clients don't get internet despite the fact that
network diagnostics on the node runs fine.
Regards
Pau <pau(a)dabax.net> schrieb am Do., 6. Apr. 2017 um 17:32 Uhr:
On 06/04/17 17:20, Juergen Kimmel wrote:
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
Many thanks Pau,
but 'I need further instructons.
I cloned lime-sdk and lede-sdk and downloaded
lede-imagebuilder-ramips-mt7620.Linux-x86_64 so I have three folders.
Whats next?
I think you misunderstood me. The lime-sdk makes everything for you, you
don't actually need to manually download anything else than lime-sdk.
The comments (starting with # in my previous mail) where to explain what
is the command doing.
Here the clean list of commands you might execute to compile for target
ramips/mt7620.
git clone https://github.com/libremesh/lime-sdk
cd lime-sdk
./cooker --profiles=ramips/mt7620
# Find the name of your hardware profile on this list
./cooker -c ramips/mt7620 --flavor=lime_default --profile=YOUR_PROFILE
That is all, once it finishes you'll find the firmware in the output/
directory.
Please, run "git pull" if you are not cloning a new lime-sdk but using
and old cloned one.
Also, I just implemented support for --remote so you don't need to
compile the SDK (all libremesh packages will be also downloaded instead
of localy compiled).
For using such feature, execute the cooker like this:
./cooker -c ramips/mt7620 --remote --flavor=lime_default
--profile=YOUR_PROFILE
Lastly, you can also use the current precompiled (using the cooker)
binaries at http://repo.libremesh.org (not yet official).
Cheers.
2017-04-06 12:40 GMT+01:00 Pau
<pau(a)dabax.net>et>:
> Hi Jurgen.
>
> I've been working on a new tool to build firmwares. Instead of using
> standard buildroot it uses the LEDE SDK and ImageBuilder. It means less
> compilation time (and problems) and better integration with official
> LEDE releases.
>
> To use it:
>
> git clone https://github.com/libremesh/lime-sdk
>
> # Download SDK and IB from LEDE
> ./cooker -d ar71xx/generic
>
> # List the hardware profiles and find your own
> ./cooker --profiles=ar71xx/generic
>
> # Cook the firmware for your profile using lime_default flavor
> ./cooker -c ar71xx/generic --flavor=lime_default --profile=tl-wdr3500-v1
>
> The current master branch points to LEDE 17.01.0. If you want to use the
> snapshot branch of LEDE checkout "development" branch of lime-sdk.
>
> This is a new tool, I'm still working on it. Please, let me know if you
> have problems.
>
> Cheers.
>
> On 06/04/17 10:41, Juergen Kimmel wrote:
>> I am pretty inexperienced in compiling
>> I have managed to compile the master branch but not 17.02
>> "git clone -b 17.02 git: //github.com/libremesh/lime-build"
>> and
>> "make T = mt7620 V = s"
>> led to the error
>> "rule for checkout failed (makefile line 168)"
>>
>> where is the problem?
>>
>> Tx
>> Jürgen Kimmel
>> _______________________________________________
>> 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
--
./p4u
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
9:20 p.m.
Something wrong with the network devices detection. Probably no one else
tried to install libremesh into this device before.
Can you post the output of:
ip link
iw list| grep Wiphy
Thanks.
On 12/04/17 18:36, Juergen Kimmel wrote:
This is the outcome of lime-config:
root@LiMe-16da88:~# lime-config
Clearing wireless config...
Clearing network config...
Disabling odhcpd
Cleaning dnsmasq
Disabling 6relayd...
/usr/lib/lua/lime/network.lua:155: attempt to index local 'dev' (a nil value)
stack traceback:
/usr/bin/lime-config:45: in function </usr/bin/lime-config:45>
[C]: in function 'foreach'
/usr/lib/lua/lime/network.lua:192: in function 'scandevices'
/usr/lib/lua/lime/network.lua:217: in function
</usr/lib/lua/lime/network.lua:208>
[C]: in function 'xpcall'
/usr/bin/lime-config:45: in function 'main'
/usr/bin/lime-config:65: in main chunk
[C]: ?
Configuring system...
Let uhttpd listen on IPv4/IPv6
So not working at all.
Cheers
2017-04-12 13:25 GMT+02:00 Pau <pau(a)dabax.net>et>:
--
./p4u
That looks like a crash during the configuration
process.
Can you run "lime-config" manually on a SSH session?
On 08/04/17 10:36, Juergen Kimmel wrote:
Digging just a bit deeper there is no
automagically libremesh configuration
at all.
Only three interfaces created (lan, wan, wan6)
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Sa., 8. Apr. 2017 um
02:33 Uhr:
--
./p4u
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users Status overview reports wlano-adhoc nodes but no
mesh nodes
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Sa., 8. Apr. 2017 um
02:24 Uhr:
There is no channel assigned to the meshing radio1
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Fr., 7. Apr. 2017 um
06:28 Uhr:
edit:
"the clients of *gateway *nodes don't get internet ( no ping response)
even after having changed wan proto to dhcp. So wan connects to the
internet router"
Having read that adhoc does not work properly in mt7620 I changed to
802.11s but here is no meshing.
I changed lan interface static address to avoid problems with my lan
(192.168.1.0) but nevertheless the gateway node tangles my lan makes it
slow if not unusable.
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Fr., 7. Apr. 2017 um
05:26 Uhr:
Thankk you again Pau,
I used the option precompiled binaries.
Here I got stuck that the clients don't get internet despite the fact that
network diagnostics on the node runs fine.
Regards
Pau <pau(a)dabax.net> schrieb am Do., 6. Apr. 2017 um 17:32 Uhr:
On 06/04/17 17:20, Juergen Kimmel wrote:
> Many thanks Pau,
> but 'I need further instructons.
> I cloned lime-sdk and lede-sdk and downloaded
> lede-imagebuilder-ramips-mt7620.Linux-x86_64 so I have three folders.
> Whats next?
I think you misunderstood me. The lime-sdk makes everything for you, you
don't actually need to manually download anything else than lime-sdk.
The comments (starting with # in my previous mail) where to explain what
is the command doing.
Here the clean list of commands you might execute to compile for target
ramips/mt7620.
git clone https://github.com/libremesh/lime-sdk
cd lime-sdk
./cooker --profiles=ramips/mt7620
# Find the name of your hardware profile on this list
./cooker -c ramips/mt7620 --flavor=lime_default --profile=YOUR_PROFILE
That is all, once it finishes you'll find the firmware in the output/
directory.
Please, run "git pull" if you are not cloning a new lime-sdk but using
and old cloned one.
Also, I just implemented support for --remote so you don't need to
compile the SDK (all libremesh packages will be also downloaded instead
of localy compiled).
For using such feature, execute the cooker like this:
./cooker -c ramips/mt7620 --remote --flavor=lime_default
--profile=YOUR_PROFILE
Lastly, you can also use the current precompiled (using the cooker)
binaries at http://repo.libremesh.org (not yet official).
Cheers.
> 2017-04-06 12:40 GMT+01:00 Pau <pau(a)dabax.net>et>:
>> Hi Jurgen.
>>
>> I've been working on a new tool to build firmwares. Instead of using
>> standard buildroot it uses the LEDE SDK and ImageBuilder. It means less
>> compilation time (and problems) and better integration with official
>> LEDE releases.
>>
>> To use it:
>>
>> git clone https://github.com/libremesh/lime-sdk
>>
>> # Download SDK and IB from LEDE
>> ./cooker -d ar71xx/generic
>>
>> # List the hardware profiles and find your own
>> ./cooker --profiles=ar71xx/generic
>>
>> # Cook the firmware for your profile using lime_default flavor
>> ./cooker -c ar71xx/generic --flavor=lime_default --profile=tl-wdr3500-v1
>>
>> The current master branch points to LEDE 17.01.0. If you want to use the
>> snapshot branch of LEDE checkout "development" branch of lime-sdk.
>>
>> This is a new tool, I'm still working on it. Please, let me know if you
>> have problems.
>>
>> Cheers.
>>
>> On 06/04/17 10:41, Juergen Kimmel wrote:
>>> I am pretty inexperienced in compiling
>>> I have managed to compile the master branch but not 17.02
>>> "git clone -b 17.02 git: //github.com/libremesh/lime-build"
>>> and
>>> "make T = mt7620 V = s"
>>> led to the error
>>> "rule for checkout failed (makefile line 168)"
>>>
>>> where is the problem?
>>>
>>> Tx
>>> Jürgen Kimmel
>>> _______________________________________________
>>> 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
>
>
>
--
./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
13 Apr
13 Apr
1:03 a.m.
Here it is:
root@LEDE:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 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 qlen 1000
link/ether 78:a3:51:16:da:88 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 78:a3:51:16:da:89 brd ff:ff:ff:ff:ff:ff
4: wlan1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 78:a3:51:16:da:88 brd ff:ff:ff:ff:ff:ff
5: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UP qlen 1000
link/ether 78:a3:51:16:da:88 brd ff:ff:ff:ff:ff:ff
6: eth0.1@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
master br-lan state UP qlen 1000
link/ether 78:a3:51:16:da:88 brd ff:ff:ff:ff:ff:ff
7: eth0.2@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP qlen 1000
link/ether 78:a3:51:16:da:89 brd ff:ff:ff:ff:ff:ff
root@LEDE:~# iw list| grep Wiphy
Wiphy phy1
Wiphy phy0
Pau <pau(a)dabax.net> schrieb am Mi., 12. Apr. 2017 um 23:20 Uhr:
Something wrong with the network devices detection.
Probably no one else
tried to install libremesh into this device before.
Can you post the output of:
ip link
iw list| grep Wiphy
Thanks.
On 12/04/17 18:36, Juergen Kimmel wrote:
--
./p4u
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
This is the outcome of lime-config:
root@LiMe-16da88:~# lime-config
Clearing wireless config...
Clearing network config...
Disabling odhcpd
Cleaning dnsmasq
Disabling 6relayd...
/usr/lib/lua/lime/network.lua:155: attempt to index local 'dev' (a nil
value)
stack traceback:
/usr/bin/lime-config:45: in function </usr/bin/lime-config:45>
[C]: in function 'foreach'
/usr/lib/lua/lime/network.lua:192: in function 'scandevices'
/usr/lib/lua/lime/network.lua:217: in function
</usr/lib/lua/lime/network.lua:208>
[C]: in function 'xpcall'
/usr/bin/lime-config:45: in function 'main'
/usr/bin/lime-config:65: in main chunk
[C]: ?
Configuring system...
Let uhttpd listen on IPv4/IPv6
So not working at all.
Cheers
2017-04-12 13:25 GMT+02:00 Pau <pau(a)dabax.net>et>:
> That looks like a crash during the configuration process.
>
> Can you run "lime-config" manually on a SSH session?
>
> On 08/04/17 10:36, Juergen Kimmel wrote:
>> Digging just a bit deeper there is no automagically libremesh
configuration
>> at all.
>> Only three interfaces created (lan, wan, wan6)
>>
>> Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Sa., 8. Apr. 2017
um
>> 02:33 Uhr:
>>
>>> Status overview reports wlano-adhoc nodes but no mesh nodes
>>>
>>> Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Sa., 8. Apr.
2017 um
>>> 02:24 Uhr:
>>>
>>> There is no channel assigned to the meshing radio1
>>>
>>> Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Fr., 7. Apr.
2017 um
>>> 06:28 Uhr:
>>>
>>> edit:
>>> "the clients of *gateway *nodes don't get internet ( no ping
response)
>>> even after having changed wan proto to dhcp. So wan connects to the
>>> internet router"
>>>
>>> Having read that adhoc does not work properly in mt7620 I changed to
>>> 802.11s but here is no meshing.
>>>
>>> I changed lan interface static address to avoid problems with my lan
>>> (192.168.1.0) but nevertheless the gateway node tangles my lan makes
it
>>> slow if not unusable.
>>>
>>> Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Fr., 7. Apr.
2017 um
>>> 05:26 Uhr:
>>>
>>> Thankk you again Pau,
>>> I used the option precompiled binaries.
>>> Here I got stuck that the clients don't get internet despite the fact
that
>>> network diagnostics on the node runs
fine.
>>> Regards
>>>
>>> Pau <pau(a)dabax.net> schrieb am Do., 6. Apr. 2017 um 17:32 Uhr:
>>>
>>> On 06/04/17 17:20, Juergen Kimmel wrote:
>>>> Many thanks Pau,
>>>> but 'I need further instructons.
>>>> I cloned lime-sdk and lede-sdk and downloaded
>>>> lede-imagebuilder-ramips-mt7620.Linux-x86_64 so I have three folders.
>>>> Whats next?
>>>
>>> I think you misunderstood me. The lime-sdk makes everything for you,
you
>>> don't actually need to manually
download anything else than lime-sdk.
>>> The comments (starting with # in my previous mail) where to explain
what
>>> is the command doing.
>>>
>>> Here the clean list of commands you might execute to compile for
target
>>> ramips/mt7620.
>>>
>>> git clone https://github.com/libremesh/lime-sdk
>>> cd lime-sdk
>>> ./cooker --profiles=ramips/mt7620
>>> # Find the name of your hardware profile on this list
>>> ./cooker -c ramips/mt7620 --flavor=lime_default
--profile=YOUR_PROFILE
>>>
>>> That is all, once it finishes you'll find the firmware in the output/
>>> directory.
>>>
>>> Please, run "git pull" if you are not cloning a new lime-sdk but
using
>>> and old cloned one.
>>>
>>> Also, I just implemented support for --remote so you don't need to
>>> compile the SDK (all libremesh packages will be also downloaded
instead
>>> of localy compiled).
>>> For using such feature, execute the cooker like this:
>>>
>>> ./cooker -c ramips/mt7620 --remote --flavor=lime_default
>>> --profile=YOUR_PROFILE
>>>
>>> Lastly, you can also use the current precompiled (using the cooker)
>>> binaries at http://repo.libremesh.org (not yet official).
>>>
>>> Cheers.
>>>
>>>> 2017-04-06 12:40 GMT+01:00 Pau <pau(a)dabax.net>et>:
>>>>> Hi Jurgen.
>>>>>
>>>>> I've been working on a new tool to build firmwares. Instead of
using
>>>>> standard buildroot it uses the LEDE SDK and ImageBuilder. It means
less
>>>>> compilation time (and
problems) and better integration with official
>>>>> LEDE releases.
>>>>>
>>>>> To use it:
>>>>>
>>>>> git clone https://github.com/libremesh/lime-sdk
>>>>>
>>>>> # Download SDK and IB from LEDE
>>>>> ./cooker -d ar71xx/generic
>>>>>
>>>>> # List the hardware profiles and find your own
>>>>> ./cooker --profiles=ar71xx/generic
>>>>>
>>>>> # Cook the firmware for your profile using lime_default flavor
>>>>> ./cooker -c ar71xx/generic --flavor=lime_default
--profile=tl-wdr3500-v1
>>>>>
>>>>> The current master branch points to LEDE 17.01.0. If you want to
use the
>>>>> snapshot branch of LEDE
checkout "development" branch of lime-sdk.
>>>>>
>>>>> This is a new tool, I'm still working on it. Please, let me know
if
you
>>> have problems.
>>>
>>> Cheers.
>>>
>>> On 06/04/17 10:41, Juergen Kimmel wrote:
>>>> I am pretty inexperienced in compiling
>>>> I have managed to compile the master branch but not 17.02
>>>> "git clone -b 17.02 git: //github.com/libremesh/lime-build"
>>>> and
>>>> "make T = mt7620 V = s"
>>>> led to the error
>>>> "rule for checkout failed (makefile line 168)"
>>>>
>>>> where is the problem?
>>>>
>>>> Tx
>>>> Jürgen Kimmel
>>>> _______________________________________________
>>>> 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
>>
>>
>>
>
> --
> ./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
--
./p4u
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users 
3:59 p.m.
On 04/13/2017 03:03 AM, Juergen Kimmel wrote:
root@LEDE:~# ip link
I suspect that there is an error in this line:
https://github.com/libremesh/lime-packages/commit/7cda1ad852055e85a3fec7376…
That should be
owrtDeviceName =
network.sanitizeIfaceName(linuxBaseIfname)..openwrtNameSuffix.."_dev"
instead of
owrtDeviceName =
network.limeIfNamePrefix..network.sanitizeIfaceName(linuxBaseIfname)..openwrtNameSuffix.."_dev"
This could give rise to all the problem.
Can you fix it on the device using
vim /usr/lib/lua/lime/network.lua
going to line 307 and deleting "network.limeIfNamePrefix.."?
If after this and a lime-config and a reboot things are not fixed can
you post the output of
uci show network
(there could be some non "lm_net_" entry of type "device" that
usually
is not present in ar71xx hardware)
Thanks,
Ilario
4:06 p.m.
On 13/04/17 17:59, Ilario Gelmetti wrote:
On 04/13/2017 03:03 AM, Juergen Kimmel wrote:
Wow, good catch! You are right, the limeIfNamePreix is already added
when calling sanitizeIfaceName(), should not be added twice.
root@LEDE:~# ip link
I suspect that there is an error in this line:
https://github.com/libremesh/lime-packages/commit/7cda1ad852055e85a3fec7376…
That should be
owrtDeviceName =
network.sanitizeIfaceName(linuxBaseIfname)..openwrtNameSuffix.."_dev"
instead of
owrtDeviceName =
network.limeIfNamePrefix..network.sanitizeIfaceName(linuxBaseIfname)..openwrtNameSuffix.."_dev"
This could give rise to all the problem.
Can you fix it on the device using
vim /usr/lib/lua/lime/network.lua
going to line 307 and deleting "network.limeIfNamePrefix.."?
If after this and a lime-config and a reboot things are not fixed can
you post the output of
uci show network
(there could be some non "lm_net_" entry of type "device" that
usually
is not present in ar71xx hardware)
Thanks,
Ilario
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
--
./p4u
7:23 p.m.
After changing line 307 here output of lime-config:
root@LiMe-16da88:~# lime-config
Clearing wireless config...
Clearing network config...
Disabling odhcpd
Cleaning dnsmasq
Disabling 6relayd...
/usr/lib/lua/lime/network.lua:155: attempt to index local 'dev' (a nil
value)
stack traceback:
/usr/bin/lime-config:45: in function </usr/bin/lime-config:45>
[C]: in function 'foreach'
/usr/lib/lua/lime/network.lua:192: in function 'scandevices'
/usr/lib/lua/lime/network.lua:217: in function
</usr/lib/lua/lime/network.lua:208>
[C]: in function 'xpcall'
/usr/bin/lime-config:45: in function 'main'
/usr/bin/lime-config:65: in main chunk
[C]: ?
Configuring system...
Let uhttpd listen on IPv4/IPv6
Cheers
Pau <pau(a)dabax.net> schrieb am Do., 13. Apr. 2017 um 18:06 Uhr:
On 13/04/17 17:59, Ilario Gelmetti wrote:
On 04/13/2017 03:03 AM, Juergen Kimmel wrote:
https://github.com/libremesh/lime-packages/commit/7cda1ad852055e85a3fec7376…
root@LEDE:~# ip link
I suspect that there is an error in this line:
That should be
owrtDeviceName =
network.sanitizeIfaceName(linuxBaseIfname)..openwrtNameSuffix.."_dev"
instead of
owrtDeviceName =
network.limeIfNamePrefix..network.sanitizeIfaceName(linuxBaseIfname)..openwrtNameSuffix.."_dev"
Wow, good catch! You are right, the limeIfNamePreix is already added
when calling sanitizeIfaceName(), should not be added twice.
This could give rise to all the problem.
Can you fix it on the device using
vim /usr/lib/lua/lime/network.lua
going to line 307 and deleting "network.limeIfNamePrefix.."?
If after this and a lime-config and a reboot things are not fixed can
you post the output of
uci show network
(there could be some non "lm_net_" entry of type "device" that
usually
is not present in ar71xx hardware)
Thanks,
Ilario
_______________________________________________
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
7:59 p.m.
The bug cached by Ilario affects only the name of the network interfaces
created on /etc/config/network.
I still think the problem with scandevices is related to the line I
posted in one of my previous mails.
On 13/04/17 21:23, Juergen Kimmel wrote:
After changing line 307 here output of lime-config:
root@LiMe-16da88:~# lime-config
Clearing wireless config...
Clearing network config...
Disabling odhcpd
Cleaning dnsmasq
Disabling 6relayd...
/usr/lib/lua/lime/network.lua:155: attempt to index local 'dev' (a nil
value)
stack traceback:
/usr/bin/lime-config:45: in function </usr/bin/lime-config:45>
[C]: in function 'foreach'
/usr/lib/lua/lime/network.lua:192: in function 'scandevices'
/usr/lib/lua/lime/network.lua:217: in function
</usr/lib/lua/lime/network.lua:208>
[C]: in function 'xpcall'
/usr/bin/lime-config:45: in function 'main'
/usr/bin/lime-config:65: in main chunk
[C]: ?
Configuring system...
Let uhttpd listen on IPv4/IPv6
Cheers
Pau <pau(a)dabax.net> schrieb am Do., 13. Apr. 2017 um 18:06 Uhr:
--
./p4u
On 13/04/17 17:59, Ilario Gelmetti wrote:
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
On 04/13/2017 03:03 AM, Juergen Kimmel wrote:
https://github.com/libremesh/lime-packages/commit/7cda1ad852055e85a3fec7376…
root@LEDE:~# ip link
I suspect that there is an error in this line:
That should be
owrtDeviceName =
network.sanitizeIfaceName(linuxBaseIfname)..openwrtNameSuffix.."_dev"
instead of
owrtDeviceName =
network.limeIfNamePrefix..network.sanitizeIfaceName(linuxBaseIfname)..openwrtNameSuffix.."_dev"
Wow, good catch! You are right, the limeIfNamePreix is already added
when calling sanitizeIfaceName(), should not be added twice.
This could give rise to all the problem.
Can you fix it on the device using
vim /usr/lib/lua/lime/network.lua
going to line 307 and deleting "network.limeIfNamePrefix.."?
If after this and a lime-config and a reboot things are not fixed can
you post the output of
uci show network
(there could be some non "lm_net_" entry of type "device" that
usually
is not present in ar71xx hardware)
Thanks,
Ilario
_______________________________________________
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
8:57 p.m.
@Pau
ls -1 /sys/class/net/ | grep -x 'eth[0-9][0-9]*' >>> eth0
ls -1 /sys/class/net/ | grep -x 'eth[0-9]' >>> eth0
changed line 196
lime-config:
root@LiMe-16da88:~# lime-config
Clearing wireless config...
Clearing network config...
Disabling odhcpd
Cleaning dnsmasq
Disabling 6relayd...
/usr/lib/lua/lime/network.lua:155: attempt to index local 'dev' (a nil
value)
stack traceback:
/usr/bin/lime-config:45: in function </usr/bin/lime-config:45>
[C]: in function 'foreach'
/usr/lib/lua/lime/network.lua:192: in function 'scandevices'
/usr/lib/lua/lime/network.lua:217: in function
</usr/lib/lua/lime/network.lua:208>
[C]: in function 'xpcall'
/usr/bin/lime-config:45: in function 'main'
/usr/bin/lime-config:65: in main chunk
[C]: ?
Configuring system...
Let uhttpd listen on IPv4/IPv6
Pau <pau(a)dabax.net> schrieb am Do., 13. Apr. 2017 um 22:00 Uhr:
The bug cached by Ilario affects only the name of the
network interfaces
created on /etc/config/network.
I still think the problem with scandevices is related to the line I
posted in one of my previous mails.
On 13/04/17 21:23, Juergen Kimmel wrote:
--
./p4u
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
After changing line 307 here output of
lime-config:
root@LiMe-16da88:~# lime-config
Clearing wireless config...
Clearing network config...
Disabling odhcpd
Cleaning dnsmasq
Disabling 6relayd...
/usr/lib/lua/lime/network.lua:155: attempt to index local 'dev' (a nil
value)
stack traceback:
/usr/bin/lime-config:45: in function </usr/bin/lime-config:45>
[C]: in function 'foreach'
/usr/lib/lua/lime/network.lua:192: in function 'scandevices'
/usr/lib/lua/lime/network.lua:217: in function
</usr/lib/lua/lime/network.lua:208>
[C]: in function 'xpcall'
/usr/bin/lime-config:45: in function 'main'
/usr/bin/lime-config:65: in main chunk
[C]: ?
Configuring system...
Let uhttpd listen on IPv4/IPv6
Cheers
Pau <pau(a)dabax.net> schrieb am Do., 13. Apr. 2017 um 18:06 Uhr:
> On 13/04/17 17:59, Ilario Gelmetti wrote:
>> On 04/13/2017 03:03 AM, Juergen Kimmel wrote:
>>> root@LEDE:~# ip link
>>
>> I suspect that there is an error in this line:
>>
>>
>
https://github.com/libremesh/lime-packages/commit/7cda1ad852055e85a3fec7376…
>>
>> That should be
>>
>> owrtDeviceName =
>> network.sanitizeIfaceName(linuxBaseIfname)..openwrtNameSuffix.."_dev"
>>
>> instead of
>>
>> owrtDeviceName =
>>
>
network.limeIfNamePrefix..network.sanitizeIfaceName(linuxBaseIfname)..openwrtNameSuffix.."_dev"
Wow, good catch! You are right, the limeIfNamePreix is already added
when calling sanitizeIfaceName(), should not be added twice.
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
This could give rise to all the problem.
Can you fix it on the device using
vim /usr/lib/lua/lime/network.lua
going to line 307 and deleting "network.limeIfNamePrefix.."?
If after this and a lime-config and a reboot things are not fixed can
you post the output of
uci show network
(there could be some non "lm_net_" entry of type "device" that
usually
is not present in ar71xx hardware)
Thanks,
Ilario
_______________________________________________
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
9:04 p.m.
Ok, thanks for testing it.
I'll try to find a ramips as soon as possible to debug it.
On 13/04/17 22:57, Juergen Kimmel wrote:
@Pau
ls -1 /sys/class/net/ | grep -x 'eth[0-9][0-9]*' >>> eth0
ls -1 /sys/class/net/ | grep -x 'eth[0-9]' >>> eth0
changed line 196
lime-config:
root@LiMe-16da88:~# lime-config
Clearing wireless config...
Clearing network config...
Disabling odhcpd
Cleaning dnsmasq
Disabling 6relayd...
/usr/lib/lua/lime/network.lua:155: attempt to index local 'dev' (a nil
value)
stack traceback:
/usr/bin/lime-config:45: in function </usr/bin/lime-config:45>
[C]: in function 'foreach'
/usr/lib/lua/lime/network.lua:192: in function 'scandevices'
/usr/lib/lua/lime/network.lua:217: in function
</usr/lib/lua/lime/network.lua:208>
[C]: in function 'xpcall'
/usr/bin/lime-config:45: in function 'main'
/usr/bin/lime-config:65: in main chunk
[C]: ?
Configuring system...
Let uhttpd listen on IPv4/IPv6
Pau <pau(a)dabax.net> schrieb am Do., 13. Apr. 2017 um 22:00 Uhr:
--
./p4u
The bug cached by Ilario affects only the name of
the network interfaces
created on /etc/config/network.
I still think the problem with scandevices is related to the line I
posted in one of my previous mails.
On 13/04/17 21:23, 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
After changing line 307 here output of
lime-config:
root@LiMe-16da88:~# lime-config
Clearing wireless config...
Clearing network config...
Disabling odhcpd
Cleaning dnsmasq
Disabling 6relayd...
/usr/lib/lua/lime/network.lua:155: attempt to index local 'dev' (a nil
value)
stack traceback:
/usr/bin/lime-config:45: in function </usr/bin/lime-config:45>
[C]: in function 'foreach'
/usr/lib/lua/lime/network.lua:192: in function 'scandevices'
/usr/lib/lua/lime/network.lua:217: in function
</usr/lib/lua/lime/network.lua:208>
[C]: in function 'xpcall'
/usr/bin/lime-config:45: in function 'main'
/usr/bin/lime-config:65: in main chunk
[C]: ?
Configuring system...
Let uhttpd listen on IPv4/IPv6
Cheers
Pau <pau(a)dabax.net> schrieb am Do., 13. Apr. 2017 um 18:06 Uhr:
> On 13/04/17 17:59, Ilario Gelmetti wrote:
>> On 04/13/2017 03:03 AM, Juergen Kimmel wrote:
>>> root@LEDE:~# ip link
>>
>> I suspect that there is an error in this line:
>>
>>
>
https://github.com/libremesh/lime-packages/commit/7cda1ad852055e85a3fec7376…
>>
>> That should be
>>
>> owrtDeviceName =
>> network.sanitizeIfaceName(linuxBaseIfname)..openwrtNameSuffix.."_dev"
>>
>> instead of
>>
>> owrtDeviceName =
>>
>
network.limeIfNamePrefix..network.sanitizeIfaceName(linuxBaseIfname)..openwrtNameSuffix.."_dev"
Wow, good catch! You are right, the limeIfNamePreix is already added
when calling sanitizeIfaceName(), should not be added twice.
> This could give rise to all the problem.
> Can you fix it on the device using
> vim /usr/lib/lua/lime/network.lua
> going to line 307 and deleting "network.limeIfNamePrefix.."?
> If after this and a lime-config and a reboot things are not fixed can
> you post the output of
>
> uci show network
>
> (there could be some non "lm_net_" entry of type "device" that
usually
> is not present in ar71xx hardware)
>
> Thanks,
> Ilario
>
>
>
> _______________________________________________
> 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
10:55 p.m.
On 04/13/2017 09:23 PM, Juergen Kimmel wrote:
After changing line 307 here output of lime-config:
root@LiMe-16da88:~# lime-config
/usr/lib/lua/lime/network.lua:155: attempt to index local 'dev' (a nil
value)
On 13/04/17 17:59, Ilario Gelmetti wrote:
> If after this and a lime-config and a reboot things are not fixed can
> you post the output of
>
> uci show network
>
> (there could be some non "lm_net_" entry of type "device"
that usually
> is not present in ar71xx hardware)
Ok, post your
uci show network
If there's some not "network.lm_net_*" entry which is of type
"device"
(not "interface") missing "name" or "ifname" options, that
could rise
the error you see.
Let us know :)
Ilario
14 Apr
14 Apr
3:53 a.m.
Here is
/etc/config/network
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
config interface 'lan'
option type 'bridge'
option ifname 'eth0.1'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
config device 'lan_dev'
option name 'eth0.1'
option macaddr '78:a3:51:16:da:88'
config interface 'wan'
option ifname 'eth0.2'
option proto 'none'
config device 'wan_dev'
option name 'eth0.2'
option macaddr '78:a3:51:16:da:89'
config interface 'wan6'
option ifname 'eth0.2'
option proto 'none'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0 1 2 3 6t'
config switch_vlan
option device 'switch0'
option vlan '2'
option ports '4 6t'
Cheers
Ilario Gelmetti <iochesonome(a)gmail.com> schrieb am Fr., 14. Apr. 2017 um
00:55 Uhr:
On 04/13/2017 09:23 PM, Juergen Kimmel wrote:
After changing line 307 here output of
lime-config:
root@LiMe-16da88:~# lime-config
/usr/lib/lua/lime/network.lua:155: attempt to index local 'dev' (a nil
value)
On 13/04/17 17:59, Ilario Gelmetti wrote:
> If after this and a lime-config and a reboot things are not fixed
can
> you post the output of
>
> uci show network
>
> (there could be some non "lm_net_" entry of type "device"
that
usually
> is not present in ar71xx hardware)
Ok, post your
uci show network
If there's some not "network.lm_net_*" entry which is of type
"device"
(not "interface") missing "name" or "ifname" options, that
could rise
the error you see.
Let us know :)
Ilario
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
11:39 a.m.
On 04/14/2017 05:53 AM, Juergen Kimmel wrote:
Here is
/etc/config/network
config device 'lan_dev'
option name 'eth0.1'
option macaddr '78:a3:51:16:da:88'
config device 'wan_dev'
option name 'eth0.2'
option macaddr '78:a3:51:16:da:89'
Ok, now can you try to comment out (prepending "--!") line 178 in
/usr/lib/lua/lime/network.lua ?
function owrt_device_parser(section)
dev_parser(section["name"])
--! dev_parser(section["ifname"])
end
https://github.com/libremesh/lime-packages/blob/develop/packages/lime-syste…
According to LEDE and OpenWrt wikis [1,2], sections of type device in
/etc/config/network should have an ifname option.
LibreMesh scripts assume that there is such option and the crash you
experienced could be due to the lack of an "option ifname 'eth0'" in
device sections in /etc/config/network on ramips.
I hope this works... :)
Ilario
[1] https://wiki.openwrt.org/doc/uci/network#devices
[2] https://lede-project.org/docs/user-guide/switch_configuration#devices
15 Apr
15 Apr
1:15 a.m.
I'm so sorry lost orientation once moree, should be at sleep at this time
of the night ;).
So here is network after changing line 178, reboot and lime-config:
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
config interface 'lan'
option type 'bridge'
option proto 'static'
option ip6assign '60'
option ip6addr '2a00:1508:a0d:fe00::16:da88/64'
option ipaddr '10.13.218.136'
option netmask '255.255.0.0'
option mtu '1500'
list ifname 'bat0'
list ifname 'eth0.1'
config device 'lan_dev'
option name 'eth0.1'
option macaddr '78:a3:51:16:da:88'
config interface 'wan'
option ifname 'eth0.2'
option proto 'dhcp'
config device 'wan_dev'
option name 'eth0.2'
option macaddr '78:a3:51:16:da:89'
config interface 'wan6'
option ifname 'eth0.2'
option proto 'none'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0 1 2 3 6t'
config switch_vlan
option device 'switch0'
option vlan '2'
option ports '4 6t'
config device 'lm_net_br_lan_anygw_dev'
option type 'macvlan'
option name 'anygw'
option ifname 'br-lan'
option macaddr 'aa:aa:aa:0d:fe:aa'
config interface 'lm_net_br_lan_anygw_if'
option ifname 'anygw'
option auto '1'
option netmask '255.255.0.0'
option proto 'static'
option ipaddr '10.13.0.1'
option ip6addr '2a00:1508:a0d:fe00::1/64'
config rule6 'lm_net_anygw_rule6'
option src '2a00:1508:a0d:fe00::1/128'
option lookup '170'
config route6 'lm_net_anygw_route6'
option interface 'lm_net_br_lan_anygw_if'
option target '2a00:1508:a0d:fe00::/64'
option table '170'
config rule 'lm_net_anygw_rule4'
option src '10.13.0.1/32'
option lookup '170'
config route 'lm_net_anygw_route4'
option interface 'lm_net_br_lan_anygw_if'
option target '10.13.0.0'
option netmask '255.255.0.0'
option table '170'
config interface 'lm_net_batadv_dummy_if'
option ifname 'dummy0'
option macaddr 'aa:a3:51:16:da:88'
option proto 'batadv'
option mesh 'bat0'
config device 'lm_net_lm_net_eth0_1_bmx6_dev'
option type '8021ad'
option name 'eth0-1_13'
option ifname 'eth0.1'
option vid '13'
option mtu '1398'
config interface 'lm_net_eth0_1_bmx6_if'
option proto 'none'
option auto '1'
option ifname 'eth0-1_13'
config interface 'lm_net_wlan1_adhoc'
option proto 'none'
option mtu '1536'
option auto '1'
config device 'lm_net_lm_net_wlan1_adhoc_batadv_dev'
option type '8021ad'
option name 'wlan1-adhoc_29'
option ifname '@lm_net_wlan1_adhoc'
option vid '29'
option mtu '1532'
config interface 'lm_net_wlan1_adhoc_batadv_if'
option auto '1'
option ifname 'wlan1-adhoc_29'
option proto 'batadv'
option mesh 'bat0'
config device 'lm_net_lm_net_wlan1_adhoc_bmx6_dev'
option type '8021ad'
option name 'wlan1-adhoc_13'
option ifname '@lm_net_wlan1_adhoc'
option vid '13'
option mtu '1398'
config interface 'lm_net_wlan1_adhoc_bmx6_if'
option auto '1'
option ifname 'wlan1-adhoc_13'
option proto 'static'
option ipaddr '169.254.218.136'
option netmask '255.255.255.255'
config device 'lm_net_lm_net_eth0_2_batadv_dev'
option type '8021ad'
option name 'eth0-2_29'
option ifname 'eth0.2'
option vid '29'
option mtu '1532'
config interface 'lm_net_eth0_2_batadv_if'
option auto '1'
option ifname 'eth0-2_29'
option proto 'batadv'
option mesh 'bat0'
config device 'lm_net_lm_net_eth0_2_bmx6_dev'
option type '8021ad'
option name 'eth0-2_13'
option ifname 'eth0.2'
option vid '13'
option mtu '1398'
config interface 'lm_net_eth0_2_bmx6_if'
option proto 'none'
option auto '1'
option ifname 'eth0-2_13'
config interface 'lm_net_wlan0_adhoc'
option proto 'none'
option mtu '1536'
option auto '1'
config device 'lm_net_lm_net_wlan0_adhoc_batadv_dev'
option type '8021ad'
option name 'wlan0-adhoc_29'
option ifname '@lm_net_wlan0_adhoc'
option vid '29'
option mtu '1532'
config interface 'lm_net_wlan0_adhoc_batadv_if'
option auto '1'
option ifname 'wlan0-adhoc_29'
option proto 'batadv'
option mesh 'bat0'
config device 'lm_net_lm_net_wlan0_adhoc_bmx6_dev'
option type '8021ad'
option name 'wlan0-adhoc_13'
option ifname '@lm_net_wlan0_adhoc'
option vid '13'
option mtu '1398'
config interface 'lm_net_wlan0_adhoc_bmx6_if'
option auto '1'
option ifname 'wlan0-adhoc_13'
option proto 'static'
option ipaddr '169.254.218.137'
option netmask '255.255.255.255'
config device 'lm_net_lm_net_eth0_bmx6_dev'
option type '8021ad'
option name 'eth0_13'
option ifname 'eth0'
option vid '13'
option mtu '1398'
config interface 'lm_net_eth0_bmx6_if'
option proto 'none'
option auto '1'
option ifname 'eth0_13'
Ilario Gelmetti <iochesonome(a)gmail.com> schrieb am Fr., 14. Apr. 2017 um
13:39 Uhr:
On 04/14/2017 05:53 AM, Juergen Kimmel wrote:
Here is
/etc/config/network
config device 'lan_dev'
option name 'eth0.1'
option macaddr '78:a3:51:16:da:88'
config device 'wan_dev'
option name 'eth0.2'
option macaddr '78:a3:51:16:da:89'
Ok, now can you try to comment out (prepending "--!") line 178 in
/usr/lib/lua/lime/network.lua ?
function owrt_device_parser(section)
dev_parser(section["name"])
--! dev_parser(section["ifname"])
end
https://github.com/libremesh/lime-packages/blob/develop/packages/lime-syste…
According to LEDE and OpenWrt wikis [1,2], sections of type device in
/etc/config/network should have an ifname option.
LibreMesh scripts assume that there is such option and the crash you
experienced could be due to the lack of an "option ifname 'eth0'" in
device sections in /etc/config/network on ramips.
I hope this works... :)
Ilario
[1] https://wiki.openwrt.org/doc/uci/network#devices
[2] https://lede-project.org/docs/user-guide/switch_configuration#devices
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
18 Apr
18 Apr
9:11 a.m.
Ok, that's great, this means that lime-config now does its work.
The line I asked you to comment out was added by G10h4ck 2 years ago:
https://github.com/libremesh/lime-packages/commit/caad3acb2d0512ba80558aabf…
@G10h4ck how should we fix it? Can we just delete that line?
@Juergen how is the router behavior now? Is it working as expected?
Bye!
Ilario
On 04/15/2017 03:15 AM, Juergen Kimmel wrote:
I'm so sorry lost orientation once moree, should
be at sleep at this
time of the night ;).
So here is network after changing line 178, reboot and lime-config:
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
config interface 'lan'
option type 'bridge'
option proto 'static'
option ip6assign '60'
option ip6addr '2a00:1508:a0d:fe00::16:da88/64'
option ipaddr '10.13.218.136'
option netmask '255.255.0.0'
option mtu '1500'
list ifname 'bat0'
list ifname 'eth0.1'
config device 'lan_dev'
option name 'eth0.1'
option macaddr '78:a3:51:16:da:88'
config interface 'wan'
option ifname 'eth0.2'
option proto 'dhcp'
config device 'wan_dev'
option name 'eth0.2'
option macaddr '78:a3:51:16:da:89'
config interface 'wan6'
option ifname 'eth0.2'
option proto 'none'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0 1 2 3 6t'
config switch_vlan
option device 'switch0'
option vlan '2'
option ports '4 6t'
config device 'lm_net_br_lan_anygw_dev'
option type 'macvlan'
option name 'anygw'
option ifname 'br-lan'
option macaddr 'aa:aa:aa:0d:fe:aa'
config interface 'lm_net_br_lan_anygw_if'
option ifname 'anygw'
option auto '1'
option netmask '255.255.0.0'
option proto 'static'
option ipaddr '10.13.0.1'
option ip6addr '2a00:1508:a0d:fe00::1/64'
config rule6 'lm_net_anygw_rule6'
option src '2a00:1508:a0d:fe00::1/128'
option lookup '170'
config route6 'lm_net_anygw_route6'
option interface 'lm_net_br_lan_anygw_if'
option target '2a00:1508:a0d:fe00::/64'
option table '170'
config rule 'lm_net_anygw_rule4'
option src '10.13.0.1/32 <http://10.13.0.1/32>'
option lookup '170'
config route 'lm_net_anygw_route4'
option interface 'lm_net_br_lan_anygw_if'
option target '10.13.0.0'
option netmask '255.255.0.0'
option table '170'
config interface 'lm_net_batadv_dummy_if'
option ifname 'dummy0'
option macaddr 'aa:a3:51:16:da:88'
option proto 'batadv'
option mesh 'bat0'
config device 'lm_net_lm_net_eth0_1_bmx6_dev'
option type '8021ad'
option name 'eth0-1_13'
option ifname 'eth0.1'
option vid '13'
option mtu '1398'
config interface 'lm_net_eth0_1_bmx6_if'
option proto 'none'
option auto '1'
option ifname 'eth0-1_13'
config interface 'lm_net_wlan1_adhoc'
option proto 'none'
option mtu '1536'
option auto '1'
config device 'lm_net_lm_net_wlan1_adhoc_batadv_dev'
option type '8021ad'
option name 'wlan1-adhoc_29'
option ifname '@lm_net_wlan1_adhoc'
option vid '29'
option mtu '1532'
config interface 'lm_net_wlan1_adhoc_batadv_if'
option auto '1'
option ifname 'wlan1-adhoc_29'
option proto 'batadv'
option mesh 'bat0'
config device 'lm_net_lm_net_wlan1_adhoc_bmx6_dev'
option type '8021ad'
option name 'wlan1-adhoc_13'
option ifname '@lm_net_wlan1_adhoc'
option vid '13'
option mtu '1398'
config interface 'lm_net_wlan1_adhoc_bmx6_if'
option auto '1'
option ifname 'wlan1-adhoc_13'
option proto 'static'
option ipaddr '169.254.218.136'
option netmask '255.255.255.255'
config device 'lm_net_lm_net_eth0_2_batadv_dev'
option type '8021ad'
option name 'eth0-2_29'
option ifname 'eth0.2'
option vid '29'
option mtu '1532'
config interface 'lm_net_eth0_2_batadv_if'
option auto '1'
option ifname 'eth0-2_29'
option proto 'batadv'
option mesh 'bat0'
config device 'lm_net_lm_net_eth0_2_bmx6_dev'
option type '8021ad'
option name 'eth0-2_13'
option ifname 'eth0.2'
option vid '13'
option mtu '1398'
config interface 'lm_net_eth0_2_bmx6_if'
option proto 'none'
option auto '1'
option ifname 'eth0-2_13'
config interface 'lm_net_wlan0_adhoc'
option proto 'none'
option mtu '1536'
option auto '1'
config device 'lm_net_lm_net_wlan0_adhoc_batadv_dev'
option type '8021ad'
option name 'wlan0-adhoc_29'
option ifname '@lm_net_wlan0_adhoc'
option vid '29'
option mtu '1532'
config interface 'lm_net_wlan0_adhoc_batadv_if'
option auto '1'
option ifname 'wlan0-adhoc_29'
option proto 'batadv'
option mesh 'bat0'
config device 'lm_net_lm_net_wlan0_adhoc_bmx6_dev'
option type '8021ad'
option name 'wlan0-adhoc_13'
option ifname '@lm_net_wlan0_adhoc'
option vid '13'
option mtu '1398'
config interface 'lm_net_wlan0_adhoc_bmx6_if'
option auto '1'
option ifname 'wlan0-adhoc_13'
option proto 'static'
option ipaddr '169.254.218.137'
option netmask '255.255.255.255'
config device 'lm_net_lm_net_eth0_bmx6_dev'
option type '8021ad'
option name 'eth0_13'
option ifname 'eth0'
option vid '13'
option mtu '1398'
config interface 'lm_net_eth0_bmx6_if'
option proto 'none'
option auto '1'
option ifname 'eth0_13'
Ilario Gelmetti <iochesonome(a)gmail.com <mailto:iochesonome@gmail.com>>
schrieb am Fr., 14. Apr. 2017 um 13:39 Uhr:
On 04/14/2017 05:53 AM, Juergen Kimmel wrote:
Here is
/etc/config/network
config device 'lan_dev'
option name 'eth0.1'
option macaddr '78:a3:51:16:da:88'
config device 'wan_dev'
option name 'eth0.2'
option macaddr '78:a3:51:16:da:89'
Ok, now can you try to comment out (prepending "--!") line 178 in
/usr/lib/lua/lime/network.lua ?
function owrt_device_parser(section)
dev_parser(section["name"])
--! dev_parser(section["ifname"])
end
https://github.com/libremesh/lime-packages/blob/develop/packages/lime-syste…
According to LEDE and OpenWrt wikis [1,2], sections of type device in
/etc/config/network should have an ifname option.
LibreMesh scripts assume that there is such option and the crash you
experienced could be due to the lack of an "option ifname 'eth0'"
in
device sections in /etc/config/network on ramips.
I hope this works... :)
Ilario
[1] https://wiki.openwrt.org/doc/uci/network#devices
[2]
https://lede-project.org/docs/user-guide/switch_configuration#devices
1:52 p.m.
@Ilario
radio0 behaves as expected
radio1 has issues
1. on site: http://10.13.0.1/cgi-bin/luci/admin/network/wireless there is
no channel assigned to the adhoc despite the fact that on site:
http://10.13.0.1/cgi-bin/luci/admin/network/wireless/radio1.network3 everything
seems ok. Fact is radio1 is not meshing.
2. as with earlier firmwares (except the stock openwrt) radio1 crashes
under traffic. Device reboots.
Cheers
Ilario Gelmetti <iochesonome(a)gmail.com> schrieb am Di., 18. Apr. 2017 um
11:12 Uhr:
Ok, that's great, this means that lime-config now
does its work.
The line I asked you to comment out was added by G10h4ck 2 years ago:
https://github.com/libremesh/lime-packages/commit/caad3acb2d0512ba80558aabf…
@G10h4ck how should we fix it? Can we just delete that line?
@Juergen how is the router behavior now? Is it working as expected?
Bye!
Ilario
On 04/15/2017 03:15 AM, Juergen Kimmel wrote:
I'm so sorry lost orientation once moree,
should be at sleep at this
time of the night ;).
So here is network after changing line 178, reboot and lime-config:
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
config interface 'lan'
option type 'bridge'
option proto 'static'
option ip6assign '60'
option ip6addr '2a00:1508:a0d:fe00::16:da88/64'
option ipaddr '10.13.218.136'
option netmask '255.255.0.0'
option mtu '1500'
list ifname 'bat0'
list ifname 'eth0.1'
config device 'lan_dev'
option name 'eth0.1'
option macaddr '78:a3:51:16:da:88'
config interface 'wan'
option ifname 'eth0.2'
option proto 'dhcp'
config device 'wan_dev'
option name 'eth0.2'
option macaddr '78:a3:51:16:da:89'
config interface 'wan6'
option ifname 'eth0.2'
option proto 'none'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0 1 2 3 6t'
config switch_vlan
option device 'switch0'
option vlan '2'
option ports '4 6t'
config device 'lm_net_br_lan_anygw_dev'
option type 'macvlan'
option name 'anygw'
option ifname 'br-lan'
option macaddr 'aa:aa:aa:0d:fe:aa'
config interface 'lm_net_br_lan_anygw_if'
option ifname 'anygw'
option auto '1'
option netmask '255.255.0.0'
option proto 'static'
option ipaddr '10.13.0.1'
option ip6addr '2a00:1508:a0d:fe00::1/64'
config rule6 'lm_net_anygw_rule6'
option src '2a00:1508:a0d:fe00::1/128'
option lookup '170'
config route6 'lm_net_anygw_route6'
option interface 'lm_net_br_lan_anygw_if'
option target '2a00:1508:a0d:fe00::/64'
option table '170'
config rule 'lm_net_anygw_rule4'
option src '10.13.0.1/32 <http://10.13.0.1/32>'
option lookup '170'
config route 'lm_net_anygw_route4'
option interface 'lm_net_br_lan_anygw_if'
option target '10.13.0.0'
option netmask '255.255.0.0'
option table '170'
config interface 'lm_net_batadv_dummy_if'
option ifname 'dummy0'
option macaddr 'aa:a3:51:16:da:88'
option proto 'batadv'
option mesh 'bat0'
config device 'lm_net_lm_net_eth0_1_bmx6_dev'
option type '8021ad'
option name 'eth0-1_13'
option ifname 'eth0.1'
option vid '13'
option mtu '1398'
config interface 'lm_net_eth0_1_bmx6_if'
option proto 'none'
option auto '1'
option ifname 'eth0-1_13'
config interface 'lm_net_wlan1_adhoc'
option proto 'none'
option mtu '1536'
option auto '1'
config device 'lm_net_lm_net_wlan1_adhoc_batadv_dev'
option type '8021ad'
option name 'wlan1-adhoc_29'
option ifname '@lm_net_wlan1_adhoc'
option vid '29'
option mtu '1532'
config interface 'lm_net_wlan1_adhoc_batadv_if'
option auto '1'
option ifname 'wlan1-adhoc_29'
option proto 'batadv'
option mesh 'bat0'
config device 'lm_net_lm_net_wlan1_adhoc_bmx6_dev'
option type '8021ad'
option name 'wlan1-adhoc_13'
option ifname '@lm_net_wlan1_adhoc'
option vid '13'
option mtu '1398'
config interface 'lm_net_wlan1_adhoc_bmx6_if'
option auto '1'
option ifname 'wlan1-adhoc_13'
option proto 'static'
option ipaddr '169.254.218.136'
option netmask '255.255.255.255'
config device 'lm_net_lm_net_eth0_2_batadv_dev'
option type '8021ad'
option name 'eth0-2_29'
option ifname 'eth0.2'
option vid '29'
option mtu '1532'
config interface 'lm_net_eth0_2_batadv_if'
option auto '1'
option ifname 'eth0-2_29'
option proto 'batadv'
option mesh 'bat0'
config device 'lm_net_lm_net_eth0_2_bmx6_dev'
option type '8021ad'
option name 'eth0-2_13'
option ifname 'eth0.2'
option vid '13'
option mtu '1398'
config interface 'lm_net_eth0_2_bmx6_if'
option proto 'none'
option auto '1'
option ifname 'eth0-2_13'
config interface 'lm_net_wlan0_adhoc'
option proto 'none'
option mtu '1536'
option auto '1'
config device 'lm_net_lm_net_wlan0_adhoc_batadv_dev'
option type '8021ad'
option name 'wlan0-adhoc_29'
option ifname '@lm_net_wlan0_adhoc'
option vid '29'
option mtu '1532'
config interface 'lm_net_wlan0_adhoc_batadv_if'
option auto '1'
option ifname 'wlan0-adhoc_29'
option proto 'batadv'
option mesh 'bat0'
config device 'lm_net_lm_net_wlan0_adhoc_bmx6_dev'
option type '8021ad'
option name 'wlan0-adhoc_13'
option ifname '@lm_net_wlan0_adhoc'
option vid '13'
option mtu '1398'
config interface 'lm_net_wlan0_adhoc_bmx6_if'
option auto '1'
option ifname 'wlan0-adhoc_13'
option proto 'static'
option ipaddr '169.254.218.137'
option netmask '255.255.255.255'
config device 'lm_net_lm_net_eth0_bmx6_dev'
option type '8021ad'
option name 'eth0_13'
option ifname 'eth0'
option vid '13'
option mtu '1398'
config interface 'lm_net_eth0_bmx6_if'
option proto 'none'
option auto '1'
option ifname 'eth0_13'
Ilario Gelmetti <iochesonome(a)gmail.com <mailto:iochesonome@gmail.com>>
schrieb am Fr., 14. Apr. 2017 um 13:39 Uhr:
On 04/14/2017 05:53 AM, Juergen Kimmel wrote:
https://github.com/libremesh/lime-packages/blob/develop/packages/lime-syste…
Here is
/etc/config/network
config device 'lan_dev'
option name 'eth0.1'
option macaddr '78:a3:51:16:da:88'
config device 'wan_dev'
option name 'eth0.2'
option macaddr '78:a3:51:16:da:89'
Ok, now can you try to comment out (prepending "--!") line 178 in
/usr/lib/lua/lime/network.lua ?
function owrt_device_parser(section)
dev_parser(section["name"])
--! dev_parser(section["ifname"])
end
According to LEDE and OpenWrt wikis [1,2], sections of type device in
/etc/config/network should have an ifname option.
LibreMesh scripts assume that there is such option and the crash you
experienced could be due to the lack of an "option ifname 'eth0'"
in
device sections in /etc/config/network on ramips.
I hope this works... :)
Ilario
[1] https://wiki.openwrt.org/doc/uci/network#devices
[2]
https://lede-project.org/docs/user-guide/switch_configuration#devices
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
1:55 p.m.
Here last syslog:
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 0.848441] Serial:
8250/16550 driver, 16 ports, IRQ sharing enabled
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 0.858198] console [ttyS0]
disabled
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 0.861704]
10000c00.uartlite: ttyS0 at MMIO 0x10000c00 (irq = 20, base_baud = 2500000)
is a Palmchip BK-3103
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 0.871312] console [ttyS0]
enabled
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 0.878357] bootconsole
[early0] disabled
Wed Apr 5 12:53:34 2017 kern.warn kernel: [ 0.893176] spi spi0.0: force
spi mode3
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 0.897659] m25p80 spi0.0:
w25q128 (16384 Kbytes)
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 0.902562] 4 ofpart
partitions found on MTD device spi0.0
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 0.908156] Creating 4 MTD
partitions on "spi0.0":
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 0.913062]
0x000000000000-0x000000030000 : "u-boot"
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 0.919962]
0x000000030000-0x000000040000 : "u-boot-env"
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 0.927304]
0x000000040000-0x000000050000 : "factory"
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 0.934342]
0x000000050000-0x000000fd0000 : "firmware"
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 2.246892] 2 uimage-fw
partitions found on MTD device firmware
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 2.252982]
0x000000050000-0x000000178296 : "kernel"
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 2.259663]
0x000000178296-0x000000fd0000 : "rootfs"
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 2.266617] mtd: device 5
(rootfs) set to be root filesystem
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 2.272609] 1
squashfs-split partitions found on MTD device rootfs
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 2.278926]
0x00000048a000-0x000000fd0000 : "rootfs_data"
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 2.289346] gsw: setting
port4 to ephy mode
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 2.293710] mtk_soc_eth
10100000.ethernet eth0 (uninitialized): port 4 link up (100Mbps/Full duplex)
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 2.303267] mtk_soc_eth
10100000.ethernet: loaded mt7620 driver
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 2.310108] mtk_soc_eth
10100000.ethernet eth0: mediatek frame engine at 0xb0100000, irq 5
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 2.319136] rt2880_wdt
10000120.watchdog: Initialized
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 2.325781] NET: Registered
protocol family 10
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 2.334859] NET: Registered
protocol family 17
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 2.339480] bridge: automatic
filtering via arp/ip/ip6tables has been deprecated. Update your scripts to
load br_netfilter if you need this.
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 2.352408] 8021q: 802.1Q
VLAN Support v1.8
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 2.371622] VFS: Mounted root
(squashfs filesystem) readonly on device 31:5.
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 2.379717] Freeing unused
kernel memory: 164K (80377000 - 803a0000)
Wed Apr 5 12:53:34 2017 user.info kernel: [ 4.753578] init: Console is
alive
Wed Apr 5 12:53:34 2017 user.info kernel: [ 4.757273] init: - watchdog -
Wed Apr 5 12:53:34 2017 user.info kernel: [ 6.551800] init: - preinit -
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 8.202710] 8021q: adding
VLAN 0 to HW filter on device eth0
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 10.916394] jffs2: notice:
(344) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of
xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
Wed Apr 5 12:53:34 2017 user.info kernel: [ 10.935462] mount_root:
switching to jffs2 overlay
Wed Apr 5 12:53:34 2017 user.warn kernel: [ 10.953513] urandom-seed:
Seeding with /etc/urandom.seed
Wed Apr 5 12:53:34 2017 user.info kernel: [ 11.089859] procd: - early -
Wed Apr 5 12:53:34 2017 user.info kernel: [ 11.092914] procd: - watchdog
-
Wed Apr 5 12:53:34 2017 user.info kernel: [ 11.432307] procd: - ubus -
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 11.672232] random: ubusd:
uninitialized urandom read (4 bytes read, 23 bits of entropy available)
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 11.687960] random: ubusd:
uninitialized urandom read (4 bytes read, 23 bits of entropy available)
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 11.697706] random: ubusd:
uninitialized urandom read (4 bytes read, 23 bits of entropy available)
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 11.707026] random: ubusd:
uninitialized urandom read (4 bytes read, 23 bits of entropy available)
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 11.716616] random: ubusd:
uninitialized urandom read (4 bytes read, 23 bits of entropy available)
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 11.726458] random: ubusd:
uninitialized urandom read (4 bytes read, 23 bits of entropy available)
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 11.736449] random: ubusd:
uninitialized urandom read (4 bytes read, 23 bits of entropy available)
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 11.745898] random: ubusd:
uninitialized urandom read (4 bytes read, 23 bits of entropy available)
Wed Apr 5 12:53:34 2017 user.info kernel: [ 11.755503] procd: - init -
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 12.315513] tun: Universal
TUN/TAP device driver, 1.6
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 12.320683] tun: (C)
1999-2004 Max Krasnyansky <maxk(a)qualcomm.com>
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 12.347556] ip6_tables: (C)
2000-2006 Netfilter Core Team
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 12.373978] Loading modules
backported from Linux version wt-2016-10-03-1-g6fcb1a6
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 12.381789] Backport
generated by backports.git backports-20160324-9-g0e38f5c
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 12.539717] batman_adv:
B.A.T.M.A.N. advanced 2017.0 (compatibility version 15) loaded
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 12.578142] mt76x2e
0000:01:00.0: ASIC revision: 76120044
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 12.592553] mt76x2e
0000:01:00.0: ROM patch already applied
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 12.599899] mt76x2e
0000:01:00.0: Firmware Version: 0.0.00
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 12.605569] mt76x2e
0000:01:00.0: Build: 1
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 12.609750] mt76x2e
0000:01:00.0: Build Time: 201507311614____
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 12.645102] mt76x2e
0000:01:00.0: Firmware running!
Wed Apr 5 12:53:34 2017 kern.debug kernel: [ 12.654956] ieee80211 phy0:
Selected rate control algorithm 'minstrel_ht'
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 12.684343] Bridge
firewalling registered
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 12.728255] Ebtables v2.0
registered
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 12.739132] ip_tables: (C)
2000-2006 Netfilter Core Team
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 12.771500] nf_conntrack
version 0.5.0 (1970 buckets, 7880 max)
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 12.912672] xt_time: kernel
timezone is -0000
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 12.948916] rt2800_wmac
10180000.wmac: loaded eeprom from mtd device "factory"
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 12.956381] ieee80211 phy1:
rt2x00_set_rt: Info - RT chipset 5390, rev 0500 detected
Wed Apr 5 12:53:34 2017 kern.info kernel: [ 12.964323] ieee80211 phy1:
rt2x00_set_rf: Info - RF chipset 7620 detected
Wed Apr 5 12:53:34 2017 kern.debug kernel: [ 12.972055] ieee80211 phy1:
Selected rate control algorithm 'minstrel_ht'
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 14.332999] random: jshn:
uninitialized urandom read (4 bytes read, 28 bits of entropy available)
Wed Apr 5 12:53:34 2017 kern.notice kernel: [ 14.430835] random: ubusd:
uninitialized urandom read (4 bytes read, 28 bits of entropy available)
Wed Apr 5 12:53:35 2017 user.notice : Added device handler type: 8021ad
Wed Apr 5 12:53:35 2017 user.notice : Added device handler type: 8021q
Wed Apr 5 12:53:35 2017 user.notice : Added device handler type: macvlan
Wed Apr 5 12:53:35 2017 user.notice : Added device handler type: bridge
Wed Apr 5 12:53:35 2017 user.notice : Added device handler type: Network
device
Wed Apr 5 12:53:35 2017 user.notice : Added device handler type: tunnel
Wed Apr 5 12:53:36 2017 cron.info crond[741]: crond (busybox 1.25.1)
started, log level 5
Wed Apr 5 12:53:37 2017 authpriv.info dropbear[774]: Not backgrounding
Wed Apr 5 12:53:37 2017 user.notice : Starting netserver with host
'IN(6)ADDR_ANY' port '12865' and family AF_UNSPEC
Wed Apr 5 12:53:39 2017 user.notice : setting up led wlan1-link
Wed Apr 5 12:53:39 2017 user.notice : setting up led wlan1
Wed Apr 5 12:53:39 2017 user.notice : setting up led wlan0
Wed Apr 5 12:53:40 2017 kern.info kernel: [ 20.177029] 8021q: adding
VLAN 0 to HW filter on device eth0
Wed Apr 5 12:53:40 2017 kern.info kernel: [ 20.226238] device eth0.1
entered promiscuous mode
Wed Apr 5 12:53:40 2017 kern.info kernel: [ 20.231220] device eth0
entered promiscuous mode
Wed Apr 5 12:53:40 2017 kern.info kernel: [ 20.295488] br-lan: port
1(eth0.1) entered forwarding state
Wed Apr 5 12:53:40 2017 kern.info kernel: [ 20.301302] br-lan: port
1(eth0.1) entered forwarding state
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface 'lan' is enabled
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface 'lan' is setting
up now
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface 'lan' is now up
Wed Apr 5 12:53:40 2017 kern.info kernel: [ 20.410410] device br-lan
entered promiscuous mode
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface
'lm_net_br_lan_anygw_if' is enabled
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface
'lm_net_br_lan_anygw_if' is setting up now
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface
'lm_net_br_lan_anygw_if' is now up
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface
'lm_net_eth0_1_bmx6_if' is enabled
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface 'wan' is enabled
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface 'wan6' is enabled
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface
'lm_net_eth0_2_bmx6_if' is enabled
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface
'lm_net_eth0_2_batadv_if' is enabled
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface
'lm_net_eth0_bmx6_if' is enabled
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface
'lm_net_batadv_dummy_if' is enabled
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface 'loopback' is
enabled
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface 'loopback' is
setting up now
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface 'loopback' is now
up
Wed Apr 5 12:53:40 2017 daemon.notice netifd: bridge 'br-lan' link is up
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface 'lan' has link
connectivity
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Network device 'eth0' link
is up
Wed Apr 5 12:53:40 2017 daemon.notice netifd: VLAN 'eth0.1' link is up
Wed Apr 5 12:53:40 2017 daemon.notice netifd: macvlan 'anygw' link is up
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface
'lm_net_br_lan_anygw_if' has link connectivity
Wed Apr 5 12:53:40 2017 daemon.notice netifd: 8021ad 'eth0-1_13' link is up
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface
'lm_net_eth0_1_bmx6_if' has link connectivity
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface
'lm_net_eth0_1_bmx6_if' is setting up now
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface
'lm_net_eth0_1_bmx6_if' is now up
Wed Apr 5 12:53:40 2017 daemon.notice netifd: VLAN 'eth0.2' link is up
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface 'wan' has link
connectivity
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface 'wan' is setting
up now
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface 'wan6' has link
connectivity
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface 'wan6' is setting
up now
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface 'wan6' is now up
Wed Apr 5 12:53:40 2017 daemon.notice netifd: 8021ad 'eth0-2_13' link is up
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface
'lm_net_eth0_2_bmx6_if' has link connectivity
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface
'lm_net_eth0_2_bmx6_if' is setting up now
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface
'lm_net_eth0_2_bmx6_if' is now up
Wed Apr 5 12:53:40 2017 daemon.notice netifd: 8021ad 'eth0-2_29' link is up
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface
'lm_net_eth0_2_batadv_if' has link connectivity
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface
'lm_net_eth0_2_batadv_if' is setting up now
Wed Apr 5 12:53:40 2017 daemon.notice netifd: 8021ad 'eth0_13' link is up
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface
'lm_net_eth0_bmx6_if' has link connectivity
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface
'lm_net_eth0_bmx6_if' is setting up now
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface
'lm_net_eth0_bmx6_if' is now up
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Network device 'lo' link is
up
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface 'loopback' has
link connectivity
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Network device 'dummy0' link
is up
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface
'lm_net_batadv_dummy_if' has link connectivity
Wed Apr 5 12:53:40 2017 daemon.notice netifd: Interface
'lm_net_batadv_dummy_if' is setting up now
Wed Apr 5 12:53:41 2017 kern.info kernel: [ 21.105620] batman_adv: bat0:
Adding interface: eth0-2_29
Wed Apr 5 12:53:41 2017 kern.info kernel: [ 21.111223] batman_adv: bat0:
The MTU of interface eth0-2_29 is too small (1500) to handle the transport
of batman-adv packets. Packets going over this interface will be fragmented
on layer2 which could impact the performance. Setting the MTU to 1532 would
solve the problem.
Wed Apr 5 12:53:41 2017 kern.info kernel: [ 21.136079] batman_adv: bat0:
Interface activated: eth0-2_29
Wed Apr 5 12:53:41 2017 kern.info kernel: [ 21.148676] 8021q: adding
VLAN 0 to HW filter on device bat0
Wed Apr 5 12:53:41 2017 kern.info kernel: [ 21.206307] device bat0
entered promiscuous mode
Wed Apr 5 12:53:41 2017 kern.info kernel: [ 21.211211] br-lan: port
2(bat0) entered forwarding state
Wed Apr 5 12:53:41 2017 kern.info kernel: [ 21.216749] br-lan: port
2(bat0) entered forwarding state
Wed Apr 5 12:53:41 2017 daemon.notice netifd: Network device 'bat0' link
is up
Wed Apr 5 12:53:41 2017 daemon.notice netifd: Interface
'lm_net_eth0_2_batadv_if' is now up
Wed Apr 5 12:53:41 2017 daemon.notice netifd: Interface
'lm_net_batadv_dummy_if' is now up
Wed Apr 5 12:53:41 2017 kern.info kernel: [ 21.511403] batman_adv: bat0:
Adding interface: dummy0
Wed Apr 5 12:53:41 2017 kern.info kernel: [ 21.516676] batman_adv: bat0:
The MTU of interface dummy0 is too small (1500) to handle the transport of
batman-adv packets. Packets going over this interface will be fragmented on
layer2 which could impact the performance. Setting the MTU to 1532 would
solve the problem.
Wed Apr 5 12:53:41 2017 kern.info kernel: [ 21.541457] batman_adv: bat0:
Interface activated: dummy0
Wed Apr 5 12:53:41 2017 daemon.notice netifd: wan (966): udhcpc: started,
v1.25.1
Wed Apr 5 12:53:41 2017 kern.info kernel: [ 21.831142] batman_adv: bat0:
No IGMP Querier present - multicast optimizations disabled
Wed Apr 5 12:53:41 2017 kern.info kernel: [ 21.839416] batman_adv: bat0:
No MLD Querier present - multicast optimizations disabled
Wed Apr 5 12:53:42 2017 kern.info kernel: [ 22.301118] br-lan: port
1(eth0.1) entered forwarding state
Wed Apr 5 12:53:42 2017 daemon.notice netifd: radio1 (918): command
failed: Not supported (-122)
Wed Apr 5 12:53:42 2017 daemon.notice netifd: wan (966): udhcpc: sending
discover
Wed Apr 5 12:53:42 2017 daemon.notice netifd: wan (966): udhcpc: sending
select for 192.168.1.63
Wed Apr 5 12:53:42 2017 user.notice : /etc/rc.d/S99alfred: waiting 30 secs
for br-lan address...
Wed Apr 5 12:53:42 2017 user.notice : /etc/rc.d/S99alfred: starting alfred
Wed Apr 5 12:53:42 2017 user.notice : /etc/rc.d/S99alfred: starting
batadv-vis
Wed Apr 5 12:53:42 2017 daemon.notice netifd: wan (966): udhcpc: lease of
192.168.1.63 obtained, lease time 43200
Wed Apr 5 12:53:43 2017 kern.info kernel: [ 23.211054] br-lan: port
2(bat0) entered forwarding state
Wed Apr 5 12:53:43 2017 kern.info kernel: [ 23.605238] batman_adv: bat0:
distributed_arp_table: Changing from: enabled to: disabled
Wed Apr 5 12:53:43 2017 kern.info kernel: [ 23.671783] batman_adv: bat0:
Changing gw mode from: off to: client
Wed Apr 5 12:53:43 2017 kern.info kernel: [ 23.678624] batman_adv: bat0:
multicast_mode: Changing from: enabled to: disabled
Wed Apr 5 12:53:43 2017 kern.warn kernel: [ 23.841731] batman_adv: The
newly added mac address (78:a3:51:16:d9:e9) already exists on: eth0-2_29
Wed Apr 5 12:53:43 2017 kern.warn kernel: [ 23.851122] batman_adv: It is
strongly recommended to keep mac addresses unique to avoid problems!
Wed Apr 5 12:53:43 2017 daemon.notice netifd: Interface 'wan' is now up
Wed Apr 5 12:53:44 2017 kern.warn kernel: [ 24.177916] batman_adv: The
newly added mac address (78:a3:51:16:d9:e9) already exists on: eth0-2_29
Wed Apr 5 12:53:44 2017 kern.warn kernel: [ 24.187319] batman_adv: It is
strongly recommended to keep mac addresses unique to avoid problems!
Wed Apr 5 12:53:47 2017 daemon.err hostapd: Configuration file:
/var/run/hostapd-phy1.conf
Wed Apr 5 12:53:47 2017 kern.info kernel: [ 27.293407] IPv6:
ADDRCONF(NETDEV_UP): wlan1-ap: link is not ready
Wed Apr 5 12:53:47 2017 kern.info kernel: [ 27.315648] device wlan1-ap
entered promiscuous mode
Wed Apr 5 12:53:47 2017 kern.warn kernel: [ 27.320799] br-lan: adding
interface wlan1-ap with same address as a received packet
Wed Apr 5 12:53:47 2017 kern.info kernel: [ 27.328811] br-lan: port
3(wlan1-ap) entered forwarding state
Wed Apr 5 12:53:47 2017 kern.info kernel: [ 27.334726] br-lan: port
3(wlan1-ap) entered forwarding state
Wed Apr 5 12:53:47 2017 daemon.err hostapd: Configuration file:
/var/run/hostapd-phy0.conf
Wed Apr 5 12:53:47 2017 user.notice : /etc/rc.common: Firewall is not
enabled. Executing /etc/firewall.lime script.
Wed Apr 5 12:53:47 2017 kern.info kernel: [ 27.875588] IPv6:
ADDRCONF(NETDEV_UP): wlan0-ap: link is not ready
Wed Apr 5 12:53:47 2017 kern.info kernel: [ 27.887721] br-lan: port
3(wlan1-ap) entered disabled state
Wed Apr 5 12:53:47 2017 daemon.err hostapd: Using interface wlan1-ap with
hwaddr 78:a3:51:16:d9:e9 and ssid "LibreMesh.org"
Wed Apr 5 12:53:47 2017 kern.info kernel: [ 27.991703] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan1-ap: link becomes ready
Wed Apr 5 12:53:47 2017 kern.info kernel: [ 27.998664] br-lan: port
3(wlan1-ap) entered forwarding state
Wed Apr 5 12:53:47 2017 kern.info kernel: [ 28.004644] br-lan: port
3(wlan1-ap) entered forwarding state
Wed Apr 5 12:53:47 2017 kern.info kernel: [ 28.016868] device
wlan1-apname entered promiscuous mode
Wed Apr 5 12:53:47 2017 kern.info kernel: [ 28.024761] device wlan0-ap
entered promiscuous mode
Wed Apr 5 12:53:47 2017 kern.info kernel: [ 28.059281] IPv6:
ADDRCONF(NETDEV_UP): wlan1-apname: link is not ready
Wed Apr 5 12:53:47 2017 kern.info kernel: [ 28.066040] br-lan: port
4(wlan1-apname) entered forwarding state
Wed Apr 5 12:53:47 2017 kern.info kernel: [ 28.072310] br-lan: port
4(wlan1-apname) entered forwarding state
Wed Apr 5 12:53:47 2017 daemon.err hostapd: Using interface wlan0-ap with
hwaddr 7a:a3:51:16:d9:e9 and ssid "LibreMesh.org"
Wed Apr 5 12:53:47 2017 user.notice : Sorry, rule does not exist.
Wed Apr 5 12:53:48 2017 user.notice : Sorry, rule does not exist.
Wed Apr 5 12:53:48 2017 daemon.err hostapd: Using interface wlan1-apname
with hwaddr 78:a3:51:16:d9:ea and ssid "LibreMesh.org/LiMe-16d9e8"
Wed Apr 5 12:53:48 2017 daemon.notice hostapd: wlan1-ap: interface state
UNINITIALIZED->ENABLED
Wed Apr 5 12:53:48 2017 daemon.notice hostapd: wlan1-ap: AP-ENABLED
Tue Apr 18 13:30:31 2017 kern.info kernel: [ 28.641653] device
wlan0-apname entered promiscuous mode
Tue Apr 18 13:30:31 2017 user.notice : iptables: No chain/target/match by
that name.
Tue Apr 18 13:30:31 2017 kern.info kernel: [ 28.851635] IPv6:
ADDRCONF(NETDEV_UP): wlan0-apname: link is not ready
Tue Apr 18 13:30:31 2017 kern.info kernel: [ 28.858324] br-lan: port
6(wlan0-apname) entered forwarding state
Tue Apr 18 13:30:31 2017 kern.info kernel: [ 28.864640] br-lan: port
6(wlan0-apname) entered forwarding state
Tue Apr 18 13:30:31 2017 user.notice : iptables: No chain/target/match by
that name.
Tue Apr 18 13:30:31 2017 daemon.err hostapd: Using interface wlan0-apname
with hwaddr 7e:a3:51:16:d9:e9 and ssid "LibreMesh.org/LiMe-16d9e8"
Tue Apr 18 13:30:31 2017 daemon.notice hostapd: wlan0-ap: interface state
UNINITIALIZED->ENABLED
Tue Apr 18 13:30:31 2017 daemon.notice hostapd: wlan0-ap: AP-ENABLED
Tue Apr 18 13:30:31 2017 kern.info kernel: [ 29.215500] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan1-apname: link becomes ready
Tue Apr 18 13:30:31 2017 kern.info kernel: [ 29.222998] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan0-ap: link becomes ready
Tue Apr 18 13:30:31 2017 kern.info kernel: [ 29.229868] br-lan: port
5(wlan0-ap) entered forwarding state
Tue Apr 18 13:30:31 2017 kern.info kernel: [ 29.235841] br-lan: port
5(wlan0-ap) entered forwarding state
Tue Apr 18 13:30:31 2017 kern.info kernel: [ 29.242275] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan0-apname: link becomes ready
Tue Apr 18 13:30:31 2017 daemon.notice netifd: radio1 (918): RTNETLINK
answers: Resource busy
Tue Apr 18 13:30:31 2017 daemon.notice netifd: radio1 (918): Interface 2
setup failed: IFUP_ERROR
Tue Apr 18 13:30:32 2017 user.notice : 917
Tue Apr 18 13:30:32 2017 user.notice : 918
Tue Apr 18 13:30:32 2017 daemon.notice netifd: Network device 'wlan1-ap'
link is up
Tue Apr 18 13:30:32 2017 daemon.notice netifd: Network device
'wlan1-apname' link is up
Tue Apr 18 13:30:32 2017 kern.info kernel: [ 29.603827] IPv6:
ADDRCONF(NETDEV_UP): wlan0-adhoc: link is not ready
Tue Apr 18 13:30:32 2017 kern.info kernel: [ 29.627164] wlan0-adhoc:
Created IBSS using preconfigured BSSID ca:fe:00:c0:ff:ee
Tue Apr 18 13:30:32 2017 kern.info kernel: [ 29.634882] wlan0-adhoc:
Creating new IBSS network, BSSID ca:fe:00:c0:ff:ee
Tue Apr 18 13:30:32 2017 kern.info kernel: [ 29.643207] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan0-adhoc: link becomes ready
Tue Apr 18 13:30:32 2017 daemon.notice netifd: Network device 'wlan0-ap'
link is up
Tue Apr 18 13:30:32 2017 daemon.notice netifd: Network device
'wlan0-apname' link is up
Tue Apr 18 13:30:32 2017 daemon.notice netifd: Network device 'wlan0-adhoc'
link is up
Tue Apr 18 13:30:32 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc' is enabled
Tue Apr 18 13:30:32 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc' has link connectivity
Tue Apr 18 13:30:32 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc' is setting up now
Tue Apr 18 13:30:32 2017 kern.warn kernel: [ 29.937452] batman_adv: The
newly added mac address (78:a3:51:16:d9:e9) already exists on: eth0-2_29
Tue Apr 18 13:30:32 2017 kern.warn kernel: [ 29.946857] batman_adv: It is
strongly recommended to keep mac addresses unique to avoid problems!
Tue Apr 18 13:30:32 2017 kern.info kernel: [ 30.001147] br-lan: port
3(wlan1-ap) entered forwarding state
Tue Apr 18 13:30:32 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_bmx6_if' is enabled
Tue Apr 18 13:30:32 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_bmx6_if' is setting up now
Tue Apr 18 13:30:32 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_bmx6_if' is now up
Tue Apr 18 13:30:32 2017 kern.warn kernel: [ 30.043339] batman_adv: The
newly added mac address (78:a3:51:16:d9:e9) already exists on: eth0-2_29
Tue Apr 18 13:30:32 2017 kern.warn kernel: [ 30.052981] batman_adv: It is
strongly recommended to keep mac addresses unique to avoid problems!
Tue Apr 18 13:30:32 2017 kern.info kernel: [ 30.071146] br-lan: port
4(wlan1-apname) entered forwarding state
Tue Apr 18 13:30:32 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_batadv_if' is enabled
Tue Apr 18 13:30:32 2017 daemon.notice netifd: Network alias 'wlan0-adhoc'
link is up
Tue Apr 18 13:30:32 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc' is now up
Tue Apr 18 13:30:32 2017 daemon.notice netifd: 8021ad 'wlan0-adhoc_13' link
is up
Tue Apr 18 13:30:32 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_bmx6_if' has link connectivity
Tue Apr 18 13:30:32 2017 daemon.notice netifd: 8021ad 'wlan0-adhoc_29' link
is up
Tue Apr 18 13:30:32 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_batadv_if' has link connectivity
Tue Apr 18 13:30:32 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_batadv_if' is setting up now
Tue Apr 18 13:30:32 2017 kern.info kernel: [ 30.353122] batman_adv: bat0:
Adding interface: wlan0-adhoc_29
Tue Apr 18 13:30:32 2017 kern.info kernel: [ 30.359113] batman_adv: bat0:
Interface activated: wlan0-adhoc_29
Tue Apr 18 13:30:32 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_batadv_if' is now up
Tue Apr 18 13:30:33 2017 user.info watchping: starting all tasks
Tue Apr 18 13:30:33 2017 user.info watchping: started task
(interface=eth0.2;timeout=120;pinghosts=8.8.8.8;pinginterval=20;hookname=wan)
Tue Apr 18 13:30:33 2017 user.info watchping: all tasks started
Tue Apr 18 13:30:33 2017 daemon.info procd: - init complete -
Tue Apr 18 13:30:33 2017 kern.info kernel: [ 30.829469] br-lan: port
6(wlan0-apname) entered forwarding state
Tue Apr 18 13:30:33 2017 kern.warn kernel: [ 30.924159] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:30:33 2017 kern.info kernel: [ 30.971375] br-lan: port
5(wlan0-ap) entered forwarding state
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq[1691]: started, version 2.76
cachesize 150
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq[1691]: compile time options:
IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack
no-ipset no-auth no-DNSSEC no-ID loop-detect inotify
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq[1691]: DNS service limited to
local subnets
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq-dhcp[1691]: DHCP, IP range
10.13.0.2 -- 10.13.255.254, lease time 1h
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq-dhcp[1691]: DHCPv4-derived
IPv6 names on 2a00:1508:a0d:fe00::
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq-dhcp[1691]: router
advertisement on 2a00:1508:a0d:fe00::
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq-dhcp[1691]: IPv6 router
advertisement enabled
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq[1691]: using nameserver
2001:470:20::2#53
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq[1691]: using nameserver
141.1.1.1#53
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq[1691]: using nameserver
4.2.2.2#53
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq[1691]: using local addresses
only for domain lan
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq[1691]: reading
/tmp/resolv.conf.auto
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq[1691]: using nameserver
2001:470:20::2#53
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq[1691]: using nameserver
141.1.1.1#53
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq[1691]: using nameserver
4.2.2.2#53
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq[1691]: using local addresses
only for domain lan
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq[1691]: using nameserver
80.58.61.254#53
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq[1691]: using nameserver
80.58.61.250#53
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq[1691]: read /etc/hosts - 4
addresses
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dhcp.cfg02411c - 1 addresses
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dnsmasq-lease-share - 0 addresses
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq-dhcp[1691]: read /etc/ethers -
0 addresses
Tue Apr 18 13:30:35 2017 daemon.info dnsmasq-dhcp[1691]: read
/tmp/dhcp.hosts_remote
Tue Apr 18 13:30:42 2017 cron.err crond[741]: time disparity of 18757
minutes detected
Tue Apr 18 13:30:43 2017 kern.warn kernel: [ 35.376439] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:30:51 2017 kern.notice kernel: [ 38.220794] random:
nonblocking pool is initialized
Tue Apr 18 13:30:53 2017 daemon.info watchping[1623]: ping reply. Running
wan-ok.d hooks...
Tue Apr 18 13:30:53 2017 user.notice bmx6-auto-gw: We got Internet access,
announcing it to the mesh
Tue Apr 18 13:30:53 2017 kern.warn kernel: [ 39.022788] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:31:03 2017 kern.warn kernel: [ 42.549530] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:31:13 2017 kern.warn kernel: [ 46.085451] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:31:15 2017 kern.info kernel: [ 46.850625] mtk_soc_eth
10100000.ethernet eth0: port 0 link up (100Mbps/Full duplex)
Tue Apr 18 13:31:16 2017 daemon.info dnsmasq-dhcp[1691]: DHCPREQUEST(anygw)
10.13.237.24 74:27:ea:48:23:18
Tue Apr 18 13:31:16 2017 daemon.info dnsmasq-dhcp[1691]: DHCPACK(anygw)
10.13.237.24 74:27:ea:48:23:18 JK-PC
Tue Apr 18 13:31:16 2017 daemon.info dnsmasq-dhcp[1691]: RTR-SOLICIT(anygw)
Tue Apr 18 13:31:16 2017 daemon.info dnsmasq-dhcp[1691]: RTR-ADVERT(anygw)
2a00:1508:a0d:fe00::
Tue Apr 18 13:31:23 2017 kern.warn kernel: [ 50.245989] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:31:33 2017 kern.warn kernel: [ 55.216464] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:31:43 2017 kern.warn kernel: [ 59.130569] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:31:53 2017 kern.warn kernel: [ 63.143543] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:31:54 2017 user.warn libremap-agent[803]: unable to execute
plugin "wireless"; ?:0: attempt to index a nil value
Tue Apr 18 13:31:54 2017 user.err libremap-agent[803]: submission to
http://libremap.net/api/ failed
Tue Apr 18 13:31:54 2017 user.err libremap-agent[803]: error
creating/updating router document at URL http://libremap.net/api//router/;
{"error":"forbidden","reason":"key lat expected"}
Tue Apr 18 13:31:54 2017 user.warn libremap-agent[803]: unable to execute
plugin "wireless"; ?:0: attempt to index a nil value
Tue Apr 18 13:31:54 2017 user.err libremap-agent[803]: submission to
http://libremap.berlin.freifunk.net/api failed
Tue Apr 18 13:31:54 2017 user.err libremap-agent[803]: error
creating/updating router document at URL
http://libremap.berlin.freifunk.net/api/router/; -2
Tue Apr 18 13:32:00 2017 cron.info crond[741]: USER root pid 1765 cmd
/usr/bin/bmx6hosts_dnsmasq_update
Tue Apr 18 13:32:01 2017 user.notice bmx6hosts: New bmx6 hosts found,
updating dnsmasq
Tue Apr 18 13:32:01 2017 daemon.info dnsmasq[1691]: read /etc/hosts - 4
addresses
Tue Apr 18 13:32:01 2017 daemon.info dnsmasq[1691]: read /tmp/hosts/bmx6 -
8 addresses
Tue Apr 18 13:32:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dhcp.cfg02411c - 1 addresses
Tue Apr 18 13:32:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dnsmasq-lease-share - 0 addresses
Tue Apr 18 13:32:01 2017 daemon.info dnsmasq-dhcp[1691]: read /etc/ethers -
0 addresses
Tue Apr 18 13:32:01 2017 daemon.info dnsmasq-dhcp[1691]: read
/tmp/dhcp.hosts_remote
Tue Apr 18 13:32:03 2017 kern.warn kernel: [ 67.625438] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:32:13 2017 kern.warn kernel: [ 71.176271] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:32:23 2017 kern.warn kernel: [ 74.710476] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:32:33 2017 kern.warn kernel: [ 78.248802] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:32:43 2017 kern.warn kernel: [ 83.231780] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:32:53 2017 kern.warn kernel: [ 88.669848] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:33:03 2017 kern.warn kernel: [ 94.074454] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:33:13 2017 kern.warn kernel: [ 99.482594] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:33:23 2017 kern.warn kernel: [ 104.879109] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:33:34 2017 kern.warn kernel: [ 110.340451] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:33:44 2017 kern.warn kernel: [ 115.960712] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:33:54 2017 kern.warn kernel: [ 121.379046] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:34:04 2017 kern.warn kernel: [ 126.784244] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:34:14 2017 kern.warn kernel: [ 132.652087] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:34:24 2017 kern.warn kernel: [ 138.573234] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:34:34 2017 kern.warn kernel: [ 142.815278] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:34:44 2017 kern.warn kernel: [ 146.720913] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:34:54 2017 kern.warn kernel: [ 150.638456] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:35:00 2017 cron.info crond[741]: USER root pid 2122 cmd ( for
file in /etc/alfred/* ; do [ -x $file ] && $file ; done )
Tue Apr 18 13:35:00 2017 daemon.info dnsmasq[1691]: read /etc/hosts - 4
addresses
Tue Apr 18 13:35:00 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/d-d-h_78:a3:51:16:da:88 - 2 addresses
Tue Apr 18 13:35:00 2017 daemon.info dnsmasq[1691]: read /tmp/hosts/bmx6 -
8 addresses
Tue Apr 18 13:35:00 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dhcp.cfg02411c - 1 addresses
Tue Apr 18 13:35:00 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dnsmasq-lease-share - 0 addresses
Tue Apr 18 13:35:00 2017 daemon.info dnsmasq-dhcp[1691]: read /etc/ethers -
0 addresses
Tue Apr 18 13:35:00 2017 daemon.info dnsmasq-dhcp[1691]: read
/tmp/dhcp.hosts_remote
Tue Apr 18 13:35:01 2017 daemon.info dnsmasq[1691]: read /etc/hosts - 4
addresses
Tue Apr 18 13:35:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/d-d-h_78:a3:51:16:da:88 - 2 addresses
Tue Apr 18 13:35:01 2017 daemon.info dnsmasq[1691]: read /tmp/hosts/bmx6 -
8 addresses
Tue Apr 18 13:35:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dhcp.cfg02411c - 1 addresses
Tue Apr 18 13:35:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dnsmasq-lease-share - 4 addresses
Tue Apr 18 13:35:01 2017 daemon.info dnsmasq-dhcp[1691]: read /etc/ethers -
0 addresses
Tue Apr 18 13:35:01 2017 daemon.info dnsmasq-dhcp[1691]: read
/tmp/dhcp.hosts_remote
Tue Apr 18 13:35:04 2017 kern.warn kernel: [ 154.706748] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:35:14 2017 kern.warn kernel: [ 158.652300] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:35:24 2017 kern.warn kernel: [ 162.569827] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:35:34 2017 kern.warn kernel: [ 166.501718] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:35:44 2017 kern.warn kernel: [ 170.408874] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:35:54 2017 kern.warn kernel: [ 174.329088] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:36:00 2017 cron.info crond[741]: USER root pid 2201 cmd
/usr/bin/bmx6hosts_dnsmasq_update
Tue Apr 18 13:36:04 2017 kern.warn kernel: [ 178.355231] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:36:14 2017 kern.warn kernel: [ 182.286466] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:36:24 2017 kern.warn kernel: [ 186.202537] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:36:31 2017 kern.info kernel: [ 190.309359] device
wlan0-apname left promiscuous mode
Tue Apr 18 13:36:31 2017 kern.info kernel: [ 190.314713] br-lan: port
6(wlan0-apname) entered disabled state
Tue Apr 18 13:36:31 2017 daemon.notice hostapd: wlan0-ap: interface state
ENABLED->DISABLED
Tue Apr 18 13:36:31 2017 daemon.notice hostapd: wlan0-apname: AP-DISABLED
Tue Apr 18 13:36:31 2017 daemon.notice hostapd: wlan0-apname:
CTRL-EVENT-TERMINATING
Tue Apr 18 13:36:31 2017 daemon.notice hostapd: nl80211: Failed to remove
interface wlan0-apname from bridge br-lan: No such device
Tue Apr 18 13:36:31 2017 daemon.notice hostapd: wlan0-ap: AP-DISABLED
Tue Apr 18 13:36:31 2017 daemon.notice hostapd: wlan0-ap:
CTRL-EVENT-TERMINATING
Tue Apr 18 13:36:31 2017 daemon.notice hostapd: nl80211: deinit
ifname=wlan0-ap disabled_11b_rates=0
Tue Apr 18 13:36:31 2017 kern.info kernel: [ 190.884000] device wlan0-ap
left promiscuous mode
Tue Apr 18 13:36:31 2017 kern.info kernel: [ 190.889178] br-lan: port
5(wlan0-ap) entered disabled state
Tue Apr 18 13:36:32 2017 daemon.notice netifd: Network device 'wlan0-ap'
link is down
Tue Apr 18 13:36:32 2017 kern.info kernel: [ 191.373961] batman_adv: bat0:
Interface deactivated: wlan0-adhoc_29
Tue Apr 18 13:36:32 2017 daemon.notice netifd: Network device 'wlan0-adhoc'
link is down
Tue Apr 18 13:36:32 2017 daemon.notice netifd: Network alias 'wlan0-adhoc'
link is down
Tue Apr 18 13:36:32 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc' has link connectivity loss
Tue Apr 18 13:36:32 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc' is now down
Tue Apr 18 13:36:32 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_bmx6_if' is now down
Tue Apr 18 13:36:32 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_bmx6_if' is disabled
Tue Apr 18 13:36:32 2017 daemon.notice netifd: 8021ad 'wlan0-adhoc_29' link
is down
Tue Apr 18 13:36:32 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_batadv_if' has link connectivity loss
Tue Apr 18 13:36:32 2017 daemon.notice netifd: 8021ad 'wlan0-adhoc_13' link
is down
Tue Apr 18 13:36:32 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_bmx6_if' has link connectivity loss
Tue Apr 18 13:36:32 2017 kern.info kernel: [ 191.486575] batman_adv: bat0:
Removing interface: wlan0-adhoc_29
Tue Apr 18 13:36:32 2017 daemon.notice netifd: lm_net_wlan0_adhoc_batadv_if
(2305): ./batadv.sh: eval: line 1: can't create
/sys/class/net/wlan0-adhoc_29/batman_adv/mesh_iface: nonexistent directory
Tue Apr 18 13:36:32 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_batadv_if' is now down
Tue Apr 18 13:36:32 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_batadv_if' is disabled
Tue Apr 18 13:36:34 2017 kern.warn kernel: [ 193.281276] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:36:34 2017 kern.warn kernel: [ 193.406026] batman_adv: The
newly added mac address (78:a3:51:16:d9:e9) already exists on: eth0-2_29
Tue Apr 18 13:36:34 2017 kern.warn kernel: [ 193.415440] batman_adv: It is
strongly recommended to keep mac addresses unique to avoid problems!
Tue Apr 18 13:36:35 2017 daemon.err hostapd: Configuration file:
/var/run/hostapd-phy0.conf
Tue Apr 18 13:36:36 2017 kern.info kernel: [ 195.149258] IPv6:
ADDRCONF(NETDEV_UP): wlan0-ap: link is not ready
Tue Apr 18 13:36:36 2017 kern.info kernel: [ 195.203375] device wlan0-ap
entered promiscuous mode
Tue Apr 18 13:36:36 2017 daemon.notice hostapd: wlan0-ap: interface state
UNINITIALIZED->COUNTRY_UPDATE
Tue Apr 18 13:36:36 2017 daemon.err hostapd: Using interface wlan0-ap with
hwaddr 7a:a3:51:16:d9:e9 and ssid "LibreMesh.org"
Tue Apr 18 13:36:36 2017 kern.info kernel: [ 195.629112] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan0-ap: link becomes ready
Tue Apr 18 13:36:36 2017 kern.info kernel: [ 195.636151] br-lan: port
5(wlan0-ap) entered forwarding state
Tue Apr 18 13:36:36 2017 kern.info kernel: [ 195.642113] br-lan: port
5(wlan0-ap) entered forwarding state
Tue Apr 18 13:36:36 2017 kern.info kernel: [ 195.668694] device
wlan0-apname entered promiscuous mode
Tue Apr 18 13:36:36 2017 kern.info kernel: [ 195.721449] IPv6:
ADDRCONF(NETDEV_UP): wlan0-apname: link is not ready
Tue Apr 18 13:36:36 2017 kern.info kernel: [ 195.728222] br-lan: port
6(wlan0-apname) entered forwarding state
Tue Apr 18 13:36:36 2017 kern.info kernel: [ 195.734537] br-lan: port
6(wlan0-apname) entered forwarding state
Tue Apr 18 13:36:36 2017 daemon.err hostapd: Using interface wlan0-apname
with hwaddr 7e:a3:51:16:d9:e9 and ssid "LibreMesh.org/LiMe-16d9e8_5"
Tue Apr 18 13:36:36 2017 kern.info kernel: [ 195.811956] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan0-apname: link becomes ready
Tue Apr 18 13:36:36 2017 daemon.notice hostapd: wlan0-ap: interface state
COUNTRY_UPDATE->ENABLED
Tue Apr 18 13:36:36 2017 daemon.notice hostapd: wlan0-ap: AP-ENABLED
Tue Apr 18 13:36:37 2017 kern.info kernel: [ 196.378322] IPv6:
ADDRCONF(NETDEV_UP): wlan0-adhoc: link is not ready
Tue Apr 18 13:36:37 2017 kern.info kernel: [ 196.436269] wlan0-adhoc:
Created IBSS using preconfigured BSSID ca:fe:00:c0:ff:ee
Tue Apr 18 13:36:37 2017 kern.info kernel: [ 196.443997] wlan0-adhoc:
Creating new IBSS network, BSSID ca:fe:00:c0:ff:ee
Tue Apr 18 13:36:37 2017 kern.info kernel: [ 196.452309] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan0-adhoc: link becomes ready
Tue Apr 18 13:36:37 2017 daemon.notice netifd: Network device 'wlan0-ap'
link is up
Tue Apr 18 13:36:37 2017 daemon.notice netifd: Network device
'wlan0-apname' link is up
Tue Apr 18 13:36:37 2017 daemon.notice netifd: Network device 'wlan0-adhoc'
link is up
Tue Apr 18 13:36:37 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc' has link connectivity
Tue Apr 18 13:36:37 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc' is setting up now
Tue Apr 18 13:36:37 2017 kern.warn kernel: [ 196.704101] batman_adv: The
newly added mac address (78:a3:51:16:d9:e9) already exists on: eth0-2_29
Tue Apr 18 13:36:37 2017 kern.warn kernel: [ 196.713505] batman_adv: It is
strongly recommended to keep mac addresses unique to avoid problems!
Tue Apr 18 13:36:37 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_bmx6_if' is enabled
Tue Apr 18 13:36:37 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_bmx6_if' is setting up now
Tue Apr 18 13:36:37 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_bmx6_if' is now up
Tue Apr 18 13:36:37 2017 kern.warn kernel: [ 196.842557] batman_adv: The
newly added mac address (78:a3:51:16:d9:e9) already exists on: eth0-2_29
Tue Apr 18 13:36:37 2017 kern.warn kernel: [ 196.852189] batman_adv: It is
strongly recommended to keep mac addresses unique to avoid problems!
Tue Apr 18 13:36:38 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_batadv_if' is enabled
Tue Apr 18 13:36:38 2017 daemon.notice netifd: Network alias 'wlan0-adhoc'
link is up
Tue Apr 18 13:36:38 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc' is now up
Tue Apr 18 13:36:38 2017 daemon.notice netifd: 8021ad 'wlan0-adhoc_13' link
is up
Tue Apr 18 13:36:38 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_bmx6_if' has link connectivity
Tue Apr 18 13:36:38 2017 daemon.notice netifd: 8021ad 'wlan0-adhoc_29' link
is up
Tue Apr 18 13:36:38 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_batadv_if' has link connectivity
Tue Apr 18 13:36:38 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_batadv_if' is setting up now
Tue Apr 18 13:36:38 2017 kern.info kernel: [ 197.198379] batman_adv: bat0:
Adding interface: wlan0-adhoc_29
Tue Apr 18 13:36:38 2017 kern.info kernel: [ 197.204419] batman_adv: bat0:
Interface activated: wlan0-adhoc_29
Tue Apr 18 13:36:38 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_batadv_if' is now up
Tue Apr 18 13:36:38 2017 kern.info kernel: [ 197.641135] br-lan: port
5(wlan0-ap) entered forwarding state
Tue Apr 18 13:36:38 2017 kern.info kernel: [ 197.731132] br-lan: port
6(wlan0-apname) entered forwarding state
Tue Apr 18 13:36:44 2017 kern.warn kernel: [ 201.938105] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:36:54 2017 kern.warn kernel: [ 207.476491] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:37:04 2017 kern.warn kernel: [ 212.894764] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:37:14 2017 kern.warn kernel: [ 218.325224] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:37:24 2017 kern.warn kernel: [ 223.884609] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:37:34 2017 kern.warn kernel: [ 229.420434] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:37:44 2017 kern.warn kernel: [ 234.827092] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:37:54 2017 kern.warn kernel: [ 240.277654] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:38:04 2017 kern.warn kernel: [ 245.697269] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:38:14 2017 kern.warn kernel: [ 251.133163] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:38:22 2017 daemon.info hostapd: wlan0-apname: STA
4c:66:41:95:3b:c9 IEEE 802.11: authenticated
Tue Apr 18 13:38:22 2017 daemon.info hostapd: wlan0-apname: STA
4c:66:41:95:3b:c9 IEEE 802.11: associated (aid 1)
Tue Apr 18 13:38:22 2017 daemon.notice hostapd: wlan0-apname:
AP-STA-CONNECTED 4c:66:41:95:3b:c9
Tue Apr 18 13:38:24 2017 daemon.info dnsmasq-dhcp[1691]: RTR-SOLICIT(anygw)
4c:66:41:95:3b:c9
Tue Apr 18 13:38:24 2017 daemon.info dnsmasq-dhcp[1691]: RTR-ADVERT(anygw)
2a00:1508:a0d:fe00::
Tue Apr 18 13:38:24 2017 kern.warn kernel: [ 256.563517] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:38:25 2017 daemon.info dnsmasq-dhcp[1691]: RTR-SOLICIT(anygw)
4c:66:41:95:3b:c9
Tue Apr 18 13:38:25 2017 daemon.info dnsmasq-dhcp[1691]: RTR-ADVERT(anygw)
2a00:1508:a0d:fe00::
Tue Apr 18 13:38:27 2017 daemon.info dnsmasq-dhcp[1691]:
DHCPDISCOVER(anygw) 4c:66:41:95:3b:c9
Tue Apr 18 13:38:27 2017 daemon.info dnsmasq-dhcp[1691]: DHCPOFFER(anygw)
10.13.12.148 4c:66:41:95:3b:c9
Tue Apr 18 13:38:27 2017 daemon.info dnsmasq-dhcp[1691]: DHCPREQUEST(anygw)
10.13.12.148 4c:66:41:95:3b:c9
Tue Apr 18 13:38:27 2017 daemon.info dnsmasq-dhcp[1691]: DHCPACK(anygw)
10.13.12.148 4c:66:41:95:3b:c9 android-171fad8e332aaaf2
Tue Apr 18 13:38:34 2017 kern.warn kernel: [ 262.125519] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:38:44 2017 kern.warn kernel: [ 267.824118] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:38:55 2017 kern.warn kernel: [ 273.300248] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:39:05 2017 kern.warn kernel: [ 279.008342] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:39:15 2017 kern.warn kernel: [ 284.511787] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:39:25 2017 kern.warn kernel: [ 290.734482] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:39:35 2017 kern.warn kernel: [ 297.304466] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:39:45 2017 kern.warn kernel: [ 302.848762] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:39:55 2017 kern.warn kernel: [ 308.280147] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:40:00 2017 cron.info crond[741]: USER root pid 3315 cmd
/usr/bin/bmx6hosts_dnsmasq_update
Tue Apr 18 13:40:00 2017 cron.info crond[741]: USER root pid 3316 cmd ( for
file in /etc/alfred/* ; do [ -x $file ] && $file ; done )
Tue Apr 18 13:40:01 2017 daemon.info dnsmasq[1691]: read /etc/hosts - 4
addresses
Tue Apr 18 13:40:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/d-d-h_78:a3:51:16:da:88 - 2 addresses
Tue Apr 18 13:40:01 2017 daemon.info dnsmasq[1691]: read /tmp/hosts/bmx6 -
0 addresses
Tue Apr 18 13:40:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dhcp.cfg02411c - 1 addresses
Tue Apr 18 13:40:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dnsmasq-lease-share - 4 addresses
Tue Apr 18 13:40:01 2017 daemon.info dnsmasq-dhcp[1691]: read /etc/ethers -
0 addresses
Tue Apr 18 13:40:01 2017 daemon.info dnsmasq-dhcp[1691]: read
/tmp/dhcp.hosts_remote
Tue Apr 18 13:40:01 2017 daemon.info dnsmasq[1691]: read /etc/hosts - 4
addresses
Tue Apr 18 13:40:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/d-d-h_78:a3:51:16:da:88 - 2 addresses
Tue Apr 18 13:40:01 2017 daemon.info dnsmasq[1691]: read /tmp/hosts/bmx6 -
1 addresses
Tue Apr 18 13:40:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dhcp.cfg02411c - 1 addresses
Tue Apr 18 13:40:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dnsmasq-lease-share - 4 addresses
Tue Apr 18 13:40:01 2017 daemon.info dnsmasq-dhcp[1691]: read /etc/ethers -
0 addresses
Tue Apr 18 13:40:01 2017 daemon.info dnsmasq-dhcp[1691]: read
/tmp/dhcp.hosts_remote
Tue Apr 18 13:40:01 2017 user.notice bmx6hosts: New bmx6 hosts found,
updating dnsmasq
Tue Apr 18 13:40:01 2017 daemon.info dnsmasq[1691]: read /etc/hosts - 4
addresses
Tue Apr 18 13:40:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/d-d-h_78:a3:51:16:da:88 - 2 addresses
Tue Apr 18 13:40:01 2017 daemon.info dnsmasq[1691]: read /tmp/hosts/bmx6 -
8 addresses
Tue Apr 18 13:40:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dhcp.cfg02411c - 1 addresses
Tue Apr 18 13:40:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dnsmasq-lease-share - 4 addresses
Tue Apr 18 13:40:01 2017 daemon.info dnsmasq-dhcp[1691]: read /etc/ethers -
0 addresses
Tue Apr 18 13:40:01 2017 daemon.info dnsmasq-dhcp[1691]: read
/tmp/dhcp.hosts_remote
Tue Apr 18 13:40:05 2017 kern.warn kernel: [ 314.091379] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:40:15 2017 kern.warn kernel: [ 319.604309] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:40:20 2017 kern.info kernel: [ 322.803450] device wlan0-ap
left promiscuous mode
Tue Apr 18 13:40:20 2017 kern.info kernel: [ 322.808446] br-lan: port
5(wlan0-ap) entered disabled state
Tue Apr 18 13:40:20 2017 daemon.notice hostapd: wlan0-ap: interface state
ENABLED->DISABLED
Tue Apr 18 13:40:20 2017 daemon.notice hostapd: wlan0-apname:
AP-STA-DISCONNECTED 4c:66:41:95:3b:c9
Tue Apr 18 13:40:20 2017 daemon.notice hostapd: wlan0-apname: AP-DISABLED
Tue Apr 18 13:40:20 2017 daemon.notice hostapd: wlan0-apname:
CTRL-EVENT-TERMINATING
Tue Apr 18 13:40:20 2017 daemon.notice netifd: Network device
'wlan0-apname' link is down
Tue Apr 18 13:40:20 2017 kern.info kernel: [ 323.333510] br-lan: port
6(wlan0-apname) entered disabled state
Tue Apr 18 13:40:20 2017 kern.info kernel: [ 323.358124] device
wlan0-apname left promiscuous mode
Tue Apr 18 13:40:20 2017 kern.info kernel: [ 323.363305] br-lan: port
6(wlan0-apname) entered disabled state
Tue Apr 18 13:40:20 2017 daemon.notice hostapd: nl80211: Failed to remove
interface wlan0-apname from bridge br-lan: No such device
Tue Apr 18 13:40:20 2017 daemon.notice hostapd: wlan0-ap: AP-DISABLED
Tue Apr 18 13:40:20 2017 daemon.notice hostapd: wlan0-ap:
CTRL-EVENT-TERMINATING
Tue Apr 18 13:40:20 2017 daemon.notice hostapd: nl80211: deinit
ifname=wlan0-ap disabled_11b_rates=0
Tue Apr 18 13:40:20 2017 daemon.notice hostapd: nl80211: Failed to remove
interface wlan0-ap from bridge br-lan: Invalid argument
Tue Apr 18 13:40:21 2017 daemon.notice netifd: Network device 'wlan0-adhoc'
link is down
Tue Apr 18 13:40:21 2017 daemon.notice netifd: Network alias 'wlan0-adhoc'
link is down
Tue Apr 18 13:40:21 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc' has link connectivity loss
Tue Apr 18 13:40:21 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc' is now down
Tue Apr 18 13:40:21 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_bmx6_if' is now down
Tue Apr 18 13:40:21 2017 kern.info kernel: [ 323.875127] batman_adv: bat0:
Interface deactivated: wlan0-adhoc_29
Tue Apr 18 13:40:21 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_bmx6_if' is disabled
Tue Apr 18 13:40:21 2017 daemon.notice netifd: 8021ad 'wlan0-adhoc_29' link
is down
Tue Apr 18 13:40:21 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_batadv_if' has link connectivity loss
Tue Apr 18 13:40:21 2017 daemon.notice netifd: 8021ad 'wlan0-adhoc_13' link
is down
Tue Apr 18 13:40:21 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_bmx6_if' has link connectivity loss
Tue Apr 18 13:40:21 2017 kern.info kernel: [ 323.983016] batman_adv: bat0:
Removing interface: wlan0-adhoc_29
Tue Apr 18 13:40:21 2017 daemon.notice netifd: lm_net_wlan0_adhoc_batadv_if
(3484): ./batadv.sh: eval: line 1: can't create
/sys/class/net/wlan0-adhoc_29/batman_adv/mesh_iface: nonexistent directory
Tue Apr 18 13:40:21 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_batadv_if' is now down
Tue Apr 18 13:40:21 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_batadv_if' is disabled
Tue Apr 18 13:40:23 2017 kern.warn kernel: [ 325.843750] batman_adv: The
newly added mac address (78:a3:51:16:d9:e9) already exists on: eth0-2_29
Tue Apr 18 13:40:23 2017 kern.warn kernel: [ 325.853164] batman_adv: It is
strongly recommended to keep mac addresses unique to avoid problems!
Tue Apr 18 13:40:24 2017 daemon.err hostapd: Configuration file:
/var/run/hostapd-phy0.conf
Tue Apr 18 13:40:24 2017 kern.info kernel: [ 327.551950] IPv6:
ADDRCONF(NETDEV_UP): wlan0-ap: link is not ready
Tue Apr 18 13:40:24 2017 kern.info kernel: [ 327.593281] device wlan0-ap
entered promiscuous mode
Tue Apr 18 13:40:24 2017 daemon.notice hostapd: wlan0-ap: interface state
UNINITIALIZED->COUNTRY_UPDATE
Tue Apr 18 13:40:24 2017 daemon.err hostapd: Using interface wlan0-ap with
hwaddr 7a:a3:51:16:d9:e9 and ssid "LibreMesh.org_5"
Tue Apr 18 13:40:25 2017 kern.info kernel: [ 328.025817] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan0-ap: link becomes ready
Tue Apr 18 13:40:25 2017 kern.info kernel: [ 328.032872] br-lan: port
5(wlan0-ap) entered forwarding state
Tue Apr 18 13:40:25 2017 kern.info kernel: [ 328.038831] br-lan: port
5(wlan0-ap) entered forwarding state
Tue Apr 18 13:40:25 2017 kern.info kernel: [ 328.059052] device
wlan0-apname entered promiscuous mode
Tue Apr 18 13:40:25 2017 kern.info kernel: [ 328.108205] IPv6:
ADDRCONF(NETDEV_UP): wlan0-apname: link is not ready
Tue Apr 18 13:40:25 2017 kern.info kernel: [ 328.114982] br-lan: port
6(wlan0-apname) entered forwarding state
Tue Apr 18 13:40:25 2017 kern.info kernel: [ 328.121309] br-lan: port
6(wlan0-apname) entered forwarding state
Tue Apr 18 13:40:25 2017 kern.warn kernel: [ 328.128777] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:40:25 2017 daemon.err hostapd: Using interface wlan0-apname
with hwaddr 7e:a3:51:16:d9:e9 and ssid "LibreMesh.org/LiMe-16d9e8_5"
Tue Apr 18 13:40:25 2017 daemon.notice hostapd: wlan0-ap: interface state
COUNTRY_UPDATE->ENABLED
Tue Apr 18 13:40:25 2017 daemon.notice hostapd: wlan0-ap: AP-ENABLED
Tue Apr 18 13:40:25 2017 kern.info kernel: [ 328.252570] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan0-apname: link becomes ready
Tue Apr 18 13:40:25 2017 daemon.info hostapd: wlan0-apname: STA
4c:66:41:95:3b:c9 IEEE 802.11: authenticated
Tue Apr 18 13:40:25 2017 daemon.info hostapd: wlan0-apname: STA
4c:66:41:95:3b:c9 IEEE 802.11: associated (aid 1)
Tue Apr 18 13:40:25 2017 daemon.notice hostapd: wlan0-apname:
AP-STA-CONNECTED 4c:66:41:95:3b:c9
Tue Apr 18 13:40:26 2017 kern.info kernel: [ 328.861691] IPv6:
ADDRCONF(NETDEV_UP): wlan0-adhoc: link is not ready
Tue Apr 18 13:40:26 2017 kern.info kernel: [ 328.944171] wlan0-adhoc:
Created IBSS using preconfigured BSSID ca:fe:00:c0:ff:ee
Tue Apr 18 13:40:26 2017 kern.info kernel: [ 328.951896] wlan0-adhoc:
Creating new IBSS network, BSSID ca:fe:00:c0:ff:ee
Tue Apr 18 13:40:26 2017 kern.info kernel: [ 328.959568] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan0-adhoc: link becomes ready
Tue Apr 18 13:40:26 2017 daemon.notice netifd: Network device 'wlan0-ap'
link is up
Tue Apr 18 13:40:26 2017 daemon.notice netifd: Network device
'wlan0-apname' link is up
Tue Apr 18 13:40:26 2017 daemon.notice netifd: Network device 'wlan0-adhoc'
link is up
Tue Apr 18 13:40:26 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc' has link connectivity
Tue Apr 18 13:40:26 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc' is setting up now
Tue Apr 18 13:40:26 2017 kern.warn kernel: [ 329.211810] batman_adv: The
newly added mac address (78:a3:51:16:d9:e9) already exists on: eth0-2_29
Tue Apr 18 13:40:26 2017 kern.warn kernel: [ 329.221400] batman_adv: It is
strongly recommended to keep mac addresses unique to avoid problems!
Tue Apr 18 13:40:26 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_bmx6_if' is enabled
Tue Apr 18 13:40:26 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_bmx6_if' is setting up now
Tue Apr 18 13:40:26 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_bmx6_if' is now up
Tue Apr 18 13:40:26 2017 kern.warn kernel: [ 329.400455] batman_adv: The
newly added mac address (78:a3:51:16:d9:e9) already exists on: eth0-2_29
Tue Apr 18 13:40:26 2017 kern.warn kernel: [ 329.409901] batman_adv: It is
strongly recommended to keep mac addresses unique to avoid problems!
Tue Apr 18 13:40:26 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_batadv_if' is enabled
Tue Apr 18 13:40:26 2017 daemon.notice netifd: Network alias 'wlan0-adhoc'
link is up
Tue Apr 18 13:40:26 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc' is now up
Tue Apr 18 13:40:26 2017 daemon.notice netifd: 8021ad 'wlan0-adhoc_13' link
is up
Tue Apr 18 13:40:26 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_bmx6_if' has link connectivity
Tue Apr 18 13:40:26 2017 daemon.notice netifd: 8021ad 'wlan0-adhoc_29' link
is up
Tue Apr 18 13:40:26 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_batadv_if' has link connectivity
Tue Apr 18 13:40:26 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_batadv_if' is setting up now
Tue Apr 18 13:40:27 2017 kern.info kernel: [ 329.855839] batman_adv: bat0:
Adding interface: wlan0-adhoc_29
Tue Apr 18 13:40:27 2017 kern.info kernel: [ 329.861886] batman_adv: bat0:
Interface activated: wlan0-adhoc_29
Tue Apr 18 13:40:27 2017 daemon.notice netifd: Interface
'lm_net_wlan0_adhoc_batadv_if' is now up
Tue Apr 18 13:40:27 2017 kern.info kernel: [ 330.037800] br-lan: port
5(wlan0-ap) entered forwarding state
Tue Apr 18 13:40:27 2017 kern.info kernel: [ 330.117796] br-lan: port
6(wlan0-apname) entered forwarding state
Tue Apr 18 13:40:27 2017 daemon.info dnsmasq-dhcp[1691]: RTR-SOLICIT(anygw)
4c:66:41:95:3b:c9
Tue Apr 18 13:40:27 2017 daemon.info dnsmasq-dhcp[1691]: RTR-ADVERT(anygw)
2a00:1508:a0d:fe00::
Tue Apr 18 13:40:27 2017 daemon.info dnsmasq-dhcp[1691]: DHCPREQUEST(anygw)
10.13.12.148 4c:66:41:95:3b:c9
Tue Apr 18 13:40:27 2017 daemon.info dnsmasq-dhcp[1691]: DHCPACK(anygw)
10.13.12.148 4c:66:41:95:3b:c9 android-171fad8e332aaaf2
Tue Apr 18 13:40:28 2017 daemon.info dnsmasq-dhcp[1691]: RTR-SOLICIT(anygw)
4c:66:41:95:3b:c9
Tue Apr 18 13:40:28 2017 daemon.info dnsmasq-dhcp[1691]: RTR-ADVERT(anygw)
2a00:1508:a0d:fe00::
Tue Apr 18 13:40:35 2017 kern.warn kernel: [ 336.666272] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:40:45 2017 kern.warn kernel: [ 342.185747] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:40:52 2017 daemon.notice hostapd: wlan0-apname:
AP-STA-DISCONNECTED 4c:66:41:95:3b:c9
Tue Apr 18 13:40:52 2017 daemon.info hostapd: wlan0-apname: STA
4c:66:41:95:3b:c9 IEEE 802.11: disassociated
Tue Apr 18 13:40:52 2017 daemon.info hostapd: wlan0-ap: STA
4c:66:41:95:3b:c9 IEEE 802.11: authenticated
Tue Apr 18 13:40:52 2017 daemon.info hostapd: wlan0-ap: STA
4c:66:41:95:3b:c9 IEEE 802.11: associated (aid 1)
Tue Apr 18 13:40:52 2017 daemon.notice hostapd: wlan0-ap: AP-STA-CONNECTED
4c:66:41:95:3b:c9
Tue Apr 18 13:40:53 2017 daemon.info dnsmasq-dhcp[1691]: RTR-SOLICIT(anygw)
4c:66:41:95:3b:c9
Tue Apr 18 13:40:53 2017 daemon.info dnsmasq-dhcp[1691]: RTR-ADVERT(anygw)
2a00:1508:a0d:fe00::
Tue Apr 18 13:40:53 2017 daemon.info dnsmasq-dhcp[1691]:
DHCPDISCOVER(anygw) 4c:66:41:95:3b:c9
Tue Apr 18 13:40:53 2017 daemon.info dnsmasq-dhcp[1691]: DHCPOFFER(anygw)
10.13.12.148 4c:66:41:95:3b:c9
Tue Apr 18 13:40:53 2017 daemon.info dnsmasq-dhcp[1691]: DHCPREQUEST(anygw)
10.13.12.148 4c:66:41:95:3b:c9
Tue Apr 18 13:40:53 2017 daemon.info dnsmasq-dhcp[1691]: DHCPACK(anygw)
10.13.12.148 4c:66:41:95:3b:c9 android-171fad8e332aaaf2
Tue Apr 18 13:40:54 2017 daemon.info dnsmasq-dhcp[1691]: RTR-SOLICIT(anygw)
4c:66:41:95:3b:c9
Tue Apr 18 13:40:54 2017 daemon.info dnsmasq-dhcp[1691]: RTR-ADVERT(anygw)
2a00:1508:a0d:fe00::
Tue Apr 18 13:40:55 2017 kern.warn kernel: [ 347.707611] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:41:05 2017 kern.warn kernel: [ 353.340601] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:41:15 2017 kern.warn kernel: [ 358.824999] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:41:25 2017 kern.warn kernel: [ 364.344507] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:41:35 2017 kern.warn kernel: [ 371.186664] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:41:45 2017 kern.warn kernel: [ 377.131345] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:41:55 2017 kern.warn kernel: [ 382.600389] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:42:05 2017 kern.warn kernel: [ 388.027194] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:42:15 2017 kern.warn kernel: [ 393.459183] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:42:25 2017 kern.warn kernel: [ 398.886651] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:42:35 2017 kern.warn kernel: [ 405.435538] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:42:45 2017 kern.warn kernel: [ 410.881764] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:42:55 2017 kern.warn kernel: [ 416.304365] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:43:05 2017 kern.warn kernel: [ 422.668798] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:43:15 2017 kern.warn kernel: [ 427.046477] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:43:25 2017 kern.warn kernel: [ 431.414030] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:43:35 2017 kern.warn kernel: [ 435.792671] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:43:45 2017 kern.warn kernel: [ 440.171403] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:43:55 2017 kern.warn kernel: [ 444.562040] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:44:00 2017 cron.info crond[741]: USER root pid 4472 cmd
/usr/bin/bmx6hosts_dnsmasq_update
Tue Apr 18 13:44:00 2017 user.notice bmx6hosts: New bmx6 hosts found,
updating dnsmasq
Tue Apr 18 13:44:01 2017 daemon.info dnsmasq[1691]: read /etc/hosts - 4
addresses
Tue Apr 18 13:44:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/d-d-h_78:a3:51:16:da:88 - 2 addresses
Tue Apr 18 13:44:01 2017 daemon.info dnsmasq[1691]: read /tmp/hosts/bmx6 -
8 addresses
Tue Apr 18 13:44:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dhcp.cfg02411c - 1 addresses
Tue Apr 18 13:44:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dnsmasq-lease-share - 4 addresses
Tue Apr 18 13:44:01 2017 daemon.info dnsmasq-dhcp[1691]: read /etc/ethers -
0 addresses
Tue Apr 18 13:44:01 2017 daemon.info dnsmasq-dhcp[1691]: read
/tmp/dhcp.hosts_remote
Tue Apr 18 13:44:05 2017 kern.warn kernel: [ 449.105307] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:44:15 2017 kern.warn kernel: [ 453.504530] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:44:25 2017 kern.warn kernel: [ 457.865852] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:44:36 2017 kern.warn kernel: [ 462.271860] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:44:46 2017 kern.warn kernel: [ 466.668247] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:44:56 2017 kern.warn kernel: [ 471.053440] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:45:00 2017 cron.info crond[741]: USER root pid 4537 cmd ( for
file in /etc/alfred/* ; do [ -x $file ] && $file ; done )
Tue Apr 18 13:45:00 2017 daemon.info dnsmasq[1691]: read /etc/hosts - 4
addresses
Tue Apr 18 13:45:00 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/d-d-h_78:a3:51:16:da:88 - 2 addresses
Tue Apr 18 13:45:00 2017 daemon.info dnsmasq[1691]: read /tmp/hosts/bmx6 -
8 addresses
Tue Apr 18 13:45:00 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dhcp.cfg02411c - 1 addresses
Tue Apr 18 13:45:00 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dnsmasq-lease-share - 4 addresses
Tue Apr 18 13:45:00 2017 daemon.info dnsmasq-dhcp[1691]: read /etc/ethers -
0 addresses
Tue Apr 18 13:45:00 2017 daemon.info dnsmasq-dhcp[1691]: read
/tmp/dhcp.hosts_remote
Tue Apr 18 13:45:01 2017 daemon.info dnsmasq[1691]: read /etc/hosts - 4
addresses
Tue Apr 18 13:45:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/d-d-h_78:a3:51:16:da:88 - 2 addresses
Tue Apr 18 13:45:01 2017 daemon.info dnsmasq[1691]: read /tmp/hosts/bmx6 -
8 addresses
Tue Apr 18 13:45:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dhcp.cfg02411c - 1 addresses
Tue Apr 18 13:45:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dnsmasq-lease-share - 4 addresses
Tue Apr 18 13:45:01 2017 daemon.info dnsmasq-dhcp[1691]: read /etc/ethers -
0 addresses
Tue Apr 18 13:45:01 2017 daemon.info dnsmasq-dhcp[1691]: read
/tmp/dhcp.hosts_remote
Tue Apr 18 13:45:06 2017 kern.warn kernel: [ 475.627715] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:45:16 2017 kern.warn kernel: [ 480.016848] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:45:26 2017 kern.warn kernel: [ 484.406262] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:45:36 2017 kern.warn kernel: [ 488.784877] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:45:46 2017 kern.warn kernel: [ 493.150194] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:45:56 2017 kern.warn kernel: [ 497.557046] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:46:06 2017 kern.warn kernel: [ 501.926915] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:46:16 2017 kern.warn kernel: [ 506.332655] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:46:26 2017 kern.warn kernel: [ 511.634968] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:46:36 2017 kern.warn kernel: [ 517.063705] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:46:46 2017 kern.warn kernel: [ 522.475048] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:46:56 2017 kern.warn kernel: [ 527.902091] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:47:06 2017 kern.warn kernel: [ 533.316875] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:47:16 2017 kern.warn kernel: [ 538.743709] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:47:26 2017 kern.warn kernel: [ 544.172275] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:47:36 2017 kern.warn kernel: [ 549.597331] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:47:46 2017 kern.warn kernel: [ 555.015871] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:47:56 2017 kern.warn kernel: [ 560.438628] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:48:00 2017 cron.info crond[741]: USER root pid 4921 cmd
/usr/bin/bmx6hosts_dnsmasq_update
Tue Apr 18 13:48:06 2017 kern.warn kernel: [ 565.972192] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:48:16 2017 kern.warn kernel: [ 571.406837] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:48:26 2017 kern.warn kernel: [ 578.012848] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:48:36 2017 kern.warn kernel: [ 582.520037] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:48:46 2017 kern.warn kernel: [ 586.899706] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:48:56 2017 kern.warn kernel: [ 591.269630] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:49:06 2017 kern.warn kernel: [ 595.634435] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:49:16 2017 kern.warn kernel: [ 600.024760] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:49:26 2017 kern.warn kernel: [ 604.405014] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:49:36 2017 kern.warn kernel: [ 608.785423] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:49:46 2017 kern.warn kernel: [ 613.157397] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:49:56 2017 kern.warn kernel: [ 617.530087] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:50:00 2017 cron.info crond[741]: USER root pid 5082 cmd ( for
file in /etc/alfred/* ; do [ -x $file ] && $file ; done )
Tue Apr 18 13:50:00 2017 daemon.info dnsmasq[1691]: read /etc/hosts - 4
addresses
Tue Apr 18 13:50:00 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/d-d-h_78:a3:51:16:da:88 - 2 addresses
Tue Apr 18 13:50:00 2017 daemon.info dnsmasq[1691]: read /tmp/hosts/bmx6 -
8 addresses
Tue Apr 18 13:50:00 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dhcp.cfg02411c - 1 addresses
Tue Apr 18 13:50:00 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dnsmasq-lease-share - 4 addresses
Tue Apr 18 13:50:00 2017 daemon.info dnsmasq-dhcp[1691]: read /etc/ethers -
0 addresses
Tue Apr 18 13:50:00 2017 daemon.info dnsmasq-dhcp[1691]: read
/tmp/dhcp.hosts_remote
Tue Apr 18 13:50:01 2017 daemon.info dnsmasq[1691]: read /etc/hosts - 4
addresses
Tue Apr 18 13:50:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/d-d-h_78:a3:51:16:da:88 - 2 addresses
Tue Apr 18 13:50:01 2017 daemon.info dnsmasq[1691]: read /tmp/hosts/bmx6 -
8 addresses
Tue Apr 18 13:50:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dhcp.cfg02411c - 1 addresses
Tue Apr 18 13:50:01 2017 daemon.info dnsmasq[1691]: read
/tmp/hosts/dnsmasq-lease-share - 4 addresses
Tue Apr 18 13:50:01 2017 daemon.info dnsmasq-dhcp[1691]: read /etc/ethers -
0 addresses
Tue Apr 18 13:50:01 2017 daemon.info dnsmasq-dhcp[1691]: read
/tmp/dhcp.hosts_remote
Tue Apr 18 13:50:06 2017 kern.warn kernel: [ 622.076814] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:50:16 2017 kern.warn kernel: [ 626.448855] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:50:26 2017 kern.warn kernel: [ 630.818305] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:50:36 2017 kern.warn kernel: [ 635.197228] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:50:46 2017 kern.warn kernel: [ 639.578393] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:50:56 2017 kern.warn kernel: [ 643.979689] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:51:06 2017 kern.warn kernel: [ 648.356709] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:51:16 2017 kern.warn kernel: [ 652.758803] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:51:26 2017 kern.warn kernel: [ 657.140839] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:51:36 2017 kern.warn kernel: [ 661.507304] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:51:46 2017 kern.warn kernel: [ 665.863998] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:51:56 2017 kern.warn kernel: [ 670.233672] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:52:00 2017 cron.info crond[741]: USER root pid 5215 cmd
/usr/bin/bmx6hosts_dnsmasq_update
Tue Apr 18 13:52:06 2017 kern.warn kernel: [ 674.726131] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:52:16 2017 kern.warn kernel: [ 679.089356] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:52:26 2017 kern.warn kernel: [ 683.443034] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:52:36 2017 kern.warn kernel: [ 687.813116] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:52:46 2017 kern.warn kernel: [ 692.167532] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:52:57 2017 kern.warn kernel: [ 696.533811] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:53:07 2017 kern.warn kernel: [ 700.915965] br-lan: received
packet on bat0 with own address as source address
Tue Apr 18 13:53:17 2017 kern.warn kernel: [ 705.289365] br-lan: received
packet on bat0 with own address as source address
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Di., 18. Apr. 2017 um
15:52 Uhr:
@Ilario
radio0 behaves as expected
radio1 has issues
1. on site: http://10.13.0.1/cgi-bin/luci/admin/network/wireless there is
no channel assigned to the adhoc despite the fact that on site:
http://10.13.0.1/cgi-bin/luci/admin/network/wireless/radio1.network3 everything
seems ok. Fact is radio1 is not meshing.
2. as with earlier firmwares (except the stock openwrt) radio1 crashes
under traffic. Device reboots.
Cheers
Ilario Gelmetti <iochesonome(a)gmail.com> schrieb am Di., 18. Apr. 2017 um
11:12 Uhr:
Ok, that's great, this means that
lime-config now does its work.
The line I asked you to comment out was added by G10h4ck 2 years ago:
https://github.com/libremesh/lime-packages/commit/caad3acb2d0512ba80558aabf…
@G10h4ck how should we fix it? Can we just delete that line?
@Juergen how is the router behavior now? Is it working as expected?
Bye!
Ilario
On 04/15/2017 03:15 AM, Juergen Kimmel wrote:
I'm so sorry lost orientation once moree,
should be at sleep at this
time of the night ;).
So here is network after changing line 178, reboot and lime-config:
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
config interface 'lan'
option type 'bridge'
option proto 'static'
option ip6assign '60'
option ip6addr '2a00:1508:a0d:fe00::16:da88/64'
option ipaddr '10.13.218.136'
option netmask '255.255.0.0'
option mtu '1500'
list ifname 'bat0'
list ifname 'eth0.1'
config device 'lan_dev'
option name 'eth0.1'
option macaddr '78:a3:51:16:da:88'
config interface 'wan'
option ifname 'eth0.2'
option proto 'dhcp'
config device 'wan_dev'
option name 'eth0.2'
option macaddr '78:a3:51:16:da:89'
config interface 'wan6'
option ifname 'eth0.2'
option proto 'none'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0 1 2 3 6t'
config switch_vlan
option device 'switch0'
option vlan '2'
option ports '4 6t'
config device 'lm_net_br_lan_anygw_dev'
option type 'macvlan'
option name 'anygw'
option ifname 'br-lan'
option macaddr 'aa:aa:aa:0d:fe:aa'
config interface 'lm_net_br_lan_anygw_if'
option ifname 'anygw'
option auto '1'
option netmask '255.255.0.0'
option proto 'static'
option ipaddr '10.13.0.1'
option ip6addr '2a00:1508:a0d:fe00::1/64'
config rule6 'lm_net_anygw_rule6'
option src '2a00:1508:a0d:fe00::1/128'
option lookup '170'
config route6 'lm_net_anygw_route6'
option interface 'lm_net_br_lan_anygw_if'
option target '2a00:1508:a0d:fe00::/64'
option table '170'
config rule 'lm_net_anygw_rule4'
option src '10.13.0.1/32 <http://10.13.0.1/32>'
option lookup '170'
config route 'lm_net_anygw_route4'
option interface 'lm_net_br_lan_anygw_if'
option target '10.13.0.0'
option netmask '255.255.0.0'
option table '170'
config interface 'lm_net_batadv_dummy_if'
option ifname 'dummy0'
option macaddr 'aa:a3:51:16:da:88'
option proto 'batadv'
option mesh 'bat0'
config device 'lm_net_lm_net_eth0_1_bmx6_dev'
option type '8021ad'
option name 'eth0-1_13'
option ifname 'eth0.1'
option vid '13'
option mtu '1398'
config interface 'lm_net_eth0_1_bmx6_if'
option proto 'none'
option auto '1'
option ifname 'eth0-1_13'
config interface 'lm_net_wlan1_adhoc'
option proto 'none'
option mtu '1536'
option auto '1'
config device 'lm_net_lm_net_wlan1_adhoc_batadv_dev'
option type '8021ad'
option name 'wlan1-adhoc_29'
option ifname '@lm_net_wlan1_adhoc'
option vid '29'
option mtu '1532'
config interface 'lm_net_wlan1_adhoc_batadv_if'
option auto '1'
option ifname 'wlan1-adhoc_29'
option proto 'batadv'
option mesh 'bat0'
config device 'lm_net_lm_net_wlan1_adhoc_bmx6_dev'
option type '8021ad'
option name 'wlan1-adhoc_13'
option ifname '@lm_net_wlan1_adhoc'
option vid '13'
option mtu '1398'
config interface 'lm_net_wlan1_adhoc_bmx6_if'
option auto '1'
option ifname 'wlan1-adhoc_13'
option proto 'static'
option ipaddr '169.254.218.136'
option netmask '255.255.255.255'
config device 'lm_net_lm_net_eth0_2_batadv_dev'
option type '8021ad'
option name 'eth0-2_29'
option ifname 'eth0.2'
option vid '29'
option mtu '1532'
config interface 'lm_net_eth0_2_batadv_if'
option auto '1'
option ifname 'eth0-2_29'
option proto 'batadv'
option mesh 'bat0'
config device 'lm_net_lm_net_eth0_2_bmx6_dev'
option type '8021ad'
option name 'eth0-2_13'
option ifname 'eth0.2'
option vid '13'
option mtu '1398'
config interface 'lm_net_eth0_2_bmx6_if'
option proto 'none'
option auto '1'
option ifname 'eth0-2_13'
config interface 'lm_net_wlan0_adhoc'
option proto 'none'
option mtu '1536'
option auto '1'
config device 'lm_net_lm_net_wlan0_adhoc_batadv_dev'
option type '8021ad'
option name 'wlan0-adhoc_29'
option ifname '@lm_net_wlan0_adhoc'
option vid '29'
option mtu '1532'
config interface 'lm_net_wlan0_adhoc_batadv_if'
option auto '1'
option ifname 'wlan0-adhoc_29'
option proto 'batadv'
option mesh 'bat0'
config device 'lm_net_lm_net_wlan0_adhoc_bmx6_dev'
option type '8021ad'
option name 'wlan0-adhoc_13'
option ifname '@lm_net_wlan0_adhoc'
option vid '13'
option mtu '1398'
config interface 'lm_net_wlan0_adhoc_bmx6_if'
option auto '1'
option ifname 'wlan0-adhoc_13'
option proto 'static'
option ipaddr '169.254.218.137'
option netmask '255.255.255.255'
config device 'lm_net_lm_net_eth0_bmx6_dev'
option type '8021ad'
option name 'eth0_13'
option ifname 'eth0'
option vid '13'
option mtu '1398'
config interface 'lm_net_eth0_bmx6_if'
option proto 'none'
option auto '1'
option ifname 'eth0_13'
Ilario Gelmetti <iochesonome(a)gmail.com <mailto:iochesonome@gmail.com>>
schrieb am Fr., 14. Apr. 2017 um 13:39 Uhr:
On 04/14/2017 05:53 AM, Juergen Kimmel wrote:
https://github.com/libremesh/lime-packages/blob/develop/packages/lime-syste…
Here is
/etc/config/network
config device 'lan_dev'
option name 'eth0.1'
option macaddr '78:a3:51:16:da:88'
config device 'wan_dev'
option name 'eth0.2'
option macaddr '78:a3:51:16:da:89'
Ok, now can you try to comment out (prepending "--!") line 178 in
/usr/lib/lua/lime/network.lua ?
function owrt_device_parser(section)
dev_parser(section["name"])
--! dev_parser(section["ifname"])
end
According to LEDE and OpenWrt wikis [1,2], sections of type device
in
/etc/config/network should have an ifname
option.
LibreMesh scripts assume that there is such option and the crash you
experienced could be due to the lack of an "option ifname 'eth0'"
in
device sections in /etc/config/network on ramips.
I hope this works... :)
Ilario
[1] https://wiki.openwrt.org/doc/uci/network#devices
[2]
https://lede-project.org/docs/user-guide/switch_configuration#devices
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users 
5:50 p.m.
On Tuesday 18 April 2017 11:11:57 Ilario Gelmetti wrote:
Ok, that's great, this means that lime-config now
does its work.
The line I asked you to comment out was added by G10h4ck 2 years ago:
https://github.com/libremesh/lime-packages/commit/caad3acb2d0512ba80558aabf6
7c3ff21d233e88#diff-b62243e9ade7bd69d43e6f71647fded4R153
@G10h4ck how should we fix it? Can we just delete that line?
No, at worse if ifname is not always defined it can be changed like this
if section["ifname"] then dev_parser(section["ifname"]) end
@Juergen how is the router behavior now? Is it working as expected?
Bye!
Ilario
On 04/15/2017 03:15 AM, Juergen Kimmel wrote:
> I'm so sorry lost orientation once moree, should be at sleep at this
> time of the night ;).
>
> So here is network after changing line 178, reboot and lime-config:
>
>
> config interface 'loopback'
> option ifname 'lo'
> option proto 'static'
> option ipaddr '127.0.0.1'
> option netmask '255.0.0.0'
>
> config globals 'globals'
>
> config interface 'lan'
> option type 'bridge'
> option proto 'static'
> option ip6assign '60'
> option ip6addr '2a00:1508:a0d:fe00::16:da88/64'
> option ipaddr '10.13.218.136'
> option netmask '255.255.0.0'
> option mtu '1500'
> list ifname 'bat0'
> list ifname 'eth0.1'
>
> config device 'lan_dev'
> option name 'eth0.1'
> option macaddr '78:a3:51:16:da:88'
>
> config interface 'wan'
> option ifname 'eth0.2'
> option proto 'dhcp'
>
> config device 'wan_dev'
> option name 'eth0.2'
> option macaddr '78:a3:51:16:da:89'
>
> config interface 'wan6'
> option ifname 'eth0.2'
> option proto 'none'
>
> config switch
> option name 'switch0'
> option reset '1'
> option enable_vlan '1'
>
> config switch_vlan
> option device 'switch0'
> option vlan '1'
> option ports '0 1 2 3 6t'
>
> config switch_vlan
> option device 'switch0'
> option vlan '2'
> option ports '4 6t'
>
> config device 'lm_net_br_lan_anygw_dev'
> option type 'macvlan'
> option name 'anygw'
> option ifname 'br-lan'
> option macaddr 'aa:aa:aa:0d:fe:aa'
>
> config interface 'lm_net_br_lan_anygw_if'
> option ifname 'anygw'
> option auto '1'
> option netmask '255.255.0.0'
> option proto 'static'
> option ipaddr '10.13.0.1'
> option ip6addr '2a00:1508:a0d:fe00::1/64'
>
> config rule6 'lm_net_anygw_rule6'
> option src '2a00:1508:a0d:fe00::1/128'
> option lookup '170'
>
> config route6 'lm_net_anygw_route6'
> option interface 'lm_net_br_lan_anygw_if'
> option target '2a00:1508:a0d:fe00::/64'
> option table '170'
>
> config rule 'lm_net_anygw_rule4'
> option src '10.13.0.1/32 <http://10.13.0.1/32>'
> option lookup '170'
>
> config route 'lm_net_anygw_route4'
> option interface 'lm_net_br_lan_anygw_if'
> option target '10.13.0.0'
> option netmask '255.255.0.0'
> option table '170'
>
> config interface 'lm_net_batadv_dummy_if'
> option ifname 'dummy0'
> option macaddr 'aa:a3:51:16:da:88'
> option proto 'batadv'
> option mesh 'bat0'
>
> config device 'lm_net_lm_net_eth0_1_bmx6_dev'
> option type '8021ad'
> option name 'eth0-1_13'
> option ifname 'eth0.1'
> option vid '13'
> option mtu '1398'
>
> config interface 'lm_net_eth0_1_bmx6_if'
> option proto 'none'
> option auto '1'
> option ifname 'eth0-1_13'
>
> config interface 'lm_net_wlan1_adhoc'
> option proto 'none'
> option mtu '1536'
> option auto '1'
>
> config device 'lm_net_lm_net_wlan1_adhoc_batadv_dev'
> option type '8021ad'
> option name 'wlan1-adhoc_29'
> option ifname '@lm_net_wlan1_adhoc'
> option vid '29'
> option mtu '1532'
>
> config interface 'lm_net_wlan1_adhoc_batadv_if'
> option auto '1'
> option ifname 'wlan1-adhoc_29'
> option proto 'batadv'
> option mesh 'bat0'
>
> config device 'lm_net_lm_net_wlan1_adhoc_bmx6_dev'
> option type '8021ad'
> option name 'wlan1-adhoc_13'
> option ifname '@lm_net_wlan1_adhoc'
> option vid '13'
> option mtu '1398'
>
> config interface 'lm_net_wlan1_adhoc_bmx6_if'
> option auto '1'
> option ifname 'wlan1-adhoc_13'
> option proto 'static'
> option ipaddr '169.254.218.136'
> option netmask '255.255.255.255'
>
> config device 'lm_net_lm_net_eth0_2_batadv_dev'
> option type '8021ad'
> option name 'eth0-2_29'
> option ifname 'eth0.2'
> option vid '29'
> option mtu '1532'
>
> config interface 'lm_net_eth0_2_batadv_if'
> option auto '1'
> option ifname 'eth0-2_29'
> option proto 'batadv'
> option mesh 'bat0'
>
> config device 'lm_net_lm_net_eth0_2_bmx6_dev'
> option type '8021ad'
> option name 'eth0-2_13'
> option ifname 'eth0.2'
> option vid '13'
> option mtu '1398'
>
> config interface 'lm_net_eth0_2_bmx6_if'
> option proto 'none'
> option auto '1'
> option ifname 'eth0-2_13'
>
> config interface 'lm_net_wlan0_adhoc'
> option proto 'none'
> option mtu '1536'
> option auto '1'
>
> config device 'lm_net_lm_net_wlan0_adhoc_batadv_dev'
> option type '8021ad'
> option name 'wlan0-adhoc_29'
> option ifname '@lm_net_wlan0_adhoc'
> option vid '29'
> option mtu '1532'
>
> config interface 'lm_net_wlan0_adhoc_batadv_if'
> option auto '1'
> option ifname 'wlan0-adhoc_29'
> option proto 'batadv'
> option mesh 'bat0'
>
> config device 'lm_net_lm_net_wlan0_adhoc_bmx6_dev'
> option type '8021ad'
> option name 'wlan0-adhoc_13'
> option ifname '@lm_net_wlan0_adhoc'
> option vid '13'
> option mtu '1398'
>
> config interface 'lm_net_wlan0_adhoc_bmx6_if'
> option auto '1'
> option ifname 'wlan0-adhoc_13'
> option proto 'static'
> option ipaddr '169.254.218.137'
> option netmask '255.255.255.255'
>
> config device 'lm_net_lm_net_eth0_bmx6_dev'
> option type '8021ad'
> option name 'eth0_13'
> option ifname 'eth0'
> option vid '13'
> option mtu '1398'
>
> config interface 'lm_net_eth0_bmx6_if'
> option proto 'none'
> option auto '1'
> option ifname 'eth0_13'
>
>
>
>
> Ilario Gelmetti <iochesonome(a)gmail.com <mailto:iochesonome@gmail.com>>
>
> schrieb am Fr., 14. Apr. 2017 um 13:39 Uhr:
> On 04/14/2017 05:53 AM, Juergen Kimmel wrote:
> > Here is
> > /etc/config/network
> >
> > config device 'lan_dev'
> > option name 'eth0.1'
> > option macaddr '78:a3:51:16:da:88'
> >
> > config device 'wan_dev'
> > option name 'eth0.2'
> > option macaddr '78:a3:51:16:da:89'
>
> Ok, now can you try to comment out (prepending "--!") line 178 in
> /usr/lib/lua/lime/network.lua ?
>
> function owrt_device_parser(section)
>
> dev_parser(section["name"])
>
> --! dev_parser(section["ifname"])
> end
>
> https://github.com/libremesh/lime-packages/blob/develop/packages/lime-> >
system/files/usr/lib/lua/lime/network.lua#L178
>
> According to LEDE and OpenWrt wikis [1,2], sections of type device in
> /etc/config/network should have an ifname option.
> LibreMesh scripts assume that there is such option and the crash you
> experienced could be due to the lack of an "option ifname
'eth0'" in
> device sections in /etc/config/network on ramips.
> I hope this works... :)
> Ilario
>
> [1] https://wiki.openwrt.org/doc/uci/network#devices
> [2]
> https://lede-project.org/docs/user-guide/switch_configuration#devices
15 Apr
15 Apr
12:43 a.m.
...and here the syslog:
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 0.000000] Linux version
4.4.50 (buildbot(a)builds-02.infra.lede-project.org) (gcc version 5.4.0 (LEDE
GCC 5.4.0 r3103-1b51a49) ) #0 Mon Feb 20 17:13:44 2017
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Board has DDR2
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Analog PMU set to
hw control
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Digital PMU set
to hw control
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] SoC Type:
MediaTek MT7620A ver:2 eco:6
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] bootconsole
[early0] enabled
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] CPU0 revision is:
00019650 (MIPS 24KEc)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] MIPS: machine is
ZBT-APE522II
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Determined
physical RAM map:
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] memory: 08000000
@ 00000000 (usable)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Initrd not found
or empty - disabling initrd
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Zone ranges:
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Normal [mem
0x0000000000000000-0x0000000007ffffff]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Movable zone
start for each node
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Early memory node
ranges
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] node 0: [mem
0x0000000000000000-0x0000000007ffffff]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Initmem setup
node 0 [mem 0x0000000000000000-0x0000000007ffffff]
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.000000] On node 0
totalpages: 32768
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.000000]
free_area_init_node: node 0, pgdat 8035a4b0, node_mem_map 81000000
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.000000] Normal zone:
256 pages used for memmap
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.000000] Normal zone: 0
pages reserved
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.000000] Normal zone:
32768 pages, LIFO batch:7
Fri Apr 14 04:03:28 2017 kern.warn kernel: [ 0.000000] Primary
instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
Fri Apr 14 04:03:28 2017 kern.warn kernel: [ 0.000000] Primary data
cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.000000] pcpu-alloc: s0
r0 d32768 u32768 alloc=1*32768
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.000000] pcpu-alloc: [0]
0
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Built 1 zonelists
in Zone order, mobility grouping on. Total pages: 32512
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 0.000000] Kernel command
line: console=ttyS0,115200 rootfstype=squashfs,jffs2
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] PID hash table
entries: 512 (order: -1, 2048 bytes)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Dentry cache hash
table entries: 16384 (order: 4, 65536 bytes)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Inode-cache hash
table entries: 8192 (order: 3, 32768 bytes)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Writing ErrCtl
register=00067070
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Readback ErrCtl
register=00067070
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Memory:
125924K/131072K available (3012K kernel code, 144K rwdata, 384K rodata,
164K init, 208K bss, 5148K reserved, 0K cma-reserved)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] SLUB: HWalign=32,
Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] NR_IRQS:256
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] CPU Clock: 580MHz
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] clocksource:
systick: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 583261500 ns
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] systick: enable
autosleep mode
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] systick: running
- mult: 214748, shift: 32
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] clocksource:
MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6590553264 ns
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000011] sched_clock: 32
bits at 290MHz, resolution 3ns, wraps every 7405115902ns
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.007578] Calibrating delay
loop... 385.84 BogoMIPS (lpj=1929216)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.070069] pid_max: default:
32768 minimum: 301
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.074692] Mount-cache hash
table entries: 1024 (order: 0, 4096 bytes)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.081060] Mountpoint-cache
hash table entries: 1024 (order: 0, 4096 bytes)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.094466] clocksource:
jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:
19112604462750000 ns
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.104067] pinctrl core:
initialized pinctrl subsystem
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.110363] NET: Registered
protocol family 16
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.373101] PCI host bridge
/pcie@10140000 ranges:
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.377715] MEM
0x0000000020000000..0x000000002fffffff
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.382767] IO
0x0000000010160000..0x000000001016ffff
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.400644] rt2880_gpio
10000600.gpio: registering 24 gpios
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.406038] rt2880_gpio
10000600.gpio: registering 24 irq handlers
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.412276] rt2880_gpio
10000638.gpio: registering 16 gpios
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.417643] rt2880_gpio
10000638.gpio: registering 16 irq handlers
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.423832] rt2880_gpio
10000660.gpio: registering 32 gpios
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.429198] rt2880_gpio
10000660.gpio: registering 32 irq handlers
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.435386] rt2880_gpio
10000688.gpio: registering 1 gpios
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.440668] rt2880_gpio
10000688.gpio: registering 1 irq handlers
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.447360] PCI host bridge
to bus 0000:00
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.451288] pci_bus 0000:00:
root bus resource [mem 0x20000000-0x2fffffff]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.458002] pci_bus 0000:00:
root bus resource [io 0xffffffff]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.463703] pci_bus 0000:00:
root bus resource [??? 0x00000000 flags 0x0]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.470306] pci_bus 0000:00:
No busn resource found for root bus, will use [bus 00-ff]
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.478028] pci
0000:00:00.0: [1814:0802] type 01 class 0x060400
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.478076] pci
0000:00:00.0: reg 0x10: [mem 0x00000000-0x7fffffff]
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.478100] pci
0000:00:00.0: reg 0x14: [mem 0x20200000-0x2020ffff]
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.478175] pci
0000:00:00.0: supports D1
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.478194] pci
0000:00:00.0: PME# supported from D0 D1 D3hot
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.478670] pci
0000:01:00.0: [14c3:7662] type 00 class 0x028000
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.478742] pci
0000:01:00.0: reg 0x10: [mem 0x00000000-0x000fffff 64bit]
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.478805] pci
0000:01:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.478900] pci
0000:01:00.0: PME# supported from D0 D3hot D3cold
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.479146] pci_bus 0000:01:
busn_res: [bus 01-ff] end is updated to 01
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.479176] pci_bus 0000:00:
busn_res: [bus 00-ff] end is updated to 01
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.479234] pci 0000:00:00.0:
BAR 0: no space for [mem size 0x80000000]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.485645] pci 0000:00:00.0:
BAR 0: failed to assign [mem size 0x80000000]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.492362] pci 0000:00:00.0:
BAR 8: assigned [mem 0x20000000-0x200fffff]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.498968] pci 0000:00:00.0:
BAR 9: assigned [mem 0x20100000-0x201fffff pref]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.505968] pci 0000:00:00.0:
BAR 1: assigned [mem 0x20200000-0x2020ffff]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.512586] pci 0000:01:00.0:
BAR 0: assigned [mem 0x20000000-0x200fffff 64bit]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.519678] pci 0000:01:00.0:
BAR 6: assigned [mem 0x20100000-0x2010ffff pref]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.526689] pci 0000:00:00.0:
PCI bridge to [bus 01]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.531498] pci 0000:00:00.0:
bridge window [mem 0x20000000-0x200fffff]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.538099] pci 0000:00:00.0:
bridge window [mem 0x20100000-0x201fffff pref]
Fri Apr 14 04:03:28 2017 kern.err kernel: [ 0.545116] pci 0000:00:00.0:
card - bus=0x0, slot = 0x0 irq=0
Fri Apr 14 04:03:28 2017 kern.err kernel: [ 0.550786] pci 0000:01:00.0:
card - bus=0x1, slot = 0x0 irq=4
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.557294] clocksource:
Switched to clocksource systick
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.563716] NET: Registered
protocol family 2
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.568950] TCP established
hash table entries: 1024 (order: 0, 4096 bytes)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.575675] TCP bind hash
table entries: 1024 (order: 0, 4096 bytes)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.581903] TCP: Hash tables
configured (established 1024 bind 1024)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.588125] UDP hash table
entries: 256 (order: 0, 4096 bytes)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.593750] UDP-Lite hash
table entries: 256 (order: 0, 4096 bytes)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.600133] NET: Registered
protocol family 1
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.604355] PCI: CLS 80
bytes, default 32
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.609207] rt-timer
10000100.timer: maximum frequency is 1220Hz
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.615783] futex hash table
entries: 256 (order: -1, 3072 bytes)
Fri Apr 14 04:03:28 2017 kern.warn kernel: [ 0.621779] Crashlog
allocated RAM at address 0x3f00000
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.642942] squashfs: version
4.0 (2009/01/31) Phillip Lougher
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.648611] jffs2: version
2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat,
Inc.
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.660735] io scheduler noop
registered
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.664480] io scheduler
deadline registered (default)
Fri Apr 14 04:03:28 2017 kern.err kernel: [ 0.669778] ralink-usb-phy
usbphy: invalid resource
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.675080] Serial:
8250/16550 driver, 16 ports, IRQ sharing enabled
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.684847] console [ttyS0]
disabled
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.688355]
10000c00.uartlite: ttyS0 at MMIO 0x10000c00 (irq = 20, base_baud = 2500000)
is a Palmchip BK-3103
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.697965] console [ttyS0]
enabled
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.705007] bootconsole
[early0] disabled
Fri Apr 14 04:03:28 2017 kern.warn kernel: [ 0.719828] spi spi0.0: force
spi mode3
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.724312] m25p80 spi0.0:
w25q128 (16384 Kbytes)
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 0.729215] 4 ofpart
partitions found on MTD device spi0.0
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 0.734809] Creating 4 MTD
partitions on "spi0.0":
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 0.739717]
0x000000000000-0x000000030000 : "u-boot"
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 0.746620]
0x000000030000-0x000000040000 : "u-boot-env"
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 0.753962]
0x000000040000-0x000000050000 : "factory"
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 0.760998]
0x000000050000-0x000000fd0000 : "firmware"
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 2.073525] 2 uimage-fw
partitions found on MTD device firmware
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 2.079616]
0x000000050000-0x000000178296 : "kernel"
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 2.086294]
0x000000178296-0x000000fd0000 : "rootfs"
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 2.093247] mtd: device 5
(rootfs) set to be root filesystem
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 2.099238] 1
squashfs-split partitions found on MTD device rootfs
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 2.105555]
0x00000048a000-0x000000fd0000 : "rootfs_data"
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 2.115979] gsw: setting
port4 to ephy mode
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 2.120343] mtk_soc_eth
10100000.ethernet eth0 (uninitialized): port 0 link up (100Mbps/Full duplex)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 2.129902] mtk_soc_eth
10100000.ethernet: loaded mt7620 driver
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 2.136743] mtk_soc_eth
10100000.ethernet eth0: mediatek frame engine at 0xb0100000, irq 5
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 2.145769] rt2880_wdt
10000120.watchdog: Initialized
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 2.152414] NET: Registered
protocol family 10
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 2.161507] NET: Registered
protocol family 17
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 2.166127] bridge: automatic
filtering via arp/ip/ip6tables has been deprecated. Update your scripts to
load br_netfilter if you need this.
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 2.179055] 8021q: 802.1Q
VLAN Support v1.8
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 2.198258] VFS: Mounted root
(squashfs filesystem) readonly on device 31:5.
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 2.206354] Freeing unused
kernel memory: 164K (80377000 - 803a0000)
Fri Apr 14 04:03:28 2017 user.info kernel: [ 4.580373] init: Console is
alive
Fri Apr 14 04:03:28 2017 user.info kernel: [ 4.584067] init: - watchdog -
Fri Apr 14 04:03:28 2017 user.info kernel: [ 6.378665] init: - preinit -
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 8.031317] 8021q: adding
VLAN 0 to HW filter on device eth0
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 10.750732] jffs2: notice:
(344) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of
xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
Fri Apr 14 04:03:28 2017 user.info kernel: [ 10.769772] mount_root:
switching to jffs2 overlay
Fri Apr 14 04:03:28 2017 user.warn kernel: [ 10.787131] urandom-seed:
Seeding with /etc/urandom.seed
Fri Apr 14 04:03:28 2017 user.info kernel: [ 10.925635] procd: - early -
Fri Apr 14 04:03:28 2017 user.info kernel: [ 10.928688] procd: - watchdog
-
Fri Apr 14 04:03:28 2017 user.info kernel: [ 11.264343] procd: - ubus -
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 11.505897] random: ubusd:
uninitialized urandom read (4 bytes read, 25 bits of entropy available)
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 11.521578] random: ubusd:
uninitialized urandom read (4 bytes read, 25 bits of entropy available)
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 11.531321] random: ubusd:
uninitialized urandom read (4 bytes read, 25 bits of entropy available)
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 11.540634] random: ubusd:
uninitialized urandom read (4 bytes read, 25 bits of entropy available)
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 11.550226] random: ubusd:
uninitialized urandom read (4 bytes read, 25 bits of entropy available)
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 11.560069] random: ubusd:
uninitialized urandom read (4 bytes read, 26 bits of entropy available)
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 11.570285] random: ubusd:
uninitialized urandom read (4 bytes read, 26 bits of entropy available)
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 11.579697] random: ubusd:
uninitialized urandom read (4 bytes read, 26 bits of entropy available)
Fri Apr 14 04:03:28 2017 user.info kernel: [ 11.589299] procd: - init -
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.152863] tun: Universal
TUN/TAP device driver, 1.6
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.158112] tun: (C)
1999-2004 Max Krasnyansky <maxk(a)qualcomm.com>
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.186457] ip6_tables: (C)
2000-2006 Netfilter Core Team
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.211200] Loading modules
backported from Linux version wt-2016-10-03-1-g6fcb1a6
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.219005] Backport
generated by backports.git backports-20160324-9-g0e38f5c
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.361109] batman_adv:
B.A.T.M.A.N. advanced 2017.0 (compatibility version 15) loaded
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.399118] mt76x2e
0000:01:00.0: ASIC revision: 76120044
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.416681] mt76x2e
0000:01:00.0: ROM patch already applied
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.424018] mt76x2e
0000:01:00.0: Firmware Version: 0.0.00
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.429688] mt76x2e
0000:01:00.0: Build: 1
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.433870] mt76x2e
0000:01:00.0: Build Time: 201507311614____
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.475286] mt76x2e
0000:01:00.0: Firmware running!
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 12.485846] ieee80211 phy0:
Selected rate control algorithm 'minstrel_ht'
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 12.507113] Bridge
firewalling registered
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.557828] Ebtables v2.0
registered
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.569169] ip_tables: (C)
2000-2006 Netfilter Core Team
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.602777] nf_conntrack
version 0.5.0 (1970 buckets, 7880 max)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.746781] xt_time: kernel
timezone is -0000
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.783137] rt2800_wmac
10180000.wmac: loaded eeprom from mtd device "factory"
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.790602] ieee80211 phy1:
rt2x00_set_rt: Info - RT chipset 5390, rev 0500 detected
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.798543] ieee80211 phy1:
rt2x00_set_rf: Info - RF chipset 7620 detected
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 12.806315] ieee80211 phy1:
Selected rate control algorithm 'minstrel_ht'
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 14.155930] random: jshn:
uninitialized urandom read (4 bytes read, 30 bits of entropy available)
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 14.253639] random: ubusd:
uninitialized urandom read (4 bytes read, 30 bits of entropy available)
Fri Apr 14 04:03:29 2017 user.notice : Added device handler type: 8021ad
Fri Apr 14 04:03:29 2017 user.notice : Added device handler type: 8021q
Fri Apr 14 04:03:29 2017 user.notice : Added device handler type: macvlan
Fri Apr 14 04:03:29 2017 user.notice : Added device handler type: bridge
Fri Apr 14 04:03:29 2017 user.notice : Added device handler type: Network
device
Fri Apr 14 04:03:29 2017 user.notice : Added device handler type: tunnel
Fri Apr 14 04:03:30 2017 cron.info crond[741]: crond (busybox 1.25.1)
started, log level 5
Fri Apr 14 04:03:31 2017 authpriv.info dropbear[774]: Not backgrounding
Fri Apr 14 04:03:31 2017 user.notice : Starting netserver with host
'IN(6)ADDR_ANY' port '12865' and family AF_UNSPEC
Fri Apr 14 04:03:33 2017 user.notice : setting up led wlan1-link
Fri Apr 14 04:03:33 2017 user.notice : setting up led wlan1
Fri Apr 14 04:03:33 2017 user.notice : setting up led wlan0
Fri Apr 14 04:03:33 2017 daemon.err bmx6[813]: WARN
recv_ruleEvent_netlink_sk(): FIXING lost rule family=2 pref=60 to table=60
should=1 is=0
Fri Apr 14 04:03:33 2017 daemon.err bmx6[813]: WARN
recv_ruleEvent_netlink_sk(): FIXING lost rule family=10 pref=60 to
table=60 should=1 is=0
Fri Apr 14 04:03:33 2017 kern.info kernel: [ 19.641425] 8021q: adding
VLAN 0 to HW filter on device eth0
Fri Apr 14 04:03:33 2017 kern.info kernel: [ 19.687937] device eth0.1
entered promiscuous mode
Fri Apr 14 04:03:33 2017 kern.info kernel: [ 19.692846] device eth0
entered promiscuous mode
Fri Apr 14 04:03:33 2017 kern.info kernel: [ 19.746331] br-lan: port
1(eth0.1) entered forwarding state
Fri Apr 14 04:03:33 2017 kern.info kernel: [ 19.752069] br-lan: port
1(eth0.1) entered forwarding state
Fri Apr 14 04:03:33 2017 daemon.notice netifd: Interface 'lan' is enabled
Fri Apr 14 04:03:33 2017 daemon.notice netifd: Interface 'lan' is setting
up now
Fri Apr 14 04:03:33 2017 daemon.notice netifd: Interface 'lan' is now up
Fri Apr 14 04:03:33 2017 daemon.notice netifd: Interface 'loopback' is
enabled
Fri Apr 14 04:03:33 2017 daemon.notice netifd: Interface 'loopback' is
setting up now
Fri Apr 14 04:03:33 2017 daemon.notice netifd: Interface 'loopback' is now
up
Fri Apr 14 04:03:33 2017 daemon.notice netifd: Interface 'wan' is enabled
Fri Apr 14 04:03:33 2017 daemon.notice netifd: Interface 'wan6' is enabled
Fri Apr 14 04:03:33 2017 daemon.notice netifd: bridge 'br-lan' link is up
Fri Apr 14 04:03:33 2017 daemon.notice netifd: Interface 'lan' has link
connectivity
Fri Apr 14 04:03:33 2017 daemon.notice netifd: Network device 'eth0' link
is up
Fri Apr 14 04:03:33 2017 daemon.notice netifd: VLAN 'eth0.1' link is up
Fri Apr 14 04:03:33 2017 daemon.notice netifd: Network device 'lo' link is
up
Fri Apr 14 04:03:34 2017 daemon.notice netifd: Interface 'loopback' has
link connectivity
Fri Apr 14 04:03:34 2017 daemon.notice netifd: VLAN 'eth0.2' link is up
Fri Apr 14 04:03:34 2017 daemon.notice netifd: Interface 'wan' has link
connectivity
Fri Apr 14 04:03:34 2017 daemon.notice netifd: Interface 'wan' is setting
up now
Fri Apr 14 04:03:34 2017 daemon.notice netifd: Interface 'wan6' has link
connectivity
Fri Apr 14 04:03:34 2017 daemon.notice netifd: Interface 'wan6' is setting
up now
Fri Apr 14 04:03:34 2017 daemon.notice netifd: Interface 'wan6' is now up
Fri Apr 14 04:03:34 2017 daemon.notice netifd: wan (928): udhcpc: started,
v1.25.1
Fri Apr 14 04:03:35 2017 daemon.notice netifd: radio1 (871): command
failed: Not supported (-122)
Fri Apr 14 04:03:35 2017 daemon.notice netifd: wan (928): udhcpc: sending
discover
Fri Apr 14 04:03:35 2017 kern.info kernel: [ 21.745226] br-lan: port
1(eth0.1) entered forwarding state
Fri Apr 14 04:03:35 2017 user.notice : /etc/rc.d/S99alfred: waiting 30 secs
for bat0 interface...
Fri Apr 14 04:03:37 2017 daemon.err hostapd: Configuration file:
/var/run/hostapd-phy1.conf
Fri Apr 14 04:03:37 2017 daemon.err hostapd: Configuration file:
/var/run/hostapd-phy0.conf
Fri Apr 14 04:03:37 2017 kern.info kernel: [ 23.828425] IPv6:
ADDRCONF(NETDEV_UP): wlan1-ap: link is not ready
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 23.976393] IPv6:
ADDRCONF(NETDEV_UP): wlan0-ap: link is not ready
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 23.983311] device wlan1-ap
entered promiscuous mode
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 23.998821] device wlan0-ap
entered promiscuous mode
Fri Apr 14 04:03:38 2017 daemon.err hostapd: Using interface wlan1-ap with
hwaddr 78:a3:51:16:da:89 and ssid "LibreMesh.org"
Fri Apr 14 04:03:38 2017 daemon.notice netifd: wan (928): udhcpc: sending
discover
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.023748] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan1-ap: link becomes ready
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.030688] br-lan: port
2(wlan1-ap) entered forwarding state
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.036664] br-lan: port
2(wlan1-ap) entered forwarding state
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.051815] device
wlan1-apname entered promiscuous mode
Fri Apr 14 04:03:38 2017 daemon.err hostapd: Using interface wlan0-ap with
hwaddr 7a:a3:51:16:da:89 and ssid "LibreMesh.org"
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.228510] IPv6:
ADDRCONF(NETDEV_UP): wlan1-apname: link is not ready
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.235265] br-lan: port
4(wlan1-apname) entered forwarding state
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.241560] br-lan: port
4(wlan1-apname) entered forwarding state
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.251871] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan0-ap: link becomes ready
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.258868] br-lan: port
3(wlan0-ap) entered forwarding state
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.264773] br-lan: port
3(wlan0-ap) entered forwarding state
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.276978] device
wlan0-apname entered promiscuous mode
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.298808] IPv6:
ADDRCONF(NETDEV_UP): wlan0-apname: link is not ready
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.305510] br-lan: port
5(wlan0-apname) entered forwarding state
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.311808] br-lan: port
5(wlan0-apname) entered forwarding state
Fri Apr 14 04:03:38 2017 daemon.err hostapd: Using interface wlan1-apname
with hwaddr 78:a3:51:16:da:8a and ssid "LibreMesh.org/LiMe-16da88"
Fri Apr 14 04:03:38 2017 daemon.notice hostapd: wlan1-ap: interface state
UNINITIALIZED->ENABLED
Fri Apr 14 04:03:38 2017 daemon.notice hostapd: wlan1-ap: AP-ENABLED
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.331882] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan1-apname: link becomes ready
Fri Apr 14 04:03:38 2017 daemon.err hostapd: Using interface wlan0-apname
with hwaddr 7e:a3:51:16:da:89 and ssid "LibreMesh.org/LiMe-16da88"
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.373262] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan0-apname: link becomes ready
Fri Apr 14 04:03:38 2017 daemon.notice hostapd: wlan0-ap: interface state
UNINITIALIZED->ENABLED
Fri Apr 14 04:03:38 2017 daemon.notice hostapd: wlan0-ap: AP-ENABLED
Fri Apr 14 04:03:39 2017 daemon.notice netifd: radio1 (871): RTNETLINK
answers: Resource busy
Fri Apr 14 04:03:39 2017 daemon.notice netifd: radio1 (871): Interface 2
setup failed: IFUP_ERROR
Fri Apr 14 04:03:39 2017 kern.info kernel: [ 24.717380] IPv6:
ADDRCONF(NETDEV_UP): wlan0-adhoc: link is not ready
Fri Apr 14 04:03:39 2017 kern.info kernel: [ 24.753641] wlan0-adhoc:
Created IBSS using preconfigured BSSID ca:fe:00:c0:ff:ee
Fri Apr 14 04:03:39 2017 kern.info kernel: [ 24.761360] wlan0-adhoc:
Creating new IBSS network, BSSID ca:fe:00:c0:ff:ee
Fri Apr 14 04:03:39 2017 kern.info kernel: [ 24.768921] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan0-adhoc: link becomes ready
Fri Apr 14 04:03:39 2017 daemon.notice netifd: Network device 'wlan1-ap'
link is up
Fri Apr 14 04:03:39 2017 daemon.notice netifd: Network device
'wlan1-apname' link is up
Fri Apr 14 04:03:39 2017 daemon.notice netifd: Network device 'wlan0-ap'
link is up
Fri Apr 14 04:03:39 2017 daemon.notice netifd: Network device
'wlan0-apname' link is up
Fri Apr 14 04:03:39 2017 daemon.notice netifd: Network device 'wlan0-adhoc'
link is up
Fri Apr 14 04:03:40 2017 kern.info kernel: [ 25.210370] br-lan: port
2(wlan1-ap) entered forwarding state
Fri Apr 14 04:03:40 2017 kern.info kernel: [ 25.431525] br-lan: port
4(wlan1-apname) entered forwarding state
Fri Apr 14 04:03:40 2017 kern.info kernel: [ 25.451390] br-lan: port
3(wlan0-ap) entered forwarding state
Fri Apr 14 04:03:40 2017 kern.info kernel: [ 25.501378] br-lan: port
5(wlan0-apname) entered forwarding state
Fri Apr 14 04:03:40 2017 daemon.info dnsmasq[1273]: started, version 2.76
cachesize 150
Fri Apr 14 04:03:40 2017 daemon.info dnsmasq[1273]: compile time options:
IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack
no-ipset no-auth no-DNSSEC no-ID loop-detect inotify
Fri Apr 14 04:03:40 2017 daemon.info dnsmasq[1273]: DNS service limited to
local subnets
Fri Apr 14 04:03:40 2017 daemon.info dnsmasq-dhcp[1273]: DHCP, IP range
192.168.2.100 -- 192.168.2.249, lease time 12h
Fri Apr 14 04:03:40 2017 daemon.info dnsmasq[1273]: using local addresses
only for domain lan
Fri Apr 14 04:03:40 2017 daemon.warn dnsmasq[1273]: no servers found in
/tmp/resolv.conf.auto, will retry
Fri Apr 14 04:03:40 2017 daemon.info dnsmasq[1273]: read /etc/hosts - 4
addresses
Fri Apr 14 04:03:40 2017 daemon.info dnsmasq[1273]: read
/tmp/hosts/dhcp.cfg02411c - 1 addresses
Fri Apr 14 04:03:40 2017 daemon.info dnsmasq-dhcp[1273]: read /etc/ethers -
0 addresses
Fri Apr 14 04:03:41 2017 daemon.notice netifd: wan (928): udhcpc: sending
discover
Fri Apr 14 04:03:43 2017 daemon.info dnsmasq-dhcp[1273]:
DHCPREQUEST(br-lan) 192.168.1.134 74:27:ea:48:23:18
Fri Apr 14 04:03:43 2017 daemon.info dnsmasq-dhcp[1273]: DHCPNAK(br-lan)
192.168.1.134 74:27:ea:48:23:18 wrong network
Fri Apr 14 04:03:46 2017 daemon.info dnsmasq-dhcp[1273]:
DHCPDISCOVER(br-lan) 74:27:ea:48:23:18
Fri Apr 14 04:03:46 2017 daemon.info dnsmasq-dhcp[1273]: DHCPOFFER(br-lan)
192.168.2.134 74:27:ea:48:23:18
Fri Apr 14 04:03:46 2017 daemon.info dnsmasq-dhcp[1273]:
DHCPREQUEST(br-lan) 192.168.2.134 74:27:ea:48:23:18
Fri Apr 14 04:03:46 2017 daemon.info dnsmasq-dhcp[1273]: DHCPACK(br-lan)
192.168.2.134 74:27:ea:48:23:18 JK-PC
Fri Apr 14 04:04:00 2017 cron.info crond[741]: USER root pid 1300 cmd
/usr/bin/bmx6hosts_dnsmasq_update
Fri Apr 14 04:04:01 2017 user.notice bmx6hosts: New bmx6 hosts found,
updating dnsmasq
Fri Apr 14 04:04:01 2017 daemon.info dnsmasq[1273]: read /etc/hosts - 4
addresses
Fri Apr 14 04:04:01 2017 daemon.info dnsmasq[1273]: read /tmp/hosts/bmx6 -
0 addresses
Fri Apr 14 04:04:01 2017 daemon.info dnsmasq[1273]: read
/tmp/hosts/dhcp.cfg02411c - 1 addresses
Fri Apr 14 04:04:01 2017 daemon.info dnsmasq-dhcp[1273]: read /etc/ethers -
0 addresses
Fri Apr 14 04:04:06 2017 user.notice : /etc/rc.d/S99alfred: bat0 not
detected, alfred not starting.
Fri Apr 14 04:04:06 2017 user.notice : /etc/rc.common: Firewall is not
enabled. Executing /etc/firewall.lime script.
Fri Apr 14 04:04:06 2017 user.info watchping: starting all tasks
Fri Apr 14 04:04:06 2017 user.info watchping: started task
(interface=eth0.2;timeout=120;pinghosts=8.8.8.8;
pinginterval=20;hookname=wan)
Fri Apr 14 04:04:06 2017 user.info watchping: all tasks started
Fri Apr 14 04:04:06 2017 daemon.info procd: - init complete -
Fri Apr 14 04:04:08 2017 kern.notice kernel: [ 36.597320] random:
nonblocking pool is initialized
Fri Apr 14 04:04:13 2017 authpriv.info dropbear[1352]: Child connection
from 192.168.2.134:15482
Fri Apr 14 04:04:16 2017 authpriv.notice dropbear[1352]: Auth succeeded
with blank password for 'root' from 192.168.2.134:15482
Fri Apr 14 04:04:50 2017 user.warn libremap-agent[803]: unable to execute
plugin "bmx6"; /var/run/bmx6/json/links: No such file or directory
Fri Apr 14 04:04:50 2017 user.warn libremap-agent[803]: unable to execute
plugin "wireless"; ?:0: attempt to index a nil value
Fri Apr 14 04:04:55 2017 user.err libremap-agent[803]: submission to
http://libremap.net/api/ failed
Fri Apr 14 04:04:55 2017 user.err libremap-agent[803]: error
creating/updating router document at URL http://libremap.net/api//router/;
-3
Fri Apr 14 04:04:55 2017 user.warn libremap-agent[803]: unable to execute
plugin "bmx6"; /var/run/bmx6/json/links: No such file or directory
Fri Apr 14 04:04:55 2017 user.warn libremap-agent[803]: unable to execute
plugin "wireless"; ?:0: attempt to index a nil value
Fri Apr 14 04:05:00 2017 user.err libremap-agent[803]: submission to
http://libremap.berlin.freifunk.net/api failed
Fri Apr 14 04:05:00 2017 user.err libremap-agent[803]: error
creating/updating router document at URL http://libremap.berlin.
freifunk.net/api/router/; -3
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Fr., 14. Apr. 2017 um
05:53 Uhr:
Here is
/etc/config/network
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
config interface 'lan'
option type 'bridge'
option ifname 'eth0.1'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
config device 'lan_dev'
option name 'eth0.1'
option macaddr '78:a3:51:16:da:88'
config interface 'wan'
option ifname 'eth0.2'
option proto 'none'
config device 'wan_dev'
option name 'eth0.2'
option macaddr '78:a3:51:16:da:89'
config interface 'wan6'
option ifname 'eth0.2'
option proto 'none'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0 1 2 3 6t'
config switch_vlan
option device 'switch0'
option vlan '2'
option ports '4 6t'
Cheers
Ilario Gelmetti <iochesonome(a)gmail.com> schrieb am Fr., 14. Apr. 2017 um
00:55 Uhr:
On 04/13/2017 09:23 PM, Juergen Kimmel wrote:
After changing line 307 here output of
lime-config:
root@LiMe-16da88:~# lime-config
/usr/lib/lua/lime/network.lua:155: attempt to index local 'dev' (a nil
value)
On 13/04/17 17:59, Ilario Gelmetti wrote:
> If after this and a lime-config and a reboot things are not fixed
can
> you post the output of
>
> uci show network
>
> (there could be some non "lm_net_" entry of type "device"
that
usually
> is not present in ar71xx hardware)
Ok, post your
uci show network
If there's some not "network.lm_net_*" entry which is of type
"device"
(not "interface") missing "name" or "ifname" options, that
could rise
the error you see.
Let us know :)
Ilario
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
12:48 a.m.
Sorry, last post is obsolete is an old syslog.
After changing line 178 of network.lua network looks like:
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0 1 2 3 6t'
config switch_vlan
option device 'switch0'
option vlan '2'
option ports '4 6t'
config device 'eth0_1_12'
option type '8021ad'
option name 'eth0_1_12'
option ifname 'eth0.1'
option vid '12'
option proto 'static'
option ip6addr 'FD02:0:0:78A3:5116:DA88:0:312/128'
config interface 'eth0_1_12_ad'
option ifname 'eth0_1_12'
option auto '1'
config device 'eth0_2_12'
option type '8021ad'
option name 'eth0_2_12'
option ifname 'eth0.2'
option vid '12'
option proto 'static'
option ip6addr 'FD02:0:0:78A3:5116:DA88:0:412/128'
config interface 'eth0_2_12_ad'
option ifname 'eth0_2_12'
option auto '1'
config device 'wlan0_12'
option type '8021q'
option name 'wlan0_12'
option ifname '@mesh_w0'
option vid '12'
option proto 'static'
option ip6addr 'FD02:0:0:78A3:5116:DA88:0:112/128'
config interface 'wlan0_12_ad'
option ifname 'wlan0_12'
option auto '1'
config device 'wlan1_12'
option type '8021q'
option name 'wlan1_12'
option ifname '@mesh_w1'
option vid '12'
option proto 'static'
option ip6addr 'FD02:0:0:78A3:5116:DA88:0:212/128'
config interface 'wlan1_12_ad'
option ifname 'wlan1_12'
option auto '1'
config interface 'wan_e0_2'
option ifname 'eth0.2'
option proto 'dhcp'
config interface 'lan'
option type 'bridge'
option auto '1'
option proto 'static'
option dns '208.67.222.222 77.109.148.136 109.69.8.34'
option ip6addr '2a00:1508:a0d:fe00::16:da88/64'
option ipaddr '10.13.218.136'
option netmask '255.255.0.0'
option mtu '1500'
list ifname 'bat0'
list ifname 'eth0.1'
list ifname 'eth0.2'
config interface 'mesh_w0'
option proto 'static'
option ipaddr '169.254.137.1'
option netmask '255.255.255.248'
config interface 'mesh_w1'
option proto 'static'
option ipaddr '169.254.136.1'
option netmask '255.255.255.248'
config interface 'wwan'
option proto 'dhcp'
config device 'lm_net_br_lan_anygw_dev'
option type 'macvlan'
option name 'anygw'
option ifname 'br-lan'
option macaddr 'aa:aa:aa:0d:fe:aa'
config interface 'lm_net_br_lan_anygw_if'
option ifname 'anygw'
option auto '1'
option netmask '255.255.0.0'
option proto 'static'
option ipaddr '10.13.0.1'
option ip6addr '2a00:1508:a0d:fe00::1/64'
config rule6 'lm_net_anygw_rule6'
option src '2a00:1508:a0d:fe00::1/128'
option lookup '170'
config route6 'lm_net_anygw_route6'
option interface 'lm_net_br_lan_anygw_if'
option target '2a00:1508:a0d:fe00::/64'
option table '170'
config rule 'lm_net_anygw_rule4'
option src '10.13.0.1/32'
option lookup '170'
config route 'lm_net_anygw_route4'
option interface 'lm_net_br_lan_anygw_if'
option target '10.13.0.0'
option netmask '255.255.0.0'
option table '170'
config interface 'lm_net_batadv_dummy_if'
option ifname 'dummy0'
option macaddr 'aa:a3:51:16:da:88'
option proto 'batadv'
option mesh 'bat0'
config device 'lm_net_lm_net_eth0_1_bmx6_dev'
option type '8021ad'
option name 'eth0-1_13'
option ifname 'eth0.1'
option vid '13'
option mtu '1398'
config interface 'lm_net_eth0_1_bmx6_if'
option proto 'none'
option auto '1'
option ifname 'eth0-1_13'
config interface 'lm_net_wlan1_adhoc'
option proto 'none'
option mtu '1536'
option auto '1'
config device 'lm_net_lm_net_wlan1_adhoc_batadv_dev'
option type '8021ad'
option name 'wlan1-adhoc_29'
option ifname '@lm_net_wlan1_adhoc'
option vid '29'
option mtu '1532'
config interface 'lm_net_wlan1_adhoc_batadv_if'
option auto '1'
option ifname 'wlan1-adhoc_29'
option proto 'batadv'
option mesh 'bat0'
config device 'lm_net_lm_net_wlan1_adhoc_bmx6_dev'
option type '8021ad'
option name 'wlan1-adhoc_13'
option ifname '@lm_net_wlan1_adhoc'
option vid '13'
option mtu '1398'
config interface 'lm_net_wlan1_adhoc_bmx6_if'
option auto '1'
option ifname 'wlan1-adhoc_13'
option proto 'static'
option ipaddr '169.254.218.136'
option netmask '255.255.255.255'
config device 'lm_net_lm_net_eth0_2_bmx6_dev'
option type '8021ad'
option name 'eth0-2_13'
option ifname 'eth0.2'
option vid '13'
option mtu '1398'
config interface 'lm_net_eth0_2_bmx6_if'
option proto 'none'
option auto '1'
option ifname 'eth0-2_13'
config interface 'lm_net_wlan0_adhoc'
option proto 'none'
option mtu '1536'
option auto '1'
config device 'lm_net_lm_net_wlan0_adhoc_batadv_dev'
option type '8021ad'
option name 'wlan0-adhoc_29'
option ifname '@lm_net_wlan0_adhoc'
option vid '29'
option mtu '1532'
config interface 'lm_net_wlan0_adhoc_batadv_if'
option auto '1'
option ifname 'wlan0-adhoc_29'
option proto 'batadv'
option mesh 'bat0'
config device 'lm_net_lm_net_wlan0_adhoc_bmx6_dev'
option type '8021ad'
option name 'wlan0-adhoc_13'
option ifname '@lm_net_wlan0_adhoc'
option vid '13'
option mtu '1398'
config interface 'lm_net_wlan0_adhoc_bmx6_if'
option auto '1'
option ifname 'wlan0-adhoc_13'
option proto 'static'
option ipaddr '169.254.218.137'
option netmask '255.255.255.255'
config device 'lm_net_lm_net_eth0_bmx6_dev'
option type '8021ad'
option name 'eth0_13'
option ifname 'eth0'
option vid '13'
option mtu '1398'
config interface 'lm_net_eth0_bmx6_if'
option proto 'none'
option auto '1'
option ifname 'eth0_13'
Looks strange to me?
2017-04-15 2:43 GMT+02:00 Juergen Kimmel <juergenkimmel(a)gmail.com>om>:
...and here the syslog:
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 0.000000] Linux version
4.4.50 (buildbot(a)builds-02.infra.lede-project.org) (gcc version 5.4.0 (LEDE
GCC 5.4.0 r3103-1b51a49) ) #0 Mon Feb 20 17:13:44 2017
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Board has DDR2
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Analog PMU set to
hw control
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Digital PMU set to
hw control
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] SoC Type: MediaTek
MT7620A ver:2 eco:6
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] bootconsole
[early0] enabled
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] CPU0 revision is:
00019650 (MIPS 24KEc)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] MIPS: machine is
ZBT-APE522II
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Determined
physical RAM map:
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] memory: 08000000
@ 00000000 (usable)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Initrd not found
or empty - disabling initrd
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Zone ranges:
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Normal [mem
0x0000000000000000-0x0000000007ffffff]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Movable zone start
for each node
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Early memory node
ranges
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] node 0: [mem
0x0000000000000000-0x0000000007ffffff]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Initmem setup node
0 [mem 0x0000000000000000-0x0000000007ffffff]
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.000000] On node 0
totalpages: 32768
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.000000]
free_area_init_node: node 0, pgdat 8035a4b0, node_mem_map 81000000
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.000000] Normal zone:
256 pages used for memmap
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.000000] Normal zone: 0
pages reserved
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.000000] Normal zone:
32768 pages, LIFO batch:7
Fri Apr 14 04:03:28 2017 kern.warn kernel: [ 0.000000] Primary
instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
Fri Apr 14 04:03:28 2017 kern.warn kernel: [ 0.000000] Primary data cache
32kB, 4-way, PIPT, no aliases, linesize 32 bytes
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.000000] pcpu-alloc: s0 r0
d32768 u32768 alloc=1*32768
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.000000] pcpu-alloc: [0] 0
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Built 1 zonelists
in Zone order, mobility grouping on. Total pages: 32512
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 0.000000] Kernel command
line: console=ttyS0,115200 rootfstype=squashfs,jffs2
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] PID hash table
entries: 512 (order: -1, 2048 bytes)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Dentry cache hash
table entries: 16384 (order: 4, 65536 bytes)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Inode-cache hash
table entries: 8192 (order: 3, 32768 bytes)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Writing ErrCtl
register=00067070
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Readback ErrCtl
register=00067070
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] Memory:
125924K/131072K available (3012K kernel code, 144K rwdata, 384K rodata, 164K
init, 208K bss, 5148K reserved, 0K cma-reserved)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] SLUB: HWalign=32,
Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] NR_IRQS:256
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] CPU Clock: 580MHz
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] clocksource:
systick: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 583261500 ns
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] systick: enable
autosleep mode
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] systick: running -
mult: 214748, shift: 32
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000000] clocksource: MIPS:
mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6590553264 ns
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.000011] sched_clock: 32
bits at 290MHz, resolution 3ns, wraps every 7405115902ns
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.007578] Calibrating delay
loop... 385.84 BogoMIPS (lpj=1929216)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.070069] pid_max: default:
32768 minimum: 301
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.074692] Mount-cache hash
table entries: 1024 (order: 0, 4096 bytes)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.081060] Mountpoint-cache
hash table entries: 1024 (order: 0, 4096 bytes)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.094466] clocksource:
jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:
19112604462750000 ns
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.104067] pinctrl core:
initialized pinctrl subsystem
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.110363] NET: Registered
protocol family 16
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.373101] PCI host bridge
/pcie@10140000 ranges:
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.377715] MEM
0x0000000020000000..0x000000002fffffff
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.382767] IO
0x0000000010160000..0x000000001016ffff
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.400644] rt2880_gpio
10000600.gpio: registering 24 gpios
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.406038] rt2880_gpio
10000600.gpio: registering 24 irq handlers
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.412276] rt2880_gpio
10000638.gpio: registering 16 gpios
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.417643] rt2880_gpio
10000638.gpio: registering 16 irq handlers
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.423832] rt2880_gpio
10000660.gpio: registering 32 gpios
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.429198] rt2880_gpio
10000660.gpio: registering 32 irq handlers
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.435386] rt2880_gpio
10000688.gpio: registering 1 gpios
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.440668] rt2880_gpio
10000688.gpio: registering 1 irq handlers
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.447360] PCI host bridge to
bus 0000:00
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.451288] pci_bus 0000:00:
root bus resource [mem 0x20000000-0x2fffffff]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.458002] pci_bus 0000:00:
root bus resource [io 0xffffffff]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.463703] pci_bus 0000:00:
root bus resource [??? 0x00000000 flags 0x0]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.470306] pci_bus 0000:00:
No busn resource found for root bus, will use [bus 00-ff]
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.478028] pci 0000:00:00.0:
[1814:0802] type 01 class 0x060400
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.478076] pci 0000:00:00.0:
reg 0x10: [mem 0x00000000-0x7fffffff]
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.478100] pci 0000:00:00.0:
reg 0x14: [mem 0x20200000-0x2020ffff]
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.478175] pci 0000:00:00.0:
supports D1
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.478194] pci 0000:00:00.0:
PME# supported from D0 D1 D3hot
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.478670] pci 0000:01:00.0:
[14c3:7662] type 00 class 0x028000
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.478742] pci 0000:01:00.0:
reg 0x10: [mem 0x00000000-0x000fffff 64bit]
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.478805] pci 0000:01:00.0:
reg 0x30: [mem 0x00000000-0x0000ffff pref]
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.478900] pci 0000:01:00.0:
PME# supported from D0 D3hot D3cold
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.479146] pci_bus 0000:01:
busn_res: [bus 01-ff] end is updated to 01
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.479176] pci_bus 0000:00:
busn_res: [bus 00-ff] end is updated to 01
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.479234] pci 0000:00:00.0:
BAR 0: no space for [mem size 0x80000000]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.485645] pci 0000:00:00.0:
BAR 0: failed to assign [mem size 0x80000000]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.492362] pci 0000:00:00.0:
BAR 8: assigned [mem 0x20000000-0x200fffff]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.498968] pci 0000:00:00.0:
BAR 9: assigned [mem 0x20100000-0x201fffff pref]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.505968] pci 0000:00:00.0:
BAR 1: assigned [mem 0x20200000-0x2020ffff]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.512586] pci 0000:01:00.0:
BAR 0: assigned [mem 0x20000000-0x200fffff 64bit]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.519678] pci 0000:01:00.0:
BAR 6: assigned [mem 0x20100000-0x2010ffff pref]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.526689] pci 0000:00:00.0:
PCI bridge to [bus 01]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.531498] pci 0000:00:00.0:
bridge window [mem 0x20000000-0x200fffff]
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.538099] pci 0000:00:00.0:
bridge window [mem 0x20100000-0x201fffff pref]
Fri Apr 14 04:03:28 2017 kern.err kernel: [ 0.545116] pci 0000:00:00.0:
card - bus=0x0, slot = 0x0 irq=0
Fri Apr 14 04:03:28 2017 kern.err kernel: [ 0.550786] pci 0000:01:00.0:
card - bus=0x1, slot = 0x0 irq=4
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.557294] clocksource:
Switched to clocksource systick
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.563716] NET: Registered
protocol family 2
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.568950] TCP established
hash table entries: 1024 (order: 0, 4096 bytes)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.575675] TCP bind hash
table entries: 1024 (order: 0, 4096 bytes)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.581903] TCP: Hash tables
configured (established 1024 bind 1024)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.588125] UDP hash table
entries: 256 (order: 0, 4096 bytes)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.593750] UDP-Lite hash
table entries: 256 (order: 0, 4096 bytes)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.600133] NET: Registered
protocol family 1
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 0.604355] PCI: CLS 80
bytes, default 32
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.609207] rt-timer
10000100.timer: maximum frequency is 1220Hz
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.615783] futex hash table
entries: 256 (order: -1, 3072 bytes)
Fri Apr 14 04:03:28 2017 kern.warn kernel: [ 0.621779] Crashlog allocated
RAM at address 0x3f00000
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.642942] squashfs: version
4.0 (2009/01/31) Phillip Lougher
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.648611] jffs2: version 2.2
(NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.660735] io scheduler noop
registered
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.664480] io scheduler
deadline registered (default)
Fri Apr 14 04:03:28 2017 kern.err kernel: [ 0.669778] ralink-usb-phy
usbphy: invalid resource
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.675080] Serial: 8250/16550
driver, 16 ports, IRQ sharing enabled
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.684847] console [ttyS0]
disabled
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.688355] 10000c00.uartlite:
ttyS0 at MMIO 0x10000c00 (irq = 20, base_baud = 2500000) is a Palmchip
BK-3103
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.697965] console [ttyS0]
enabled
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.705007] bootconsole
[early0] disabled
Fri Apr 14 04:03:28 2017 kern.warn kernel: [ 0.719828] spi spi0.0: force
spi mode3
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 0.724312] m25p80 spi0.0:
w25q128 (16384 Kbytes)
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 0.729215] 4 ofpart
partitions found on MTD device spi0.0
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 0.734809] Creating 4 MTD
partitions on "spi0.0":
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 0.739717]
0x000000000000-0x000000030000 : "u-boot"
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 0.746620]
0x000000030000-0x000000040000 : "u-boot-env"
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 0.753962]
0x000000040000-0x000000050000 : "factory"
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 0.760998]
0x000000050000-0x000000fd0000 : "firmware"
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 2.073525] 2 uimage-fw
partitions found on MTD device firmware
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 2.079616]
0x000000050000-0x000000178296 : "kernel"
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 2.086294]
0x000000178296-0x000000fd0000 : "rootfs"
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 2.093247] mtd: device 5
(rootfs) set to be root filesystem
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 2.099238] 1 squashfs-split
partitions found on MTD device rootfs
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 2.105555]
0x00000048a000-0x000000fd0000 : "rootfs_data"
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 2.115979] gsw: setting port4
to ephy mode
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 2.120343] mtk_soc_eth
10100000.ethernet eth0 (uninitialized): port 0 link up (100Mbps/Full duplex)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 2.129902] mtk_soc_eth
10100000.ethernet: loaded mt7620 driver
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 2.136743] mtk_soc_eth
10100000.ethernet eth0: mediatek frame engine at 0xb0100000, irq 5
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 2.145769] rt2880_wdt
10000120.watchdog: Initialized
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 2.152414] NET: Registered
protocol family 10
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 2.161507] NET: Registered
protocol family 17
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 2.166127] bridge: automatic
filtering via arp/ip/ip6tables has been deprecated. Update your scripts to
load br_netfilter if you need this.
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 2.179055] 8021q: 802.1Q VLAN
Support v1.8
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 2.198258] VFS: Mounted root
(squashfs filesystem) readonly on device 31:5.
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 2.206354] Freeing unused
kernel memory: 164K (80377000 - 803a0000)
Fri Apr 14 04:03:28 2017 user.info kernel: [ 4.580373] init: Console is
alive
Fri Apr 14 04:03:28 2017 user.info kernel: [ 4.584067] init: - watchdog -
Fri Apr 14 04:03:28 2017 user.info kernel: [ 6.378665] init: - preinit -
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 8.031317] 8021q: adding VLAN
0 to HW filter on device eth0
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 10.750732] jffs2: notice:
(344) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of
xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
Fri Apr 14 04:03:28 2017 user.info kernel: [ 10.769772] mount_root:
switching to jffs2 overlay
Fri Apr 14 04:03:28 2017 user.warn kernel: [ 10.787131] urandom-seed:
Seeding with /etc/urandom.seed
Fri Apr 14 04:03:28 2017 user.info kernel: [ 10.925635] procd: - early -
Fri Apr 14 04:03:28 2017 user.info kernel: [ 10.928688] procd: - watchdog
-
Fri Apr 14 04:03:28 2017 user.info kernel: [ 11.264343] procd: - ubus -
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 11.505897] random: ubusd:
uninitialized urandom read (4 bytes read, 25 bits of entropy available)
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 11.521578] random: ubusd:
uninitialized urandom read (4 bytes read, 25 bits of entropy available)
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 11.531321] random: ubusd:
uninitialized urandom read (4 bytes read, 25 bits of entropy available)
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 11.540634] random: ubusd:
uninitialized urandom read (4 bytes read, 25 bits of entropy available)
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 11.550226] random: ubusd:
uninitialized urandom read (4 bytes read, 25 bits of entropy available)
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 11.560069] random: ubusd:
uninitialized urandom read (4 bytes read, 26 bits of entropy available)
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 11.570285] random: ubusd:
uninitialized urandom read (4 bytes read, 26 bits of entropy available)
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 11.579697] random: ubusd:
uninitialized urandom read (4 bytes read, 26 bits of entropy available)
Fri Apr 14 04:03:28 2017 user.info kernel: [ 11.589299] procd: - init -
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.152863] tun: Universal
TUN/TAP device driver, 1.6
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.158112] tun: (C) 1999-2004
Max Krasnyansky <maxk(a)qualcomm.com>
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.186457] ip6_tables: (C)
2000-2006 Netfilter Core Team
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.211200] Loading modules
backported from Linux version wt-2016-10-03-1-g6fcb1a6
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.219005] Backport generated
by backports.git backports-20160324-9-g0e38f5c
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.361109] batman_adv:
B.A.T.M.A.N. advanced 2017.0 (compatibility version 15) loaded
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.399118] mt76x2e
0000:01:00.0: ASIC revision: 76120044
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.416681] mt76x2e
0000:01:00.0: ROM patch already applied
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.424018] mt76x2e
0000:01:00.0: Firmware Version: 0.0.00
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.429688] mt76x2e
0000:01:00.0: Build: 1
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.433870] mt76x2e
0000:01:00.0: Build Time: 201507311614____
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.475286] mt76x2e
0000:01:00.0: Firmware running!
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 12.485846] ieee80211 phy0:
Selected rate control algorithm 'minstrel_ht'
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 12.507113] Bridge
firewalling registered
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.557828] Ebtables v2.0
registered
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.569169] ip_tables: (C)
2000-2006 Netfilter Core Team
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.602777] nf_conntrack
version 0.5.0 (1970 buckets, 7880 max)
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.746781] xt_time: kernel
timezone is -0000
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.783137] rt2800_wmac
10180000.wmac: loaded eeprom from mtd device "factory"
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.790602] ieee80211 phy1:
rt2x00_set_rt: Info - RT chipset 5390, rev 0500 detected
Fri Apr 14 04:03:28 2017 kern.info kernel: [ 12.798543] ieee80211 phy1:
rt2x00_set_rf: Info - RF chipset 7620 detected
Fri Apr 14 04:03:28 2017 kern.debug kernel: [ 12.806315] ieee80211 phy1:
Selected rate control algorithm 'minstrel_ht'
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 14.155930] random: jshn:
uninitialized urandom read (4 bytes read, 30 bits of entropy available)
Fri Apr 14 04:03:28 2017 kern.notice kernel: [ 14.253639] random: ubusd:
uninitialized urandom read (4 bytes read, 30 bits of entropy available)
Fri Apr 14 04:03:29 2017 user.notice : Added device handler type: 8021ad
Fri Apr 14 04:03:29 2017 user.notice : Added device handler type: 8021q
Fri Apr 14 04:03:29 2017 user.notice : Added device handler type: macvlan
Fri Apr 14 04:03:29 2017 user.notice : Added device handler type: bridge
Fri Apr 14 04:03:29 2017 user.notice : Added device handler type: Network
device
Fri Apr 14 04:03:29 2017 user.notice : Added device handler type: tunnel
Fri Apr 14 04:03:30 2017 cron.info crond[741]: crond (busybox 1.25.1)
started, log level 5
Fri Apr 14 04:03:31 2017 authpriv.info dropbear[774]: Not backgrounding
Fri Apr 14 04:03:31 2017 user.notice : Starting netserver with host
'IN(6)ADDR_ANY' port '12865' and family AF_UNSPEC
Fri Apr 14 04:03:33 2017 user.notice : setting up led wlan1-link
Fri Apr 14 04:03:33 2017 user.notice : setting up led wlan1
Fri Apr 14 04:03:33 2017 user.notice : setting up led wlan0
Fri Apr 14 04:03:33 2017 daemon.err bmx6[813]: WARN
recv_ruleEvent_netlink_sk(): FIXING lost rule family=2 pref=60 to table=60
should=1 is=0
Fri Apr 14 04:03:33 2017 daemon.err bmx6[813]: WARN
recv_ruleEvent_netlink_sk(): FIXING lost rule family=10 pref=60 to table=60
should=1 is=0
Fri Apr 14 04:03:33 2017 kern.info kernel: [ 19.641425] 8021q: adding VLAN
0 to HW filter on device eth0
Fri Apr 14 04:03:33 2017 kern.info kernel: [ 19.687937] device eth0.1
entered promiscuous mode
Fri Apr 14 04:03:33 2017 kern.info kernel: [ 19.692846] device eth0
entered promiscuous mode
Fri Apr 14 04:03:33 2017 kern.info kernel: [ 19.746331] br-lan: port
1(eth0.1) entered forwarding state
Fri Apr 14 04:03:33 2017 kern.info kernel: [ 19.752069] br-lan: port
1(eth0.1) entered forwarding state
Fri Apr 14 04:03:33 2017 daemon.notice netifd: Interface 'lan' is enabled
Fri Apr 14 04:03:33 2017 daemon.notice netifd: Interface 'lan' is setting up
now
Fri Apr 14 04:03:33 2017 daemon.notice netifd: Interface 'lan' is now up
Fri Apr 14 04:03:33 2017 daemon.notice netifd: Interface 'loopback' is
enabled
Fri Apr 14 04:03:33 2017 daemon.notice netifd: Interface 'loopback' is
setting up now
Fri Apr 14 04:03:33 2017 daemon.notice netifd: Interface 'loopback' is now
up
Fri Apr 14 04:03:33 2017 daemon.notice netifd: Interface 'wan' is enabled
Fri Apr 14 04:03:33 2017 daemon.notice netifd: Interface 'wan6' is enabled
Fri Apr 14 04:03:33 2017 daemon.notice netifd: bridge 'br-lan' link is up
Fri Apr 14 04:03:33 2017 daemon.notice netifd: Interface 'lan' has link
connectivity
Fri Apr 14 04:03:33 2017 daemon.notice netifd: Network device 'eth0' link is
up
Fri Apr 14 04:03:33 2017 daemon.notice netifd: VLAN 'eth0.1' link is up
Fri Apr 14 04:03:33 2017 daemon.notice netifd: Network device 'lo' link is
up
Fri Apr 14 04:03:34 2017 daemon.notice netifd: Interface 'loopback' has link
connectivity
Fri Apr 14 04:03:34 2017 daemon.notice netifd: VLAN 'eth0.2' link is up
Fri Apr 14 04:03:34 2017 daemon.notice netifd: Interface 'wan' has link
connectivity
Fri Apr 14 04:03:34 2017 daemon.notice netifd: Interface 'wan' is setting up
now
Fri Apr 14 04:03:34 2017 daemon.notice netifd: Interface 'wan6' has link
connectivity
Fri Apr 14 04:03:34 2017 daemon.notice netifd: Interface 'wan6' is setting
up now
Fri Apr 14 04:03:34 2017 daemon.notice netifd: Interface 'wan6' is now up
Fri Apr 14 04:03:34 2017 daemon.notice netifd: wan (928): udhcpc: started,
v1.25.1
Fri Apr 14 04:03:35 2017 daemon.notice netifd: radio1 (871): command failed:
Not supported (-122)
Fri Apr 14 04:03:35 2017 daemon.notice netifd: wan (928): udhcpc: sending
discover
Fri Apr 14 04:03:35 2017 kern.info kernel: [ 21.745226] br-lan: port
1(eth0.1) entered forwarding state
Fri Apr 14 04:03:35 2017 user.notice : /etc/rc.d/S99alfred: waiting 30 secs
for bat0 interface...
Fri Apr 14 04:03:37 2017 daemon.err hostapd: Configuration file:
/var/run/hostapd-phy1.conf
Fri Apr 14 04:03:37 2017 daemon.err hostapd: Configuration file:
/var/run/hostapd-phy0.conf
Fri Apr 14 04:03:37 2017 kern.info kernel: [ 23.828425] IPv6:
ADDRCONF(NETDEV_UP): wlan1-ap: link is not ready
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 23.976393] IPv6:
ADDRCONF(NETDEV_UP): wlan0-ap: link is not ready
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 23.983311] device wlan1-ap
entered promiscuous mode
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 23.998821] device wlan0-ap
entered promiscuous mode
Fri Apr 14 04:03:38 2017 daemon.err hostapd: Using interface wlan1-ap with
hwaddr 78:a3:51:16:da:89 and ssid "LibreMesh.org"
Fri Apr 14 04:03:38 2017 daemon.notice netifd: wan (928): udhcpc: sending
discover
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.023748] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan1-ap: link becomes ready
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.030688] br-lan: port
2(wlan1-ap) entered forwarding state
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.036664] br-lan: port
2(wlan1-ap) entered forwarding state
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.051815] device
wlan1-apname entered promiscuous mode
Fri Apr 14 04:03:38 2017 daemon.err hostapd: Using interface wlan0-ap with
hwaddr 7a:a3:51:16:da:89 and ssid "LibreMesh.org"
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.228510] IPv6:
ADDRCONF(NETDEV_UP): wlan1-apname: link is not ready
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.235265] br-lan: port
4(wlan1-apname) entered forwarding state
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.241560] br-lan: port
4(wlan1-apname) entered forwarding state
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.251871] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan0-ap: link becomes ready
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.258868] br-lan: port
3(wlan0-ap) entered forwarding state
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.264773] br-lan: port
3(wlan0-ap) entered forwarding state
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.276978] device
wlan0-apname entered promiscuous mode
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.298808] IPv6:
ADDRCONF(NETDEV_UP): wlan0-apname: link is not ready
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.305510] br-lan: port
5(wlan0-apname) entered forwarding state
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.311808] br-lan: port
5(wlan0-apname) entered forwarding state
Fri Apr 14 04:03:38 2017 daemon.err hostapd: Using interface wlan1-apname
with hwaddr 78:a3:51:16:da:8a and ssid "LibreMesh.org/LiMe-16da88"
Fri Apr 14 04:03:38 2017 daemon.notice hostapd: wlan1-ap: interface state
UNINITIALIZED->ENABLED
Fri Apr 14 04:03:38 2017 daemon.notice hostapd: wlan1-ap: AP-ENABLED
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.331882] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan1-apname: link becomes ready
Fri Apr 14 04:03:38 2017 daemon.err hostapd: Using interface wlan0-apname
with hwaddr 7e:a3:51:16:da:89 and ssid "LibreMesh.org/LiMe-16da88"
Fri Apr 14 04:03:38 2017 kern.info kernel: [ 24.373262] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan0-apname: link becomes ready
Fri Apr 14 04:03:38 2017 daemon.notice hostapd: wlan0-ap: interface state
UNINITIALIZED->ENABLED
Fri Apr 14 04:03:38 2017 daemon.notice hostapd: wlan0-ap: AP-ENABLED
Fri Apr 14 04:03:39 2017 daemon.notice netifd: radio1 (871): RTNETLINK
answers: Resource busy
Fri Apr 14 04:03:39 2017 daemon.notice netifd: radio1 (871): Interface 2
setup failed: IFUP_ERROR
Fri Apr 14 04:03:39 2017 kern.info kernel: [ 24.717380] IPv6:
ADDRCONF(NETDEV_UP): wlan0-adhoc: link is not ready
Fri Apr 14 04:03:39 2017 kern.info kernel: [ 24.753641] wlan0-adhoc:
Created IBSS using preconfigured BSSID ca:fe:00:c0:ff:ee
Fri Apr 14 04:03:39 2017 kern.info kernel: [ 24.761360] wlan0-adhoc:
Creating new IBSS network, BSSID ca:fe:00:c0:ff:ee
Fri Apr 14 04:03:39 2017 kern.info kernel: [ 24.768921] IPv6:
ADDRCONF(NETDEV_CHANGE): wlan0-adhoc: link becomes ready
Fri Apr 14 04:03:39 2017 daemon.notice netifd: Network device 'wlan1-ap'
link is up
Fri Apr 14 04:03:39 2017 daemon.notice netifd: Network device 'wlan1-apname'
link is up
Fri Apr 14 04:03:39 2017 daemon.notice netifd: Network device 'wlan0-ap'
link is up
Fri Apr 14 04:03:39 2017 daemon.notice netifd: Network device 'wlan0-apname'
link is up
Fri Apr 14 04:03:39 2017 daemon.notice netifd: Network device 'wlan0-adhoc'
link is up
Fri Apr 14 04:03:40 2017 kern.info kernel: [ 25.210370] br-lan: port
2(wlan1-ap) entered forwarding state
Fri Apr 14 04:03:40 2017 kern.info kernel: [ 25.431525] br-lan: port
4(wlan1-apname) entered forwarding state
Fri Apr 14 04:03:40 2017 kern.info kernel: [ 25.451390] br-lan: port
3(wlan0-ap) entered forwarding state
Fri Apr 14 04:03:40 2017 kern.info kernel: [ 25.501378] br-lan: port
5(wlan0-apname) entered forwarding state
Fri Apr 14 04:03:40 2017 daemon.info dnsmasq[1273]: started, version 2.76
cachesize 150
Fri Apr 14 04:03:40 2017 daemon.info dnsmasq[1273]: compile time options:
IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack
no-ipset no-auth no-DNSSEC no-ID loop-detect inotify
Fri Apr 14 04:03:40 2017 daemon.info dnsmasq[1273]: DNS service limited to
local subnets
Fri Apr 14 04:03:40 2017 daemon.info dnsmasq-dhcp[1273]: DHCP, IP range
192.168.2.100 -- 192.168.2.249, lease time 12h
Fri Apr 14 04:03:40 2017 daemon.info dnsmasq[1273]: using local addresses
only for domain lan
Fri Apr 14 04:03:40 2017 daemon.warn dnsmasq[1273]: no servers found in
/tmp/resolv.conf.auto, will retry
Fri Apr 14 04:03:40 2017 daemon.info dnsmasq[1273]: read /etc/hosts - 4
addresses
Fri Apr 14 04:03:40 2017 daemon.info dnsmasq[1273]: read
/tmp/hosts/dhcp.cfg02411c - 1 addresses
Fri Apr 14 04:03:40 2017 daemon.info dnsmasq-dhcp[1273]: read /etc/ethers -
0 addresses
Fri Apr 14 04:03:41 2017 daemon.notice netifd: wan (928): udhcpc: sending
discover
Fri Apr 14 04:03:43 2017 daemon.info dnsmasq-dhcp[1273]: DHCPREQUEST(br-lan)
192.168.1.134 74:27:ea:48:23:18
Fri Apr 14 04:03:43 2017 daemon.info dnsmasq-dhcp[1273]: DHCPNAK(br-lan)
192.168.1.134 74:27:ea:48:23:18 wrong network
Fri Apr 14 04:03:46 2017 daemon.info dnsmasq-dhcp[1273]:
DHCPDISCOVER(br-lan) 74:27:ea:48:23:18
Fri Apr 14 04:03:46 2017 daemon.info dnsmasq-dhcp[1273]: DHCPOFFER(br-lan)
192.168.2.134 74:27:ea:48:23:18
Fri Apr 14 04:03:46 2017 daemon.info dnsmasq-dhcp[1273]: DHCPREQUEST(br-lan)
192.168.2.134 74:27:ea:48:23:18
Fri Apr 14 04:03:46 2017 daemon.info dnsmasq-dhcp[1273]: DHCPACK(br-lan)
192.168.2.134 74:27:ea:48:23:18 JK-PC
Fri Apr 14 04:04:00 2017 cron.info crond[741]: USER root pid 1300 cmd
/usr/bin/bmx6hosts_dnsmasq_update
Fri Apr 14 04:04:01 2017 user.notice bmx6hosts: New bmx6 hosts found,
updating dnsmasq
Fri Apr 14 04:04:01 2017 daemon.info dnsmasq[1273]: read /etc/hosts - 4
addresses
Fri Apr 14 04:04:01 2017 daemon.info dnsmasq[1273]: read /tmp/hosts/bmx6 - 0
addresses
Fri Apr 14 04:04:01 2017 daemon.info dnsmasq[1273]: read
/tmp/hosts/dhcp.cfg02411c - 1 addresses
Fri Apr 14 04:04:01 2017 daemon.info dnsmasq-dhcp[1273]: read /etc/ethers -
0 addresses
Fri Apr 14 04:04:06 2017 user.notice : /etc/rc.d/S99alfred: bat0 not
detected, alfred not starting.
Fri Apr 14 04:04:06 2017 user.notice : /etc/rc.common: Firewall is not
enabled. Executing /etc/firewall.lime script.
Fri Apr 14 04:04:06 2017 user.info watchping: starting all tasks
Fri Apr 14 04:04:06 2017 user.info watchping: started task
(interface=eth0.2;timeout=120;pinghosts=8.8.8.8;pinginterval=20;hookname=wan)
Fri Apr 14 04:04:06 2017 user.info watchping: all tasks started
Fri Apr 14 04:04:06 2017 daemon.info procd: - init complete -
Fri Apr 14 04:04:08 2017 kern.notice kernel: [ 36.597320] random:
nonblocking pool is initialized
Fri Apr 14 04:04:13 2017 authpriv.info dropbear[1352]: Child connection from
192.168.2.134:15482
Fri Apr 14 04:04:16 2017 authpriv.notice dropbear[1352]: Auth succeeded with
blank password for 'root' from 192.168.2.134:15482
Fri Apr 14 04:04:50 2017 user.warn libremap-agent[803]: unable to execute
plugin "bmx6"; /var/run/bmx6/json/links: No such file or directory
Fri Apr 14 04:04:50 2017 user.warn libremap-agent[803]: unable to execute
plugin "wireless"; ?:0: attempt to index a nil value
Fri Apr 14 04:04:55 2017 user.err libremap-agent[803]: submission to
http://libremap.net/api/ failed
Fri Apr 14 04:04:55 2017 user.err libremap-agent[803]: error
creating/updating router document at URL http://libremap.net/api//router/;
-3
Fri Apr 14 04:04:55 2017 user.warn libremap-agent[803]: unable to execute
plugin "bmx6"; /var/run/bmx6/json/links: No such file or directory
Fri Apr 14 04:04:55 2017 user.warn libremap-agent[803]: unable to execute
plugin "wireless"; ?:0: attempt to index a nil value
Fri Apr 14 04:05:00 2017 user.err libremap-agent[803]: submission to
http://libremap.berlin.freifunk.net/api failed
Fri Apr 14 04:05:00 2017 user.err libremap-agent[803]: error
creating/updating router document at URL
http://libremap.berlin.freifunk.net/api/router/; -3
Juergen Kimmel <juergenkimmel(a)gmail.com> schrieb am Fr., 14. Apr. 2017 um
05:53 Uhr:
--
Mit freundlichen Grüssen
Jürgen Kimmel
Here is
/etc/config/network
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
config interface 'lan'
option type 'bridge'
option ifname 'eth0.1'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
config device 'lan_dev'
option name 'eth0.1'
option macaddr '78:a3:51:16:da:88'
config interface 'wan'
option ifname 'eth0.2'
option proto 'none'
config device 'wan_dev'
option name 'eth0.2'
option macaddr '78:a3:51:16:da:89'
config interface 'wan6'
option ifname 'eth0.2'
option proto 'none'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0 1 2 3 6t'
config switch_vlan
option device 'switch0'
option vlan '2'
option ports '4 6t'
Cheers
Ilario Gelmetti <iochesonome(a)gmail.com> schrieb am Fr., 14. Apr. 2017 um
00:55 Uhr:
On 04/13/2017 09:23 PM, Juergen Kimmel wrote:
After changing line 307 here output of
lime-config:
root@LiMe-16da88:~# lime-config
/usr/lib/lua/lime/network.lua:155: attempt to index local 'dev' (a nil
value)
On 13/04/17 17:59, Ilario Gelmetti wrote:
> If after this and a lime-config and a reboot things are not fixed
can
> you post the output of
>
> uci show network
>
> (there could be some non "lm_net_" entry of type "device"
that
usually
> is not present in ar71xx hardware)
Ok, post your
uci show network
If there's some not "network.lm_net_*" entry which is of type
"device"
(not "interface") missing "name" or "ifname" options, that
could rise
the error you see.
Let us know :)
Ilario
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users 
13 Apr
13 Apr
1:36 p.m.
Am 12.04.2017 um 18:36 schrieb Juergen Kimmel:
root@LiMe-16da88:~# lime-config
Clearing wireless config...
Clearing network config...
Disabling odhcpd
Cleaning dnsmasq
Disabling 6relayd...
/usr/lib/lua/lime/network.lua:155: attempt to index local 'dev' (a nil value)
stack traceback:
/usr/bin/lime-config:45: in function </usr/bin/lime-config:45>
[C]: in function 'foreach'
/usr/lib/lua/lime/network.lua:192: in function 'scandevices'
/usr/lib/lua/lime/network.lua:217: in function
</usr/lib/lua/lime/network.lua:208>
[C]: in function 'xpcall'
/usr/bin/lime-config:45: in function 'main'
/usr/bin/lime-config:65: in main chunk
[C]: ?
Configuring system...
Let uhttpd listen on IPv4/IPv6
Funny, just ran into the same problem, it's a d-link dir-600 b5 - so
seems to be a (general?) problem with ramips target?
>> root@000000:~# iw list| grep Wiphy
>> Wiphy phy0
greetings,
micha
3:36 p.m.
I opened a new ticket for this issue.
https://github.com/libremesh/lime-packages/issues/117
Unfortunately I do not have any Ramips device to test, I'll try to get
one. Any extra info would be appreciated.
Cheers.
On 13/04/17 15:36, Micha Stöcker wrote:
Am 12.04.2017 um 18:36 schrieb Juergen Kimmel:
--
./p4u
root@LiMe-16da88:~# lime-config
Clearing wireless config...
Clearing network config...
Disabling odhcpd
Cleaning dnsmasq
Disabling 6relayd...
/usr/lib/lua/lime/network.lua:155: attempt to index local 'dev' (a nil value)
stack traceback:
/usr/bin/lime-config:45: in function </usr/bin/lime-config:45>
[C]: in function 'foreach'
/usr/lib/lua/lime/network.lua:192: in function 'scandevices'
/usr/lib/lua/lime/network.lua:217: in function
</usr/lib/lua/lime/network.lua:208>
[C]: in function 'xpcall'
/usr/bin/lime-config:45: in function 'main'
/usr/bin/lime-config:65: in main chunk
[C]: ?
Configuring system...
Let uhttpd listen on IPv4/IPv6
Funny, just ran into the same problem, it's a d-link dir-600 b5 - so
seems to be a (general?) problem with ramips target?
>> root@000000:~# iw list| grep Wiphy
>> Wiphy phy0
greetings,
micha
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
3:50 p.m.
I think the problem might come from this line [1].
Can you run:
ls -1 /sys/class/net/ | grep -x 'eth[0-9][0-9]*'
And check if there is any output?
And this?
ls -1 /sys/class/net/ | grep -x 'eth[0-9]'
If the second works, you can manually edit this file (vim
/usr/lib/lua/lime/network.lua) and change the content of this line.
[1]
https://github.com/libremesh/lime-packages/blob/develop/packages/lime-syste…
On 13/04/17 17:36, Pau wrote:
I opened a new ticket for this issue.
https://github.com/libremesh/lime-packages/issues/117
Unfortunately I do not have any Ramips device to test, I'll try to get
one. Any extra info would be appreciated.
Cheers.
On 13/04/17 15:36, Micha Stöcker wrote:
--
./p4u
Am 12.04.2017 um 18:36 schrieb Juergen Kimmel:
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
root@LiMe-16da88:~# lime-config
Clearing wireless config...
Clearing network config...
Disabling odhcpd
Cleaning dnsmasq
Disabling 6relayd...
/usr/lib/lua/lime/network.lua:155: attempt to index local 'dev' (a nil value)
stack traceback:
/usr/bin/lime-config:45: in function </usr/bin/lime-config:45>
[C]: in function 'foreach'
/usr/lib/lua/lime/network.lua:192: in function 'scandevices'
/usr/lib/lua/lime/network.lua:217: in function
</usr/lib/lua/lime/network.lua:208>
[C]: in function 'xpcall'
/usr/bin/lime-config:45: in function 'main'
/usr/bin/lime-config:65: in main chunk
[C]: ?
Configuring system...
Let uhttpd listen on IPv4/IPv6
Funny, just ran into the same problem, it's a d-link dir-600 b5 - so
seems to be a (general?) problem with ramips target?
>> root@000000:~# iw list| grep Wiphy
>> Wiphy phy0
greetings,
micha
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users
3121
days inactive
3133
days old
lime-users@lists.libremesh.org
31 comments
5 participants
participants (5)
-
Gio -
Ilario Gelmetti -
Juergen Kimmel -
Micha Stöcker -
Pau