Additional Interface Support for IPv6

Additional Interface Support for IPv6

With this release, Pervasive PSQL has increased its support for IPv6, the next-generation Internet Protocol version. This section discusses the following topics:

•

Using Pervasive PSQL With IPv6

•

Frequently Asked Questions

•

Pervasive PSQL Utilities and IPv6

For information about implications for application programmers of IPv6 support, see IPv6 Aspects for Application Programmers.

For complete details about IPv6 and Pervasive PSQL, see IPv6 in Getting Started With Pervasive PSQL.

Using Pervasive PSQL With IPv6

Pervasive PSQL v11 SP3 supports IPv6 for the following additional access methods on Windows operating systems. (See also Support for IPv6 in Appendix C.)

•

•

•

•

There is now complete IPv6 support for the following Pervasive PSQL utilities. (See also Pervasive PSQL Utilities and IPv6 in Appendix C.)

•

•

All of these access methods function correctly in an IPv4 environment, an IPv6 environment, or an environment that combines the two. No special configurations of Pervasive PSQL are required.

Client Connections

With any of the access methods listed above, a Pervasive PSQL Client connects using IPv6 to a host running the Pervasive PSQL database engine (Server or Workgroup) the same way as it connects using IPv4. That is, the Client specifies a server either by name or using its IP address and connects through a supported access method.

For a complete discussion of address formats for IPv6, please see the following topics in this document:

•

IPv6 Address Formats

•

IPv6 With UNC Paths and URI Connections

Certain restrictions that applied to IPv6 addresses have changed. These are summarized in the following table:

Table 3

IPv6 Restrictions With Pervasive PSQL

The Pervasive PSQL Server Engine in an IPv6-only environment

The Pervasive PSQL Server Engine is not supported in an IPv6-only environment on Windows Server 2003 or Windows XP operating systems. The Server Engine is supported in an IPv6-only environment on Windows Vista and later operating systems.

If you wish to append a port number to an IPv6 address, you must use UNC-safe notation

The inclusion of a port number with an IP address is necessary only when you need to override the default port. Generally, a port number can be appended to an IP address using either a colon (:port number) or a dot (.port number).

UNC-safe names (see IPv6 With UNC Paths and URI Connections) support the appending of a port number.

Square brackets are required for raw IPv6 addresses when the address is used in a URI or UNC

Raw IPv6 addresses, abbreviated or not, must be enclosed by square brackets if the address is used in a URI or UNC.

•

btrv://czjones@[2001:b1::23]/demodata

•

btrv://abanderas@[2001:12:34:56:78:90:12:23]/demodata

•

\\[2001:12:34:56:78:90:12:23]\acctsvr1\Domestic\file.mkd

Failure to bracket the IPv6 address results in status code 3014 or 3103 for Btrieve calls using a URI, or status code 11, 94, or 170 for Btrieve calls using a UNC.

In a URI, if you include a ZoneID to a server address, the “%” ZoneID character must be escaped with “%25”

If you use a btrv:// connection with an IPv6 address, you must escape the ZoneID for the host name. Zone IDs are usually required with IPv6 Link Local numeric addresses.

A UNC-safe addresses like

btrv://@[fe80::20c:29ff:fe67:2ee4%4]

must be changed to

btrv://@[fe80::20c:29ff:fe67:2ee4%254]

License Administrator (and clilcadm)

The Pervasive licensing server does not yet support IPv6. Because of this, you can use License Administrator over IPv6 to administer licenses but you cannot authorize a license with the utility. To authorize a license, you must use an IPv4 network, remote authorization, or telephone authorization.

Frequently Asked Questions

The following table answers some frequently asked questions (FAQs) about IPv6 support for interfaces in Pervasive PSQL v11 SP3.

Table 4

FAQs About IPv6 Support for Interfaces

Is the fact that PSQL Clients will now have both IPv4 and IPv6 addresses going to lead to confusion over how many licenses I should have?

No. This is not a new situation. In the past, Clients have sometimes had more than one IPv4 address. Pervasive PSQL has handled the situation by recognizing all of the addresses of a machine to identify it. PSQL will follow the same logic for multiple addresses using more than one IP version.

What formats should I use for IPv6 addresses?

See IPv6 Address Formats and IPv6 With UNC Paths and URI Connections for a complete description.

Does this in any way change my use of DSNs?

No, continue to use DSNs as usual.

Can I still use Pervasive System Analyzer to test connections?

Yes, you can use IPv6 addresses.

Can I use Pervasive Auto Reconnect (PARC) with IPv6?

Does Pervasive PSQL support IPv6 communications in virtual machine environments?

Is IPv6 supported for Linux distributions or Macintosh OS X?

No. Only Windows platforms are supported.

Is IPv6 supported for Pervasive DataExchange, and AuditMaster?

Does a network environment that includes both IPv4 and IPv6 affect Pervasive PSQL user counts?

No. Pervasive PSQL Server or Workgroup uses one user count for each unique incoming protocol from the same client computer session (such as TCP/IP and SPX). IPv4 and IPv6 are just different address formats of TCP/IP.

Can the Listen IP Address configuration setting be set to multiple addresses?

Yes. See Listen IP Address.

Pervasive PSQL Utilities and IPv6

As a result of the implementation of IPv6 for additional interfaces, the following changes have occurred in Pervasive PSQL utilities:.


Utility	Description	See Also
Pervasive PSQL Control Center (PCC)	PCC is now completely supported and fully functional in an IPv6 environment.	Using Pervasive PSQL Control Center in Pervasive PSQL User's Guide
DDF Builder	DDF Builder is now completely supported and fully functional in an IPv6 environment.	DDF Builder User’s Guide
Monitor	Network Address is one of the display fields in the “MicroKernel Active Sessions” Session Information and in “MicroKernel Active Files” Handle Information. If the calling process uses TCP/IP, the address is preceded by “T:”. This applies whether the address shown is a hostname, an IPv4 address or an IPv6 address.	Monitoring Database Resources in Advanced Operations Guide.