I want to install LEDE on a Lamobo R1. I have read several times that this has been done. Unfortunately, I do not succeed.
I can not find instructions for it. Would you help me?
I brought “lede-17.01.4-sunxi-sun7i-a20-lamobo-r1-squashfs-sdcard.img” with Etcher to an 8GB SD card. I then tried to access the 192.168.1.1 with IE. For this I connected the single Ethernet socket of the Lamobo R1 with a network cable with my laptop with Windows 7. In Windows, I have given the ethernet port the 192.168.1.2 (subnet mask 255.255.0.0 default gateway 192.168.1.1 and DNS server 192.168.1.1).
Where is my mistake?
I find no solution to the problem. I have now even created an image (see https://lede-project.org/docs/guide-developer/quickstart-build-images). But also with this image I get no contact to the Lamobo R1. Are the network settings I described above in Windows correct? Do I have to access via telnet or ssh?
You have installed a snapshot image, which does not come with LuCI pre-installed.
You have to install LuCI yourself. -> https://lede-project.org/docs/user-guide/luci.essentials
Apart from that, even with snapshot images you should be able to access your device via ssh.
How do I configure the computer's Ethernet port? Do I have to give it a fixed IP (In Windows, I have given the ethernet port the 192.168.1.2 (subnet mask 255.255.0.0 default gateway 192.168.1.1 and DNS server 192.168.1.1) or set it to DHCP? I can't ping the Lamobo R1 on 192.168.1.1 or it is the false IP?
I would download and run the free tool Advanced IP Scanner and see what IP addresses are assigned...
http://www.advanced-ip-scanner.com/
The default IP address for LEDE is 192.168.1.1. You can downloading PuTTY and try to ssh in using that...
The user ID is root, and the password is whatever password you set up after installing LEDE.
https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html
You might take a look at the LEDE User Guide for tips on configuration...
Please ... no:
https://www.linuxquestions.org/questions/blog/caysho-16429/banana-pi-bpi-r1-bad-for-routing-37234/
I still have not been able to establish the first connection to the Lamobo R1. Here are my steps.
- Created an Image.
- Unzip lede-sunxi-cortexa7-sun7i-a20-lamobo-r1-ext4-sdcard.img.gz
- Write lede-sunxi-cortexa7-sun7i-a20-lamobo-r1-ext4-sdcard with Etcher on an 8GB microSD Card.
- Connect the WAN port of the Lamobo R1 with an Ethernet cable directly to the computer.
- Configure the computer with the fixed IP 192.168.1.2 (subnet mask 255.255.0.0 default gateway 192.168.1.1 and DNS server 192.168.1.1).
- Ping 192.168.1.1 -> No Connection
Where is my mistake?
Shouldn't this be 255.255.255.0?
Even with the subnet mask 255.255.255.0 no success 
.
Have you already tried with all ports, not only WAN port?
There are rare cases where you need to connect to a LAN port instead of WAN port.
Have you already tried the IP scanner recommended by jwoods above?
I've tested all five Ethernet ports and don't get a connection to 192.168.1.1 on any port.
I have not tested an IP scanner because I have a direct connection between the Ethernet port of the Lamobo R1 and the computer.
Please do so.
I have a serial console connected and ifconfig delivers the following output:
BusyBox v1.25.1 () built-in shell (ash)
_________
/ /\ _ ___ ___ ___
/ LE / \ | | | __| \| __|
/ DE / \ | |__| _|| |) | _|
/________/ LE \ |____|___|___/|___| lede-project.org
\ \ DE /
\ LE \ / -----------------------------------------------------------
\ DE \ / Reboot (17.01.4, r3560-79f57e422d)
\________\/ -----------------------------------------------------------
root@LEDE:/# ifconfig
br-lan Link encap:Ethernet HWaddr 02:58:03:42:51:E1
inet6 addr: fe80::58:3ff:fe42:51e1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:4500 (4.3 KiB)
eth0 Link encap:Ethernet HWaddr 02:58:03:42:51:E1
inet6 addr: fe80::58:3ff:fe42:51e1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:57 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:12395 (12.1 KiB)
Interrupt:48
eth0.1 Link encap:Ethernet HWaddr 02:58:03:42:51:E1
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:4500 (4.3 KiB)
eth0.2 Link encap:Ethernet HWaddr 02:58:03:42:51:E1
inet6 addr: fe80::58:3ff:fe42:51e1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:5354 (5.2 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:32 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:2136 (2.0 KiB) TX bytes:2136 (2.0 KiB)
No Ethernet port has an IP associated with it. Therefore, access will probably also fail?!?