New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


web GUI from IPv6 client

Votes:

0

Your Vote:

Up

Down

What is the status of IPv6 support for PRTG's web GUI? It seems to only listen on IPv4 addresses. In 2013, this is pretty unacceptable. IPv6 *is* getting used in the real world nowadays.

In a dual-stack environment, listening only on IPv4 means that the browser first tries reaching the web GUI on the server's IPv6 interface, introduces a short wait while this attempt fails, then tries the IPv4 address. Tolerable, but far from ideal.

Worse, this makes it impossible to access the web GUI from a Microsoft DirectAccess client. DirectAccess, being a technology of the modern "cloudy" "borderless" sort of paradigm, does not support IPv4 at all. It can connect to IPv4 servers using the DNS64/NAT64 transition mechanism, but the transition mechanism does not get invoked if the server has an IPv6 address. The client assumes that a server having both address families will provide its service on both, which is a reasonable assumption IMO.

I could disable the IPv6 stack on the server as a workaround... but then what if I need PRTG to monitor IPv6 devices?

I guess I could always install Apache on the server and have it listen on the IPv6 interface and be a reverse-proxy to the web GUI... but that would be an unpleasant hack more suited to 2005 than 2013.

Is there any timeline as to when PRTG will support IPv6 properly (i.e. completely)?

directaccess ipv6 prtg web

Created on Jan 31, 2013 10:09:29 PM by  miken (0) 1



Best Answer

Accepted Answer

Votes:

0

Your Vote:

Up

Down

Sorry, IPv6 support for the PRTG webserver is not on our current roadmap.

Created on Jul 16, 2015 2:35:58 PM by  Daniel Zobel [Paessler Support]



27 Replies

Votes:

0

Your Vote:

Up

Down

From our user feedback we do not at all get the impression that there is an urgent need for an IPv6 capable web server in PRTG. The general usage of IPv6 throughout our customer base is still very very low. Although I agree that it would be great to have IPv6 in PRTG's web server we have to direct our development resources as to achieve the most "bang for the buck" for the product and for the majority of our customers. And in this case we have decided to postpone IPv6 for some time, there is no ETA that I can give you right now.

See my blog article "How We Rate Your Feature Requests": http://www.paessler.com/blog/2012/07/03/other/how-we-rate-your-feature-requests-company-culture-2

Created on Feb 1, 2013 12:47:42 PM by  Dirk Paessler [Founder Paessler AG] (10,869) 3 4



Votes:

0

Your Vote:

Up

Down

Now we're in 2015. Still no plans to make the webserver ipv6 capable? Multiple ISP's are pushing their customers in my country to ipv6 (dual stack). About 30 to 40% of the (first) DNS query's are AAAA instead of A. Feels like I'm betting on the wrong horse...

Created on May 28, 2015 1:51:03 PM by  ikheetleon (0)



Votes:

0

Your Vote:

Up

Down

As you can see, there have been no further requests for a IPv6 capable PRTG web server for over 2 years. That meant, we had to put this on a very low priority, as other features (requests) have been much more popular. We still have it one the list though, and will keep an eye on this thread!

Created on May 28, 2015 7:27:30 PM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

We and some clients would like it to start use ipv6 on the webserver.... is there any ETA?

If supplies are waiting for the customer to start use ipv6 and the customer is waiting for the supplier to support it this is never going to happen.

Google didn't start with ipv6 because people where asking about this.

We have a problem with the web GUI on android since we have IPv6 in our network I can't connect to the web server because it is trying to connect to the IPv6 address.

Created on Jul 13, 2015 1:47:12 PM by  Tim (20)



Accepted Answer

Votes:

0

Your Vote:

Up

Down

Sorry, IPv6 support for the PRTG webserver is not on our current roadmap.

Created on Jul 16, 2015 2:35:58 PM by  Daniel Zobel [Paessler Support]



Votes:

0

Your Vote:

Up

Down

How about the official PRTG mobile app..... we can't connect anymore with the app on andriod because our phones are using IPv6.... some maybe it would be good to support IPv6 on the webserver, this is the future Internet.

Created on Jul 29, 2015 1:28:24 PM by  Tim (20)



Votes:

0

Your Vote:

Up

Down

Well, I was just evaluating PRTG to use it in our environment. However, lack of IPv6 is a show stopper for me. Back to Nagios.

Just to explain why we need IPv6: many of our servers are behind NAT. Sometimes multiply NAT. Accessing them through global IPv6 address is much simpler and faster.

