Hi there!
First of all, I apologize for opening an Issue when it's really a question - I normally never do that, but then again, I have at least one small improvement to the project to describe at the end.
Second:
I have an IoT device that I'd like to analyze and see what traffic it generates to try and reverse-engineer some local control over it. The device seems to be communicating almost exclusively via websockets. I've used wedgeberry in multiple configurations to try and capture the traffic and see any websocket activity but failed to do so.
When configuring wedgeberry with mitmweb on ports 80 and 443, I see some "ping" like HTTP request popping up but the device itself never goes online - I assume some of the connectivity breaks here.
Next, I configured wedgeberry to use my remote burpsuite as a proxy, in this case, my remote burpsuite doesn't get any traffic. I doubled checked this config and can see traffic from my phone when connected to wedge-ap.
Just for completeness, when the connection is set to "Direct", the device goes online as intended.
Hence I'm curious if someone might have an idea on how to best analyze websockets and/or why my device under test can't go online with mitmweb enabled on ports 80 and 443?
As for the enhancement: I think there's a small error in the scripts - tcpdump isn't installed when capturing raw traffic.
Thanks a ton! Great project!
Hi there!
First of all, I apologize for opening an Issue when it's really a question - I normally never do that, but then again, I have at least one small improvement to the project to describe at the end.
Second:
I have an IoT device that I'd like to analyze and see what traffic it generates to try and reverse-engineer some local control over it. The device seems to be communicating almost exclusively via websockets. I've used wedgeberry in multiple configurations to try and capture the traffic and see any websocket activity but failed to do so.
When configuring wedgeberry with mitmweb on ports 80 and 443, I see some "ping" like HTTP request popping up but the device itself never goes online - I assume some of the connectivity breaks here.
Next, I configured wedgeberry to use my remote burpsuite as a proxy, in this case, my remote burpsuite doesn't get any traffic. I doubled checked this config and can see traffic from my phone when connected to wedge-ap.
Just for completeness, when the connection is set to "Direct", the device goes online as intended.
Hence I'm curious if someone might have an idea on how to best analyze websockets and/or why my device under test can't go online with mitmweb enabled on ports 80 and 443?
As for the enhancement: I think there's a small error in the scripts -
tcpdumpisn't installed when capturing raw traffic.Thanks a ton! Great project!