![]() In any case, I haven't found another way to send these broadcasts across different networks until your plugin existed, though I admit I'm not exactly fully familiar with OpnSense yet. The packet data themselves contain the same thing, even reference the same "device-discovery-protocol-version", so it's a little funny they do broadcasts differently. I agree, it's a bit strange but that's what is being done (and to be honest I've mostly just been testing the 2nd screen app so far, figured that'd be the simpler of the two). 5.2 Analysing a TCP Session using Wireshark. ![]() Their remote play application is the one that does a wide open 255.255.255.255 (I see it once from the OpnSense box). Start the capture, and generate some Web traffic again, then stop the capture. ![]() And just to be clear, the only SSDP traffic I see on either interface is just UPnP.Ģnd screen is the application that does a network broadcast I'd expect (so for example if the network is 192.168.1.0/24, the broadcast address is 192.168.1.255), and at the OpnSense box I see up to 5 of those when UDPR is off. I just did another capture to be sure of what I saw per application. There's actually 2 different broadcasts in play here on port 987 (it's different for 2nd screen vs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |