We would like to create a dedicated Ethernet bridge for an HDMI over IP application using hardware from Just Add Power (see http://www.justaddpower.com/products-topmenu-45.html?page=shop.browse&category_id=16). While we have found that the Just Add Power HDMI over IP solution works flawlessly in a wired environment, Just Add Power technical support tells us that they have never seen their technology work over a standard 802.11 wireless network, presumably because the overhead of the wireless access point remaining available to multiple wireless devices interferes with the data flow, even when only one device is actually connected to that access point. In a wired environment, Just Add Power recommends a capacity of 60 Mbps. Our hope is that a dedicated WDS bridge will reduce or eliminate the multi-client overhead sufficiently for this technology to work.
In a standard setup, each Just Add Power Transmitter and Receiver will have its own dedicated Ethernet connection to a Cisco SG 300-28P managed switch, and each transmitter will be assigned to its own unique VLAN. Each Receiver is then dynamically assigned to one of those VLANS, via the managed switch, in order to specify that the given Receiver should receive the output of the specified Transmitter until further notice. A Transmitter converts an HDMI signal received from a media device into an IP data stream and passes this to the switch via its dedicated Ethernet cable, and the switch then passed this IP data stream to all of the Receivers that have been assigned to the same VLAN as that Transmitter, each via its own dedicated Ethernet cable. The Receivers then convert the IP back into an HDMI signal, which is sent over an HDMI cable to a television.
We are happy to maintain this wired infrastructure for all of our Transmitters and all but one of our Receivers. However, for that one receiver, we would like its dedicated Ethernet cable to run from the Cisco switch to a dedicated access point, which will transmit wirelessly to a dedicated bridge in the same room, which would be hard-wired with an Ethernet cable to the Just Add Power Receiver. There will be other 802.11 wireless traffic in that room, but this will be over a separate wireless network and hopefully will not interfere with the capability and capacity of our bridge.
We are happy to spend a day or so trying to get this to work, and we are happy to spend hundreds, but not thousands, of dollars on the right equipment, even if we are not certain that this will all work. However, we obviously have no appetite to spend time and money on a project that is doomed to failure from the outset, so this leaves us with the following questions:
1) Is WDS the best candidate for our application, or is there a wireless client adapter solution that might promise a higher likelihood of success?
2) Will WDS (or whatever other solution you suggest) be able to handle the dynamically changing VLAN of the Just Add Power Receiver, as described above, or is this a potentially fatal complication?
3) What specific hardware model would you recommend for this task, in order to maximize data throughput and the probability of success, while minimizing the expected time to get this working and the potential for configuration hiccups? Cost is obviously also a factor, but since our time is billed at an hourly rate, ease of implementation is probably more important than hardware cost.
Any advice that you could provide would be greatly appreciated.
In a standard setup, each Just Add Power Transmitter and Receiver will have its own dedicated Ethernet connection to a Cisco SG 300-28P managed switch, and each transmitter will be assigned to its own unique VLAN. Each Receiver is then dynamically assigned to one of those VLANS, via the managed switch, in order to specify that the given Receiver should receive the output of the specified Transmitter until further notice. A Transmitter converts an HDMI signal received from a media device into an IP data stream and passes this to the switch via its dedicated Ethernet cable, and the switch then passed this IP data stream to all of the Receivers that have been assigned to the same VLAN as that Transmitter, each via its own dedicated Ethernet cable. The Receivers then convert the IP back into an HDMI signal, which is sent over an HDMI cable to a television.
We are happy to maintain this wired infrastructure for all of our Transmitters and all but one of our Receivers. However, for that one receiver, we would like its dedicated Ethernet cable to run from the Cisco switch to a dedicated access point, which will transmit wirelessly to a dedicated bridge in the same room, which would be hard-wired with an Ethernet cable to the Just Add Power Receiver. There will be other 802.11 wireless traffic in that room, but this will be over a separate wireless network and hopefully will not interfere with the capability and capacity of our bridge.
We are happy to spend a day or so trying to get this to work, and we are happy to spend hundreds, but not thousands, of dollars on the right equipment, even if we are not certain that this will all work. However, we obviously have no appetite to spend time and money on a project that is doomed to failure from the outset, so this leaves us with the following questions:
1) Is WDS the best candidate for our application, or is there a wireless client adapter solution that might promise a higher likelihood of success?
2) Will WDS (or whatever other solution you suggest) be able to handle the dynamically changing VLAN of the Just Add Power Receiver, as described above, or is this a potentially fatal complication?
3) What specific hardware model would you recommend for this task, in order to maximize data throughput and the probability of success, while minimizing the expected time to get this working and the potential for configuration hiccups? Cost is obviously also a factor, but since our time is billed at an hourly rate, ease of implementation is probably more important than hardware cost.
Any advice that you could provide would be greatly appreciated.
