Can't connect remotely via Android

[GrimReaper 4739]

4 minutes ago, Morphium said:

Now it's working on mobile connection.

 

Just now, Morphium said:

Yes! That works!

You should be settled then, everything working. Well done. 

[Morphium 5]

Just to summarize, so that I understand. The problem is still, that I have a non-static IPV4 address and somehow the mobile browser is not directing to the IPV4, only to the IPV6 address? So if I want to give remote access to someone, he also needs to make sure that IPV6 is enabled as APN?

And if I don't want to have this struggle with people remotely accessing (I plan to move from Videostation to emby and there are around 20 users) I need to update my internet plan to a static IPV4 address?

And BTW: Is it important for you, whose post I mark as a solution? As it was a combined effort of you and Q-Droid.

Either way: Thank you so much!

Edited June 3, 2025 by Morphium

[GrimReaper 4739]

For me, main question there would be why Synology DDNS did not resolve that to IPv6 adress in one instance and did in another. 

You shouldn't have to give your address to anyone, domain name should be sufficient (though as said, all devices in the chain need to support IPv6 protocol). 

Obtaining static IPv4 address might alleviate some of the issues you'd likely face down the road with users that don't fulfill above criteria, so it is always a viable solution. 

And no, of course it doesn't matter which post do you mark as a solution, we all like a good challenge, none (I suppose) of us is here for the points, but providing asistance/support when/where/if we can. Feel free to mark Q-Droid's post. 

Edited June 3, 2025 by GrimReaper

[Morphium 5]

6 minutes ago, GrimReaper said:

For me, main question there would be why Synology DDNS did not resolve that to IPv6 adress in one instance and did in another. 

Yes, that is strange indeed. I'll probably post the question in a synology forum to get to the ground of it.

[Q-Droid 989]

I confess to not having read every single post but what I gathered from scanning them is that your ISP is not giving you a true public IPv4 address? You might be stuck with IPv6 only for remote access if this is the case unless you want to put in place a VPN/tunnel solution. If you are getting a public v4 IP then make sure DDNS is getting updated frequently enough to avoid long gaps between IP changes.

 

Edited June 4, 2025 by Q-Droid

[pwhodges 2012]

8 hours ago, Q-Droid said:

You might be stuck with IPv6 only for remote access if this is the case unless you want to put in place a VPN/tunnel solution. 

They're "stuck with" a modern and simple answer - why would they want to use an outmoded and complicated alternative?

Even though the solution has been to use the IPv6 address (which the DDNS is giving out anyway), I feel frustrated that the conversation seems to view this as an oddity and only the true IPv4 as somehow "real".  IPv6 has been around for a couple of decades now, though the take up has been remarkably and sadly slow - I've only had it at home for 10 years now, and the university I worked in at that time didn't implement it for a couple of years after that! IPv6 was invented with the specific intention of removing the need for NAT and all the complication of address manipulation, and the restrictions of cgNAT, and yet people still try to avoid it - even when it's simply the answer.

This is why I've started suggesting it as an answer to cgNAT.  But sadly there are still too many ISPs who can't be bothered to offer IPv6 - but perhaps at least when asking them how to remove their cgNAT restriction, asking about IPv6 should be part of the conversation.

Paul

[Q-Droid 989]

I don't disagree. People have their reasons for wanting to stay with v4 even though v6 is better and the way forward. It seems to be working for the OP so count them as one more convert.

 

[Morphium 5]

Haha, it doesn't really matter what I think. Before yesterday, I didn't know what IPV4 or 6 is. But when my new Samsung phone on default settings has IPV6 disabled, people obviously have to work with IPV4 or go through a 50 post thread of which they understand only half of.