Created on Sep 10, 2015 1:21:16 PM by  michal (0)



Votes:

0

Your Vote:

Up

Down

I would vote for PRTG webserver to begin supporting IPv6 at least on the road map with a goal of the next 12 to 18 months supporting IPv6 as a web host. Any end point on mobile carrier and even residential cable services in the US are going to be very soon IPv6 only at least for new service customers. So if I have a remote probe out there, I need to be able to connect an IPv6 PRTG host. Our PRTG hosts are properly configured for IPv6 on our network already. We are looking to begin monitoring IPv6 devices, it appears that most common sensors already support IPv6 which is great news!

Not having IPv6 web host shouldn't be a game stopper by any means for using the PRTG platform.

Created on Oct 5, 2015 4:42:57 PM by  nellermann (0)



Votes:

0

Your Vote:

Up

Down

Come on guys... it's November 2015. Every web server supports IPv6, time to make this happen.

We've been running IPv6 internally for a while. After finally receiving an IPv6 allocation from our providers we've decided to switch it on for external access to our services.

Imagine our surprise when we found a piece of software, specifically designed for network stuff, doesn't support what is one of the most important things happening in our industry. If we and industry pro's can't do this, how can we expect the rest of the world to?

Created on Nov 7, 2015 3:19:52 AM by  shanecaznet (0)



Votes:

0

Your Vote:

Up

Down

+1

Created on Apr 19, 2016 11:55:02 AM by  Kai (0)



Votes:

0

Your Vote:

Up

Down

Hi, I want to Use the webserver via IPV6. Why this work? Every Year we pay for maintenance... 2011 Paessler says "Wir arbeiten derzeit an der nächsten großen Version von PRTG und diese wird natürlich auch IPv6 unterstützen." Whats going on? I need the native IPV& not an workaround after many years IPV4.

Matthias

Created on Jul 7, 2016 6:37:31 AM by  Matthias Körner (0) 1



Votes:

0

Your Vote:

Up

Down

Matthias, I'm afraid there may be a slight mix-up here. The IPv6-Support announced in 2011 was for part of the available sensors, not the webserver or Probe Connections though.
To explain a bit why this is not yet available, not even 1% (by far) of all sensors in PRTG are using IPv6. So there is very very very little usage of IPv6 in relation to our application, while in turn the development efforts would be so huge to implement IPv6 support for the webserver and Probe Connections. Due to this very skewed relation, we rather invest the development time into features and improvements where much more installations benefit from.
We do of course listen to our users, so should this relation change significantly, we will look into the decision again.

Created on Jul 7, 2016 1:32:45 PM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I would vote for PRTG webserver to begin supporting IPv6.

Created on Oct 30, 2016 5:27:51 PM by  Martin Morken (0) 1



Votes:

0

Your Vote:

Up

Down

Hello,

if you "all" just need to Access the webServer part of your PRTG Infrastructure via IPv6 just bring a Little Reverse Proxy which is 6to4 capable.

We have one Customer with some nice gear from a not named ADC vendor here(Best in Gartners Magic Quadrant) , which is doing quite fine with this stuff. Besides, we loadbalance the Web Access across more than one Core Server, because we all know, PRTG Web Interface is getting slow above a certain number of sensors.

So for example our Customer is working via prtg.domain.com which get loadbalanced accross 3 Core/Failover Server Installations. Since Administration is only allowed via the Primary, we defined prtg-admin.domain.com to get directly to the Primary machine. with this technique we are able to handle user load AND the IPv6 Issue :) because in the backend the PRTG Installation is still ipv4 but the Access for Users is dualstack with ipv6 reachable

Sorry for typos it is late already but saw this article

Greetings Michele

Created on Nov 8, 2016 9:17:50 PM by  Michele Jetz (81) 1



Votes:

0

Your Vote:

Up

Down

I would love to see the Web GUI being available on IPv6.

Created on Feb 7, 2017 10:10:36 AM by  TyzzyT (0) 1



Votes:

0

Your Vote:

Up

Down

We need the Web GUI to be available on IPv6

Created on Jun 15, 2017 8:45:50 AM by  Graham Creek (0)



Votes:

0

Your Vote:

Up

Down

Hello Graham,
thank you for your post.

I'm afraid that this isn't currently an option. You may want to refer to Michele's contribution:

Best Regards,
Luciano Lingnau [Paessler Support]

