Airtame 2

[Ena Marklund]

Whats the output when you run the following commands while the Airtame and Windows Machine are both connected? I would hazard a guess the the Mac OS X is using mDNS for discovery while the Windows Machine is using SSDP:

Do you want me to run the commands when the Windows machine is connected via LAN to the Airtame ? Or should I manually type the IP into the airtame app to connect the Windows machine through WiFi and run these commands?

2. With your Windows Machine on the LAN - can you run wireshark on the laptop and capture the discovery process of the Airtame App from first launch? You could do a capture-filter on "udp 1900" or a display-filter on "ssdp" and export the displayed packets that way to keep too much info from being exposed (or pm the capture).

Also disabling on the Windows machines the SSDP service as Windows has the ability to run its on SSDP multicast group ( the same service that airtame uses) and this was grabbing the airtame multicast packets.

Glad to hear you got it working. Interesting about the Anti-Virus and Windows SSDP Service -> I could understand the Anti-Virus if it was also functioning as a firewall (differentiating between two network type/locations and applying separate policies) - but the service is a bit perplexing since it worked on LAN but not WLAN. I was initially thinking they're was a "service id" issue - I saw that Airgroup was dropping "airtame:recv" service - I did a packet capture on my machine - and saw two M-Searches -> 1 for the "urn:airtame-com:device:airtame:1 " that you added - and 1 for that "airtame:recv" which is considered invalid with the uPnP Architecture as it doesn't contain the "URN:" prefix among other things - such as the Roku Remote Control app - which i see that your Airgroup is also dropping "roku:ecp". But didn't see that AirGroup received any queries for "urn:airtame-com:device:airtame:1".

The anti-virus has a built in firewall policies and it's policy is assigned by subnet. The wireless subnet is different than the lan subnet which means the policies are different. We will need to amend this.

I noticed that airtame:recv had massive dropped queries but i could not find this in the guide as to what this is even used for, we dont' even have this listed as a service ID as it is not a valid service ID.

Have you tried adding "permit" policies for SSDP-239.255.255.250 and mDNS-224.0.0.251 to send that discovery traffic over the tunnel to the controller for AirGroup processing instead of src-nat for SSDP/mDNS?

OK so here is a little update after thinking about the advice you gave me I allowed the UDP ports 1900-1901 and 5353 for SSDP discovery on the controller itself. This means that now the RAP (the AP on the remote site) can discover all of the airtame devices on the site we have the controller (Back here at main office).

However static MDNS entries should still be shared by the controller? If the static MDNS entries are there then the connection should work as I can manually connect by typing the IP - this is the party I do not understand.

It's not a supported use-case for Airgroup. Because the RAP is operating in split-tunnel mode, there is a split between what is seen by the RAP and what is seen by the controller. Airgroup is not currently intended to operate in this scenario.

So what is the purpose of the static MDNS entries ? Because surely if they are able to be seen by the controller the auto discovery will work anyway so there would be no need for static entries?

That is not a supported configuration. If you are able to move the airtame devices behind the RAP so that the controller has visibility, that should work, but do to the NAT occuring at the RAP with split-tunneling it will not work.

Description Summary: Cat 1-- Built-in wireless projection capability, lectern with PC, full audio system (ceiling installation). External device connectivity: Laptop, USB, HDMI, VGA. Ethernet and wireless network access.

Instructions: Request chalk, markers and erasers from your department. For Airtame instructions go to -repository/airtame-instructions.pdf ; for iProjection go to -repository/iprojection-instructions.pdf

3a8082e126