Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index

I read your email and was wondering about having all those IP addresses.

Is their any way for some of the domain/sub-domains to share IP addresses more?

It has been about 10 years since I got a degree in Network Technology, but I am wondering what it the advantage of having so many IP addresses?

I know that if you have a retail site you should have a non-shared one for the commerce systems, but what does TDF have that required all those IP addresses?

I know that a lot of users access systems do not have IPv6 complaint systems [or access services], so it will be a long time before everyone will be able to deal with IPv6 addresses. I know my "giant cable modem company" has not told us anything about having the ability to deal with IPv6 addresses. So there will be a need for users to access IPv6 servers with their IPv4 systems. I do not know if TDF has to have the system in place or the access provider for the IPv6 system will need to have it on their equipment.

Actually, I do not remember seeing any home or small business routers that are IPv6 complaint. But I have to looked for about 6 months for one.

The upgrading to IPv6 will be a problem for years to come. Until every access service has the ability to use those IP addresses, and the users have equipment that can use them as well, there will be problems dealing with the IPv4/IPv6 system changeover.



we received the news that our ISP will be much more restrictive about
IPv4 addresses in the near future, probably beginning in early December.

Right now, their pricing is 1 € per extra IP, and for our subnet with 30
usable IPs, we pay 22,50 € per month.

In the worst case, they will charge 5 € per extra IP and month in the
future, which woulde produce additional costs of more than 100 € per
month. We have no pricing details yet, so the above is based on assumptions.

However, this will mean that very shortly, we might run into the
situation that we can not provide IPv4 addresses generously anymore for
virtual machines, not even for all productive ones.

Ideally, we can at least migrate some internal services exclusively to
IPv6, but this won't work for all public services. In this case, we then
might have to use port forwarding and proxying.

I hope we can avoid most inconveniences, and keep a safe amount of IPv4
addresses, but I wanted to warn all of you already now that the
luxurious situation we are in at the moment might end soon.

It definitely makes sense for anyone who runs testing VMs or internal
services to make yourself comfortable with IPv6 *now*. Should your ISP
not provide native IPv6 connectivity (which unfortunately is true for
most ISPs around the globe), have a look at, or google for "6to4".


Florian Effenberger, Chairman of the Board (Vorstandsvorsitzender)
Tel: +49 8341 99660880 | Mobile: +49 151 14424108
Jabber: | SIP:
The Document Foundation, Zimmerstr. 69, 10117 Berlin, Germany
Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
Legal details:

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.