Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Pete Erskine]

I have never been successful keeping Wireless workbench connected.
In my current setup, all IP is set static.  Everything including my computer is 10.14.21.XXX with Mask 255.255.0.0
I am also connected to Riedel Artist at 10.13.255.14 and it has no issues staying connected.

Only some of the UHF-R RX disconnect and to get it back I need to select another network in WB and then re-select the correct one.

IP scanner shows:

[Tom Bourke]

What is your physical set up?   I count 5 sub nets.  I also see some of the mac addresses are VERY close.

[Jordan Wolf]

Pete,

Unless something has changed, monitoring and control of Wireless Workbench cannot happen across subnets.

Your problem seems to be the subnet that your computer is set to. With the subnet set to 255.255.0.0, your computer will only be able to see devices that share the first two octets of your computer's IP address (10.14). If you were to set the subnet to 255.0.0.0, then your computer could see any network devices that have a "10" as the first octet...the rest of the IP address wouldn't matter. A better option would be to stick with the same subnet, but make your IP range for everything in Wireless Workbench 10.13.x.x

[Pete Erskine]

Pete,

Unless something has changed, monitoring and control of Wireless Workbench cannot happen across subnets.

Your problem seems to be the subnet that your computer is set to. With the subnet set to 255.255.0.0, your computer will only be able to see devices that share the first two octets of your computer's IP address (10.14). If you were to set the subnet to 255.0.0.0, then your computer could see any network devices that have a "10" as the first octet...the rest of the IP address wouldn't matter. A better option would be to stick with the same subnet, but make your IP range for everything in Wireless Workbench 10.13.x.x

It doesn't work at all like that, only partially the way I have it.

[Scott Holtzman]

As a clarification the subnet mask would have to be changed on all devices in order to have the broadcast IP consistent.  Just opening up the subnet mask on one host does not allow it to see across network boundaries.  That is called promiscuous mode and you need to have a sniffer program to do that.

The math behind a subnet mask is simple.   The subnet mask is logically "anded" with the IP and the result is the significant bits. 

Sent from my SM-T800 using Tapatalk

[Jordan Wolf]

As a clarification the subnet mask would have to be changed on all devices in order to have the broadcast IP consistent.  Just opening up the subnet mask on one host does not allow it to see across network boundaries.

Ah, yes, agreed. Sorry for the lack of clarification.


Sent from my iPhone using Tapatalk

[Jelmer de Jong]

This is a old topic, did you ever get it figured out?

[Dan Mortensen]

I have never been successful keeping Wireless workbench connected.
In my current setup, all IP is set static.  Everything including my computer is 10.14.21.XXX with Mask 255.255.0.0
I am also connected to Riedel Artist at 10.13.255.14 and it has no issues staying connected.

Only some of the UHF-R RX disconnect and to get it back I need to select another network in WB and then re-select the correct one.

IP scanner shows:

I'm late to several parties today and just saw this post.

I've found that WWB and/or the Shure ULX-D's need to have routers set to DHCP and not static. Changing routers back and forth set one way vs. the other gives instant reliable connection (DHCP) vs. non-connection or unreliable (Static).

That is exactly opposite from my mixing consoles (X32), go figure.

HTH, if you didn't figure it out already.

[Jordan Wolf]

I've found that WWB and/or the Shure ULX-D's need to have routers set to DHCP and not static. Changing routers back and forth set one way vs. the other gives instant reliable connection (DHCP) vs. non-connection or unreliable (Static).

I haven't found this to be the case - in fact, I've been running 7 ULXD4 kits for the past few days in "manual" (aka Static) mode with no issues whatsoever.

I have my Airport Express set up for Bridge mode, so no IPs are being handed out. You just have to set every parameter that is normally auto-populated by the device from DHCP.


- Jordan Wolf

[Dan Mortensen]

I haven't found this to be the case - in fact, I've been running 7 ULXD4 kits for the past few days in "manual" (aka Static) mode with no issues whatsoever.

I have my Airport Express set up for Bridge mode, so no IPs are being handed out. You just have to set every parameter that is normally auto-populated by the device from DHCP.


- Jordan Wolf

Interesting. Mine *absolutely* refused to work with Static, no matter how many times I tried it (reentering all the values), and *instantly* connected with DHCP.

Huh.

[Jordan Wolf]

Interesting. Mine *absolutely* refused to work with Static, no matter how many times I tried it (reentering all the values), and *instantly* connected with DHCP.

Huh.

What version firmware are you running? I haven't had any issues with using static IPs yet, even with previous versions, but that's not to say it isn't possible, particularly if firmwares are mismatched.

I'm on the most recent release (1.7.34).


- Jordan Wolf

[Dan Mortensen]

What version firmware are you running? I haven't had any issues with using static IPs yet, even with previous versions, but that's not to say it isn't possible, particularly if firmwares are mismatched.

I'm on the most recent release (1.7.34).


- Jordan Wolf

Sorry for the delay in replying.

It turns out I'm not on the most recent; I have one unit that's 1.5.6 and the rest are 1.6.6.

Funny how there's been 5 or 6 updates in the last year and I've missed all of them, yet the units are working just great. The Static/DHCP hasn't been a big deal since DHCP works just fine every time. I'm tempted to not mess with it, but realize one is always supposed to be up to date.

Thanks for making me aware.

[Ike Zimbel]

Sorry for the delay in replying.

It turns out I'm not on the most recent; I have one unit that's 1.5.6 and the rest are 1.6.6.

Funny how there's been 5 or 6 updates in the last year and I've missed all of them, yet the units are working just great. The Static/DHCP hasn't been a big deal since DHCP works just fine every time. I'm tempted to not mess with it, but realize one is always supposed to be up to date.

Thanks for making me aware.

This raises an interesting conundrum...the age-old "if-it-ain't broke..." vs. the "always stay up-to-date" theory. I've been using the latter one based on the assumption that if I ever do have to phone tech support, the first thing they are going to ask is "What version of the firmware are you on?" which is usually then followed by "You should update that..."
When I was prepping for TED this year, I spent a fair bit of time updating all of the units to 1.7.34...and I still had issues with WB dropping the connection several times a day.

[Pete Jones]

I dont know if this is useful to anyone but....
I have all my ulx-d receivers connected to a dante network, and wanted to use dante controller, wwb and the console editor at the same time.

Dante uses the auto ip in the 169.254.x.x range
The console defaults to 192.168.1.x range
And I discovered the receivers have a dante ip address, but also a *control* ip address, which defaults to 192.168.2.x range.

Having had all kinds of issues with wwb using the a 169.254.x.x address on my laptop ( units disappearing, unable to perform scans etc.) I set my pc to have 3 ip addresses, one in each of the ranges I mentioned above, and set wwb to use thie 192.168.2.x address (appears as a separate network interface in wwb settings.

It worked a treat and I was able to use wwb, Dante controller and console editor no problem.

In order to add extra ip addresses in windows you need to go to the ipv4 settings and click on advanced, then click add. I had no idea you could do this until we googled it during a very long boring show.....

[Pete Erskine]

Pete,

Unless something has changed, monitoring and control of Wireless Workbench cannot happen across subnets.

Your problem seems to be the subnet that your computer is set to. With the subnet set to 255.255.0.0, your computer will only be able to see devices that share the first two octets of your computer's IP address (10.14). If you were to set the subnet to 255.0.0.0, then your computer could see any network devices that have a "10" as the first octet...the rest of the IP address wouldn't matter. A better option would be to stick with the same subnet, but make your IP range for everything in Wireless Workbench 10.13.x.x

I was recently told by Steve Caldwell that the Shure AAB works best on a 10Mb network and do not work well on 100Mb. 

[ProSoundWeb Community]