[MAGNOLIA-3758] Request for information. Is Magnolia-CMS ready for IPv6? Created: 11/Jul/11  Updated: 19/Jul/11  Resolved: 19/Jul/11

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: James Dy Assignee: Unassigned
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 2008 / IPv6


Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Hi, we are planning to implement IPv6 in our office environment. We currently use Magnolia and would like to know the answers to the following questions:

1. Is the application known to crash upon receipt of IPv6 traffic?
2. Does the application rely on the Windows XP or Server 2003 TCP/IP stack?
3. Does the application source packets from an IPv4 address within the 127.0.0.0/8 range or any loopback IP address?
4. Does the application contain data structures that limit IP address lengths to 32 bits?
5. Does the application require the use of any hard coded IP addresses?
6. Does the application contain any user interface dialog boxes that only accommodate IPv4 addresses?
7. Does the application use any underlying protocols that have IP-version dependant functions?
8. Does the Microsoft Checkv4.exe utility find any IPv4 dependencies in the application code?
9. Is the application not compatible with the strong-host routing model?
10. Does the application make use of older Windows Sockets functions that do not allow connection by name and/or do not choose the appropriate address automatically? (If new functions such as getaddrinfo, getnameinfo, WSAConnectByName, and WSAConnectByList are used, choose no)



 Comments   
Comment by Jan Haderka [ 12/Jul/11 ]

Hi James you might want to move this issue to a Support project. If you do not have access to support you can request it following the instructions described at documentation

1. Is the application known to crash upon receipt of IPv6 traffic?

No, there are no such reports at this time.

2. Does the application rely on the Windows XP or Server 2003 TCP/IP stack?

Since Magnolia is a web application it relies on web access which is usually realized over TCP/IP, however it doesn't explicitly depend on any windows infrastructure.

3. Does the application source packets from an IPv4 address within the 127.0.0.0/8 range or any loopback IP address?

no

4. Does the application contain data structures that limit IP address lengths to 32 bits?

no

5. Does the application require the use of any hard coded IP addresses?

no, Magnolia offers possibility of restricting access based on the IP address and also allows use of IP address to locate other Magnolia instances as a target for activation, but it doesn't require such.

6. Does the application contain any user interface dialog boxes that only accommodate IPv4 addresses?

no

7. Does the application use any underlying protocols that have IP-version dependant functions?

no

8. Does the Microsoft Checkv4.exe utility find any IPv4 dependencies in the application code?

haven't ran such utility, but I doubt it. The utility checks for dependency on ip4 libraries, since Magnolia is a Java application and doesn't perform any JNA calls it doesn't have any direct dependency on any libraries. The only dependency is via JVM used to run application server hosting Magnolia.

9. Is the application not compatible with the strong-host routing model?

we are not aware of any such incompatibility at the moment

10. Does the application make use of older Windows Sockets functions that do not allow connection by name and/or do not choose the appropriate address automatically? (If new functions such as getaddrinfo, getnameinfo, WSAConnectByName, and WSAConnectByList are used, choose no)

no

Generated at Mon Feb 12 03:49:24 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.