Hello Bernhard Schmidt,
Am 2012-09-09 12:07:26, hacktest Du folgendes herunter:
> So you already have NAT44 (IPv4 NAT).
NAT? Ehm no. I have an public IPv4 /24 assigned to my AS.
> > If I give my "private" customers fixed or DHCP assigned IPv6 addresses,
> > they can not more access the IPv4 Internet.
>
> Why?
I do not know why, because if I go to my customer and connect my Debian
Laptop to tzhe FTTH Modem, all is working fine and I can access ANY
servers with IPv4 and IPv6.
But if a customer connect with Windows Vista/2007 which get the IPv6
address over my PPPoE server and then can not more connect to servers
which use IPv4.
Only IPv6 aware services are working.
If I use a CISCO roter between the FTTH Modem and the Windows machine,
Windows get a NATed IIP Address from the CISCO Router and then Windows
can access IPv4 and IPv6 services...
The problem is, most Low-Cost Roters do not support IPv6 which let me
run into trouble with private customers. It seems, there are currently
not very much routers which support IPv6 (AVM has for example two
working boxes)
> People often wrongly assume that deploying IPv6 means switching off
> IPv4. This is not the case. Your IPv4 will continue to work as-is (with
> NAT).
But why NAT? I have not enough public IPv4 adresses (even my Managed
GE Switches do not support it) and the only way would be private IPs for
the NAT.
> Switching off IPv4 can be done (and has been done) in enterprise
> deployments, where you have control of the applications and can ensure
> they are working correctly (i.e. using proxies or NAT64).
Hmmm, I do not realy know, what I have configured (used an Ubuntu HOWTO)
but my <intranet1> is entirely IPv6 (no IPv4 available anymore) and
ANYTHING is working except my embedded systems, which I now access using
an IPv6 running admin server.
E.g. my current workstation:
[michelle.konzack@work1:~] ifconfig eth0
eth0 Link encap:Ethernet Hardware Adresse 00:0e:0c:22:8f:0a
inet6-Adresse: 2a01:4f8:d12:1300::1:13/64 Gültigkeitsbereich:Global
inet6-Adresse: fe80::20e:cff:fe22:8f0a/64 Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
RX packets:478344816 errors:0 dropped:13399 overruns:0 frame:0
TX packets:528880089 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:100
RX bytes:3404297287 (3.1 GiB) TX bytes:2744681181 (2.5 GiB)
It just works. I do not know, where the fe80:... is coming from, which
I have never configured, but it works properly
> I think there
> are at least 5+ years to go before you can do so in ISP environments.
Very grmpf!
> > So, what I have to do (or the customers?), to let the outdated IPv4 keep
> > working?
> You keep IPv4 up and running.
I have only 180 IPs available but in some month arround 4500 customers.
> Best Regards,
> Bernhard
Thanks, Greetings and nice Day/Evening
Michelle Konzack
--
##################### Debian GNU/Linux Consultant ######################
Development of Intranet and Embedded Systems with Debian GNU/Linux
Internet Service Provider, Cloud Computing
<http://www.itsystems.tamay-dogan.net/>
<http://www.debian.tamay-dogan.net/>
itsystems@tdnet Jabber linux4michelle@jabber.ccc.de
Owner Michelle Konzack
Gewerbe Strasse 3 Tel office: +49-176-86004575
77694 Kehl Tel mobil: +49-177-9351947
Germany Tel mobil: +33-6-61925193 (France)
USt-ID: DE 278 049 239
Linux-User #280138 with the Linux Counter, http://counter.li.org/
Attachment:
signature.pgp
Description: Digital signature