Zimablade / Zimaos/Casaos network speed

Hardware ZimaBlade
,
1

MY ZimaBlade only can work on 100 Mbps, whatever I try, it will only work on this speed. It has it since day one, but now I need some more speed from it and I would like to solve it.

All possible settings on the switch I already tried. It is not the cables. Forcing the ZimaBlade to 1 Gbps makes the connection fail.

Anybody an idea how to solve this?

2

also mine says 1GBit Ethernet if I Benchmark my Samba Share I get 5-6 MB / sec …. its hopelessy slow

3

Hi PaulM,

If the ZimaBlade is only negotiating at 100 Mbps and forcing 1 Gbps makes the connection fail, I would first confirm what the NIC is actually reporting from ZimaOS/CasaOS, not just from the switch UI.

Could you please run:

ip link

Then identify the Ethernet interface name, usually something like eth0, enp1s0, etc.

Then run:

ethtool eth0

Replace eth0 with your actual interface name.

The important lines are:

Speed:
Duplex:
Auto-negotiation:
Link detected:

If it shows Speed: 100Mb/s, then the issue is at the physical/link negotiation level: cable, switch port, adapter/NIC negotiation, or possibly a hardware issue.

Also, do not force 1 Gbps unless both sides are happy with it. Gigabit Ethernet normally needs auto-negotiation to work properly. If forcing 1 Gbps kills the link, that usually points to a negotiation or physical layer problem.

For Antonius, 5-6 MB/s over Samba is a different issue if your link really shows 1 Gbit. That would need separate checking, because slow SMB speed can be caused by disk speed, Wi-Fi, the client device, SMB settings, Docker volume path, or the drive mount location. The first step there is also to confirm the real negotiated link speed with ethtool.

4

Yes was my bad :slight_smile: didnt plug in my netwotk cable and used wifi instead

5

Speed: 100Mb/s

Duplex: Full

Auto-negotiation: on

Link detected: yes

How can I check if the hardware failure is at the ZimaBlade,I checked everything else.

6

Hi PaulM,

If ethtool shows:

Speed: 100Mb/sDuplex: FullAuto-negotiation: onLink detected: yes

then ZimaOS is only negotiating a 100 Mbps physical link.

Before calling it a ZimaBlade hardware fault, I would isolate it with a few simple checks:

  1. Try a known-good Cat5e/Cat6 cable directly into the router/switch, not through a wall socket or patch panel.
  2. Try a different switch/router port.
  3. Check the advertised link modes from the ZimaBlade:
ethtool eth0

Replace eth0 with your real interface name.

Look for these lines:

Supported link modes:Advertised link modes:Link partner advertised link modes:

If the ZimaBlade supports/advertises 1000baseT/Full, but the link partner only negotiates 100baseT/Full, it is usually cable, port, or link partner related.

  1. Also check the NIC detected by the system:
lspci | grep -i ethernet

If possible, test the ZimaBlade with another known gigabit switch and another short cable. If it still only negotiates 100 Mbps across multiple known-good cables and ports, then it starts to point more toward the ZimaBlade Ethernet port or hardware side.

I would not force 1 Gbps. If forcing 1 Gbps drops the link, that usually confirms the physical link cannot establish gigabit cleanly.