KeithL
Administrator 
Posts: 10,261
|
Post by KeithL on Jul 21, 2016 9:15:07 GMT -5
In many cases, NOT allowing Ping to work is considered a security feature. - By blocking Ping and other "nonessential services" they prevent most types of device scanning (by hackers). - There are also several "classic" denial-of-service attacks (like the "Smurf" attack) that rely on local broadcasts to "multiply" traffic. (This means that some equipment will identify any unidentified broadcast traffic as "a threat".) I think you'll find that, at least on some routers, even though Ping or UDP in general are disabled by default, you can change the security rule to allow them. After a bunch of research I have found out that MANY Wireless Routers and Wireless APs will NOT pass UDP broadcasts. I will investigate an alternate method for doing a XMC-1 scan for the next release. |
|
|
|
Post by number8 on Jul 21, 2016 12:03:25 GMT -5
Thanks Keith, but it is not a matter of blocking the ping traffic, that I'm aware of, just because I'm inside the network and there is no firewall in the path. since Chuck's program triggers an exception, it can't be of any help for the time being. I'll be back on site in a couple of hours and I will try to communicate with the XMC-1 with a TCP/UDP Packet sender. I'm convinced that the unit is working I just have to understand how it communicates.
|
|
|
|
Post by number8 on Jul 21, 2016 12:05:06 GMT -5
Thanks Chuck, I'll let you know my findings.
|
|
|
|
Post by Chuck Elliot on Jul 21, 2016 16:02:35 GMT -5
Thanks Chuck, I'll let you know my findings. We have 2 issues here: I have a handle on the wireless issue, see above. Use wired for now. The exception issue is the second. If you can get a response to the ping packet by other means, I'd really like to see what is send back by the XMC-1. It should be similar to: <?xml version="1.0"?> <emotivaTransponder> <model>XMC-1</model> <name>XMC-1</name> <control> <version>1.0</version> <controlPort>7002</controlPort> <notifyPort>7003</notifyPort> <infoPort>7004</infoPort> <setupPortTCP>7100</setupPortTCP> </control> </emotivaTransponder> |
|
|
|
Post by millst on Jul 21, 2016 17:05:09 GMT -5
Blocking ping doesn't prevent network scanning. At best, it slows it down. There are plenty of other ways to scan for hosts that don't involve ICMP. It's pretty awesome for annoying anyone trying to diagnose network problems, however.
-tm
|
|
|
|
Post by number8 on Jul 22, 2016 2:28:30 GMT -5
chuckI confirm that your tool is currently not supporting the Wifi interface. Using TCP/IP builder, a nice TCP/UDP tool, I've able to receive a response from the XMC-1, using either wired or wireless connection. the Emotiva iOS app crashes, and the Emotiva Android is not very stable either. XMC-1 does send back what is described in the spec ie, what you stated in the last post
|
|
|
|
Post by number8 on Jul 22, 2016 2:41:09 GMT -5
chuck : here is the capture exported from Wireshark XMC.txt (9.28 KB)
|
|
|
|
Post by Chuck Elliot on Jul 22, 2016 5:33:52 GMT -5
Let's go offline to PMs until we can find a solution and then post it back here. |
|
|
|
Post by ÈlTwo on Jul 22, 2016 7:19:17 GMT -5
Chuck,
You have all of my respect for everything you're doing here.
|
|
|
|
Post by geebo on Jul 22, 2016 7:21:10 GMT -5
Chuck, You have all of my respect for everything you're doing here. +1000 |
|
|
|
Post by Chuck Elliot on Jul 22, 2016 8:14:24 GMT -5
Thanks guys!
|
|
|
|
Post by Chuck Elliot on Aug 9, 2016 15:50:47 GMT -5
Number8 and I are close to having a fix for his exception problem. Looks like it has to do with the difference in number formats used in US and France.
US = 1.23
France = 1,23
|
|
|
|
Post by number8 on Aug 19, 2016 0:50:56 GMT -5
I confirm that the last version Chuck released to me solved the problem. Thanks very much to Chuck for the support
|
|
|
|
Post by Chuck Elliot on Aug 23, 2016 7:51:24 GMT -5
I will provide this release to anyone who wants it! No other changes except the # fix for countries that use "," as their decimal character.
Be aware that the next release of firmware will require me to release a new version of the program. I should be able to do this very quickly.
|
|
|
|
Post by Chuck Elliot on Oct 7, 2016 19:43:43 GMT -5
Version 4 of the XMC-1 firmware is out. Not only does this support the new HDMI board, it also has many changes to the UDP protocol that improve this apps connectivity and operation, Thanks Ray!
I will publish a new version of the app by the end of the weekend.
I've had about 80 downloads of the app. Could you drop a note here if you are using it?
|
|
|
|
Post by geebo on Oct 7, 2016 19:58:59 GMT -5
Version 4 of the XMC-1 firmware is out. Not only does this support the new HDMI board, it also has many changes to the UDP protocol that improve this apps connectivity and operation, Thanks Ray! I will publish a new version of the app by the end of the weekend. I've had about 80 downloads of the app. Could you drop a note here if you are using it? I was using it occasionaly before the HDMI upgrade and it stopped working afterwards. I assumed it was the firmware change. |
|
|
|
Post by Chuck Elliot on Oct 7, 2016 20:13:02 GMT -5
Version 4 of the XMC-1 firmware is out. Not only does this support the new HDMI board, it also has many changes to the UDP protocol that improve this apps connectivity and operation, Thanks Ray! I will publish a new version of the app by the end of the weekend. I've had about 80 downloads of the app. Could you drop a note here if you are using it? I was using it occasionaly before the HDMI upgrade and it stopped working afterwards. I assumed it was the firmware change. Yes, that's the problem! You should have gotten a Parser Error. The protocol has changed. Wait 'till Sunday and I'll have a new version. It is done, but I need to do a packaging script. |
|
|
|
Post by geebo on Oct 7, 2016 20:41:57 GMT -5
I was using it occasionaly before the HDMI upgrade and it stopped working afterwards. I assumed it was the firmware change. Yes, that's the problem! You should have gotten a Parser Error. The protocol has changed. Wait 'till Sunday and I'll have a new version. It is done, but I need to do a packaging script. Yep, parser error 144. I'll be watching for the new release. |
|
|
|
Post by Chuck Elliot on Oct 8, 2016 11:40:33 GMT -5
========================== Version 4.0.0 (XMC-1 firmware 4.0 only) ========================== 10/08/16 Description: This is the first version for firmware 4.0. Links: XMC-1 PC Remote Version 4.0.0Known bugs: TBD |
|
|
|
Post by geebo on Oct 8, 2016 12:21:15 GMT -5
========================== Version 4.0.0 (XMC-1 firmware 4.0 only) ========================== 10/08/16 Description: This is the first version for firmware 4.0. Links: XMC-1 PC Remote Version 4.0.0Known bugs: TBD It's working well for me with the new HDMI board and firmware 4.0. Thanks! |
|
After a bunch of research I have found out that MANY Wireless Routers and Wireless APs will NOT pass UDP broadcasts.
