The IPv6 package is installed (or included on bundle package)?
The IPv6 package is enabled?
a) The router must be configured to receive, on some way, IPv6 address to redistribute it internally.
b) On your os just do not touch nothing, if all is configured correctly on RouterOS, the PC receive it’s own IPv6 by SLAAC.
ipv4 works
ipv4 does not have recent MT vulnerability
ipv4 on MT works well, ipv6 they seem to be playing never ending game of almost there…
IPv4 has NAT and devices are not accessible from anywhere on the internet … ( waiting for ipv6 security experts to explain why this is not an issue )
I concur MRZ, was just being provacative. NAT is a byproduct not a measured approach.
Not having ventured in IPV6 space, i have severe trepidation of the unknown.
[quote=dryzonked post_id=1003369 time=1684729163 user_id=217483]
Detailed and easy to understand steps to solve this problem. Thank you for sharing your answer
[/quote]
If that’s detailed enough for you, maybe you can make it detailed enough for me? How do I make the router receive IPv6 address to redistribute it internally? Or no further steps are required? It just receives and redistributes it after installing and enabling the ipv6 package?
[quote=xyuri post_id=1003885 time=1684885932 user_id=193669] [quote=dryzonked post_id=1003369 time=1684729163 user_id=217483]
Detailed and easy to understand steps to solve this problem. Thank you for sharing your answer
[/quote]
How do I make the router receive IPv6 address to redistribute it internally?
[/quote]
If you want to distribute IPv6 addresses in LAN, then router gas to obtain a prefix. Which is done by running DHCPv6 client and it has to request a prefix (not address). Then assign an IPv6 address from pool to LAN interface.
Could you elaborate? I don’t see much difference in configuration capabilities as a home-user.
Here is the aggregate of ipv6 changes for v7:
!) ipv6 - fixed DNS server processing by IPv6/ND services (CVE-2023-32154);
*) ipv6 - added “valid” and “lifetime” parameters for SLAAC IPv6 addresses;
*) ipv6 - send out RA packet with “preferred-lifetime” set to “0” when IPv6 address is deactivated;
*) ipv6 - added “pref64” option configuration for RA;
*) ipv6 - improved handling of “advertise” IPv6 address status changes;
*) ipv6 - limited “hop-limit” parameter value range to 255;
*) ipv6 - made distributed DNS lifetime RFC8106 compliant;
*) ipv6 - do not generate LL addresses for VPN interfaces when IPv6 is disabled;
*) ipv6 - do not use invalid/disabled global addresses for IPv6 ND;
*) ipv6 - fixed system stability when adding/removing IPv6 address;
*) ipv6 - added “ra-preference” parameter support for RA;
*) ipv6 - fixed dynamic non link-local addresses displaying;
*) ipv6 - removed bogus commands from IPv6 neighbors menu;
*) ipv6 - do not add duplicate dynamic prefix when static already exists;
*) ipv6 - fixed “retransmissit-interval” unit value;
*) ipv6 - fixed VLAN tagged PPPoE packet receiving on RB5009;
!) support for IPv6 NAT;
!) completely new IPv6 stack;
!) support for IPv6 ECMP and VRF (including VRF-lite);
!) support for IPv6 recursive routing and policy routing;
Perhaps many of these fixes are due to “completely new IPv6 stack;”. What does the latter imply practically? Would love to learn about your experience.
IPv6 configuration on MikroTik is actually too simple and minimalistic for my taste. No RA-Guard for example. No explicit ALG configuration for NAT66/NPTv6 use-cases, even though I hate both.
But the OP needs to first learn to walk, before trying to run. Meaning OP, start by learning IPv6 fundamentals.
why would its (ipv6) development need to build that? won’t it against its own development spirit - which is every device will have its own ip and reducing the router numbers? (read : to overcome ipv4 exhaustion).
NAT66: probably requested by those who are used to the NAT perspective on IPv4 who can’t understand what IPv6 was studied for…
NPTv6: required by those (business users) who do not have their own AS,
but have multiple lines for their offices and want to keep the internal IPv6 configuration if one of the multiple IPv6 WANs goes down,
or, if the provider is changed, is not requested the change of internal IPv6 addresses.
So, NAT66 or NPTv6 is not required for normal end users.
supposed you were right, but won’t that lead us back to the old ipv4 mind set?
@rextended,
[]
if the provider is changed, is not requested the change of internal IPv6 addresses
[]
yes. this is exactly what has been holding ipv6 first deployment spirit. even though there are similar scope for ipv4 private address. but back then, this private ipv6 can go nowhere but local → and now nat66/npt6.
The problem is that these protocols often seem to have been studied by those who don’t work there.
If each company had its own public pool, independent of the ISP/AS, the route table, which currently has ~1,000,000 just for IPv4,
would become so gigantic that it would be unmanageable…
Therefore, if the company changes provider, it cannot keep the IPv6s, but would be forced to exchange them everywhere.
That’s why NPTv6…
[quote=xyuri post_id=1003885 time=1684885932 user_id=193669] [quote=dryzonked post_id=1003369 time=1684729163 user_id=217483]
Detailed and easy to understand steps to solve this problem. Thank you for sharing your answer
[/quote]
If that’s detailed enough for you, maybe you can make it detailed enough for me? How do I make the router receive IPv6 address to redistribute it internally? Or no further steps are required? It just receives and redistributes it after installing and enabling the ipv6 package?
[/quote]
It (partly) depends on your ISP. There are different ways of handling IPv6 and some ISPs do not understand it and give you only 1 subnet, meaning you cannot redistribute it internally.
Look in your ISP documentation (probably via their webpage) to see what techniques they use and what kind of IPv6 range they assign to you (/64, /60, /56, /48).