Nest wifi will not pass DLNA/uPnP

[Mouldy]

Just got a Humax recorder and you can watch recordings using DLNA.  This works fine over the ethernet connection but the Nest wifi is not passing it,  So for example vlc on my Mac will not see the recorder if I use wifi  but will if I connect using ethernet network.  The two networks are on different subnets.  

uPnP is "On" in the Google Home app for the Nest wifi network.

Any suggestions?  

The recorder is also connected to both Ethernet and wifi ok.  I even made wifi mask 16 bit  so both subnets should be visible

[Mouldy]

I have now tried unplugging the ethernet from the recorder so there is no conflict of traffic and it is on the same subnet.  Still no joy.  I can ping the recorder ip address from the Mac.  Just cant see the DLNA server. 

[Mouldy]

and one last note, in the Google Home app, I can see the recorder sending and receiving data over the wifi network

[olavrb]

How is everything in your network connected? Do you have multiple devices acting as NAT router and DHCP? Why do you mess with the subnet mask on the Nest Wifi? Will you ever get close to ~250 connected devices? If so, Nest Wifi, or any other AIO home mesh system, is probably not the solution for you.

I think you are overcomplicating it. Keep it simple and stock. Bridge any modem/ router combi box in front of Nest Wifi. And connect all devices behind the primary/ master Nest Wifi to avoid NAT in between.

One more tip is to set ip address reservation for things like NAS, speakers/ Chromecast.

• https://support.google.com/googlenest/answer/6274660?hl=en

[Mouldy]

I tried the mask so that it could "see both subnets".  Ethernet is 192.168.1.x  and Google has chosen 192.168.86.x for the wifi.  Dont think that is the issue though as I can ping the box.  Also if I unplug ethernet from the recorder device so both Mac and recorder are on same wifi and so same subnet, it still cant see it.   I wonder if its an issue with vlan player.  However iphone can also not see it as a dlna server if I use something like "8player".  Very odd.

router  --- ethernet1 -- GoogleNest wifi (198.168.86) ....Macbook, phones, tv2

        --- ethernet 2 - Mains ethernet (192.168.1.x) ..  Recorder, Mac, TV etc       

[olavrb · Accepted solution]

Your problem is that you are using multiple of the ethernet ports on the router in front of the Nest Wifi. And the fact that the ethernet ports on the router gives private IP addresses (RFC 1918) tells us that you haven't bridged it.

Nest Wifi itself is also a router, with NAT, DHCP, firewall and access point. Bridge the router/ modem, else you'll have double NAT.

• https://support.google.com/googlenest/answer/6240987?hl=en

Put all devices behind Nest Wifi, it too has a LAN port. If you need more LAN ports, add a unmanaged switch to the LAN port of the Nest Wifi router:

• https://support.google.com/googlenest/answer/6274262?hl=en

[Mouldy]

Ok have done that as it seems a good idea.  Still didnt work.  

Since I have very few devices on the ethernet, I have unplugged the recorder from Ethenet so it only sees its wifi.  It is connected.   Mac now also on the same wifi network.  Still cant see the server.  I can still ping the recorder wifi IP address from the Mac wifi connection.  

Thanks for your help.  My network knowlegde is very sketchy  lol

[Mouldy]

Now with both ethernet and wifi via the google nest networks, switched the Recorder off and on and it saw the wifi and ethernet, it IS now showing over both networks from the Mac.

Thanks for your help on this.

[olavrb]

Sweet! Happy to help. 🙂

[Jeff]

Hi, Mouldy.

It looks like olavrb was able to sort this one out with you. I'm happy to see things working fully for you. I just wanted to check in to see if there's anything else you needed or if you're all set here. Let me know if there's more I can do.

Thanks.

[Jeff]

Hi, all.
As we got our resolution here, I'm going to mark this one as resolved in the next 24 hours unless anyone needs anything else. Thanks to all who helped and contributed. If anyone has any other needs, please let me know.
Thanks!

[Jeff]

Hi, everyone.
As we haven't had any activity here recently I'm going to go ahead and close the thread. If you have more to add, feel free to start a new discussion.
Thanks