[131253] in North American Network Operators' Group
Re: ipv6 vs. LAMP
daemon@ATHENA.MIT.EDU (Leo Bicknell)
Thu Oct 21 17:44:05 2010
Date: Thu, 21 Oct 2010 14:43:54 -0700
From: Leo Bicknell <bicknell@ufp.org>
To: nanog@nanog.org
Mail-Followup-To: nanog@nanog.org
In-Reply-To: <1287694429.4968.96.camel@wednesday>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--huq684BweRXVnRxX
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In a message written on Thu, Oct 21, 2010 at 01:53:49PM -0700, Christopher =
McCrory wrote:
> open to the world. After a few google searches, it seems that
> PostgreSQL is in a similar situation. =20
I don't know when PostgreSQL first supported IPv6, but it works just
fine. I just fired up a stock FreeBSD 8.1 system and built the Postgres
8.4 port with no changes, and viola:
postgresql# netstat -a=20
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address Foreign Address (state)
tcp4 0 0 localhost.postgresql *.* LISTEN
tcp6 0 0 localhost.postgresql *.* LISTEN
$ psql -h ::1=20
psql (8.4.4)
Type "help" for help.
pgsql=3D# \l
List of databases
Name | Owner | Encoding | Collation | Ctype | Access privileges=20
-----------+-------+----------+-----------+-------+-------------------
pgsql | pgsql | UTF8 | C | C |=20
postgres | pgsql | UTF8 | C | C |=20
template0 | pgsql | UTF8 | C | C | =3Dc/pgsql
: pgsql=3DCTc/pgsql
template1 | pgsql | UTF8 | C | C | =3Dc/pgsql
: pgsql=3DCTc/pgsql
(4 rows)
~pgsql/data/pg_hba.conf contains:
# CIDR-ADDRESS specifies the set of hosts the record matches.
# It is made up of an IP address and a CIDR mask that is an integer
# (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that specifies
# the number of significant bits in the mask. Alternatively, you can write
# an IP address and netmask in separate columns to specify the set of hosts.
And later:
# "local" is for Unix domain socket connections only
local all all trust
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
host all all ::1/128 trust
So of your "LAMP" stack, I'm pretty sure all the L's are in good shape
(Linux/FreeBSD/NetBSD/etc), the A is in good shape, been working fine
for years. Perhaps the M needs some work on the MySQL side, but I'm
fairly sure PostgreSQL is solid. I'm not exactly sure how the P would
need IPv6 support, but I think it's generally a non-issue there other
than updating software that acutally stores IPv4 addresses...
--=20
Leo Bicknell - bicknell@ufp.org - CCIE 3440
PGP keys at http://www.ufp.org/~bicknell/
--huq684BweRXVnRxX
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.13 (FreeBSD)
iQIVAwUBTMC0GrN3O8aJIdTMAQLAyhAAuI0q8Xh3f+YfRsh0D64y9p/RHAMW8SF5
pNUmAH9mBQ2Xtt0Ogq8c4tAdUT9Aaz4glNyNicCA4JWs6qKMQqxa3eEXGV//+miw
UjZob7Y1ZbsOTU1g5gkp3mvgPOYs+C2Rz2i09XUOkM/hqXWl50bmWIIDHBr19vEY
HxWgMbJ8wH3c4t4/GoyRHanGMdDX+QRY4FpdKgkDpSPr6DtRgj5wbfjG+LVfk2kZ
9ZFmv5MDaF6caKFjZI/NI1bAEpIWz8ghhm1WIkXPw//EHWysCNE9xwAX0qkFOndB
aDxgyg2l2/uxEe+Jna5dCfHhqJONJ23iBOJnCDXif+38XjiHHHGm7lnAyB1Uwhga
EUL4zX+f8kHp+H0J4yi8j7cqT7kitcpyn16WrJD3Ms343wKtMaMZFGEk8+1xu1o0
henzqVNm8ZK6xleBbqQ4A5sdSBWhiTz98jWWkoy27wvBmJfYYdAU7wi01PSV13a5
V9AxM7Ju8fBBc9muxolTzqy5W3WImVQqg9X2oLVpMAkbn8RkP/zKorX27wL1sCx0
VJ/MyAhb0823rLZob6uU6HyW+A0+CyiF59yt6z6vzL0k/FKisQw3y26rl8Wzd+VU
iSBfv8lGgH8J0y/ZXkVgZ3E9l5Gx+es/42p2UW7akF40NxiPZkKtRrGKI5c6A+sI
7M0e5x80h8w=
=6Hv6
-----END PGP SIGNATURE-----
--huq684BweRXVnRxX--
