Timeline for Clients cannot connect to each other on WLAN. No reply on ARP requests
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 8, 2024 at 16:03 | answer | added | StevenClapton | timeline score: 0 | |
| Apr 18, 2021 at 11:11 | comment | added | A.B | Ok I was curious on why would a NIC or driver get a special effect with ARP, but this led nowhere. | |
| Apr 18, 2021 at 11:05 | comment | added | Andreas Matthias |
@A.B ping -b is working if icmp_echo_ignore_broadcasts=0.
|
|
| Apr 17, 2021 at 17:38 | comment | added | A.B |
ARP starts with an Ethernet broadcast. Are other broadcasts affected? Like ping -b 192.168.1.255 (which doesn't require ARP) once you allow answering broadcasts (sysctl -w net.ipv4.icmp_echo_ignore_broadcasts=0) in peers . Also toggling ap_isolate like told in the answer might change behaviour (but answer talks about a non-existing bridge). multicast (and broadcast) can be handled differently than unicast sometimes in Wifi (related to shared group key etc.)
|
|
| Apr 17, 2021 at 17:27 | history | edited | Andreas Matthias | CC BY-SA 4.0 |
added 1041 characters in body
|
| Apr 17, 2021 at 5:00 | answer | added | Eduardo Trápani | timeline score: 0 | |
| Apr 17, 2021 at 2:17 | history | asked | Andreas Matthias | CC BY-SA 4.0 |