Search results

IPv6 or not made no difference, it was just another random dead end due to the weird interaction between Avahi and the WiiM app. Nothing else was impacted anyway. WiiM told me to either put my phone on the IoT segment or move the WiiM Pro into the main lan. Put it another way, they did not...

As an update, it looks like I solved my problem and things have been working reliably for a couple of days now. I waited until things were working long enough, because in the past I had periods of working followed by refusal to work. After trying all the mDNS reflectors/repeaters in the OpenWRt...

Got it now, sorry. I can only log rejected packets, not dropped, so I will have to change my settings and play with it, but need to ensure I don't break what's working for the family https://openwrt.org/docs/guide-user/firewall/fw3_configurations/fw3_traffic_logging Right now, with IPv6...

Well, yes, if I enable all packets, it works. But that defeats the purpose of having an iot vlan in the first place (I know you are suggesting it only as a test). My router is fast enough that dropped packets should never happen, so if it happens, it happens on the WiiM or the WiiM Home app...

Uh, that's interesting. I know I could do something similar with nftables, but the UDP relay has a debug output and that helps. I installed the relay, disabled ahavi, and ran the following (br-lan.101 is the iot lan) udp-broadcast-relay-redux --id 1 --port 5353 --dev br-lan.101 --dev br-lan.1...

Sure, happy to. I'm using a Dynalink DL-WRX36 running OpenWRT 23.05.2, and the standard Ahavi redirector. My network is relatively simple, a main network, plus IoT and Camera vlans. IoT devices can access the internet, cameras cannot (Chinese cameras are notoriously bad). standard firewall to...

Well, it turns out that all Android devices on my network have the same issue, the other device worked that one time I tried, but it's not working reliably anymore, exhibiting the same problem. As for elegance, the OP and I (and probably others) have poorly working WiiM devices. Something is...

Well, the business justification is that caching the IP makes it faster for everyone, and for people like me and the user posting this thread, solves an actual problem where the Wiim app is unusable. You have at least 2 people reporting this problem. So, advantages for everyone, no downside...

The old "works for me" reply, I see 😉 It used to work for me, too. Now it's hit and miss (Android). IT works from another Android device. Still, it would all work much better caching the last address (and running discovery in the background for other devices) How's "using an IP address" in the...

Yes, of course: you can define a static DHCP lease for the WiiM. But how the WiiM gets a static address is irrelevant, that's not the issue. The WiiM app doesn't allow you to enter a static address to find the device at. It lets you set the device as a static address (so clearly they support the...

I'm sorry, but this is completely wrong. Yes, mDNS by itself won't traverse vlans, but with any type of redirector or smcroutes, it does. My network works for any other device and app, excluding only the WiiM Home app. Everything else, including the WiiM when acting as a Chromecast, Alexa Cast...

I sure don't need UPnP nor want it 😁 It's the Android WiiM Home app that wants it, at least according to WiiM support and starting from a few releases back. My network and the WiiM app were working well with just mDNS reflector enabled, until it started not working anymore. As I said, that's...

Not the original poster, but I have the same problem (has gotten worse lately, for a while everything worked, then something changed in the WiiM Home app, at least for Android) I have a main lan and an iot vlan. The main lan can access iot (and wan), but the iot lan cannot access main lan, only...

The WiiM home apps works from the iot network, but I don't want my smartphone to be in that network (as a matter of fact, I need to change settings on the router to allow my phone to log there, so it's not something I can do every time I need to log onto the WiiM). The WiiM home app also works...

No, the iot network has full internet access. And, in any case, when it's not working, the Andoid WiiM app is on the main lan (the WiiM Home app works anyway on the iot network).

I tried thinking about that, too. The firewall rules are to allow any new traffic from main lan to iot lan, any established traffic across both networks, to allow mDNS traffic (UDP 5353) and the Avahi reflector is enabled. I cannot enable unrestricted traffic from iot to main lan, because that...

This is now offtopic, but Alexa listens all the time. It should only recognize the wake word, and only start recording when the wake word is recognized, but that is not a hard guarantee. After all, there are many ways to misinterpret something as a wake word, especially with non-native English...

To be clear: it is connected to the same network, just a different IP range. But it's all one network, and every service works across all IP ranges. All other devices and even the WiiM services can be found by all other apps and the Bonjour browser. It's just the WiiM app that has problems...

You are right: Alexa Cast doesn't listen. Alexa does. My problem was that I was logged into the Amazon Music app, and also needed to be logged into the Amazon Alexa app. The WiiM app lists all services in alphabetical order, starting with Amazon Music. But, for reasons I can't fathom, Amazon...

You mean, "not signing to Alexa" like this? 😁 If you never signed up for Alexa, when you click on the Alexa icon in the Amazon Music app, that's what you get And in any case, even if I wanted to sign in to Alexa, that still doesn't let me manage the rest of the WiiM functions