Hello:

I'm afraid that dropbear does not do blowfish.

~$ rsync -e "ssh -o compression=no -c blowfish" -a --stats /media/bckups root@192.168.1.3:/mnt/sda3
Unknown cipher type 'blowfish'
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(235) [sender=3.1.3]
~$ 

See: https://dropbear.nl/mirror/CHANGES

Unfortunately, I have not found the rsh package in the OpenWRT repository so that's a dead end.

Looking around for similar situations, I found this:

https://www.glidk.com/2021/12/22/benchm … ppy-router

It's a post by a chap using a small travel router with a lower spec than the WD-MBL:

Brand/Name		WD-MBL		GL-AR750
CPU:			PowePC 44x     Qualcomm Atheros
Model:			APM82181	QCA9531
CPU Cores:		1		1
CPU MHz:		800		650       <----- #
Flash Mb:		512		16
RAM MB:			256		128       <----- #
BogoMIPS:		1600		432.53    <----- # 

It would seem that he achieved speeds using just the rsync protocol and bypassing ssh.
I don't undertand how he's set this up and cannot find how to contact the guy.

The WD-MBL, save for the HDD/SD card difference, seems to be much heftier.
Could I be able to get at least his 10.0Mb/s?

Can you make any sense of what he's done there?

Thanks in advance.

A.

Hello:

---

---

Part of this problem had to do with the CAT5e cables I was using.
Found out when I used ethtool to check the on-board ethernet adapter on the NAS and saw it was reporting 100M:

root@OpenWrt:~# ethtool eth0
Settings for eth0:
--- snip ---
    Advertised auto-negotiation: Yes
    Advertised FEC modes: Not reported
    Speed: 100Mb/s    <-------------------------- #####
    Duplex: Full
--- snip ---
root@OpenWrt:~# 

With a set of new CAT5e cables and properly negotiating 1000Mb/s between my box and the NAS, I tested the link with iperf:

root@OpenWrt:~# iperf -s
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size:  128 KByte (default)
------------------------------------------------------------
[  4] local 192.168.1.3 port 5001 connected with 192.168.1.2 port 35408
[ ID] Interval       Transfer     Bandwidth
[  4]  0.0-10.0 sec   771 MBytes   645 Mbits/sec
root@OpenWrt:~# 

groucho@devuan:~$ iperf -c 192.168.1.3
------------------------------------------------------------
Client connecting to 192.168.1.3, TCP port 5001
TCP window size: 85.0 KByte (default)
------------------------------------------------------------
[  3] local 192.168.1.2 port 35408 connected with 192.168.1.3 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec   771 MBytes   646 Mbits/sec
pcl@devuan:~$ 

Good enough, I guess.

But I was expecting something like the 94Mb /s I get between the NAS and my netbook which has a 10/100 ethernet adapter.
ie: if with a 10/100 connection I can get 94% of 100M, I was expecting at least 85% from the box to NAS connection at 1000M - 850 Mbits /s instead of 645 Mbits /s.

I'm assuming it is proportional, it probably isn't.

I've just finished running the same rsync job that took over 18 hours (first time/empty destination) the last time I ran it ie: before switching all the patch cables for new CAT5e ones and as a result getting the iperf speeds reported above, 646 Mbits/sec

All through the job, my conky panel reported a speed of ~7.45MiB /s

    Incoming: 114KiB /s
    Outgoing: 7.46MiB /s

These were the NAS's CPU/Memory loads during the job:

PID   Owner  CPU   Mem    Process
 213  root    9%    0%    kswapd0
1904  root   67%    0%    Dropbear
1905  root    0%    7%    rsync  --server
1906  root   22%   13%    rsync  --server

My guess is that NAS's CPU is totally maxed out.
ie: just kswap 9% + dropbear 67% + rsync 22% =>>> 98%

dropbear is the SSH2 server/client included in OpenWRT installation image, only 82k.
Evidently, with this hardware* a 67% CPU load is rather expensive to run.

