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.
On 01/10/2015 10:10 AM, F. Mendez wrote:> > But of course I am assuming that like in IPv4 IPADDR_START/END is > implemented.I don't think so. The START and END bits of ifup-aliases appear to be v4 specific.> Please give some guidance as I need this to done already and the hole > /48 must be available and virtualized.Well, the whole network will be available as long as you have an active address on a node that's capable of acting as a router. I'm not sure what you mean by virtualized, though. https://access.redhat.com/solutions/347693
El 10/01/2015 a las 03:40 p.m., Gordon Messmer escribi?:> On 01/10/2015 10:10 AM, F. Mendez wrote: >> >> But of course I am assuming that like in IPv4 IPADDR_START/END is >> implemented. > > I don't think so. The START and END bits of ifup-aliases appear to be > v4 specific. > >> Please give some guidance as I need this to done already and the hole >> /48 must be available and virtualized. > > Well, the whole network will be available as long as you have an > active address on a node that's capable of acting as a router. I'm not > sure what you mean by virtualized, though. > > https://access.redhat.com/solutions/347693 > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >Hello. Thanks for your reply. Currently we have a /26 range of IPv4. So we have eth0:1...eth0:59 We need that same with IPv6 since we have a /48 and we need to have all IPv6s available for usage. I tried to use same ifcfg-eth0-range0 same config by adding: IPV6ADDR_START= which seems not to work for this. None IPADDR_START too. We need a simple way to have our virtual eth's with IPv6 all the range available.
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 at terra.com> 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 at centos.org > http://lists.centos.org/mailman/listinfo/centos >