[nog] IPv6

Stefan Dimitrov dimitrov.stefan787 at gmail.com
Thu Sep 4 22:23:15 EEST 2014


In Sofia University network we use /126 for p2p links to our ISPs and BG
peers. With this prefix you have a free address for a monitoring
station, for instance.

Best Regards,
Stefan Dimitrov, SU

On 09/04/2014 10:17 AM, Ivan Popov wrote:
> On 03.09.2014 ?. 22:39 ?., Stefan Dimitrov wrote:
>> On 09/02/2014 11:45 AM, Ivan Popov wrote:
>>> On 02.09.2014 ?. 10:50 ?., Marian Marinov wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>>
>>>> Hi guys,
>>>> I'm preparing to configure my Ripe Atlas Anchor in Sofia and I wish
>>>> to have both IPv4 and IPv6 for it.
>>>>
>>>> Since I don't have much experience with IPv6 I would like to ask a
>>>> few questions :)
>>>>
>>>> - - If I want to use a /64 from my RIPE provided IPv6 addresses, do
>>>> I need to give another /64 to my uplink ISP for
>>>> transport?
>>>>
>>>> - - I have received /64 from my ISP but I did not receive any
>>>> transport IPs. Is this normal?
>>>>
>>>>
>>>> Marian
>>>>
>>> It depends... as usual
>>> By RIPE's  recommendations /64 IPv6 Networks should be assigned to
>>> end users and by definition end users should not deal with BGP,
>>> routers and other networking mumbo-jumbo's
>>> I don't know details about your current setup with ISP but it's
>>> probably follows well known logic: 1'st address is default gateway
>>> so you must just assign IPv6 address to end station and point it to
>>> the "default gateway". ISP will advertise aggregated prefixes (incl.
>>> your /64) to entire world
>>>
>>> About IPv6 p2p links we can refer to RFC6164
>>> (http://tools.ietf.org/html/rfc6164)
>>
>> How to use 127-bit IPv6 prefixes (/127)
> By the same way as IPv4 /31  p2p
> (http://tools.ietf.org/html/rfc3021)... MTEL uses that convention a
> lot in their networks.
> Personally, I don't like it. Using IPv6 /126 and IPv4 /30 for p2p is
> more handy and scalable and  a bit address wasting ofcourse  :)
>
>>>
>>> Probably this is not your case but ... KISS forever! :)
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Nog mailing list
>>> Nog at nog.bg
>>> http://lists.ludost.net/cgi-bin/mailman/listinfo/nog
>>
>>
>>
>> _______________________________________________
>> Nog mailing list
>> Nog at nog.bg
>> http://lists.ludost.net/cgi-bin/mailman/listinfo/nog
>
>
>
> _______________________________________________
> Nog mailing list
> Nog at nog.bg
> http://lists.ludost.net/cgi-bin/mailman/listinfo/nog

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ludost.net/pipermail/nog/attachments/20140904/71ea1137/attachment.html>


More information about the Nog mailing list