I'm not sure how you plan to manage your /48, but this is how I've seen it
done in the past:
1) You are given a single IPv6 address (a /128) for your Internet-facing
router. You are expected to add this address to your untrusted interface.
You are also given the address of a router at your ISP which is your IPv6
default route.
2) You are also given a block of addresses. In my case this case a /64,
although it should work for any size prefix. You are expected to hand
these addresses out on your trusted interface via either DHCPv6 or SLAAC
(depending on your preference). Assign one of the addresses in the block
to your router's LAN interface and supply this as the default route for
your LAN hosts.
Good luck.
On Jan 10, 2015 10:10 AM, "F. Mendez" <fmendez73@xxxxxxxxx> wrote:
> Hello.
>
> It happens that at the company I'm working decided to start migration of
> IPs tech.
>
> So they got a /48 block. I were trying to add it with:
>
> ifcfg-eth0-range1 (0 is already in use with IPv4 range):
>
> IPV6ADDR_START=xxxx
> IPV6ADDR_END=xxxx
> CLONENUM_START=0
>
> But of course I am assuming that like in IPv4 IPADDR_START/END is
> implemented.
>
> Please give some guidance as I need this to done already and the hole /48
> must be available and virtualized.
>
>
> Thanks.
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
