I just installed 5.0beta1 on my RB750.

Does SSTP listen on IPv6? It does not seem to. If not, is this planned for a future release? I was really hoping for this.

I assume IPv6 over the SSTP tunnel works because the changelog says IPv6 over PPP is supported. Yes?

IPv6 over SSTP is possible. Make sure that ppp profile has "use-ipv6=yes"

Ok, I have IPv6 working over SSTP. But what about the first part of my question, does SSTP listen on the IPv6 addresses? Can I connect to the SSTP server using IPv6?

Currently you can't connect to the router using IPv6 address. This feature will be added in future versions.

Currently you can't connect to the router using IPv6 address. This feature will be added in future versions.

Thanks for the reply, I appreciate it.

Currently you can't connect to the router using IPv6 address. This feature will be added in future versions.

Can you provide us with some kind of time frame for that? Currently I am stuck in a IPv6-only network and it would be really helpful, if I could SSTP VPN to my infrastructure over IPv6.

Thanks.
Nejc

Currently you can't connect to the router using IPv6 address. This feature will be added in future versions.

Is there any updates as to when it's expected to be able to connect with SSTP using the IPv6 address?

More and more external addresses are on IPv6.

Thanks
Philippe

Would it be possible to get an IPv6 roadmap?

This and many other IPv6 related features seem to just get ignored.

Hallo,
I plan to run sstp via IPv6. Is there any progress in the problem.

Currently you can't connect to the router using IPv6 address. This feature will be added in future versions.

This appears to still be an issue that also applies to normal L2TP road warrior VPNs.

Would it be possible to get an IPv6 roadmap?
This and many other IPv6 related features seem to just get ignored.

Yup, really needed. Set a calendar invite w/your team MRZ and get the community a formal update on all things IPv6 at MikroTik. A lot of threads lately about the feature parity that needs to be addressed.

Currently you can't connect to the router using IPv6 address. This feature will be added in future versions.

may we have this also for L2TP?
we need this really badly as our deployment will be run on IPv6 using LTE as backhaul.

Currently you can't connect to the router using IPv6 address. This feature will be added in future versions.

This was 7 years ago. How future was that version you were talking about MRZ?

Currently you can't connect to the router using IPv6 address. This feature will be added in future versions.

This was 7 years ago. How future was that version you were talking about MRZ?

I just tried it in CHR 6.41rc and . . . it stiiiil doesn't work.

I was talking to Janis at MUM 2017 about the inability to do 464XLAT due to the lack of Stateful/Stateless NAT64. He suggested that we tunnel across native-v6 space to deliver IPv4 CGNat, which sounded good, and I seem to recall his mentioning SSTP as a possibility for the tunneling protocol, but alas I must be mistaken. (Or else he thought I meant to tunnel v6 to the CPE using SSTP over IPv4)

Obviously GREv6 / EoIPv6 would work, but I'd rather have something that works on profiles to maintain some degree of central (AAA-based) control over which devices may connect to the central box.

Currently only tunnels you can use for transporting IPv4 over IPv6 is EoIPv6 Gre6, and IPSec

... and for the sake of completeness for anyone else reading the thread, IPIPv6 tunnel also works for transporting v4 over v6. (just tested to make sure)

Currently only tunnels you can use for transporting IPv4 over IPv6 is EoIPv6 Gre6, and IPSec

Given that this thread started quite a long while ago and Mikrotik's position was that SSTP over IPv6 was going to be implemented in the future - is there any chance that this might make the features road map after v6.41 is finalized. I know that the HW forwarding changes are probably consuming lots of time and effort over there, but IPv6 really does need to taken seriously.

Most likely new IPv6 features will not be added in ROS v6.

Most likely new IPv6 features will not be added in ROS v6.

