Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Banister5024

#1
After a bit more troubleshooting.

I'm using the 3 firewall rules I posted above. With these settings for the UDP Broadcast Relay plugin -> imgur link. I enabled IGMP Snooping on the switches/AP like I mentioned on my post above.

What I found out is that if I try to cast from my phone or any other wireless device the connection will work for the first device that tries it. Any other device will see the speaker and will try to connect to it but will never actually start casting. The original device can stop casting, start again, do anything but the other ones will get stuck in that even if the original one already stopped.
This even persists through the speaker itself being rebooted and only seems to clear itself when I restart the wireless network itself.

I can replicate this every time.

For whatever weird reason though. Wired devices do not face this issue. I can start casting on my laptop connected to the LAN VLAN by ethernet -> Works -> Grab one wireless device connected to the LAN VLAN through wifi -> Works -> Grab another ethernet computer -> works -> grab any other number of wireless devices -> Nope! -> Back to the first wireless device -> Still works.

I have absolutely no clue what's going on XD.
#2
Hey! Thanks for the reply!.

So, I added the rules you mentioned as floating rules selecting the interfaces that I think need to be affected (the IoT vlan, the one where my NAS is for windows samba discovery, things like that). Would you mind checking if this looks right? imgur screenshot of how the 3 rules look like.

Now, onto the actual casting part.

I was having absolutely no luck. I could see the devices on the other side (my phone could see the nest hub) but connection would fail regardless of what I did. The logs/debugging I could see in the terminal didn't really tell me anything.

What you said about things depending on other switches/routers/whatever made me realize that I never actually looked into the rest of the networking gear to see if there was anything there.
I'm using TP-Link's Omada gear for AP and switches and poking around the configuration where I set the VLAN tags for each network there's a checkbox labeled "IGMP Snooping" that's disabled by default (imgur screenshot link). I checked that option and everything started working right away.


Thanks!.


//Edit: Or maybe not. It worked last night before bed but now that I'm trying it again I'm getting the same behavior than before >.>. Still troubleshooting it seems haha.
#3
I'm pretty sure this has been asked several times. I found a bunch of posts with suggestions but so far I haven't managed to make it work so figured I'd ask here again.

I think it's a pretty standard arrangement. I have a bunch of Google Assistant devices (speakers and hubs) that I want to put into a dedicated IoT VLAN but I would like to still be able to cast to them and control them using the Google Home application.

I've seen posts and guides saying "Just install the MDNS repeater and enable it" and I've done that following the documentation here. It does something because scanning for devices from my phone shows the one in the other VLANS and if I disable it they disappear but I can't connect nor cast anything to them. I tried putting a blanket "allow all from anywhere" rule in the firewall for that interface and no luck.

Am I missing something?. Any idea on how I can troubleshoot this?.

Another thing I tried was the UDP Broadcast Relay plugin that seemed to have more options and a more involved configuration but still no luck.