Timeline for Cannot connect Raspberry Pi
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 9, 2017 at 13:12 | vote | accept | Merve Sahin | ||
| Oct 6, 2017 at 19:22 | answer | added | 88weighed | timeline score: 0 | |
| Oct 5, 2017 at 0:56 | comment | added | hcheung | If your laptop is running on the network 10.42.0.xxx, and if you are connecting your RPI to the same router, then you shouldn't setup your RPI with an static IP of 192.168.1.2. You should pick an address within 10.42.0.xxx as the static IP for your RPI. | |
| Oct 4, 2017 at 21:28 | comment | added | MatsK | 10.42.0.1 is from the WiFi interface from your ifconfig output. You have to check your network configuration! | |
| Oct 4, 2017 at 21:21 | comment | added | Merve Sahin | @MatsK Since 10.42.0.1 is my own laptop, it just enters the terminal when I ssh to it. And the reason why I used ifconfig is to retrieve an ip for scanning with nmap. I don't know what to say about the docker, I changed its ip from localhost to 172.17.0.1, but I don't think it should have an effect on the broadcast | |
| Oct 4, 2017 at 20:58 | comment | added | MatsK | 1. You have a very strange broadcast on the docker interface and the bridge Bcast:0.0.0.0. 2. And you try to ssh to an IP address that isn't showing up in the output from ifconfig. 3. And what happens if you try to ssh to 10.42.0.1? | |
| Oct 4, 2017 at 20:41 | review | First posts | |||
| Oct 5, 2017 at 8:17 | |||||
| Oct 4, 2017 at 20:38 | history | asked | Merve Sahin | CC BY-SA 3.0 |