2018-01-13 16:42:43 +0000 | commented answer | Why cant I see SSDP protocol packets when using Wifi Monitor mode on Ubuntu I cheated and just turned off encryption. I wouldn't recommend it as an approach but I live in the countryside :-) |
2018-01-13 16:40:46 +0000 | marked best answer | Why cant I see SSDP protocol packets when using Wifi Monitor mode on Ubuntu I'm looking to snoop on an SSDP conversation between two devices on Wifi. I've set up a WireShark instance on a Ubuntu machine and configured a "Monitor" device using these instructions: https://sandilands.info/sgordon/captu... However when I now capture via the mon0 device I only see 802.11 protocol packets and can't see any SSDP packets I had tried just ticking the the "monitor" box on the interfaces list but it would not stay "ticked". The output of iw dev is: Is there away to capture a SSDP conversation in Monitor mode? |
2018-01-13 14:26:05 +0000 | edited question | Why cant I see SSDP protocol packets when using Wifi Monitor mode on Ubuntu Why cant I see SSDP protocol packets when using Wifi Monitor mode on Ubuntu I'm looking to snoop on an SSDP conversation |
2018-01-13 14:25:26 +0000 | edited question | Why cant I see SSDP protocol packets when using Wifi Monitor mode on Ubuntu Why cant I see SSDP protocol packets when using Wifi Monitor mode on Ubuntu I'm looking to snoop on an SSDP conversation |
2018-01-13 14:24:20 +0000 | asked a question | Why cant I see SSDP protocol packets when using Wifi Monitor mode on Ubuntu Why cant I see SSDP protocol packets when using Wifi Monitor mode on Ubuntu I'm looking to snoop on an SSDP conversation |
2018-01-03 15:27:08 +0000 | commented answer | why cant I see both sides of a SSDP M-SEARCH interaction? Thanks Graham |
2018-01-03 15:26:48 +0000 | marked best answer | why cant I see both sides of a SSDP M-SEARCH interaction? I'm trying to understand the interaction between an SSDP M-Search initiator (Amazon Echo) and an ESP8266 based device emulating a Wemo switch. I can see the the initiation message from the Echo in the WireShark packet log but not the response from the device although I am certain it is sent because the Echo acts on the response. I know the IP and mac addr of both the devices. I should say that this is the first time I've used WireShark. What am I doing wrong? |
2018-01-03 15:26:48 +0000 | received badge | ● Scholar (source) |
2018-01-03 10:15:20 +0000 | commented question | why cant I see both sides of a SSDP M-SEARCH interaction? Hi Graham, I'm using a PC running WireShark (@192.168.1.100) on the same private subnet as both devices (.32 and .72) De |
2018-01-03 10:14:51 +0000 | answered a question | why cant I see both sides of a SSDP M-SEARCH interaction? Hi Graham, I'm using a PC running WireShark (@192.168.1.100) on the same private subnet as both devices (.32 and .72) De |
2018-01-03 10:14:51 +0000 | received badge | ● Rapid Responder (source) |
2018-01-02 18:17:29 +0000 | received badge | ● Editor (source) |
2018-01-02 18:17:29 +0000 | edited question | why cant I see both sides of a SSDP M-SEARCH interaction? why cant I see both sides of a SSDP M-SEARCH interaction? I'm trying to understand the interaction between an SSDP M-Sea |
2018-01-02 18:15:43 +0000 | asked a question | why cant I see both sides of a SSDP M-SEARCH interaction? why cant I see both sides of a SSDP M-SEARCH interaction? I'm trying to understand the interaction between an SSDP M-Sea |