The flashing yellow light is probably due to the massive collisions caused because you have a duplex mismatch.
See edit As I said in my previous post, regardless if I use full or half duplex the issue remains the same. Yellow blinking light with working network access.
This is related how WD sets the LED light and not wether or not the device has an active connection.
The issue has shifted from my first post and I’m now only trying to fix the yellow light:
My switch, probably because it’s a green one, causes auto-negotiation to fail (not enough power to port as suspected earlier)
Turning off auto-negotiation via /etc/network/interfaces results the device connecting correctly to the network and working
at the same time this setting causes the LED light to continously keep flashing yellow even though there is network access
Anyways, while writing this, I managed to fix it with a stuipid 50s delay before issuing the ethtool command by doing this
# Configure Loopback
iface lo inet loopback
iface eth0 inet dhcp
/sbin/ethtool -s eth0 speed 100 duplex half autoneg off;
Obviously ethtool.sh needs to be executable so chmod +x /shares/ethtool.sh for anyone reading this after a while, also if your network is capable of 1gbit you should use speed 1000 and not speed 100
The pause (sleep 50) is simply to make sure that all of WDs init scripts for lights/whatelse have finished running and are working properly. While this causes a slightly longer zero-to-fully-working boot I’m gonna take it since its working for now.
Edit: TonyPh12345 was right of course, half duplex, while you’ll be able to connect with full it causes a whole lot of colissions and severly degrades your connection. Thx Tony