I have been using my Pi3 happily for years now. Then I recently decided to update some projects to Pi3b+ boards in search of that small CPU power advantage, but I am finding a very annoying problem regarding ethernet connection. I am using the same sd card on both the Pi3 and the Pi3b+.
I have already updated the Raspbian system to the latest stable versions of the firmware and kernel before coming here to ask for help, by doing:
So, the problem is as follows.
Code: Select all
sudo apt update && sudo apt full-upgrade -y
The network connection on my Pi systems is NOT managed by systemd, instead it's manually configured by me with this simple sequence of commands in a bash script I run whenever I need to access the board via ssh, etc. No X server or networking services are active. Just simple manual configuration like this:
It works perfectly well on the Pi3, and apparently it works too on the Pi3b+, but the problem is that I can't access the Pi3b+ via ssh after this. In fact, I can't even ping to it's IP address! Of course, I can ping and access the Pi3 after running the same exact sequence with no problems whatsoever. Only the Pi3b+ is giving me this problem.
Code: Select all
# Up with the ethernet and ssh! sudo ifconfig eth0 up sudo ip addr add 192.168.5.8/24 dev eth0 sudo ip route add default via 192.168.5.7 sudo /etc/init.d/dropbear start > /dev/null 2>&1
And now for the funny part: If I ping the PC from the Pi3b+, then I can ping the Pi3+ from the PC back!!!
That's crazy, I know. Never encountered anything like this before. It's as if pinging from the Pi3b+ would be activating something that does not need to be activated on a plain Pi3...
Any idea on what's going on here?
NOTE: I am using the vc4 plan kms overlay. I don't think it's related, but.. just in case.