Created on Jun 15, 2017 12:40:23 PM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

We are trying to make use of the port 5050 push sensor feature, and doing that through nat will be a real nuisance. There is really no excuse to not support ipv6 in 2017. Please fix this.

Created on Jun 21, 2017 12:04:30 AM by  alan (0)



Votes:

0

Your Vote:

Up

Down

Hello Alan, thank you for your reply.

The socket created by the HTTP Push Data Advanced Sensor is completely separated from the webserver and is done by the PRTG Probe, not Core. However, the HTTP Push Data Advanced Sensor is also not IPv6 ready at the present time, but we are aware of this limitation.

Best Regards,
Luciano Lingnau [Paessler Support]

Created on Jun 26, 2017 6:39:54 AM by  Luciano Lingnau [Paessler Support]

Last change on Jun 26, 2017 6:41:01 AM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

+1

I just started deploying IPv6 on my 110+ site network, I would also like to be able to access the website over IPv6.

Created on Jul 14, 2017 10:56:51 PM by  Aaron Lusk (0)



Votes:

0

Your Vote:

Up

Down

It's now August 2017. I decided to give PRTG a go. It all fell apart once I eliminated IPv4 from my testserver. Come on, IPv6 is here to stay, you better get used to it. Sadly, being a newcomer I can't upvote any of the prior comments atm.

Created on Aug 9, 2017 9:35:32 AM by  Ximalas (0)



Votes:

0

Your Vote:

Up

Down

Hello Ximalas,
thank you for your reply.

There may come a point where the current webserver engine is replaced, that could mean that a new webserver with ipv6 could be implemented, but we're unable to provide any details/confirmation at this point.

Best Regards,
Luciano Lingnau [Paessler Support]

Created on Aug 9, 2017 12:00:45 PM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

So we finally get the real reason why, your webserver engine doesn't support it... I think it is time to upgrade.

Created on Sep 6, 2017 1:00:58 AM by  Aaron Lusk (0)



Votes:

2

Your Vote:

Up

Down

As a (temporary?) workaround, you can use Windows Built-in Portproxy to create an IPv6 TCP listener and forward the request to the IPv4 address of the PRTG Core Server.

Execute this on the PRTG Core Server:

netsh interface portproxy add v6tov4 listenaddress=<IPv6_address_PRTGServer> listenport=443 connectaddress=<IPv4_address_PRTGServer> connectport=443
netsh interface portproxy add v6tov4 listenaddress=<IPv6_address_PRTGServer> listenport=80 connectaddress=<IPv4_address_PRTGServer> connectport=80

Don't forget to open the ports in your Windows Firewall (allowing "PRTG Server.exe" is not enough, since that Program only support IPv4, remember?). Also check the "IP Helper" Windows Service is started.

If the Webserver Engine ever is going to support IPv6, you can remove this configuration to prevent port conflicts, with:

netsh interface portproxy delete v6tov4 listenaddress=<IPv6_address_PRTGServer> listenport=443
netsh interface portproxy delete v6tov4 listenaddress=<IPv6_address_PRTGServer> listenport=80

To check the settings:

netsh interface portproxy show all

Listen on ipv6:             Connect to ipv4:

Address         Port        Address         Port
--------------- ----------  --------------- ----------
<IPv6_address_PRTGServer> 443         <IPv4_address_PRTGServer>     443
<IPv6_address_PRTGServer> 80          <IPv4_address_PRTGServer>     80

Kind regards,
Robert

Created on Dec 27, 2017 10:43:11 PM by  RGlintmeijer (20)



Votes:

0

Your Vote:

Up

Down

Thanks for sharing RGlintmeijer!

Best regards, Felix

Created on Dec 28, 2017 7:32:54 AM by  Felix Saure [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Almost mid 2018 and no IPv6 support.

Almost mid 2018 and a clunky and slow almost inusable WebGUI. Maybe PRTG could learn something from Grafana?

We are already thinking on moving to something better supported. It's a shame, we really liked the old PRTG.

Just my 2 cents

Created on May 29, 2018 12:50:23 PM by  Diego Mayan (0)



Votes:

0

Your Vote:

Up

Down

IPv6 is here to stay, and some technologies are only available on IPv6. If you were to use IIS as your web engine the service could be bound to the IP4 or IPv6 interface. PRTG needs modern protocol support.

Created on Mar 7, 2019 12:15:54 AM by  sgratsinger (0)



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.