dolphs
-
Posts
273 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by dolphs
-
-
Hi,
I owe a fritzbox 5530 which is configured for both IPv6 and IPv4.
My armbian ( debian 11 ) SBC ( neo2 running kernel 5.19.1 ) shows:
root@armbian:~# ip a |grep inet6 inet6 ::1/128 scope host inet6 2a02:a45f:b977:1:3383:1a4e:38e2:733f/128 scope global dynamic noprefixroute inet6 2a02:a45f:b977:1:a05d:7fc7:a5d0:d647/64 scope global dynamic noprefixroute inet6 fe80::3383:1a4e:38e2:733f/64 scope link noprefixrouteHowever I am unable to resolve the IPv6 address while for another debian box it is working fine:
root@armbian:~# ping debian.fritz.box PING debian.fritz.box(debian.fritz.box (2a02:a45f:b977:1:21d:ecff:fe0f:e2e0)) 56 data bytes 64 bytes from debian.fritz.box (2a02:a45f:b977:1:21d:ecff:fe0f:e2e0): icmp_seq=1 ttl=255 time=4.12 ms 64 bytes from debian.fritz.box (2a02:a45f:b977:1:21d:ecff:fe0f:e2e0): icmp_seq=2 ttl=255 time=3.34 ms ^C root@armbian:~# ping armbian.fritz.box PING armbian.fritz.box (192.168.10.6) 56(84) bytes of data. 64 bytes from armbian.fritz.box (192.168.10.6): icmp_seq=1 ttl=64 time=0.999 ms 64 bytes from armbian.fritz.box (192.168.10.6): icmp_seq=2 ttl=64 time=2.51 ms ^C
Any thoughts please?
-
Hi,
I tried to add options overlays as well ftdfile for the npi-r4s , but seems 1,8-Ghz is max ?
#kernel = 5.18.14-rockchip64
verbosity=1 bootlogo=false overlay_prefix=rockchip overlays=rk3399-opp-2ghz ftdfile=rockchip/rk3399-nanopi-r4s.dtb rootdev=UUID=83a12c16-47da-45c8-b0ff-3ebd7326dc4c rootfstype=ext4 console=serial usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:uWhat is new this does not seem to work ( anymore ).
TiA!
-
I compiled a small HOWTO to get this going with kernel 5.16 on a Rockpi4+
sudo su - apt update && apt -y install git build-essential swig4.0 python3-dev libnode-dev cmake libjson-c-devGrab "user overlay" from radxa:
mkdir -p /boot/overlay-user cd /boot/overlay-user curl -sL https://rock.sh/rockpi-poe-dtbo -o rockpi-poe.dtbo nano /boot/armbianEnv.txt user_overlays=rockpi-poe exit
Compile mraa packages
cd /home/[user] git clone https://github.com/eclipse/mraa mkdir mraa/build cd mraa/build cmake .. make -j7 #depends on cores available+1 sudo make installSpoiler---
< snip snip >
[ 97%] Linking C executable mraa-i2c
[ 98%] Linking CXX executable iio_cpp
[100%] Linking C executable mraa-gpio
[100%] Built target mraa-i2c
[100%] Built target uart_ow_cpp
[100%] Built target mraa-gpio
[100%] Built target iio_cpp
---
---
<snip snip>
[ 92%] Built target uart_ow_cpp
[ 95%] Built target mraa-uart
[ 97%] Built target mraa-i2c
[100%] Built target mraa-gpio
Install the project...
-- Install configuration: ""
-- Installing: /usr/local/include/mraa.h
-- Installing: /usr/local/include/mraa.hpp<snip snip>
-- Installing: /usr/local/share/mraa/examples/c++/spi.cpp
-- Installing: /usr/local/share/mraa/examples/c++/pwm.cpp
-- Installing: /usr/local/share/mraa/examples/c++/led.cpp
-- Installing: /usr/local/bin/mraa-gpio
-- Set runtime path of "/usr/local/bin/mraa-gpio" to ""
-- Installing: /usr/local/bin/mraa-i2c
-- Set runtime path of "/usr/local/bin/mraa-i2c" to ""
-- Installing: /usr/local/bin/mraa-uart
-- Set runtime path of "/usr/local/bin/mraa-uart" to ""
---Install PoE package and enable its service
sudo su #view /etc/ld.so.conf.d/libc.conf ldconfig # add /usr/local/lib libraries to " LD_LIBRARY_PATH " cd /tmp wget https://cos.setq.me/rockpi/deb/rockpi-poe-0.13.deb dpkg -i rockpi-poe-0.13.deb systemctl enable rockpi-poe.service rebootAfter reboot the fan should spin up like mad and after little while it slows down ( off ) :
root@rockpi-4a:~# systemctl status rockpi-poe.service ● rockpi-poe.service - Rockpi PoE-FAN Loaded: loaded (/lib/systemd/system/rockpi-poe.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2022-03-22 11:19:06 UTC; 11min ago Main PID: 659 (python3) Tasks: 1 (limit: 4464) Memory: 11.7M CPU: 264ms CGroup: /system.slice/rockpi-poe.service └─659 /usr/bin/python3 /usr/bin/rockpi-poe.py start Mar 22 11:19:06 rockpi-4a systemd[1]: Started Rockpi PoE-FAN. Mar 22 11:19:08 rockpi-4a libmraa[659]: libmraa version v2.2.0-11-gd7ae171 initialised by user 'root' with EUID 0 Mar 22 11:19:08 rockpi-4a libmraa[659]: gpio: platform doesn't support chardev, falling back to sysfs Mar 22 11:19:08 rockpi-4a libmraa[659]: libmraa initialised for platform 'ROCK Pi 4' of type 20 -
Hi,
Based on this topic it should be possible to open PWM0 and PWM1 on a RockpiS,
Yet I like to do the same thing on a Rockpi4A+ ( fdtfile=rockchip/rk3399-rock-pi-4a-plus.dtb ),
in order to enable the fan on a PoE HAT
Without any overlay it shows:
root@rockpi-4a:/sys/class/pwm# ls /sys/class/pwm/ -la total 0 drwxr-xr-x 2 root root 0 Mar 19 05:20 . drwxr-xr-x 71 root root 0 Mar 19 05:20 .. lrwxrwxrwx 1 root root 0 Mar 19 05:20 pwmchip0 -> ../../devices/platform/ff420020.pwm/pwm/pwmchip0I tried some of radxa's suggestions using their " rockpi-poe.dtbo " overlay ( user_overlays=rockpi-poe )
and indeed that makes the fan spinning up like crazy, but alas unable to control the fan, due to missing libmraa.
However the overlay mentioned does seem to open two additional PWM's, thus PWM0 till 2.
root@rockpi-4a:~# ls /sys/class/pwm/ -la total 0 drwxr-xr-x 2 root root 0 Mar 19 05:36 . drwxr-xr-x 71 root root 0 Mar 19 05:36 .. lrwxrwxrwx 1 root root 0 Mar 19 05:36 pwmchip0 -> ../../devices/platform/ff420000.pwm/pwm/pwmchip0 lrwxrwxrwx 1 root root 0 Mar 19 05:36 pwmchip1 -> ../../devices/platform/ff420010.pwm/pwm/pwmchip1 lrwxrwxrwx 1 root root 0 Mar 19 05:36 pwmchip2 -> ../../devices/platform/ff420020.pwm/pwm/pwmchip2I was wondering if this is WIP, or should is it possible already to enable pwm with a built-in armbian overlay,
was unable to retrieve anything in that direction from: /boot/dtb/rockchip/overlays except for " overlays=w1-gpio " but perhaps there is another way?
[ 6.207083] OF: /onewire@0: could not get #gpio-cells for /vop@ff900000/port/endpoint@1 [ 6.207102] w1-gpio onewire@0: gpio_request_one (ext_pullup_enable_pin) failed [ 6.207105] w1-gpio: probe of onewire@0 failed with error -22PS I am not demandig anything, just asking about PoE HAT status ( controllable fan ) in current armbian ( edge, kernel 5.16.x ) and if this is WIP?
thanks!
-
Hello,
I noticed things have been updated since I have been gone , thanks very much for that and I was able to compile 5.16.15 just now for my rockpi-4a+ !
However it seems to run at 1,8GHz , while I was expecting with " rk3399-rock-pi-4a-plus.dtb " it should run at 2GHz, also because previous overlay "rk3399-opp-2ghz " vanished ? Suppose this is WIP,.
Thanks a million for your efforts getting all this done as I found out it has been hard to take out all hurdles as posted back in January already !!!
UPDATE - this helped instead of using "overlays" option:
fdtfile=rockchip/rk3399-rock-pi-4a-plus.dtb -
Hi,
I managed to compile 5.16.1 for my Rockpi4 board, I did not flash it yet as I try to polish things before I flash things.
Also awaiting my 4A+ ( with POE HAT ) but first things first.
Could one please update the edge entry to " 5.16.y " # /config/sources/families/include/ rockchip64_common.inc
Also imho for rockpi4a(+) all bluetooth and WiFi entries should be removed from the kernel .config:
- bluetooth-rtl8822cs-hci_ver-0x8.patch
- Bluetooth-hci_h5-Add-power-reset-via-gpio-in-h5_btrt.patch
- kali-wifi-injection-*.patch
- wireless-*.patch- general-bluetooth-add-new-quirk.patch
- board-pbp-fix-wonky-wifi-bt.patch
- wifi-hf-lps170-bl602-kconfig-makefile.patch
- wifi-hf-lps170-bl602.patchTo build 5.16.y following patches have been removed :
- board-rockpi4-0005-arm64-dts-enable-es8316-audio.patch
? general-fix-es8316-kernel-panic.patch # did not remove but should be imho ?
- bootsplash-5.10.y-0003-Revert-fbcon-remove-soft-scrollback-code.patch
- 0001-bootsplash.patch
- 0006-bootsplash.patch
- 0007-bootsplash.patch
- 0008-bootsplash.patch
- 0009-bootsplash.patch./compile.sh BOARD=rockpi-4a BRANCH=edge RELEASE=bullseye BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=yes EXPERT=YES EXTRAWIFI=no
This way it built ( with WARNINGS : which is to be polished ) at least 5.16, Armbian_22.02.0-trunk_Rockpi-4a_bullseye_edge_5.16.1_minimal.img.However patches removed either need to be revised ( and come back in ) or in most happy scenario indeed simply can be removed ( like for ess audio )
Also I would be happy to see an "lsmod" from rockpi4a+ which can be compared with rockpi4a.
Perhaps also radxa image and armbian image need to be put side by side so a proper ".config" can be created for 5.16.y edge kernels.
Hopefully we ( community ) can spend some effort coming months ( years :-) ) getting the 4a+ stable as I assume there are loose ends with this 'new' OP1 board.
Meanwhile like to do some trial and error on its .config next few days, but won't expect my 4a+ in before February 2022...
If appreciated I can post my current compilation and other output logs, I attached " compilation.log " and rgd WARNINGS:
- Bootsplashes fail due to removal patches ( missing dependencies )
- Bluetooth can be ignored for rockpi4a/4a+
These need to be looked in to ( as well bootsplashes ):
[ warn ] * [l][c] board-pbp-setup-USB-type-c-port-as-dual-dat.patch [ failed ][ warn ] * [l][c] board-rockpis-0008-thermal-rockchip-add-tsadc-support-for-rk3308.patch [ failed ]
[ warn ] * [l][c] board-rockpis-0016-ASoC-rockchip-add-support-for-rockchip-i2s-tdm-contr.patch [ failed ]
[ warn ] * [l][c] general-add-panel-simple-dsi.patch [ failed ]
Yup most likely there is some rework required...
-
Hello gents,
I have been out of the loop for quite some time...
Therefore did not update my armbian dev env either for quite a while, was a bit "surprised" after a " git pull " most boards went to CSC, but read the story why...
Anyway I was wondering rgd the "new" OP1 Rockpi4+ boards, if same image can be used for these boards ?
Most likely a new entry to compile, armbian building script, will appear sooner or later. Also noticed current kernel 5.16 holds commits for 4A+ and 4B+ :
Rockchip ... Add RK3399 ROCK Pi 4A+ board commit Add RK3399 ROCK Pi 4B+ board commit ...In +/- two months like to start a PoE ROCK Pi 4A+ board project , checking current status I most likely should start building for "rockpi-4a" and change kernel config a bit.
Hopefully by then a "Bleeding edge" ( 5.16 kernel ) can be compiled for these boards ...
Currently compilation.log shows ( see below ) and suspecting these patches :
Displaying message: * [\e[32ml\e[0m][\e[32mc\e[0m] board-rockpi4-0005-arm64-dts-enable-es8316-audio.patch info Displaying message: * [\e[32ml\e[0m][\e[32mc\e[0m] general-fix-es8316-kernel-panic.patch infoSpoilerdolphs@develop:~/armbian/output/debug$ more compilation.log
== u-boot make rock-pi-4-rk3399_defconfig ==
== u-boot make BL31=/home/dolphs/armbian/cache/sources/rkbin-tools/rk33/rk3399_bl31_v1.35.elf tpl/u-boot-tpl.bin spl/u-boot-spl.bin u-boot.itb u-boot-dtb.bin ==.config:2044:warning: override: reassigning to symbol BOOTDELAY
arch/arm/mach-rockchip/rk3399/rk3399.c: In function ‘board_debug_uart_init’:
arch/arm/mach-rockchip/rk3399/rk3399.c:126:36: warning: unused variable ‘gpio’ [-Wunused-variable]
126 | struct rockchip_gpio_regs * const gpio = (void *)GPIO0_BASE;
| ^~~~
arch/arm/mach-rockchip/rk3399/rk3399.c: In function ‘board_debug_uart_init’:
arch/arm/mach-rockchip/rk3399/rk3399.c:126:36: warning: unused variable ‘gpio’ [-Wunused-variable]
126 | struct rockchip_gpio_regs * const gpio = (void *)GPIO0_BASE;
| ^~~~
arch/arm/mach-rockchip/rk3399/rk3399.c: In function ‘board_debug_uart_init’:
arch/arm/mach-rockchip/rk3399/rk3399.c:126:36: warning: unused variable ‘gpio’ [-Wunused-variable]
126 | struct rockchip_gpio_regs * const gpio = (void *)GPIO0_BASE;
| ^~~~== kernel ==
arch/arm64/boot/dts/rockchip/overlay/rockchip-spi-spidev.dts:22.11-27.6: Warning (spi_bus_reg): /fragment@1/__overlay__/spidev: SPI bus unit address format error, expected "0"
arch/arm64/boot/dts/rockchip/overlay/rockchip-spi-spidev.dts:36.11-41.6: Warning (spi_bus_reg): /fragment@2/__overlay__/spidev: SPI bus unit address format error, expected "0"
arch/arm64/boot/dts/rockchip/overlay/rockchip-spi-spidev.dts:50.11-55.6: Warning (spi_bus_reg): /fragment@3/__overlay__/spidev: SPI bus unit address format error, expected "0"
arch/arm64/boot/dts/rockchip/overlay/rockchip-spi-spidev.dts:64.11-69.6: Warning (spi_bus_reg): /fragment@4/__overlay__/spidev: SPI bus unit address format error, expected "0"
arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi:501.19-515.4: ERROR (duplicate_label): /i2c@ff130000/codec@11: Duplicate label 'es8316' on /i2c@ff130000/codec@11 and /i2c@ff110000/codec@11
arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi:511.26-513.6: ERROR (duplicate_label): /i2c@ff130000/codec@11/port/endpoint: Duplicate label 'es8316_p0_0' on /i2c@ff130000/codec@11/port/endpoint and
/i2c@ff110000/codec@11/port/endpoint
arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi:545.16-551.4: ERROR (duplicate_label): /i2s@ff890000/port: Duplicate label 'i2s0_p0' on /i2s@ff890000/port and /i2s@ff880000/port
arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi:546.23-550.5: ERROR (duplicate_label): /i2s@ff890000/port/endpoint: Duplicate label 'i2s0_p0_0' on /i2s@ff890000/port/endpoint and /i2s@ff880000/port/
endpoint
ERROR: Input tree has errors, aborting (use -f to force output)
make[2]: *** [scripts/Makefile.lib:352: arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtb] Error 2
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [scripts/Makefile.build:549: arch/arm64/boot/dts/rockchip] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:1385: dtbs] Error 2
make: *** Waiting for unfinished jobs....
Grtz!
-
-
Hmmm why moving to 11 already, better wait till bullseye hit the streets imho...
Perhaps you ae better off with backports? I do similar for unbound ( wireguard-tools )? eg:
Spoiler
apt update && apt -y install -t buster-backports unbound
Last, but not least, dont know if you have emmc installed but you might test bullseye from sdcard?
Compiling with EXPERT=yes, eg for rockpi-4a ( my scenario ):
Spoiler./compile.sh EXPERT=yes EXTRAWIFI=no USEALLCORES=yes
-
looks like this helped in the end: " rockpi-4a:~:# vnstat -i wg0 --update "
SpoilerError: Unable to read database "/var/lib/vnstat/wg0": No such file or directory
Info: -> A new database has been created. -
Just flashed rockpi-4a current buster image and it looks like I hit
" Error: Unable to read database "/var/lib/vnstat/wg0": No such file or directory Merge "eth0+wg0" failed. ",
which can be shown here
Spoilerlogin as: root
root@rockpi-4a's password:
____ _ _ _ _ _
| _ \ ___ ___| | ___ __ (_) | || | / \
| |_) / _ \ / __| |/ / '_ \| | | || |_ / _ \
| _ < (_) | (__| <| |_) | | |__ _/ ___ \
|_| \_\___/ \___|_|\_\ .__/|_| |_|/_/ \_\
|_|
Welcome to Armbian 21.05.2 Buster with bleeding edge Linux 5.12.6-rockchip64System load: 2% Up time: 12 min
Memory usage: 6% of 1.93G IP: 192.168.10.66
CPU temp: 42°C Usage of /: 15% of 15G
RX today: Error: Unable to read database "/var/lib/vnstat/wg0": No such file or directory Merge "eth0+wg0" failed.
Also have been checking vnstat to merge wg0 but did not succeed,
perhaps one can give me a hand please? TiA!
These are the adapters present:
Spoilerrockpi-4a:~:# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 86:67:c3:ba:43:ca brd ff:ff:ff:ff:ff:ff
inet 192.168.10.66/24 brd 192.168.10.255 scope global dynamic noprefixroute eth0
valid_lft 3318sec preferred_lft 3318sec
3: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000
link/none
-
.
-
bumped my OpiOnePlus H6 boards to kernel 5.12 and surprise surprise , BBR is working as it should again ...
I really wonder what was causing this as in kernel 5.10 and 11 I had to use westwood ( with cake )...
net.core.default_qdisc = fq net.ipv4.tcp_congestion_control = bbrshows 250Mbit ( meanwhile line upgraded which is max upload speed )
root@vpn01:~# iperf3 -4 -c 192.168.10.2 -t 300 -b0 -P1 Connecting to host 192.168.10.2, port 5201 [ 5] local 192.168.20.2 port 47462 connected to 192.168.10.2 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 28.4 MBytes 238 Mbits/sec 0 7.71 MBytes [ 5] 1.00-2.00 sec 35.0 MBytes 294 Mbits/sec 1789 1.81 MBytes [ 5] 2.00-3.00 sec 26.2 MBytes 220 Mbits/sec 3780 1.96 MBytes [ 5] 3.00-4.00 sec 30.0 MBytes 252 Mbits/sec 3389 1.66 MBytes [ 5] 4.00-5.00 sec 27.5 MBytes 231 Mbits/sec 4158 2.27 MBytes [ 5] 5.00-6.00 sec 28.8 MBytes 241 Mbits/sec 2252 5.84 MBytes [ 5] 6.00-7.00 sec 30.0 MBytes 252 Mbits/sec 2507 5.85 MBytes [ 5] 7.00-8.00 sec 26.2 MBytes 220 Mbits/sec 3921 2.12 MBytes [ 5] 8.00-9.00 sec 30.0 MBytes 252 Mbits/sec 2773 5.94 MBytes [ 5] 9.00-10.00 sec 27.4 MBytes 230 Mbits/sec 3675 2.02 MBytes [ 5] 10.00-11.00 sec 28.8 MBytes 241 Mbits/sec 3512 1.88 MBytes ^C[ 5] 11.00-11.22 sec 7.50 MBytes 289 Mbits/sec 319 2.68 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-11.22 sec 326 MBytes 244 Mbits/sec 32075 sender -
On 5/16/2021 at 11:43 PM, Igor said:
Another afternoon and all kernels for 5.12.y are done at build stage.
- cleaning
- do we need to archive 5.11.y. I would say no since its not LTS
- testing
5.11 to be buried, is EOL ( already ).
imho the non LTS kernels could be buried once mainline kernel hits .1 release. Thus eg. when 5.13.1 will be released bump edge kernel asap so 5.12 can be buried ( and forgotten )
( needless to say , but "currents" should stay on LTS )
-
Hello to you all,
Haven't read 2825 yet, will do after this but
did a quick checkout and built both for H6 (opioneplus) and H616( zero2 ), :
git pull sed -i 's/orange-pi-5.11/orange-pi-5.12/g' config/sources/families/include/sunxi64_common.inc ./compile.sh EXPERT=yes EXTRAWIFI=no USEALLCORES=yescompilation.log shows
---grep error output/debug/*.log output/debug/compilation.log:drivers/clk/sunxi-ng/ccu-sun50i-h6-r.c:152:27: error: redefinition of ‘sun50i_h616_r_ccu_clks’ output/debug/compilation.log:drivers/clk/sunxi-ng/ccu-sun50i-h6-r.c:178:9: error: ‘CLK_NUMBER_H616’ undeclared here (not in a function); did you mean ‘CLK_NUMBER’? output/debug/compilation.log:drivers/clk/sunxi-ng/ccu-sun50i-h6-r.c:194:35: error: redefinition of ‘sun50i_h616_r_hw_clks’ output/debug/compilation.log:drivers/clk/sunxi-ng/ccu-sun50i-h6-r.c:226:29: error: redefinition of ‘sun50i_h616_r_ccu_resets’ output/debug/compilation.log:drivers/clk/sunxi-ng/ccu-sun50i-h6-r.c:252:36: error: redefinition of ‘sun50i_h616_r_ccu_desc’Suppose once that packaging issue is solved edge will be bumped , so sed no longer needed.
cheers chaps!
-
On 3/3/2021 at 5:00 AM, legogris said:
I'd like to buy one or more NanoPi NEO2 or NanoPi NEO2 BLACK. Preferably 1GB model.
got three items gathering dust , 1Gb as well emmc 16Gb tested to be working fine!
-
cheers for your response.
eth0, eth1 solved by " extraargs=net.ifnames=0 " as @Igor pointed out in this topic
I cut down iptables script to the basics as shown below ,
allowing SSH on eth1 only and outbound traffic goes over eth0.
#!/bin/sh # Delete all existing iptables rules iptables -F # Set default chain policies to DROP all iptables -P INPUT DROP iptables -P FORWARD DROP iptables -P OUTPUT DROP # Allow SSH on eth1 iptables -A INPUT -i eth1 -p tcp --dport 22 -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A OUTPUT -o eth1 -p tcp --sport 22 -m state --state ESTABLISHED -j ACCEPT iptables -A OUTPUT -o eth1 -p tcp --dport 22 -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A INPUT -i eth1 -p tcp --sport 22 -m state --state ESTABLISHED -j ACCEPT # Allow all outbound traffic eth0 iptables -I OUTPUT -o eth0 -d 0.0.0.0/0 -j ACCEPT iptables -I INPUT -i eth0 -m state --state ESTABLISHED,RELATED -j ACCEPTNext part would be to update routing accordingly so outbound won't check for eth1 and go straight to eth0, etc etc
-
Hi,
Idea is to run a wireguard server having two ethernet devices, therefore
added an USB3 adapter "ASIX AX88179" to my rockpi4a.
I like to allow incoming traffic, incl SSH, on "eth1". Instead, outgoing, on eth0 ( RTL8211E )I wrote following ( preps, nmcli, iptables ) up - but perhaps there is an easier approach and I am sure I am missing other (routing) stuff, for sure the forwarding part.
Anyway perhaps there is one to guide me a bit, TiA!
1/ preparations
apt update && apt -y upgrade && apt -y install firmware-realtek
nano /boot/armbianEnv.txt # add extraargs=net.ifnames=0reboot2/ nmcli stuff
nmcli c mod "Wired connection 2" connection.id realtek nmcli c mod "Wired connection 1" connection.id asix nmcli c mod asix ipv6.method ignore nmcli c mod realtek ipv6.method ignore nmcli c mod asix ipv4.never-default true nmcli c up asix nmcli c up realtek3/ iptables "hardening"
# 1. Delete all existing rules iptables -F # 2. Set default chain policies to DROP all both eth0 and eth1 iptables -P INPUT DROP iptables -P FORWARD DROP iptables -P OUTPUT DROP # 3. Allow SSH on eth1 iptables -A INPUT -i eth1 -p tcp --dport 22 -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A INPUT -i eth1 -p tcp --sport 22 -m state --state ESTABLISHED -j ACCEPT iptables -A OUTPUT -o eth1 -p tcp --dport 22 -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A OUTPUT -o eth1 -p tcp --sport 22 -m state --state ESTABLISHED -j ACCEPT # 4. Allow incoming Wireguard on eth1 iptables -A INPUT -i eth1 -p udp --dport 51820 -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A OUTPUT -o eth1 -p udp --sport 51820 -m state --state ESTABLISHED -j ACCEPT FORWARD? ( wg0 ) # 5. Allow outbound Wireguard on eth0 iptables -A OUTPUT -o eth0 -p udp --dport 51820 -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A INPUT -i eth0 -p udp --sport 51820 -m state --state ESTABLISHED -j ACCEPT FORWARD? ( wg0 ) # 6. Allow outbound http(s) on eth0 ( eg updates ) iptables -A OUTPUT -o eth0 -p tcp -m multiport --sports 80,443 -m conntrack --ctstate ESTABLISHED -j ACCEPT # iperf3 excluded for now # 7. Accept all traffic on loopback interface iptables -A INPUT -i lo -j ACCEPT iptables -A OUTPUT -o lo -j ACCEPT
-
fantastic, thanks for your answer Igor
I was already about to mess with " 73-usb-net-by-mac.rules ", but this flag works so much better!
Out of the box, flashing image it shows:
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 86:67:c3:ba:43:ca brd ff:ff:ff:ff:ff:ff inet 192.168.10.188/24 brd 192.168.10.255 scope global dynamic noprefixroute eth0 valid_lft 14213sec preferred_lft 14213sec inet6 fe80::f791:3c34:96fb:aec3/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 00:0e:c6:67:f0:a2 brd ff:ff:ff:ff:ff:ff
Now remaining to configure static address , routing etc etc.This is my test "system" , so I can configure/ test settings before applying them instantly to my R4S
thanks again!
-
Hi,
I added an USB3.0 adapter to my rockpi4a , which results in: " enx000ec667f0a2 " ( eth1 )
Since NetworkManager is being used I tried to update this name using : " nmcli c modify armbian connection.interface-name "eth1" "
But alas that does not seem to be picked up while nmconnection config file has been updated:
cat /etc/NetworkManager/system-connections/armbian.nmconnection
[connection]
id=armbian
uuid=8f61a97c-d0f1-4cb2-be4a-3fe2b4c08e7c
type=ethernet
interface-name=eth1<snip snip>
Ideally this could be changed in armbian-config, but I realise this is a low-low
rockpi-4a:system-connections:# ll
total 1.0K
-rw------- 1 root root 331 Feb 2 12:12 armbian.nmconnection
-rw------- 1 root root 384 Feb 2 11:54 'Wired connection 2.nmconnection'That ideally gets changed to 'Wired connection 1.nmconnection'
which I updated manually using " nmcli c modify armbian connection.id 'Wired connection 1' "
Idea is eth0 will be used solely for outgoing traffic, while "eth1" will be used for incoming
-
no url to paste to, but 5.9.14 shows:
root@rockpi-4a:~# cpufreq-info | grep 2.02 hardware limits: 408 MHz - 2.02 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz current policy: frequency should be within 408 MHz and 2.02 GHz. cpufreq stats: 408 MHz:77.49%, 600 MHz:2.96%, 816 MHz:0.26%, 1.01 GHz:0.17%, 1.20 GHz:0.13%, 1.42 GHz:0.12%, 1.61 GHz:0.04%, 1.80 GHz:0.07%, 2.02 GHz:18.76% (288) hardware limits: 408 MHz - 2.02 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz current policy: frequency should be within 408 MHz and 2.02 GHz. cpufreq stats: 408 MHz:77.49%, 600 MHz:2.96%, 816 MHz:0.26%, 1.01 GHz:0.17%, 1.20 GHz:0.13%, 1.42 GHz:0.12%, 1.61 GHz:0.04%, 1.80 GHz:0.07%, 2.02 GHz:18.76% (288)It is not a biggie, but just noticed and that is all.
So I suppose it is a WIP and will be overlay sooner or later ( similar back then with NEO2 board : cpu-clock-1.3GHz-1.3v )
-
Hi,
Just noticed image " Linux rockpi-4a 5.9.14-rockchip64 #20.11.4 SMP PREEMPT Tue Dec 15 08:52:20 CET 2020 aarch64 GNU/Linux " my rockpi4a runs at 2Ghz.
To radxa overclocking is possible so that 2GHz is not a real surprise ...
Though checked " armbianEnv.txt " but did not find any "overlays" option present overlocking this board, neither any other files in /boot ( or /boot/dtb/rockchip/overlay ).
However building a custom image ( kernel 5.10 ) it is running at 1,8GHz again, how can I set this to 2GHz ?
( as a side note - tehre is no need to enable panfrost BTW as I run this as a headless server )
Thanks
-
tried my rockpi4a , similar results ( bad ) as H5 and H6.
Once switched to legacy 4.4 kernel, things rock and faster results again.
really wonder what is causing this: patch, kernel realtek driver, both / something else : lost?!
-
well I decided to bring in the r4s and flashed latest dev image ( 5.10.9-rockchip64 ).
Long story short .. using westwood both ways seem to be meeting my needs, using bbr to site is also fine - but from site to home bbr is rubbish
below results:
- fresh dev image built r4s , connected to " enp1s0 " and results below
- without changing anything:
iperf3 -4 -c somewhere.dynu.net -t 300 -b 0 -P 1[ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 5.10 MBytes 42.8 Mbits/sec 501 391 KBytes [ 5] 1.00-2.00 sec 3.75 MBytes 31.5 Mbits/sec 0 268 KBytes [ 5] 2.00-3.00 sec 3.75 MBytes 31.5 Mbits/sec 0 287 KBytes [ 5] 3.00-4.00 sec 3.75 MBytes 31.5 Mbits/sec 0 304 KBytes [ 5] 4.00-5.00 sec 3.75 MBytes 31.5 Mbits/sec 0 320 KBytes [ 5] 5.00-6.00 sec 3.75 MBytes 31.4 Mbits/sec 0 334 KBytes [ 5] 6.00-7.00 sec 2.50 MBytes 21.0 Mbits/sec 0 347 KBytes [ 5] 7.00-8.00 sec 3.75 MBytes 31.5 Mbits/sec 0 361 KBytes [ 5] 8.00-9.00 sec 2.50 MBytes 21.0 Mbits/sec 0 372 KBytes [ 5] 9.00-10.00 sec 3.75 MBytes 31.5 Mbits/sec 0 384 KBytes [ 5] 10.00-11.00 sec 2.50 MBytes 21.0 Mbits/sec 0 395 KBytes [ 5] 11.00-12.00 sec 3.75 MBytes 31.5 Mbits/sec 0 407 KBytes [ 5] 12.00-13.00 sec 3.75 MBytes 31.5 Mbits/sec 9 212 KBytes [ 5] 13.00-14.00 sec 2.50 MBytes 21.0 Mbits/sec 0 234 KBytes [ 5] 14.00-15.00 sec 3.75 MBytes 31.5 Mbits/sec 0 253 KBytes [ 5] 15.00-16.00 sec 3.75 MBytes 31.5 Mbits/sec 0 271 KBytes [ 5] 16.00-17.00 sec 2.50 MBytes 21.0 Mbits/sec 0 286 KBytes [ 5] 17.00-18.00 sec 3.75 MBytes 31.5 Mbits/sec 0 302 KBytes [ 5] 18.00-19.00 sec 2.50 MBytes 21.0 Mbits/sec 0 316 KBytes [ 5] 19.00-20.00 sec 3.75 MBytes 31.5 Mbits/sec 0 331 KBytes [ 5] 20.00-21.00 sec 2.50 MBytes 21.0 Mbits/sec 0 345 KBytes [ 5] 21.00-22.00 sec 3.75 MBytes 31.5 Mbits/sec 5 182 KBytes [ 5] 22.00-23.00 sec 3.75 MBytes 31.5 Mbits/sec 0 205 KBytes [ 5] 23.00-24.00 sec 2.50 MBytes 21.0 Mbits/sec 0 227 KBytes [ 5] 24.00-25.00 sec 3.75 MBytes 31.5 Mbits/sec 0 247 KBytes [ 5] 25.00-26.00 sec 3.75 MBytes 31.5 Mbits/sec 0 265 KBytes [ 5] 26.00-27.00 sec 2.50 MBytes 21.0 Mbits/sec 0 282 KBytes [ 5] 27.00-28.00 sec 3.75 MBytes 31.5 Mbits/sec 0 298 KBytes [ 5] 28.00-29.00 sec 3.75 MBytes 31.5 Mbits/sec 0 313 KBytes [ 5] 29.00-30.00 sec 2.50 MBytes 21.0 Mbits/sec 0 328 KBytes [ 5] 30.00-31.00 sec 3.75 MBytes 31.5 Mbits/sec 0 342 KBytes [ 5] 31.00-32.00 sec 3.75 MBytes 31.5 Mbits/sec 0 360 KBytes [ 5] 32.00-33.00 sec 5.00 MBytes 41.9 Mbits/sec 0 379 KBytes [ 5] 33.00-34.00 sec 5.00 MBytes 41.9 Mbits/sec 0 395 KBytes [ 5] 34.00-35.00 sec 5.00 MBytes 41.9 Mbits/sec 0 413 KBytes [ 5] 35.00-36.00 sec 5.00 MBytes 41.9 Mbits/sec 0 429 KBytes
- minimal kernel tuning:net.core.default_qdisc = fq1
net.ipv4.tcp_congestion_control = bbr
iperf3 -4 -c somewhere.go.ro -t 300 -b 0 -P 1[ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 6.50 MBytes 54.6 Mbits/sec 588 623 KBytes [ 5] 1.00-2.00 sec 5.00 MBytes 41.9 Mbits/sec 116 637 KBytes [ 5] 2.00-3.00 sec 5.00 MBytes 41.9 Mbits/sec 71 645 KBytes [ 5] 3.00-4.00 sec 5.00 MBytes 41.9 Mbits/sec 53 591 KBytes [ 5] 4.00-5.00 sec 5.00 MBytes 41.9 Mbits/sec 73 591 KBytes [ 5] 5.00-6.00 sec 3.75 MBytes 31.5 Mbits/sec 63 648 KBytes [ 5] 6.00-7.00 sec 5.00 MBytes 41.9 Mbits/sec 171 645 KBytes [ 5] 7.00-8.00 sec 5.00 MBytes 42.0 Mbits/sec 138 692 KBytes [ 5] 8.00-9.00 sec 5.00 MBytes 41.9 Mbits/sec 122 640 KBytes [ 5] 9.00-10.00 sec 3.75 MBytes 31.4 Mbits/sec 221 645 KBytes [ 5] 10.00-11.00 sec 3.75 MBytes 31.5 Mbits/sec 122 541 KBytes [ 5] 11.00-12.00 sec 5.00 MBytes 41.9 Mbits/sec 1 591 KBytes [ 5] 12.00-13.00 sec 3.75 MBytes 31.5 Mbits/sec 64 514 KBytes [ 5] 13.00-14.00 sec 5.00 MBytes 41.9 Mbits/sec 102 648 KBytes [ 5] 14.00-15.00 sec 5.00 MBytes 41.9 Mbits/sec 61 645 KBytes [ 5] 15.00-16.00 sec 5.00 MBytes 41.9 Mbits/sec 38 596 KBytes [ 5] 16.00-17.00 sec 5.00 MBytes 41.9 Mbits/sec 63 593 KBytes [ 5] 17.00-18.00 sec 5.00 MBytes 41.9 Mbits/sec 49 593 KBytes [ 5] 18.00-19.00 sec 5.00 MBytes 41.9 Mbits/sec 40 593 KBytes [ 5] 19.00-20.00 sec 5.00 MBytes 41.9 Mbits/sec 74 632 KBytes [ 5] 20.00-21.00 sec 2.50 MBytes 21.0 Mbits/sec 147 623 KBytes [ 5] 21.00-22.00 sec 6.25 MBytes 52.5 Mbits/sec 48 670 KBytes [ 5] 22.00-23.00 sec 3.75 MBytes 31.5 Mbits/sec 77 656 KBytes [ 5] 23.00-24.00 sec 5.00 MBytes 41.9 Mbits/sec 64 643 KBytes [ 5] 24.00-25.00 sec 5.00 MBytes 42.0 Mbits/sec 115 645 KBytes [ 5] 25.00-26.00 sec 5.00 MBytes 41.9 Mbits/sec 70 604 KBytes [ 5] 26.00-27.00 sec 5.00 MBytes 41.9 Mbits/sec 113 442 KBytes [ 5] 27.00-28.00 sec 5.00 MBytes 41.9 Mbits/sec 40 602 KBytes [ 5] 28.00-29.00 sec 5.00 MBytes 41.9 Mbits/sec 78 662 KBytes [ 5] 29.00-30.00 sec 5.00 MBytes 41.9 Mbits/sec 42 684 KBytes [ 5] 30.00-31.00 sec 3.75 MBytes 31.5 Mbits/sec 427 5.47 KBytes [ 5] 31.00-32.00 sec 2.50 MBytes 21.0 Mbits/sec 160 689 KBytes [ 5] 32.00-33.00 sec 5.00 MBytes 41.9 Mbits/sec 222 405 KBytes [ 5] 33.00-34.00 sec 5.00 MBytes 42.0 Mbits/sec 48 656 KBytes [ 5] 34.00-35.00 sec 5.00 MBytes 41.9 Mbits/sec 88 684 KBytes [ 5] 35.00-36.00 sec 5.00 MBytes 42.0 Mbits/sec 238 436 KBytes
now other way round site to home:
- orangepioneplus ( kernel 5.10.4 )net.core.default_qdisc = fq
net.ipv4.tcp_congestion_control = bbriperf3 -4 -c local.dynu.net -t 300 -b 0 -P 1
[ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 1.96 MBytes 16.4 Mbits/sec 0 120 KBytes [ 5] 1.00-2.00 sec 503 KBytes 4.12 Mbits/sec 0 107 KBytes [ 5] 2.00-3.00 sec 1006 KBytes 8.25 Mbits/sec 0 107 KBytes [ 5] 3.00-4.00 sec 503 KBytes 4.12 Mbits/sec 0 101 KBytes [ 5] 4.00-5.00 sec 1006 KBytes 8.24 Mbits/sec 0 98.4 KBytes [ 5] 5.00-6.00 sec 1006 KBytes 8.25 Mbits/sec 0 101 KBytes [ 5] 6.00-7.00 sec 503 KBytes 4.12 Mbits/sec 0 104 KBytes [ 5] 7.00-8.00 sec 1006 KBytes 8.25 Mbits/sec 0 101 KBytes [ 5] 8.00-9.00 sec 503 KBytes 4.12 Mbits/sec 0 98.4 KBytes [ 5] 9.00-10.00 sec 1006 KBytes 8.25 Mbits/sec 0 104 KBytes [ 5] 10.00-11.00 sec 503 KBytes 4.12 Mbits/sec 0ipe 98.4 KBytes [ 5] 11.00-12.00 sec 1006 KBytes 8.25 Mbits/sec 0 104 KBytes [ 5] 12.00-13.00 sec 1006 KBytes 8.25 Mbits/sec 0 104 KBytes [ 5] 13.00-14.00 sec 503 KBytes 4.12 Mbits/sec 0 98.4 KBytes [ 5] 14.00-15.00 sec 503 KBytes 4.12 Mbits/sec 0 5.47 KBytes [ 5] 15.00-16.00 sec 1006 KBytes 8.25 Mbits/sec 0 109 KBytes [ 5] 16.00-17.00 sec 503 KBytes 4.12 Mbits/sec 0 107 KBytes [ 5] 17.00-18.00 sec 1006 KBytes 8.25 Mbits/sec 0 104 KBytes [ 5] 18.00-19.00 sec 503 KBytes 4.12 Mbits/sec 0 98.4 KBytes [ 5] 19.00-20.00 sec 1006 KBytes 8.25 Mbits/sec 0 104 KBytes [ 5] 20.00-21.00 sec 1006 KBytes 8.25 Mbits/sec 0 109 KBytes [ 5] 21.00-22.00 sec 503 KBytes 4.12 Mbits/sec 0 109 KBytes [ 5] 22.00-23.00 sec 1006 KBytes 8.25 Mbits/sec 0 107 KBytes [ 5] 23.00-24.00 sec 503 KBytes 4.12 Mbits/sec 0 104 KBytes [ 5] 24.00-25.00 sec 1006 KBytes 8.25 Mbits/sec 0 101 KBytes [ 5] 25.00-26.00 sec 1006 KBytes 8.25 Mbits/sec 0 104 KBytes [ 5] 26.00-27.00 sec 503 KBytes 4.12 Mbits/sec 0 107 KBytes [ 5] 27.00-28.00 sec 1006 KBytes 8.25 Mbits/sec 0 112 KBytes [ 5] 28.00-29.00 sec 503 KBytes 4.12 Mbits/sec 0 104 KBytes [ 5] 29.00-30.00 sec 1006 KBytes 8.25 Mbits/sec 0 101 KBytes [ 5] 30.00-31.00 sec 503 KBytes 4.12 Mbits/sec 0 101 KBytes [ 5] 31.00-32.00 sec 1006 KBytes 8.25 Mbits/sec 0 109 KBytes [ 5] 32.00-33.00 sec 503 KBytes 4.12 Mbits/sec 0 98.4 KBytes [ 5] 33.00-34.00 sec 1006 KBytes 8.25 Mbits/sec 0 112 KBytes [ 5] 34.00-35.00 sec 1006 KBytes 8.24 Mbits/sec 0 107 KBytes [ 5] 35.00-36.00 sec 503 KBytes 4.12 Mbits/sec 0 109 KBytesnet.core.default_qdisc = fq
net.ipv4.tcp_congestion_control = westwood
iperf3 -4 -c local.dynu.net -t 300 -b 0 -P 1[ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 28.0 MBytes 235 Mbits/sec 0 6.29 MBytes [ 5] 1.00-2.00 sec 17.5 MBytes 147 Mbits/sec 1672 1.06 MBytes [ 5] 2.00-3.00 sec 13.8 MBytes 115 Mbits/sec 124 937 KBytes [ 5] 3.00-4.00 sec 18.8 MBytes 157 Mbits/sec 0 962 KBytes [ 5] 4.00-5.00 sec 17.5 MBytes 147 Mbits/sec 0 987 KBytes [ 5] 5.00-6.00 sec 20.0 MBytes 168 Mbits/sec 0 1014 KBytes [ 5] 6.00-7.00 sec 17.5 MBytes 147 Mbits/sec 71 518 KBytes [ 5] 7.00-8.00 sec 18.8 MBytes 157 Mbits/sec 0 956 KBytes [ 5] 8.00-9.00 sec 17.5 MBytes 147 Mbits/sec 0 983 KBytes [ 5] 9.00-10.00 sec 17.5 MBytes 147 Mbits/sec 40 916 KBytes [ 5] 10.00-11.00 sec 16.2 MBytes 136 Mbits/sec 0 941 KBytes [ 5] 11.00-12.00 sec 18.8 MBytes 157 Mbits/sec 0 967 KBytes [ 5] 12.00-13.00 sec 18.8 MBytes 157 Mbits/sec 0 994 KBytes [ 5] 13.00-14.00 sec 16.2 MBytes 136 Mbits/sec 54 921 KBytes [ 5] 14.00-15.00 sec 17.5 MBytes 147 Mbits/sec 0 947 KBytes [ 5] 15.00-16.00 sec 18.8 MBytes 157 Mbits/sec 0 973 KBytes [ 5] 16.00-17.00 sec 16.2 MBytes 136 Mbits/sec 36 897 KBytes [ 5] 17.00-18.00 sec 17.5 MBytes 147 Mbits/sec 0 923 KBytes [ 5] 18.00-19.00 sec 17.5 MBytes 147 Mbits/sec 0 950 KBytes [ 5] 19.00-20.00 sec 18.8 MBytes 157 Mbits/sec 0 975 KBytes [ 5] 20.00-21.00 sec 18.8 MBytes 157 Mbits/sec 0 1002 KBytes [ 5] 21.00-22.00 sec 16.2 MBytes 136 Mbits/sec 71 927 KBytes [ 5] 22.00-23.00 sec 17.5 MBytes 147 Mbits/sec 0 952 KBytes [ 5] 23.00-24.00 sec 18.8 MBytes 157 Mbits/sec 0 979 KBytes [ 5] 24.00-25.00 sec 16.2 MBytes 136 Mbits/sec 43 906 KBytes [ 5] 25.00-26.00 sec 17.5 MBytes 147 Mbits/sec 0 932 KBytes [ 5] 26.00-27.00 sec 18.8 MBytes 157 Mbits/sec 0 958 KBytes [ 5] 27.00-28.00 sec 17.5 MBytes 147 Mbits/sec 0 984 KBytes [ 5] 28.00-29.00 sec 17.5 MBytes 147 Mbits/sec 53 913 KBytes [ 5] 29.00-30.00 sec 17.5 MBytes 147 Mbits/sec 0 939 KBytes [ 5] 30.00-31.00 sec 17.5 MBytes 147 Mbits/sec 0 965 KBytes [ 5] 31.00-32.00 sec 17.5 MBytes 147 Mbits/sec 0 990 KBytes [ 5] 32.00-33.00 sec 17.5 MBytes 147 Mbits/sec 68 905 KBytes [ 5] 33.00-34.00 sec 17.5 MBytes 147 Mbits/sec 0 931 KBytes [ 5] 34.00-35.00 sec 18.8 MBytes 157 Mbits/sec 0 957 KBytes [ 5] 35.00-36.00 sec 17.5 MBytes 147 Mbits/sec 0 983 KBytesonce more
now local to site ( r4s to site )
net.core.default_qdisc = fq
net.ipv4.tcp_congestion_control = westwood[ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 6.46 MBytes 54.1 Mbits/sec 430 58.8 KBytes [ 5] 1.00-2.00 sec 1.25 MBytes 10.5 Mbits/sec 0 82.0 KBytes [ 5] 2.00-3.00 sec 1.25 MBytes 10.5 Mbits/sec 0 107 KBytes [ 5] 3.00-4.00 sec 2.50 MBytes 21.0 Mbits/sec 0 131 KBytes [ 5] 4.00-5.00 sec 2.50 MBytes 21.0 Mbits/sec 0 154 KBytes [ 5] 5.00-6.00 sec 2.50 MBytes 21.0 Mbits/sec 0 179 KBytes [ 5] 6.00-7.00 sec 2.50 MBytes 21.0 Mbits/sec 0 202 KBytes [ 5] 7.00-8.00 sec 3.75 MBytes 31.5 Mbits/sec 0 227 KBytes [ 5] 8.00-9.00 sec 5.00 MBytes 42.0 Mbits/sec 0 250 KBytes [ 5] 9.00-10.00 sec 3.75 MBytes 31.5 Mbits/sec 0 275 KBytes [ 5] 10.00-11.00 sec 5.00 MBytes 41.9 Mbits/sec 0 297 KBytes [ 5] 11.00-12.00 sec 5.00 MBytes 41.9 Mbits/sec 0 319 KBytes [ 5] 12.00-13.00 sec 5.00 MBytes 41.9 Mbits/sec 0 339 KBytes [ 5] 13.00-14.00 sec 3.75 MBytes 31.5 Mbits/sec 0 358 KBytes [ 5] 14.00-15.00 sec 5.00 MBytes 41.9 Mbits/sec 0 376 KBytes [ 5] 15.00-16.00 sec 5.00 MBytes 41.9 Mbits/sec 0 394 KBytes [ 5] 16.00-17.00 sec 5.00 MBytes 41.9 Mbits/sec 0 410 KBytes [ 5] 17.00-18.00 sec 5.00 MBytes 41.9 Mbits/sec 0 427 KBytes [ 5] 18.00-19.00 sec 5.00 MBytes 41.9 Mbits/sec 0 442 KBytes [ 5] 19.00-20.00 sec 5.00 MBytes 41.9 Mbits/sec 0 457 KBytes [ 5] 20.00-21.00 sec 3.75 MBytes 31.5 Mbits/sec 25 235 KBytes [ 5] 21.00-22.00 sec 5.00 MBytes 41.9 Mbits/sec 0 260 KBytes [ 5] 22.00-23.00 sec 3.75 MBytes 31.5 Mbits/sec 0 283 KBytes [ 5] 23.00-24.00 sec 5.00 MBytes 41.9 Mbits/sec 0 306 KBytes [ 5] 24.00-25.00 sec 5.00 MBytes 41.9 Mbits/sec 0 328 KBytes [ 5] 25.00-26.00 sec 5.00 MBytes 41.9 Mbits/sec 0 347 KBytes [ 5] 26.00-27.00 sec 5.00 MBytes 41.9 Mbits/sec 0 366 KBytes [ 5] 27.00-28.00 sec 5.00 MBytes 41.9 Mbits/sec 0 384 KBytes [ 5] 28.00-29.00 sec 3.75 MBytes 31.4 Mbits/sec 0 401 KBytes [ 5] 29.00-30.00 sec 5.00 MBytes 41.9 Mbits/sec 0 417 KBytes [ 5] 30.00-31.00 sec 5.00 MBytes 41.9 Mbits/sec 0 433 KBytes [ 5] 31.00-32.00 sec 5.00 MBytes 41.9 Mbits/sec 0 448 KBytes [ 5] 32.00-33.00 sec 5.00 MBytes 41.9 Mbits/sec 0 463 KBytes [ 5] 33.00-34.00 sec 5.00 MBytes 41.9 Mbits/sec 29 243 KBytes [ 5] 34.00-35.00 sec 3.75 MBytes 31.5 Mbits/sec 0 268 KBytes [ 5] 35.00-36.00 sec 5.00 MBytes 41.9 Mbits/sec 0 291 KBytesthis is directly over Internet, thus no VPN yet.
I really wonder what is going on as using H5/H6 allwinners give horrific results.
why uploading on the allwinner platform is limited ( though 150Mbit is fine with me )
CONFIG_USB_HIDDEV option for nanopi-r4s kernel (possibly others)
in Framework and userspace feature requests
Posted
Hello,
I would like to propose a change to the default kernel config for the r4s.
Currently in .config
#
# USB HID support
#
CONFIG_USB_HID=y
CONFIG_HID_PID=y
CONFIG_USB_HIDDEV=y
This should be altered to
CONFIG_USB_HID=m
This change has been requested previously for other boards: here and is also explained properly.
To summarise : the change would allow those using APCUPSD to communicate with their APC UPS device.
TiA!