Enabling Multicast for Yatse auto-detection wizard
-
Ok based on your latest reply with your new network layout, I'm guessing your AP has wireless multicast forwarding disabled.
Does your web interface look like the link below?
http://event.asus.com/2012/nw/dummy_ui/en/Advanced_WAdvanced_Content.html
If so, enable the "Wireless Multicast Forwarding" option. I've never dealt with any Asus products but on some wireless APs you have to enable the transmission/receiving of multicast traffic for wireless clients. I think that's probably this option on your device.
-
^ yeah there you go.. That would be an issue for sure!!
A thank you and applaud from me, just because you took the time to post up pic of the interface showing that wifi router can block that sort of stuff ;) There you go RickyBaker there is your problem.. Pretty much freaking Guarantee it!!!
-
dude lets go over this one last time!!! Pfsense has ZERO to do with multicast on the same layer2/broadcast domain – ZERO!!! Not sure what you did when you swapped out what you had before to pfsense but pfsense has nothing to do with this..
I Believe you! I swear!
Can you manually access vs using multicast for auto discovery?
I can! so no need to download/test anything. I'm mostly trouble shooting this because I'm concerned this issue, WHATEVER it may be ;), may manifest itself in the future in other forms
Ok based on your latest reply with your new network layout, I'm guessing your AP has wireless multicast forwarding disabled.
Does your web interface look like the link below?
http://event.asus.com/2012/nw/dummy_ui/en/Advanced_WAdvanced_Content.html
If so, enable the "Wireless Multicast Forwarding" option. I've never dealt with any Asus products but on some wireless APs you have to enable the transmission/receiving of multicast traffic for wireless clients. I think that's probably this option on your device.
That looks pretty close to my Asus GUI setup, and I will double check this option, but remember my Asus is in AP only mode, which I think severely limits the options available. But, this seems very promising and I will follow up tonight! (also research what Multicast DNS is:))
-
"but remember my Asus is in AP only mode, which I think severely limits the options available."
And that is a AP/Wireless feature.. Not an connection to internet/rouer feature ;) Its says hey do not forward multicast traffic between wireless clients or wired wireless clients. In a netshell do not send multicast over wireless.
Wireless multicast forwarding
: Select Enable to allow the wireless router to forward multicast traffic to other wireless devices that support multicast. Select Disable to prevent the router from forwarding multicast transmissions.You could also have an issue with the transmission rate of multicast
Multicast rate (Mbps) : Select the multicast transmission rate or click Disable to switch off simultaneous single transmissionYou could also have issues with isolation mode..
Set AP isolated : The Set AP isolated item prevents wireless devices on your network from communicating with each other. This feature is useful if many guests frequently join or
leave your network. Select Yes to enable this feature or select No to disable.Some devices when isolation is on even prevent wireless from initiating connection from wireless to wired..
When in AP mode, all of the features of "wireless" would and should still be valid features to enable or disable. When you put the device or use it AP mode the only features that are now not used would be firewall between internet and lan, or natting features - and your normally not going to want the AP to be running dhcp, or dns, etc.. But all of the "wireless" features would still be in play because your using the wireless!!!
-
@johnpoz Great! Thanks for all that information. I'll check all this tonight and report back. I'm cautiously optimistic ;D
-
https://www.dropbox.com/s/ce9ceryslykmnkx/Screen%20Shot%202017-01-05%20at%205.47.30%20PM.png?dl=0
-
There is an option for Multicast Rate(Mbps) which is set to Auto. I wouldn't know what else to set it to. The other options are a bunch of seemingly random numbers prefixed with ODFM
-
There is an option for "Set AP Isolated" but "No" is already selected.
-
There is also an option for "Enable IGMP Snooping" which I don't see in the screenshot you shared but was something you first suggested, so I enabled it on both radio frequencies…
-
-
ahhh bummer. No Enable Wirless Multicasting option. See here https://www.dropbox.com/s/ce9ceryslykmnkx/Screen%20Shot%202017-01-05%20at%205.47.30%20PM.png?dl=0
I thought that idea had so much promise! Thanks for the screenshot @jamesonp that was very useful in making sure I just wasn't missing it.
FYI, for good measure I disabled IGMP snooping to see if the auto-detection wizard would still find my running host and it appears to still be able to detect the running host. Still, thanks again to both of you:)
-
The reason that's occurring is that the wireless AP keeps a table of multicast devices/MAC addresses from when you enabled it previously. Just because you disabled it doesn't mean that it cleared that table. I bet if you manually cleared that table or restarted the AP, the auto detection wizard wouldn't display anything again.
The ability to locate your Kodi device would be directly related to you enabling IGMP snooping.
Interesting. So you're saying it wasn't a port collision? Why did it change when I changed the port? To restate what I witnessed:
-
I enabled IGMP snooping
-
Checked Yatse Auto-detection Wizard and it shows 2 clients: my Kodi client by name but with a question mark in the ip address. And a phantom client with no name or ip address.
-
Change the port in the Kodi interface from 8080 to 1000
-
Checked Yatse and it shows 1 client: my Kodi client with the correct namd AND IP address
-
I DISabled IGMP snooping
-
Checked Yatse and it shows 1 client: my Kodi client with the correct namd AND IP address
I assume you understood this timeline, just wanted to make sure. I'll try to manually restart the AP tonight to test…I'm curious now...
-
-
I rebooted the AP and "forgot" my Kodi client in the Yatse app and it reappeared when I ran the wizard despite not enabling IGMP snooping. Just reporting back, still happy everything works:)
-
"@johnpoz (repeatably:)) said, it didn't have anything to do with multicasting"
I never said that once - what I said repeatedly is that it has nothing to do with PFSENSE.. Since pfsense has ZERO to do with clients talking to each other on the same network.. Pfsense is a GATEWAY!! Of that network if clients want broadcast or multicast pfsense gives 2 shits ;) And has nothing to do with that..
