topic Re: AP122 no scan for webserver with mDNS in Aerohive Migrated Content

AP122 no scan for webserver with mDNS

m_titz1 — Thu, 06 Sep 2018 18:57:33 GMT

Hi there,

i have a strange behaviour in our company network.

We are using Hivemanager classic on premise with Hive OS 8.0r1.

We have mixed APs with AP121and AP122 on BR100 or BR200.

We are scanning with mDNS for Webservers on our non windows machine clients connected to wifi. When the webserver is recogniced our software can communicate with the machine.

So far with AP121 everything works fine.

But with AP122 the webserver from the client shows only once and than never again.

We have checked several things like multicast unicast, firewall on BR100. But nothing helps.

Strange thing is that the AP121 is working fine, only the AP122s are blocking something.

Can someone help us please.

Thanks and regards

Marius

Re: AP122 no scan for webserver with mDNS

gsmith — Thu, 06 Sep 2018 20:12:42 GMT

Hi Marius,

Your AP121s would be using HiveOS 6.5rX.

Can you get a show running-config from both AP 121 and 122 and compare the config for differences. You might find a difference that helps determine the issue. https://www.diffchecker.com/ is a useful tool for this comparison.

Kind Regards,

Gary Smith

Re: AP122 no scan for webserver with mDNS

m_titz1 — Thu, 06 Sep 2018 20:43:22 GMT

Hi,

correct AP121 is 6.5.r10 and the AP122 are on 8.0.r1.

It is difficult to get through the running config.

I can see on the AP121 the line "no bonjour-gateway enable" while this is missing on the AP122.

We are not using a bonjour-gateway and i think mDNS and bonjour gateway are quite similar?!

Re: AP122 no scan for webserver with mDNS

gsmith — Thu, 06 Sep 2018 20:49:47 GMT

Hi Marius,

Can you run a command on both AP’s and post the outputs please?

“show bonjour-gateway status”

Kind regards,
Gary Smith

Re: AP122 no scan for webserver with mDNS

m_titz1 — Thu, 06 Sep 2018 21:03:50 GMT

Here is the result.

AP121

003-AP01-Ravensburg#show bonjour-gateway status

Note: bonjour client only learning/registering aerohive special services

Running as bonjour client

Bonjour Gateway Status:Disabled

Realm Name: 003-Ravensburg_Kling

Device priority: 10

My BDD: 0.0.0.0

Local mgt0: IP(172.30.3.211/24), VLAN(10) MAC(e01c:41bb:5ec0)

Total 1 Local Attached VLANs: 10

Total Services: 0; Total Self-Services: 0; Published Times: 0

Total 0 Remote BDDs:

AP122

158-AP01-Ludwigsburg#show bonjour-gateway status

Note: bonjour client only learning/registering aerohive special services

Running as bonjour client

Bonjour Gateway Status:Disabled

Realm Name: 158-Ludwigsburg_Kling

Device priority: 10

My BDD: 0.0.0.0

Local mgt0: IP(172.30.158.211/24), VLAN(10) MAC(c866:5d2b:9300)

Total 1 Local Attached VLANs: 10

Total Services: 0; Total Self-Services: 0; Published Times: 0

Total 0 Remote BDDs:

---------

Looks like the bonjour-gateway is not enabled on both APs.

Re: AP122 no scan for webserver with mDNS

gsmith — Thu, 06 Sep 2018 21:28:51 GMT

The AP’s are in different subnets. Do you see the same issue if they are in the same subnet?

Local mgt0: IP(172.30.3.211/24), VLAN(10) MAC(e01c:41bb:5ec0)
Vs
Local mgt0: IP(172.30.158.211/24), VLAN(10) MAC(c866:5d2b:9300)

Re: AP122 no scan for webserver with mDNS

m_titz1 — Fri, 07 Sep 2018 13:17:35 GMT

The APs are in different locations. Thats because the subnet is different.

Re: AP122 no scan for webserver with mDNS

gsmith — Fri, 07 Sep 2018 15:21:52 GMT

Hi Marius,

So, ap121 in one location works. AP122 in another location does not work. It would be good to know if the AP121 would work in the AP122 location and vise-versa. This would help rule out a local network issue.

Kind Regards,
Gary Smith

Re: AP122 no scan for webserver with mDNS

m_titz1 — Fri, 07 Sep 2018 15:27:26 GMT

Hi Gary,

we have 160 locations. AP121 are 255 units and AP122 are 24 in use.

We have checked all combinations. Mixed, alone, different settings, reboot etc.

AP122 is not working with our webserver mdns search. Our sales contact couldnt help us also.

Re: AP122 no scan for webserver with mDNS

m_titz1 — Fri, 05 Oct 2018 13:12:46 GMT

Hi Gary,

update to this issue.

My coworker from Software department found a solution now for this issue.

In the programm from Github for scanning the mDNS was a TTL set to 1. It looks like the AP122 and AP121 works different with TTL=1. AP121 forward the packets and doesnt change it, but AP122 sets it to 0 and the packets are lost.

After my SD colleague changed the TTL to 2, the packets from mDNS receives the server without a problem and everything works fine.

After this difficult case we can get back to normal work 🙂

Thank you for your support.

Greetings Marius