Thanks for being forthright about that. I do hope that ROSv7 reaches beta soon, in that case. I can't even remember all of the things that are promised to be fixed in v7, but it's a lot, and much of it in the IPv4 side of the house. Mikrotik is such a fantastic product in so many ways, I hate to see such a shocking gap in feature parity where IPv6 is concerned. I can use a Mikrotik to do damned-near anything I can imagine in IPv4 - their utility as a troubleshooting tool, workaround tool, execellent low-cost CPE, etc is mind boggling. In IPv6, though, all of that goes right out the window.

My company is a complete Mikrotik shop for CPE except stuff that Mikrotik doesn't do, such as VoIP ATAs / DSL modems. I'm getting ready to focus on rolling out production IPv6 to the customer base. We've had the protocol operational for years on our core, but never have started delivering it as part of the daily production. We're actually fortunate enough to have enough IPv4 address space left to continue operations in a native dual stack model if need be, but many users on here aren't so lucky, and without any advanced functionality in IPv6, Mikrotik really loses its edge as "the lowest cost MPLS-capable router anywhere."

This saddens me, but I keep hoping that things will improve on this front.

Most likely new IPv6 features will not be added in ROS v6.

Thank for the honest feedback. At least I know for certain I do not need to watch the RC patch notes anxiously. I'll continue to ask but know that myself and others require IPv6 support. Without it I cannot recommend your product for anything past layer 2. That requirement will not change and others in our situation will only grow.

With that most likely your sales will decline. Might want to ask your boss if you should be updating your resume on LinkedIn. Alternatively, your company could get serious about building products customers need instead of spending time developing a product only you want.

6.0, 2013-05-20

Not sure when 5.0 was released. Change logs only have 5.7 at 2011-10-18. I'd say 7.0 is overdue. Your company may want to start thinking about providing a more public roadmap than "it's coming." If you want to retain customers otherwise I'll likely fall pray to only checking out your products and software out once or twice a year if I remember to.

SSTP through IPv6 seems till doesnt work (IPv6 through SSTP ok) The error message is in translation (I got hungarian message from Windows 10): "the connection has failed becouse, the target computer has refused the connection.". IPv6 firewall is open at dedicated SSTP port, the counter is rising, when I try to connect. With IPv4 it works, certification and URL is right.

We dont need fairy tale about the miracle ROS7. Should be fix it and Webproxy IPv6 support too in ROS6.

The are 6.44.7 where is support of some tunnel over ipv6?

The are 6.44.7 where is support of some tunnel over ipv6?

GRE6, EOIP6

I have tested until 6.45.5 and there is a confirmed bug that sometimes just drop big packets.
I did not have tested with 6.45.7 yet.

You can also run regular IPsec or IKEv2 over IPv6.

There is a year 2022 ...it is long and very very old /maybe ancient/ thread about very simple question.
Is any news in yr 2022 ???

SSTP with IPv6 peers ??? some ETA ??

we tried version 7.2.3 on our seminar now, without success

we tried version 7.2.3 on our seminar now, without success

Oh my gosh. That can not be serious. This implementation and bug-fixing policy by Mikrotik is that what i hate the most. There is no possibility to use that devices for professional purposes. But the hardware is able to. Only the software is leaking of features and is far behind the possibilities.

Sorry guys, but why is nobody creating a bsd or unix open source routing software for those boxes?

Waiting for BGP-ECMP since years! Sorry guys, where is the problem?

If you guys at Mikrotik are not able to do basic stuff for networking in your software, so release the source-code to the public so we can work all together. By the Way: You are using GPL Code in your products, so in the last you have to bring your source-code available to the public.

GPL code is already publicly available.

Waited for years...

I did this:

internet>>(ipv6)>>ros>>(ipv4,ipv6)>>host

run socat on a ipv6 ready host in lan. forward ipv6 sstp request to ros by ipv4.

today I found that sstp server already supports connection via ipv6 by ros v7.9.1

sstp client is also available, but the domain name pointing to ipv6 cannot be used, and it will resolve failed. only use ipv6 addresses directly.

Since I use ddns, I'm just using a script to temporarily solve this problem
This is just a code snippet. update sstp server address will cause the connection to be reset. You also need to judge whether there is a change based on your environment.

Overall not bad