*Applied Micro APM82181 @800 MHz + 256 MB RAM

I don't really neeed encryption as it is all local traffic.
ie: going nowhere else but from a back-up drive inside my box to the NAS under my desk.

But I do need rsync.
I use ssh to login to the NAS, how do I disable encryption?

Have never used/heard of rsh, have to look it up.

Thank you very much for your input.

Best,

A.

Hello:

Probably with the same infamous Telefonica ADSL routers. 8^|

Great.
But I have no need for more than 4 ports at the moment.
Unless I get a very good price for one with more.

Thanks a lot for for your input.

Best,

A.

Hello:

My telco provided ADSL router config page says that LAN/WAN speed in both ports (my box and the NAS) is 100M/Full.

My box has an on-board 82566DM-2 Gigabit Network adapter.     
The WD My Book NAS has a Gigabit Ethernet port.

Seems the problem is the bloody router as everything goes through there.
No wonder.

Can't change the telco router. I'd lose my landline.

Any suggestions?

Thanks in advance.

Best,

A.

Hello:

You're welcome.

Obviously, the use you can give it depends on the hardware you run it on.
eg: I use a MyBook Live which has a SATA HD instead of firmware.

As this would be OT/non Devuan, feel free to contact me.

Best,

A.

Hello:

Originally I had it in /usr/local/bin.
As I could not get it to work unless I used ./, I moved it.
I did not want to get into fussing with PATH.
I still have to find where it is set ...  8^|

Hmm ...
I may have a thing for abusing cat ...
But I do know that is not a thing to do.

OK.
It works well as it is but I'll move it to its proper place later today.

Thanks for your input.

Best,

A.

Hello:

I put it in just in case the system path has some issue.
Belt and suspenders thing.

But that would not seem to be the problem because the script is found and the executables in it are run properly.

What is not being found is the script that calls closebook.sh unless I run it as ./shutdown.

I just realised that the /root folder is not in the system PATH variable:

root@OpenWrt:~# $PATH
-ash: /usr/sbin:/usr/bin:/sbin:/bin: not found
root@OpenWrt:~# 

This one:

root@OpenWrt:~# ls
shutdown
root@OpenWrt:~# 

Which you can see here:

root@OpenWrt:/# ls
bin         dev         lib         mnt         proc        # root #        srv         tmp         var
boot        etc         lost+found  overlay     rom         sbin        sys         usr         www
root@OpenWrt:/# 

No idea as to how to follow up.
Surely it is not a good idea to have the root folder in the path.

Thanks for your input.

Best,

A.

Hello:

Could be.
But the idea is to avoid building anything with/for OpenWRT as it would complicate eventual sysupgrades.

I found this:
https://forum.sailfishos.org/t/busybox- … sh/6808/11

Not really a big deal.
When I finally get this NAS figured out and running as I want, I won't be needing access all the time like I'm having to do now.
I'll mark this thread solved.

Thanks for your input.

A.

Hello:

Hmm ...
I don't have a user set up on this system.
Maybe that's the reason? Have not had time to set up sudo either yet.

Edit:

I keep forgetting that this is a small footprint OS for embedded systems, a very different type of Linux.
That means that I should look in the right place and not bug my fellow Dev1 members.

OpenWRT does not use bash but ash.

From: https://forum.openwrt.org/t/enable-bash-history/70815

and

ash is part of the firmware image and while I can install the bash package, it will not survive a system upgrade.

There seems to be a work-around, I'll have to investigate further.

Thanks a lot for your input.

Best,

A.

Hello:

Seems I'm the only one here scavenging on old hardware. 8^D

I'll mark this thread as solved.

I have managed to successfully install OpenWRT 21.02.2 to the WD-MBL and it is working, albeit with an expected issue: it seems that the APM821xx processor does not have a way to poweroff or even halt.

So while I'm installing a couple of missing utils I see if I can find a suitable work around, maybe with a script and a switch for when it needs to be moved or taken off-line for a few days.

Best,

A.