mirror of
https://github.com/FirebirdSQL/firebird.git
synced 2025-01-22 20:43:02 +01:00
42 lines
1.5 KiB
Plaintext
42 lines
1.5 KiB
Plaintext
|
IPv6 support in Firebird 3.0
|
||
|
|
----------------------------
|
||
|
|
|
||
|
|
Starting with version 3.0, Firebird can use IPv6 connections, both on client
|
||
|
|
and server side.
|
||
|
|
|
||
|
|
|
||
|
|
Client
|
||
|
|
------
|
||
|
|
|
||
|
|
As standard text form of an IPv6 address uses colons which Firebird uses to
|
||
|
|
separate host and database in connection strings, IPv6 address needs to be
|
||
|
|
enclosed in brackets. Examples:
|
||
|
|
|
||
|
|
connect '[2014:1234::5]:test';
|
||
|
|
connect '[2014:1234::5]/3049:/srv/firebird/test.fdb';
|
||
|
|
|
||
|
|
For consistency, (optional) square brackets can be also used around an IPv4
|
||
|
|
address or a domain name.
|
||
|
|
|
||
|
|
If a domain name is used in connection string, all addresses (IPv4 and IPv6)
|
||
|
|
are tried in the order returned by resolver until a connection is established.
|
||
|
|
Only if all attempts fail, the client fails to connect.
|
||
|
|
|
||
|
|
|
||
|
|
Server
|
||
|
|
------
|
||
|
|
|
||
|
|
By default, Firebird server listens on zero IPv6 address (::) and accepts all
|
||
|
|
incoming connections, IPv4 and IPv6. This behaviour can be changed by config
|
||
|
|
directive IPv6V6Only. If it is set to true, server listening on zero IPv6
|
||
|
|
address (implicitely or explicitely) will accept only IPv6 connections.
|
||
|
|
|
||
|
|
Different listening address (IPv4 or IPv6) can be set using RemoteBindAddress
|
||
|
|
directive. If an IPv4 address or non-zero IPv6 address is used, IPv6V6Only
|
||
|
|
directive has no effect.
|
||
|
|
|
||
|
|
Note: on POSIX platforms, server started in Classic mode via (x)inetd ignores
|
||
|
|
the RemoteBindAddress, RemoteServicePort and RemoteServiceName directives as
|
||
|
|
the listening socket is set up by (x)inetd. Listening address and/or port need
|
||
|
|
to be set in (x)inetd configuration in this mode.
|