I don't know where that "study" comes from. I am using the same name for both just because it's convenient for users to have the same SSID and password. The name for both is "mgn".
The strange thing is that this has never been an issue before. The Pi4 has always been on 5Ghz, the Pi1 on 2.4. I've never had any problem connecting devices on different bands. As long as I have been doing networking it has always worked as you described. I would very much like to understand what's going on.
Here's a demo. In the first ping the Pi4 (raspsky) is on 2.4. In the second ping I changed it back to 5.
The strange thing is that this has never been an issue before. The Pi4 has always been on 5Ghz, the Pi1 on 2.4. I've never had any problem connecting devices on different bands. As long as I have been doing networking it has always worked as you described. I would very much like to understand what's going on.
Here's a demo. In the first ping the Pi4 (raspsky) is on 2.4. In the second ping I changed it back to 5.
Code:
pi@raspsky:~/webcam $ ping -c 3 rasp2PING rasp2 (192.168.0.62) 56(84) bytes of data.64 bytes from rasp2 (192.168.0.62): icmp_seq=1 ttl=64 time=5.15 ms64 bytes from rasp2 (192.168.0.62): icmp_seq=2 ttl=64 time=7.83 ms64 bytes from rasp2 (192.168.0.62): icmp_seq=3 ttl=64 time=2.66 ms--- rasp2 ping statistics ---3 packets transmitted, 3 received, 0% packet loss, time 5msrtt min/avg/max/mdev = 2.655/5.214/7.833/2.114 mspi@raspsky:~/webcam $ ping -c 3 rasp2PING rasp2 (192.168.0.62) 56(84) bytes of data.From raspsky (192.168.0.65) icmp_seq=1 Destination Host UnreachableFrom raspsky (192.168.0.65) icmp_seq=2 Destination Host UnreachableFrom raspsky (192.168.0.65) icmp_seq=3 Destination Host Unreachable-- rasp2 ping statistics ---3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 50mspipe 3Statistics: Posted by Ratsima — Mon Jun 16, 2025 7:05 am