I’m trying to setup my Mikrotik the best way, and I’m satisfied with it… Unless by the fact IPv6 doesn’t work properly.
I already setup, and Mikrotik sees my IPv6, I can ping out from mikrotik, etc. My devices connected also gets his IPv6… Until my session PPPoE renew itself (my ISP force the session to renew automatically every 48h), in this case, Mikrotik gets a new Prefix, but it is NOT advertising to my network (until I force it releasing and renewing on device).
When it happens, if I try to ping out (an IPv6 adress) from Mikrotik, it replies perfectly. If I try on my wired computer, it doesn’t! (as I said, unless if I reboot the computer, or disable my ethernet, and re-enabling later).
I really don’t know what can I do to fix this. It’s the only problem I didn’t fix yet.
P.S.: if I turn off my Mikrotik and create same scenario in my Archer C7, everything works FLAWLESSLY. Even if the PPPoE renews, devices automatically gets new IPv6, everything works.
Ir will take some time before a changed address is noticed.
The address can be “dynamic”, but really it isn’t supposed to change every day or two days.
When you cannot convince the ISP that this is unreasonable to do, try to disconnect your line (using schedule and script)
in the middle of the night so you won’t have the interruption during the day.
After the mentioned validity times have elapsed the new address should work OK.
I got what you said. I could do what you say, but I’d like to see mikrotik working as it’s supposed to do.
As I said before, when I’m using OpenWRT, if the connection automatically renews, it leases automatically the new IPv6 to my network.
If I force it to renew, it also leases equaly said above.
You have to keep in mind that for MikroTik IPv6 is the stepchild that receives very little attention.
A lot of features are lacking in MikroTIk IPv6 and it may well be that this is one of them or that it has bugs, and that OpenWRT works better.
At my ISP I have a “fixed” address (it can change only when required for network management reasons) and it works sort of OK.
I was thinking about all this stepchild problem. I believe some problems will not be solved until V7. Not because of lack of interest from Mikrotik, but because their kernel is ancient. The IPv6 support on Linux kernel improved quite a lot in recent years. We may be seeing just this…
I understand you, I really understand.
But, as a new user, I tried to discover the mikrotik-world. I’ve been studying the RouterOS by the 3 last weeks… I had Archer C7 with OpenWRT and everything was alright, I just tried to take this on mikrotik, my willing is to buy the hAP AC².
In my case, if my connection do not drop by whatever reason, everything will work… I’ll stuck with it, let’s see if in the future it’ll change.
The kernel in v6 is perfectly able to perform features like requested in the wellknown thread, like policy routing, 1:1 (netmap) NAT, etc.
However there is apparently less interest in making IPv6 full-featured.
I can’t tell about the problem of this topic, it may be a kernel bug that is fixed in a later kernel and I could understand they would not want
to backport that now.
However, when by now there is not yet a completed “forward port” of all RouterIOS-specific patches in the current kernel to the new kernel
planned to be used on v7, we can surely call it will never be delivered. In the meantime of course the kernel development continues
as well, so by the time v7 is released there again will be features missing.
Besides that there of course will be lots of other work, like making this completely-from-scratch BGP and OSPF implementation that will
solve all problems in that area.
Can it? If I remember correctly, ROS6.x uses a 3.6 kernel. It is REALLY old. Although Linux had IPv6 support from 2.4 (I think) onward, only in the 4.x series it really took off.
You are mistaken. You forget that in the old days the Linux version number was increasing slowly, and now
it has adopted the common policy of increasing the version number for publicity reasons rather than architectural changes.
Also, 3.6 is not really old, most of my production systems run 3.2 kernels (+ security patches), some 2.6.32 as well.
I got back to my Archer C7 with LEDE, setup everything as it was on Mikrotik (RB951G-2hND) e everything works like a charm.
I still have the will to buy the hAP AC², but I’m kinda insecure about this IPv6 “issue”, it’s my only trouble with the architecture.
3.6 is from 30 September 2012. 5 and half years old is ancient when we talk about the IPv6 and Linux kernel. The 4.x series started 12 April 2015. Already old hat - and we are past 4.10 now.
Nothing wrong with running a system with good old 3.x - just remember the patches.
Omg, I used to try some things before switch my device, and was trying something like what you post, but your link is optimized. I can’t do the test for now, but I guess it will work. Thanks again!!!
I’ll repost if it works.
The next step is to find some (basic) rules and policies for ipv4 (and ipv6) firewal.
