Currently, ROSbot Dave
has successfully booted up with full ssh, ping, arp, and ROS2 dynamic discovery Data Distribution System DDS working
- 12 out of 12 attempts
- since the change of 2.4GHz band WiFi access point
- from the xFinity Technicolor CGM4331COM XB7 router
- to my ancient DLink DIR-825 (last firmware released was 2013).
While I can say robot Carl and my DeskPi have had fitful connections with the xFinity router(s), neither has shown the “cannot remote in” (ssh) issue that ROSbot Dave exhibited, nor did I attempt distributed data messaging across the network when robot Carl was trying out ROS (1).
Carl has always been a Raspberry Pi 3B based GoPiGo3, but DeskPi was in fact using the exact Raspberry Pi 3B+ (plus) board that GoPiGo3 ROSbot Dave is running, except DeskPi has always run Raspbian/PiOS.
All these tests seem to point the finger at Ubuntu 20.04.2 on RaspberryPi 3B+ (or at least my particular Ubuntu configuration on this particular 3B+) having unreliable ICMP, ARP, or UDP handling during the DHCP link establishment phase with the xFinity router configured with a reserved IPv4 address for the board’s WiFi MAC address.
I don’t know enough to be able to diagnose this deeper, and having found a solution that enables me to progress with my ROS2 learning (through migrating the “Hands On ROS for Robotic Programming” exercises), I am leaving this mystery of the universe unsolved.
I do have a new WiFi 6 router on order, (that has ongoing firmware update support), to minimize the chance my network will become a crypto-bot or participant in the next distributed denial of service attack on internet democracy.