Jason
Minor Hero
Posts: 12 
|
Post by Jason on Dec 15, 2018 22:52:40 GMT -5
Does anyone know, specifically, what type of traffic Dirac Live uses to discover the XMC-1? I tried everything I knew to get Dirac to find the XMC-1 while both the processor and the MacBook Pro were connected to the same switch with no luck. Both devices on the same subnet, able to ping the processor from the MacBook, etc... I had no problems discovering and controlling the XMC-1 from both the Android and iOS apps, too. But could not get the MacBook to discover the XMC-1 while connected to the same switch as the XMC-1. I was able to manually configure the network settings on the XMC-1 and on the MacBook and then connect them directly using the same Cat6 cable. Dirac was immediately able to discover and control the XMC-1 when connected directly. So I'm hoping that someone can help me understand what traffic my switch doesn't like to pass so I can try and resolve that issue for the future. Thanks in advance!
|
|
|
|
Post by vcautokid on Dec 15, 2018 22:55:10 GMT -5
Not super familiar with the latest MAC OS but it could be. Network firewall issue. You may need to creat and exception for the XMC-1. Those whom live on the MAC should hopefully chime in with more.
|
|
|
|
Post by sgracing on Dec 16, 2018 8:21:42 GMT -5
Not super familiar with the latest MAC OS but it could be. Network firewall issue. You may need to creat and exception for the XMC-1. Those whom live on the MAC should hopefully chime in with more. It's not a Mac issue it's an XMC-1 issue . First you must power down the XMC-1 in the rear then plug in the Ethernet cable start your dirac program on the Mac or PC then power up your XMC This should allow for a signal ping the your IP . |
|
|
|
Post by wilburthegoose on Dec 16, 2018 8:58:19 GMT -5
What IP address was assigned? Can you ping that IP address?
|
|
|
|
Post by sgracing on Dec 16, 2018 9:01:12 GMT -5
I run to a router assigned to a serverver it will automatically assign an IP that is free(available)
|
|
|
|
Post by wilburthegoose on Dec 16, 2018 9:22:56 GMT -5
Yeah - that's called DHCP.
If the OP can share the IP, he'll be able to try to ping it. If it's pingable, it's probably going to be available.
Editorial comment - if the Apple ecosystem is so wonderful, why do so many people have so many problems with it? 20 years ago, Apple was much better than Windows. Today, Windows is more solid and usable and is as good as the Apple world. Plus, not being closed like Apple, they play with other devices.
|
|
|
|
Post by 405x5 on Dec 16, 2018 10:03:32 GMT -5
Yeah - that's called DHCP. If the OP can share the IP, he'll be able to try to ping it. If it's pingable, it's probably going to be available. Editorial comment - if the Apple ecosystem is so wonderful, why do so many people have so many problems with it? 20 years ago, Apple was much better than Windows. Today, Windows is more solid and usable and is as good as the Apple world. Plus, not being closed like Apple, they play with other devices. I enjoy my Apple gear and until recently, I figured my next computer would be a Mac 🖥. But you are so right about Windows....in the last couple of years the improvements and stability of the OS. have been huge to the point that I may not be so quick to jump ship 🛳. My old Gateway was just young enough to handle 64 bit Windows 10. Runs better than ever. Bill |
|
bootman
Emo VIPs 
Typing useless posts on internet forums....
Posts: 9,358
|
Post by bootman on Dec 16, 2018 13:20:31 GMT -5
How to do a Ping Test on MAC OS X
Go to your Applications folder
Choose Utilities and then open the Network Utility
Click the Ping tab and specify a domain or IP that you want to check
Click on the Ping button to launch the test
|
|
Jason
Minor Hero
Posts: 12
|
Post by Jason on Dec 16, 2018 15:23:00 GMT -5
Thanks all,
I let the XMC-1 grab its DHCP configuration from my (Meraki) router. IP address was assigned as 10.1.2.16 with a subnet mask of 255.255.0.0. My MacBook was assigned 10.1.2.17 with same subnet mask. I was able to ping the XMC from the MacBook with no problem. But Dirac couldn't find the XMC-1 when both devices were connected to my Ubiquiti switch in the A/V rack. I disconnected the network cable from the switch and connected my MacBook directly to the XMC-1, bypassing the switch. I disabled DHCP on both devices, but left the IPs assigned, as well as the subnet mask exactly the same as what the DHCP server assigned. Dirac was immediately able to find the XMC-1 using the exact same network settings, but without the devices being connected to the switch.
I should have mentioned this in the original post, but I also had the exact same results with a Win10 notebook. In my case, the problem seems to be that my switch is blocking whatever traffic is used for discovery. Doesn't seem to be related to the OS.
|
|
|
|
Post by wilburthegoose on Dec 16, 2018 18:19:36 GMT -5
Just curious. Why are you using 10.* IP addresses? They are certainly legit, but are more common in a workplace. Most home routers use the 192.168.* private address range.
You may want to verify your subnet mask settings. You’re using Class A addressing
|
|
bootman
Emo VIPs
Typing useless posts on internet forums....
Posts: 9,358
|
Post by bootman on Dec 17, 2018 8:14:46 GMT -5
Thanks all, I let the XMC-1 grab its DHCP configuration from my (Meraki) router. IP address was assigned as 10.1.2.16 with a subnet mask of 255.255.0.0. My MacBook was assigned 10.1.2.17 with same subnet mask. I was able to ping the XMC from the MacBook with no problem. But Dirac couldn't find the XMC-1 when both devices were connected to my Ubiquiti switch in the A/V rack. I disconnected the network cable from the switch and connected my MacBook directly to the XMC-1, bypassing the switch. I disabled DHCP on both devices, but left the IPs assigned, as well as the subnet mask exactly the same as what the DHCP server assigned. Dirac was immediately able to find the XMC-1 using the exact same network settings, but without the devices being connected to the switch. I should have mentioned this in the original post, but I also had the exact same results with a Win10 notebook. In my case, the problem seems to be that my switch is blocking whatever traffic is used for discovery. Doesn't seem to be related to the OS. The firewall om the switch is blocking the ports needed for Dirac. According to this Emotiva document: emotiva.com.ua/pdf/xmc-1/Dirac_Live_Emotiva_FAQ.pdfStandard web browser ports: HTTP 80 and 8080 used for hyptertext Transfer Protocol HTTPS 443 Used for secure web browsing IMAP 143 used for email applications FTP 20 and 21 used for well FTP or File Transfer Protocol I doubt it is using the mail ports but your firewall may be blocking FTP or one of the other web ports needed. |
|
KeithL
Administrator 
Posts: 9,926
|
Post by KeithL on Dec 17, 2018 12:46:44 GMT -5
Both 10. and 192. are legitimate "private addresses".
That basically means that, even if somebody were to mis-configure something, those addresses will NOT be visible across the Internet. (The routers that sit at the endeg of the Internet are configured by default NOT to pass them through.)
They are reserved for use inside your home or business - behind a NAT router. The choice of which to use by default is generally made by the manufacturer of your router or DHCP server... don't read any particular significance into that choice. (The number of addresses available in the 192. block is a bit too small for some really large businesses).
RFC1918 name: IP address range
24-bit block: 10.0.0.0 – 10.255.255.255
20-bit block: 172.16.0.0 – 172.31.255.255
16-bit block: 192.168.0.0 – 192.168.255.255
Just curious. Why are you using 10.* IP addresses? They are certainly legit, but are more common in a workplace. Most home routers use the 192.168.* private address range. You may want to verify your subnet mask settings. You’re using Class A addressing |
|
KeithL
Administrator
Posts: 9,926
|
Post by KeithL on Dec 17, 2018 12:51:10 GMT -5
A true SWITCH should pass pass all traffic regardless of the protocol involved. (Within reason, and some modern switches do a bit more.)
It's more likely that the firewall in your MacBook is refusing to pass traffic from a specific program. (We've also heard reports of the firewall saying it was set to pass everything - but not really doing so.)
The first thing to try would be to disable any security software running on that particular MacBook... including the internal firewall.
You could also try uninstalling and re-installing Dirac. (With any luck, when you do it will ask you once again if it should make a firewall exception for that program.)
Also note that the Dirac software works well with Yosemite.... And not well at all with Sierra and High Sierra. (If you have one of those it may just plain not work.)
Does anyone know, specifically, what type of traffic Dirac Live uses to discover the XMC-1? I tried everything I knew to get Dirac to find the XMC-1 while both the processor and the MacBook Pro were connected to the same switch with no luck. Both devices on the same subnet, able to ping the processor from the MacBook, etc... I had no problems discovering and controlling the XMC-1 from both the Android and iOS apps, too. But could not get the MacBook to discover the XMC-1 while connected to the same switch as the XMC-1. I was able to manually configure the network settings on the XMC-1 and on the MacBook and then connect them directly using the same Cat6 cable. Dirac was immediately able to discover and control the XMC-1 when connected directly. So I'm hoping that someone can help me understand what traffic my switch doesn't like to pass so I can try and resolve that issue for the future. Thanks in advance! |
|
Jason
Minor Hero
Posts: 12
|
Post by Jason on Dec 17, 2018 21:20:49 GMT -5
Thanks for the replies, all. In my case it appears that the Ubiquiti switch is not passing some sort of multicast traffic that is being used for device discovery. I borrowed a "dumb" TP-Link switch from the office, connected it to the XMC-1 and the same MacBook discovered the XMC-1 without any issues. I imagine it's something about IGMPv3 or IGMP snooping that Dirac is not liking. When I have some time after the holidays, I will try a different combination of IGMP settings on the Ubiquiti switch until I can get Dirac to discover the XMC-1 and post the results.
|
|
Jason
Minor Hero
Posts: 12
|
Post by Jason on Dec 17, 2018 21:38:59 GMT -5
Also, for whatever it's worth I found that TCP ports 22 (SSH), 2891, 7100, and 17331 are all open on the XMC-1. Again, those details aren't relevant to my particular issue. As Keith mentioned, the switch is behaving like a switch when it comes to unicast TCP traffic and just passing it. It seems to be interfering with mutlicast traffic though. For those interested, there is a good discussion about how different switches and routers contend with multicast traffic here: community.cisco.com/t5/switching/multicast-understand-how-ip-multicast-works/td-p/1886686 |
|
|
|
Post by millst on Dec 18, 2018 0:43:17 GMT -5
Is that an Edgerouter? Are the ports that your computer and XMC-1 are connected to part of the router's switch? You either need to assign them to the hardware switch or a virtual (software/slower) bridge. Otherwise, traffic will be sent out to the WAN, but not between the internal LAN ports.
-tm
|
|
KeithL
Administrator
Posts: 9,926
|
Post by KeithL on Dec 18, 2018 14:34:15 GMT -5
These days terms like "router" and "switch" are used somewhat loosely. A "pure switch" is a Network Layer 2 device - and passes all traffic in both directions. It doesn't know or care what your traffic actually is - and won't block any of it.
It also will not have any sort of firewall functionality
However, today, many boxes contain multiple network devices.... and do all sorts of interesting and sometimes problematic things.
For example, a typical "cable modem" is really a DOCSIS modem, an edge router, a WiFi router, a DHCP server, and a switch.
If you connect two devices to two of the hardware Ethernet ports on your cable modem they are probably really connected to two ports on the same switch. However, almost any other combination becomes more complicated, and somewhat uncertain.
In general, if there is doubt..... - go buy a cheap 8-port switch (eight Ethernet ports; zero configuration options; about $20) - connect your XMC-1 and your Dirac computer to that using wires
- connect the switch to your cable modem or other network somehow so it can use their Internet connection and DHCP services
Is that an Edgerouter? Are the ports that your computer and XMC-1 are connected to part of the router's switch? You either need to assign them to the hardware switch or a virtual (software/slower) bridge. Otherwise, traffic will be sent out to the WAN, but not between the internal LAN ports. -tm |
|
|
|
Post by wizardofoz on Dec 18, 2018 14:46:24 GMT -5
I was told by Dirac that their new software probably is not able to work with the Xmc-1...that is Dirac V2. Keith can you confirm or substantiate this?
The old Emotiva Dirac le software seems to not like running on win 10 or Mac OS Mojave either.so where does this leave us Xmc-1 owners now?
|
|
KeithL
Administrator
Posts: 9,926
|
Post by KeithL on Dec 18, 2018 14:58:29 GMT -5
A router decides which way to send packets based on their destination addresses and how it is configured. It knows which addresses are inside your network and which ones aren't. For an "edge router", you basically tell it which addresses are inside your network, and it assumes that all other addresses are to be accessed via the Internet. With most small home devices, the DHCP server hosted on the router sets the addresses for your equipment, and tells the router what addresses it's using. Anything with one of those addresses is assumed to be on your network; and anything else is assumed to be "outside on the Internet".
The issue with many of these devices is that by default they are NOT configured to talk to each other.
For example, if you have TWO cable modems, with some devices connected to each. Each will assign addresses to the devices connected to it. And each will allow all of the devices connected to it to talk to the Internet. However, devices connected to one will NOT be able to talk to devices connected to the other. They will NOT be able to talk to each other across the Internet because, by default, most home devices are configured to reject "unsolicited incoming connections". (When you read instructions to "open an incoming port", what they're talking about is making specific accommodations to override this default behavior.)
A switch is more like an "octopus" on an extension cord. A simple switch does not require any sort of assignment or any other type of configuration.
You simply connect various devices to its ports. The first time a device sends out a packet, that packet is "flooded" to all of the other ports.
Then, once the switch sees which port responds to that packet, it sets up a sort of virtual circuit, and only forwards packets that are part of that conversation between those two ports. How it figures out the details and keeps track of them is quite complex - but also pretty much outside your control.
(You could think of it like a self-configuring router.)
However, many modern devices combine some of the characteristics of a router, and a switch, and a firewall, among other things. You can avoid much of that complication if you just stick with the simplest and cheapest switch you can find when you want two devices to "always be able to talk to each other".
A really simple switch, if it's working right, should act pretty much like a dumb wire.... only better. 
Is that an Edgerouter? Are the ports that your computer and XMC-1 are connected to part of the router's switch? You either need to assign them to the hardware switch or a virtual (software/slower) bridge. Otherwise, traffic will be sent out to the WAN, but not between the internal LAN ports. -tm |
|
KeithL
Administrator
Posts: 9,926
|
Post by KeithL on Dec 18, 2018 15:13:03 GMT -5
We are currently in discussions with Dirac about their new software version. As of now we plan to have their new product (Dirac 2) incorporated into our new product (the RMC-1).
I don't have any definite information beyond that at the moment.
As far as we know the current Dirac Live LE works just fine on Windows 10 (as well as Windows 7, and some variants of Windows 8/8.1). It also works fine on the Yosemite version of the Apple O/S. It has problems with Sierra, and High Sierra (it can sometimes be coaxed into working - but not consistently). So far we haven't tested it with Mojave (and we aren't specifying it to work with anything past Yosemite.)
Because Dirac 2 is essentially different software, I'm pretty sure it wouldn't work with the current "XMC-1 Dirac Software Engine" that resides in the XMC-1 firmware. I don't know at this point whether it may eventually be possible to update the XMC-1 to work with the new version - or whether it would be impractical from a hardware point of view.
At this point we absolutely ARE NOT promising that the XMC-1 will ever be updated to run Dirac 2 - but I would not absolutely rule it out either. (It leaves you with Dirac Live for Emotiva, which works fine on the XMC-1, on current Windows Computers, and on the Apple computers that were current when it was released.)
I was told by Dirac that their new software probably is not able to work with the Xmc-1...that is Dirac V2. Keith can you confirm or substantiate this? The old Emotiva Dirac le software seems to not like running on win 10 or Mac OS Mojave either.so where does this leave us Xmc-1 owners now? |
|
