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@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:
> 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@dabax.net>:
>> 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@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@gmail.com> schrieb am Sa., 8. Apr. 2017 um
>>>> 02:24 Uhr:
>>>>
>>>> There is no channel assigned to the meshing radio1
>>>>
>>>> Juergen Kimmel <juergenkimmel@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@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@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@dabax.net>:
>>>>>> 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@lists.libremesh.org
>>>>>>> https://lists.libremesh.org/mailman/listinfo/lime-users
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> ./p4u
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> lime-users mailing list
>>>>>> lime-users@lists.libremesh.org
>>>>>> https://lists.libremesh.org/mailman/listinfo/lime-users
>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> ./p4u
>>>>
>>>> _______________________________________________
>>>> lime-users mailing list
>>>> lime-users@lists.libremesh.org
>>>> https://lists.libremesh.org/mailman/listinfo/lime-users
>>>>
>>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> lime-users mailing list
>>> lime-users@lists.libremesh.org
>>> https://lists.libremesh.org/mailman/listinfo/lime-users
>>>
>>
>> --
>> ./p4u
>>
>>
>> _______________________________________________
>> lime-users mailing list
>> lime-users@lists.libremesh.org
>> https://lists.libremesh.org/mailman/listinfo/lime-users
>
>
>

--
./p4u

_______________________________________________
lime-users mailing list
lime-users@lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users