mConnectHD no longer sees Bridge II

I actually have my wired and wireless clients on the same subnet / LAN segment. I use DHCP relay in the screenshot I highlighted above. I temporarily changed my DHCP mode to DHCP server for the screenshot, as I assumed that’s how your screen might appear.

I’ll give it a try (once my wife is done with work for the day - don’t want to mess her up!).

Tried it. It was already set as shown, so it was a no-go.

I’m starting to think the way to get this to work is to set up firewall rules in the router to allow one interface to see the other.

So here’s the weird thing. I can, from the same iPad that my music apps are on, successfully ping the Ethernet wired IP address of my (as an example) SB Touch. I can ping it (remember, it’s on another subnet), but none of my apps can see it.

I guess ICMP is allowed across subnets while TCP and UDP are (normally) not.

It just gets weirder and weirder.

I threw up my hands and bought a Netgear WAC510 access point. Hooked it up to my wired network switch. Set it up quickly, and switched my iPad to that SSID. No access to my wired devices. I checked the assigned IP address of the iPad to discover that it was connected, but its IP address was not on the same subnet of my wired network, nor was it on the subnet of my other (primary) wireless LAN.

Here’s where it gets weird. I switched my iPhone to this new SSID, and boom! it got an IP address assigned to it in my wired subnet, and hallelujah I could see my DS Bridge II from mConnect. Both my iPhone and my iPad are at the same iOS version, and both are 2.4GHz and 5GHz capable. I powered cycled the iPad to no avail. It seems it will not get assigned a proper IP address.

Success! I had to flush the iPad network stack. Forgetting the network didn’t work. I now have my music apps up and running! :grinning:

2 Likes

Great to hear you got it going! Crazy networking stuff like this is why I never claim to be a networking expert.