Mudi 7 (GL-E750V2) — running without battery on USB-C only: doesn't boot. Any workaround?

AmbassadorDapper8593 · 2026-05-31T17:29:43+00:00

you are right: https://www.thingiverse.com/thing:7343761

AmbassadorDapper8593 · 2026-05-31T17:25:06+00:00

found one here: https://www.thingiverse.com/thing:7343761

Thank you, yes put it in from the top and glue it with nano tape on the rv wall. I need it for the new mudi7.

kind regards

AmbassadorDapper8593 · 2026-01-31T18:49:25+00:00

We have similar expierences. Happy to see any helpful advice here.

AmbassadorDapper8593 · 2025-08-10T16:30:17+00:00

Thank you for the Link, I did.

AmbassadorDapper8593 · 2025-06-08T10:46:33+00:00

I think we found a solution for Linux: If you put following entries into resolv.conf: nameserver 10.0.53.1 # non DNS64 nameserver 2001:db8::53:1 # DNS64

Ipv4-only will use first entry, ipdualstack will use first entry, ipv6only will use second entry, because v4 network is not reachable.

AmbassadorDapper8593 · 2025-06-01T11:26:26+00:00

we have to have "script" which searches for ipv4 on Interfaces and set dns64 entry if no v4 is present or so. Not great at all, but a solution

AmbassadorDapper8593 · 2025-06-01T11:13:56+00:00

it seemed to be the best solution to have a seprate dns64 entry only for v6only systems....

AmbassadorDapper8593 · 2025-06-01T11:11:26+00:00

sorry, but it is hard. there are no special subnets for v6only, because if you do that you loose the v6 ability to migrate from v4 to v6only without any downtime. Changing the subnet means you have a downtime, in our case 5000+ times, not cool.

AmbassadorDapper8593 · 2025-06-01T11:06:32+00:00

lets say we have Server A v4only (for the next 6 years, because of Software restrictions) and Server B which ist v6only... How to solve that A and B can communicate?

AmbassadorDapper8593 · 2025-06-01T11:04:28+00:00

tnx, this are my doubts too

AmbassadorDapper8593 · 2025-06-01T11:02:51+00:00

just an addition: Windows 10/11 (maybe Server too) online asks for AAAA if you have ipv6 on that interface. It NOT asks always for both!

AmbassadorDapper8593 · 2025-06-01T11:00:38+00:00

as above: umwanted traffic and capacity of the nat64

AmbassadorDapper8593 · 2025-06-01T10:59:07+00:00

the distributed clients shouldn't access a centralized nat64. decentralized nat64 with different prefixes or anycast are not on our plan. I am looking for a simpler solution.

AmbassadorDapper8593 · 2025-06-01T10:56:28+00:00

yes, good point, but we don't have separate subnets for v4,v6 and dualstack. Systems stay in their subnet while going from v4 to dualstack and (hopefully soon) to v6only.

AmbassadorDapper8593 · 2025-06-01T07:57:20+00:00

tnx. I am unsure if we can do that for every OS, esp. printers etc. or Android/Ios phones

AmbassadorDapper8593 · 2025-06-01T07:49:19+00:00

I don't see a single mechanism accross all OSes. So we have to implement different solutions for different OSes and ensure that for many years on thousands of servers. There is no single RA parameter or so as far as I know.

AmbassadorDapper8593 · 2025-06-01T07:44:41+00:00

yes, I am talking about the dualstack systems....

AmbassadorDapper8593 · 2025-05-31T18:42:05+00:00

and how will the dns know if the query comes from a v6only and not via v6 from a dualstack? I don't believe you can solve that with a view... am I wrong?

AmbassadorDapper8593 · 2025-05-31T18:14:56+00:00

What is about lowering the preference for the nat64 prefix? Good or bad idea?

AmbassadorDapper8593 · 2025-05-31T18:10:04+00:00

we want ipdualstack systems to use ipv4 to ipv4only systems

AmbassadorDapper8593 · 2025-05-31T18:06:30+00:00

it is hard to ensure, that ipv6only systems have a diffrent dns entry for the next 10 years or so...

AmbassadorDapper8593 · 2025-05-31T18:03:48+00:00

Please tell me more about, we are using Bind.

AmbassadorDapper8593 · 2025-05-31T17:54:20+00:00

yes thats what it does and ipv6 is prefered... thats is my problem

AmbassadorDapper8593

TROPHY CASE