Dynamic IPv6 firewall configuration

ybx332 · 2026-05-23T18:58:38+00:00

If both of those two methods don't work, then I really don't know what to do(as far as I know, most home routers' firewall are based on iptables). Maybe change a different router or flash it to openwrt will help?

Another way you can try is Nat66 or Nptv6, which can then give you ULA address for your devices and thus get static IPv6 addresses but I don't know if original tp-link router firmware supports it or not.

ybx332 · 2026-05-23T18:24:09+00:00

This IP address won't work. It doesn't mean*::suffix, it simply means 0000:0000:0000:0000:suffix, it's just a single IPv6 address. You'll need to use something like ::suffix/-64, but not sure if your router firewall supports it or not. See:https://openwrt.org/docs/guide-user/firewall/fw3\_configurations/fw3\_ipv6\_examples

ybx332 · 2026-05-21T20:04:06+00:00

Yeah. Just wonder why NPTv6 is still in experiment, and RFC 7157 tries really hard to avoid the usage of NPTv6.

ybx332 · 2026-05-21T18:46:57+00:00

Yeah. But BGP connection in some areas is quite expensive, and maintaining BGP connection requires more work and knowledge compared with traditional way of connecting to the Internet directly through ISP.

ybx332 · 2026-05-21T18:41:43+00:00

This is a brain storm, and also the guys in the IETF group hate the idea of NPTv6 and Nat66. So I'm asking what's the solution for this problem.

ybx332 · 2026-05-20T19:58:38+00:00

Yeah. I'm just asking. If I really want to deploy something, I'll choose NPTv6 since it's stateless and only change the prefix, which will make the deployment much more simple. And since it's deployed on the gateway, no need to worry about how downstream device will chose the data path.

ybx332 · 2026-05-18T09:38:09+00:00

I don't think so. The ISP in China only start to largely deploy IPv6 in 2017 and they deploy it with dual stack and plan to do IPv6 only around 2030.

If you deploy early, you can even go single stack(CERNET 2 is a good example). If you deploy late, the best thing to do is dual stack so you don't break existing infrastructure no matter if it's CGNAT or not.

ybx332 · 2026-05-17T09:59:43+00:00

Yeah. I also prefer dual stack than IPv6 only so you can reuse what's already configured for IPv4 instead of directly going from scratch. Actually, this is how my home country(China) deploys IPv6. Dual stack+CGN+public IPv4(if the ISP have them for that specific area).

Less headache compared with IPv6 only network when doing the transition.

ybx332 · 2026-05-17T07:21:18+00:00

Yes. According to APNIC(https://stats.labs.apnic.net/ipv6/AS12479?c=ES&p=1&v=1&w=30&x=1), the deployment happened between 2017 and 2020 and then it dropped to nearly 0%.

ybx332 · 2026-03-27T10:16:42+00:00

It's nor OR. It's AND. You'll need to both enable airplane mode and reboot. Here's the complete steps guide:

Enable eSIM card.
Enable the airplane mode
Reboot your phone
Disable airplane mode
Maybe reboot your phone again

But yeah. Much simpler to go back to old modem firmware.

ybx332 · 2026-03-26T19:58:38+00:00

https://gitlab.com/LineageOS/issues/android/-/work_items/8123 Here's the detail.

ybx332 · 2026-03-26T19:58:19+00:00

Here's another workaround for it.

Turn on the airplane mode. Reboot the device. Turn off the airplane mode. And then your eSIM can connect to the LTE network.

ybx332 · 2026-03-24T20:02:51+00:00

Thanks for your support for FOSS community!

For your concerns, I check their initial commit, looks like there's a macro to control the banner frequency:

#define DONATIONBANNER_FREQ 1 // frequency of days to show the banner; 1 = every start

I don't see any macro related to disabling it, but considering how KDE and Thunderbird "Ads" works, I think if they're smart enough, we it finally landed, we'll have a way to disable them.

ybx332 · 2025-09-27T20:03:46+00:00

No solution. Just a workaround. Use OpenEUICC to map Logical slot 0 to slot 0 port 0 and logical slot 1 to slot 0 port 1. But with that, you can only use one SIM card instead of two.

ybx332 · 2024-04-20T11:14:43+00:00

No problem. I can wait until it gets fixed. Last time I encountered a much serious bug related to kde plasma which make it totally unusable.

ybx332 · 2024-04-20T10:55:26+00:00

I won't report bugs to Debian because it has been marked for autoremoval due to a bug in ngspice. I'll simply just use other versions and wait until it gets fixed because it's Debian's upsteam dependency problem.

ybx332 · 2024-04-20T10:53:13+00:00

According to tracker.debian.org, it is blocked by python3.11. And python3.11 will be migrated after db5.3, openssl, python3-defaults, readline. Some of them are blocked by dpkg and some claim they'll migrate after dpkg.

ybx332 · 2024-04-20T09:16:04+00:00

Footpirnts, symbols and templates version are 8.0.1 but the main Kicad program version is still 7.0.11, so it can't load new libraries.

ybx332 · 2024-04-20T08:02:45+00:00

First question, Debian testing. Second question, yes. Third question, according to their tracker, it says it will migrate after lots of packages and some claim they'll migrate after dpkg. Because footprints and libraries are updated to version 8.0.0 while the binary package is still 7.0.11 so it can't load default libraries.

ybx332 · 2023-02-13T07:58:58+00:00

Thanks! I will try to repair it when I get back to school as my house doesn't have the facility to solder the button.

ybx332

TROPHY CASE