• State Verified Answer
  • Date
    Jason Lord
  • Date
  • Replies 2 replies
  • Subscribers 184 subscribers
  • Views 6788 views
  • Users 0 members are here

Nomad and Windows 10 Loopback

I'm trying to get Nomad to send via the Microsoft KM-TEST Loopback Adapter in Windows 10 to my visualizer on the same laptop.  This worked in Windows 7 but I can't seem to get the connection to happen in 10.

I have DMX Workshop open (from Artistic License) and it's monitoring the Artnet traffic, but it's not seeing Nomad's output.  It sees my visualizer (Realizzer) as an Artnet Node, so that is configured correctly.

In the Nomad shell I make sure it's using the laptops IP of 10.101.90.113 but I can't seem to get the output routed internally to my visualizer.

Here's my setup:

  • Macbook Pro 2012 (wireless only, no ethernet port)
  • running Windows 10 in Bootcamp (native boot into Windows)
  • Nomad v2.3.3
  • Realizzer 3D (set to receive Artnet via Loopback Adapter)
  • Loopback static IP of 10.101.90.113, subnet 255.255.0.0, gateway 10.101.1.1

There's no way to select the NIC in the shell, so I make sure it's defaulting to the 10.x IP and not my wireless card (192.168.x.x).  Sometimes I need to disable the wireless and re-open the shell so it defaults to 10.x and not my wireless adapter.  Anyway, I need help getting Nomad to route in Windows 10.

Thanks,

Jason

Parents
  • 0

    Ok, I got it to work. Basically, even though the Nomad shell is showing that its IP address is the static IP of the Loopback Adapter (10.101.x.x), it's not using it. It was sending over my wi-fi card (which is IP 192.168.x.x).. After a bit of testing I changed DMX Workshop to monitor Artnet traffic on the Wireless adapter and there it all was.. Even though the Nomad shell shows 10.101.x.x as the IP it's using (the Loopback IP) it was still sending over wi-fi. This is a real problem but here's how I got it all working:

    - I disable my wireless adapter and rebooted Windows, making the Loopback adapter the only interface.
    - My visualizer "calls home" when you turn it on (which is a problem) and I have to click through Unhandled Exceptions to open my file offline
    - Nomad Shell shows 10.101.x.x as before (but is now actually using it)
    - Open Nomad and everything works
    - I can re-activate my wireless adapter and send this online and use Nomad, previz and Firefox

    It's time to create a way to let us choose the NIC in the shell of Nomad. It is defaulting to the wifi adapter therefore it does not show the correct adapter IP in the shell.

Reply
  • 0

    Ok, I got it to work. Basically, even though the Nomad shell is showing that its IP address is the static IP of the Loopback Adapter (10.101.x.x), it's not using it. It was sending over my wi-fi card (which is IP 192.168.x.x).. After a bit of testing I changed DMX Workshop to monitor Artnet traffic on the Wireless adapter and there it all was.. Even though the Nomad shell shows 10.101.x.x as the IP it's using (the Loopback IP) it was still sending over wi-fi. This is a real problem but here's how I got it all working:

    - I disable my wireless adapter and rebooted Windows, making the Loopback adapter the only interface.
    - My visualizer "calls home" when you turn it on (which is a problem) and I have to click through Unhandled Exceptions to open my file offline
    - Nomad Shell shows 10.101.x.x as before (but is now actually using it)
    - Open Nomad and everything works
    - I can re-activate my wireless adapter and send this online and use Nomad, previz and Firefox

    It's time to create a way to let us choose the NIC in the shell of Nomad. It is defaulting to the wifi adapter therefore it does not show the correct adapter IP in the shell.

Children
Related

www.etcconnect.com