Difference between revisions of "Template:FriendlyWrt19"
(updated by API) |
(updated by API) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 29: | Line 29: | ||
* Set a secure password | * Set a secure password | ||
* Only allow access to ssh from lan, change the port | * Only allow access to ssh from lan, change the port | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
===Safe shutdown operation=== | ===Safe shutdown operation=== | ||
Enter the ttyd terminal, enter the poweroff command and hit enter, wait until the led light is off, and then unplug the power supply. | Enter the ttyd terminal, enter the poweroff command and hit enter, wait until the led light is off, and then unplug the power supply. | ||
Line 113: | Line 97: | ||
| NanoPi-R2S | | NanoPi-R2S | ||
| NanoPi-R2C-Plus | | NanoPi-R2C-Plus | ||
+ | | NanoPi-R2S-Plus | ||
| NanoPi-R2C = | | NanoPi-R2C = | ||
[[File:R2S-usb2lcd-01.jpg|frameless|600px]]<br /> | [[File:R2S-usb2lcd-01.jpg|frameless|600px]]<br /> | ||
Line 151: | Line 136: | ||
| NanoPi-R2S | | NanoPi-R2S | ||
| NanoPi-R2C-Plus | | NanoPi-R2C-Plus | ||
+ | | NanoPi-R2S-Plus | ||
| NanoPi-R2C = | | NanoPi-R2C = | ||
[[File:R2s-wrt-jellyfin-002.jpg|frameless|800px]]<br /> | [[File:R2s-wrt-jellyfin-002.jpg|frameless|800px]]<br /> | ||
Line 162: | Line 148: | ||
| NanoPi-R2S | | NanoPi-R2S | ||
| NanoPi-R2C-Plus | | NanoPi-R2C-Plus | ||
+ | | NanoPi-R2S-Plus | ||
| NanoPi-R2C = | | NanoPi-R2C = | ||
[[File:R2swrt+usbwifi-09.jpg|frameless|800px]]<br /> | [[File:R2swrt+usbwifi-09.jpg|frameless|800px]]<br /> | ||
Line 175: | Line 162: | ||
| NanoPi-R2S | | NanoPi-R2S | ||
| NanoPi-R2C-Plus | | NanoPi-R2C-Plus | ||
+ | | NanoPi-R2S-Plus | ||
| NanoPi-R2C = | | NanoPi-R2C = | ||
[[File:R2swrt+usbwifi-10.jpg|frameless|800px]]<br /> | [[File:R2swrt+usbwifi-10.jpg|frameless|800px]]<br /> | ||
Line 190: | Line 178: | ||
| NanoPi-R2S | | NanoPi-R2S | ||
| NanoPi-R2C-Plus | | NanoPi-R2C-Plus | ||
+ | | NanoPi-R2S-Plus | ||
| NanoPi-R2C = | | NanoPi-R2C = | ||
[[File:R2swrt+usbwifi-01.jpg|frameless|800px]]<br /> | [[File:R2swrt+usbwifi-01.jpg|frameless|800px]]<br /> | ||
Line 200: | Line 189: | ||
| NanoPi-R2S | | NanoPi-R2S | ||
| NanoPi-R2C-Plus | | NanoPi-R2C-Plus | ||
+ | | NanoPi-R2S-Plus | ||
| NanoPi-R2C = | | NanoPi-R2C = | ||
[[File:R2swrt+usbwifi-03.jpg|frameless|800px]]<br /> | [[File:R2swrt+usbwifi-03.jpg|frameless|800px]]<br /> | ||
Line 208: | Line 198: | ||
| NanoPi-R2S | | NanoPi-R2S | ||
| NanoPi-R2C-Plus | | NanoPi-R2C-Plus | ||
+ | | NanoPi-R2S-Plus | ||
| NanoPi-R2C = | | NanoPi-R2C = | ||
[[File:R2swrt+usbwifi-04.jpg|frameless|800px]]<br /> | [[File:R2swrt+usbwifi-04.jpg|frameless|800px]]<br /> | ||
Line 216: | Line 207: | ||
| NanoPi-R2S | | NanoPi-R2S | ||
| NanoPi-R2C-Plus | | NanoPi-R2C-Plus | ||
+ | | NanoPi-R2S-Plus | ||
| NanoPi-R2C = | | NanoPi-R2C = | ||
[[File:R2swrt+usbwifi-05.jpg|frameless|800px]]<br /> | [[File:R2swrt+usbwifi-05.jpg|frameless|800px]]<br /> | ||
Line 226: | Line 218: | ||
| NanoPi-R2S | | NanoPi-R2S | ||
| NanoPi-R2C-Plus | | NanoPi-R2C-Plus | ||
+ | | NanoPi-R2S-Plus | ||
| NanoPi-R2C = | | NanoPi-R2C = | ||
[[File:R2swrt+usbwifi-07.png|frameless|277px]]<br /> | [[File:R2swrt+usbwifi-07.png|frameless|277px]]<br /> | ||
Line 277: | Line 270: | ||
| NanoPi-R2S | | NanoPi-R2S | ||
| NanoPi-R2C-Plus | | NanoPi-R2C-Plus | ||
+ | | NanoPi-R2S-Plus | ||
| NanoPi-R2C = | | NanoPi-R2C = | ||
<syntaxhighlight lang="bash"> | <syntaxhighlight lang="bash"> | ||
− | tar xvf ~/dvd/RK3328/toolchain/friendlywrt | + | tar xvf ~/dvd/RK3328/toolchain/friendlywrt/openwrt-sdk-19.07.5-rockchip-rk3328_gcc-7.5.0_musl.Linux-x86_64.tar.xz |
# If the path is too long, it will cause some package compilation errors, so change the directory name here | # If the path is too long, it will cause some package compilation errors, so change the directory name here | ||
mv openwrt-sdk-19.07.5-rockchip-rk3328_gcc-7.5.0_musl.Linux-x86_64 sdk | mv openwrt-sdk-19.07.5-rockchip-rk3328_gcc-7.5.0_musl.Linux-x86_64 sdk | ||
Line 288: | Line 282: | ||
| #default = | | #default = | ||
<syntaxhighlight lang="bash"> | <syntaxhighlight lang="bash"> | ||
− | tar xvf ~/dvd/FriendlyELEC-NanoPiR4S/toolchain/friendlywrt | + | tar xvf ~/dvd/FriendlyELEC-NanoPiR4S/toolchain/friendlywrt/openwrt-sdk-19.07.5-rockchip-rk3399_gcc-7.5.0_musl.Linux-x86_64.tar.xz |
# If the path is too long, it will cause some package compilation errors, so change the directory name here | # If the path is too long, it will cause some package compilation errors, so change the directory name here | ||
mv openwrt-sdk-19.07.5-rockchip-rk3399_gcc-7.5.0_musl.Linux-x86_64 sdk | mv openwrt-sdk-19.07.5-rockchip-rk3399_gcc-7.5.0_musl.Linux-x86_64 sdk |
Latest revision as of 10:53, 4 December 2023
Contents
- 1 Work with FriendlyWrt
- 1.1 Introduction to FriendlyWrt
- 1.2 First boot
- 1.3 Account & Password
- 1.4 Network Connection
- 1.5 Login FriendlyWrt
- 1.6 Recommended security settings
- 1.7 Safe shutdown operation
- 1.8 Install Software Packages
- 1.9 Disable IPv6
- 1.10 Configure the function of the user button
- 1.11 Some common issues of FriendlyWrt
- 1.12 Let FriendlyWrt regenerate network settings
- 1.13 Use USB2LCD to view IP and temperature
- 1.14 Work with USB WiFi Device
- 1.15 Work with Docker Applications
- 1.16 Mount smbfs
- 1.17 Use sdk to compile the package
1 Work with FriendlyWrt
1.1 Introduction to FriendlyWrt
FriendlyWrt is a customized system made by FriendlyElec based on an OpenWrt distribution. It is open source and well suitable for developing IoT applications, NAS applications etc.
1.2 First boot
For the first boot, the system needs to do the following initialization work:
1)Extended root file system
2)Initial setup(will execute /root/setup.sh)
So you need to wait for a while (about 2~3 minutes) to boot up for the first time, and then set FriendlyWrt, you can enter the ttyd terminal on the openwrt webpage, when the prompt is displayed as root@FriendlyWrt, it means the system has been initialized.
root@FriendlyWrt
1.3 Account & Password
The default password is password (empty password in some versions). Please set or change a safer password for web login and ssh login. It is recommended to complete this setting before connecting {{{1}}} to the Internet.
1.4 Network Connection
Use a network cable to connect {{{1}}}'s WAN to a master router and the board will get an IP address via DHCP. Login into the router and check {{{1}}}'s IP address.
1.5 Login FriendlyWrt
Connect the PC to the LAN port of {{{1}}}. If your PC without a built-in ethernet port, connect the LAN port of the wireless AP to the LAN port of {{{1}}}, and then connect your PC to the wireless AP via WiFi , Enter the following URL on your PC's browser to access the admin page:
- http://friendlywrt/
- http://192.168.2.1/
- http://[fd00:ab:cd::1]
The above is the LAN port address of {{{1}}}. The IP address of the WAN port will be dynamically obtained from your main router through DHCP.
1.6 Recommended security settings
The following settings are highly recommended to complete before connecting {{{1}}} to the Internet。
- Set a secure password
- Only allow access to ssh from lan, change the port
1.7 Safe shutdown operation
Enter the ttyd terminal, enter the poweroff command and hit enter, wait until the led light is off, and then unplug the power supply.
1.8 Install Software Packages
1.8.1 Update Package List
Before install software packages update the package list:
$ opkg update
1.8.2 List Available Packages
$ opkg list
1.8.3 List Installed Packages
$ opkg list-installed
1.8.4 Install Packages
$ opkg install <package names>
1.8.5 Remove Packages
$ opkg remove <package names>
1.9 Disable IPv6
sed -i -e "s/DISABLE_IPV6=0/DISABLE_IPV6=1/g" /root/setup.sh rm -rf /etc/board.json /etc/config/system /etc/config/network /etc/config/wireless /etc/firstboot_* /root/.friendlyelec reboot
1.10 Configure the function of the user button
By default, the user button is configured to reboot the device, as shown below:
echo 'BTN_1 1 /sbin/reboot' >> /etc/triggerhappy/triggers.d/example.conf
You can change its behavior by changing the configuration file above.
1.11 Some common issues of FriendlyWrt
- Unable to dial up
- Go to "Network" -> "Firewall" and set "Inbound Data", "Outbound Data" and "Forwarding" in "WAN Zone" to "Accept";
- If you still cannot access the Internet, you can try to turn off IPV6;
- Unable to power on
- Try to replace the power adapter and cable. It is recommended to use a power supply with specifications above 5V/2A;
- Note that some fast chargers with Type-C interface will have a delay, it may take a few seconds to start providing power;
- When doing secondary routing, the computer cannot connect to the Internet
- If your main network is IPv4, and {{{1}}} works in IPv6, the computer may not be able to connect to the Internet. It is recommended to turn off IPv6 (the method is described later in this WiKi), or switch the main route to IPv6;
- If you have questions or have better suggestions, please send an email to techsupport@friendlyarm.com;
1.12 Let FriendlyWrt regenerate network settings
This method will trigger FriendlyWrt to re-identify the hardware model and generate the network configuration under /etc/config, which is similar but not completely equivalent to restoring factory settings:
rm -rf /etc/board.json /etc/config/system /etc/config/network /etc/config/wireless /etc/firstboot_* /root/.friendlyelec reboot
The /root/setup.sh initialization script will be executed again at the next boot, so you can debug the /root/setup.sh script through this method.
1.13 Use USB2LCD to view IP and temperature
Plug the USB2LCD module to the USB interface of{{{1}}} and power on, the IP address and CPU temperature will be displayed on the LCD:
1.14 Work with USB WiFi Device
1.14.1 Check USB WiFi Device with Command Line Utility
(1) Click on "services>ttyd" to start the command line utility
(2) Make sure no USB devices are connected to your board and run the following command to check if any USB devices are connected or not
lsusb
(3) Connect a USB WiFi device to the board and run the command again
lsusb
You will see a new device is detected. In our test the device's ID was 0BDA:C811
(4) Type your device's ID (in our case it was "0BDA:C811" or "VID_0BDA&PID_C811") in a search engine and you may find a device that matches the ID. In our case the device we got was Realtek 8811CU.
1.14.2 Configure a USB WiFi Device as AP
(1) Connect a USB WiFi device to the {{{1}}}. We recommend you to use the following devices:
Note: devices that match these VID&PIDs would most likely work.
(2) Click on "System>Reboot" and reboot your {{{1}}}
(3) Click on "Network>Wireless" to enter the WiFi configuration page
(4) Click on "Edit" to edit the configuration
(5) On the "Interface Configuration" page you can set the WiFi mode and SSID, and then go to "Wireless Security" to change the password. By default the password is "password". After you make your changes click on "Save" to save
(6) After you change the settings you can use a smartphone or PC to search for WiFi
1.14.3 Common USB WiFi issues
1) It is recommended to plug in the usb wifi in the off state, then power it on, FriendlyWrt will automatically generate the configuration file /etc/config/wireless, if not, see if there is wlan0 by ifconfig -a, if there is no wlan0, usually there is no driver.
2) If ifconfig -a sees wlan0, but the hotspot is not working properly, try changing the channel and country code, an inappropriate country code can also cause the WiFi to not work.
3) Some USB WiFis (e.g. MTK MT7662) work in CD-ROM mode by default and need to be switched by usb_modeswitch, you can try to add usb_modeswitch configuration to the following directory: /etc/usb_modeswitch.d.
1.15 Work with Docker Applications
1.15.1 Work with Docker: Install JellyFin
mkdir -p /jellyfin/config mkdir -p /jellyfin/videos docker run --restart=always -d -p 8096:8096 -v /jellyfin/config:/config -v /jellyfin/videos:/videos jellyfin/jellyfin:10.1.0-arm64 -name myjellyfin
After installation, visit port 8096 and here is what you would find:
1.15.2 Work with Docker: Install Personal Nextcloud
mkdir /nextcloud -p docker run -d -p 8888:80 --name nextcloud -v /nextcloud/:/var/www/html/ --restart=always --privileged=true arm64v8/nextcloud
After installtion, visit port 8888.
1.16 Mount smbfs
mount -t cifs //192.168.1.10/shared /movie -o username=xxx,password=yyy,file_mode=0644
1.17 Use sdk to compile the package
1.17.1 Install the compilation environment
Download and run the following script on 64-bit Ubuntu (version 18.04+): How to setup the Compiling Environment on Ubuntu bionic
1.17.2 Download and decompress sdk from the network disk
The sdk is located in the toolchain directory of the network disk:
tar xvf ~/dvd/FriendlyELEC-NanoPiR4S/toolchain/friendlywrt/openwrt-sdk-19.07.5-rockchip-rk3399_gcc-7.5.0_musl.Linux-x86_64.tar.xz # If the path is too long, it will cause some package compilation errors, so change the directory name here mv openwrt-sdk-19.07.5-rockchip-rk3399_gcc-7.5.0_musl.Linux-x86_64 sdk cd sdk ./scripts/feeds update -a ./scripts/feeds install -a
1.17.3 Compile the package
download the source code of the example (a total of 3 examples are example1, example2, example3), and copy to the package directory:
git clone https://github.com/mwarning/openwrt-examples.git cp -rf openwrt-examples/example* package/ rm -rf openwrt-examples/
Then enter the configuration menu through the following command:
make menuconfig
In the menu, select the following packages we want to compile (actually selected by default):
"Utilities" => "example1" "Utilities" => "example3" "Network" => "VPN" => "example2"
execute the following commands to compile the three software packages:
make package/example1/compile V=99 make package/example2/compile V=99 make package/example3/compile V=99
After the compilation is successful, you can find the ipk file in the bin directory, as shown below:
$ find ./bin -name example*.ipk ./bin/packages/aarch64_cortex-a53/base/example2_0.1-1_aarch64_cortex-a53.ipk ./bin/packages/aarch64_cortex-a53/base/example3_0.1-1_aarch64_cortex-a53.ipk ./bin/packages/aarch64_cortex-a53/base/example1_0.1-1_aarch64_cortex-a53.ipk
1.17.4 Install the ipk to NanoPi
You can use the scp command to upload the ipk file to NanoPi:
cd ./bin/packages/aarch64_cortex-a53/base/ scp example*.ipk root@192.168.2.1:/root/
Then use the opkg command to install them:
cd /root/ opkg install example2_0.1-1_aarch64_cortex-a53.ipk opkg install example3_0.1-1_aarch64_cortex-a53.ipk opkg install example1_0.1-1_aarch64_cortex-a53.ipk