QUOTE(kwss @ Feb 6 2025, 05:43 PM)
I will offer my perspective from running infrastructure and also address your security hygiene issue.
IPv6 will replace IPv4 whether you like it or not:
1. IPv4 routing table is getting excessively large and fragmented they require hardware with serious amount of TCAM or HBM
2. For dual stack to work, I need 2 copy of routing table, one for IPv4, another for IPv6. For the simplest BGP setup of dual upstream, that's a minimum of 4 routing tables.
4. IPv6 don't need to calculate checksum since it doesn't have one. This is not just about end-user speed, it is about scalability. Very few routing SOC can saturate a port with single stream. The only one I know is Cisco One Silicon and Nokia FP5. This is a deep topic to discuss here. Research run to completion network silicon.
5. It prevent new player from coming into the market. If I decide to start a new ISP, I cannot get anymore new IPv4 address. Even if I am able to get IPv4 address, it will only be a /24 and it cost a fortune. It prevent competition, and network design that does IPv4 simply sucks from this point of view.
6. Running CGNAT cost money. Money in term of hardware and scaling. Money in term of licensing fees. "Money" in term of hardware choice.
7. IPv4 requires all kind of hack like ALG, STUN and firewall hole punching.
Addressing your security hygiene:
The last point above is directly related to why games will give you firewall prompt. They are performing hole punching for you to get a an end-to-end connection. Same happens to any app that makes and receive calls like WhatsApp. If it happen in your web browser, you firewall already allows it.
Not practicing security hygiene will eventually get you pwned. It is not even APT level sophistication.
1. Attack of known patched security vulnerability. Not performing Windows Update falls under this.
2. End user clicking on things. Clicking on unknown thing falls under this. Also include clicking links and running unknown codes. Your kids clicking on prompt to literally disable security. Rightly includes plugging in thumb drive you picked up outside.
Your whole argument with using IPv4 comes down to depending on NAT to protect you. All the IPv6 firewall rules in Mikrotik is to emulate this exact behavior in IPv6. The reason is a legacy one. All RouterOS before 7.2 (Don't remember exact version) do not support NAT66.
If you want to have this exact behavior, a more effective way it still to remove the rules and do NAT66 properly. By doing this, you will also requires all the NAT hack to make your app work. If your app backend don't do STUN and hole punching in IPv6, it will stop working.
Depending on your Mikrotik to secure your family with zero security hygiene is a terrible idea. It is not even an IDS / IPS. It is just a router with very basic firewall capability.
Security hygiene starts with education.
No product can save you from ignorance. Not even IPS.
Same goes to sex education and religion. Refusal to talk about it won't save you.
I understand ipv6 will takeover one day.
Most regular users just their devices, without understanding ipv4 or windows security let alone mikrotik stuff. So most people don't even know what security hygiene is, however, if they are behind a router fw, they have a better chance of not getting into trouble. I'd like to believe i configured my mikrotik ipv4 fw pretty well, reject as default, no passwords, and using non standard ports or otherwise requiring vpn to enter internal network. (maybe i should all methods of remote since i havent traveled for a while). So tell me, where do most people stand when it comes to security hygiene? I can at least understand what you're saying. Others just want to watch movie/game. Aren't most people vulnerable then?
I can have the best practices, weekly audits, immediate os updates but take: CVE-2024-38063 for example. Is it not a severe vulnerability until first discovered and then patched? Who knows for how long exploiters have actually been abusing it. That's only one to name, I saw there were a few other ones in the past. So what do you say to this?
Also, i think its more likely for people to look for vulnerabilities on an endpoint address than first hack a router, meddle with the firewall and then find vulnerabilities on internal addresses, even more so when vlans are involved. altho yes ive witnessed mikrotiks hacked in the past when there was a serious vulnerability... good thing it didnt go any further than that.
but OK, I will look into 'security hygiene'. I'll probably redo all endpoint firewall, get everything up to date... maybe enable autoupdate? (and then windows will rebloat the OS and reset some configuration to default.. and risk bsods with bad updates -- u know this has happened). And then probably write a script to audit each computer periodically and also report via discord bot.... man this is a lot of work. what do you think of this? good enough for hygiene? a plan is better than no plan.