Because the Route servers were setup with the incorrect data.  The
IPv6 address should be your ASN. The :6: probably crept in from some
previous member that has a 32-bit ASN, as those overflow the one field into the next.

It would be best to get change to get all on the same page and be the
standard setup.

Can I go reconfig now? Or did you want to schedule it with me?


On Thu, May 28, 2020 at 09:08:07AM -0700, Nate Sales wrote:
>The participants page on the website lists the zero in the address
>(2001:504:27:0:0:86f9::1) but i'm established with the route servers using
>the 6 address (2001:504:27:0:6:86f9::1).
>
>Should I switch to the zero one?
>
>Additionally, the order form was sent to peering@micemn.ne
><peering@micemn.net>t.
>
>Thanks,
>Nate
>
>On Wed, May 27, 2020, 11:34 PM Richard Laager <rlaager@wiktel.com> wrote:
>
>> On 5/27/20 9:35 AM, Jay Hanke wrote:
>> > Name: Nate Sales
>> > Port: MN VoIP Remote
>> > ASN: 34553
>> > IPv4: 206.108.255.166/24
>> > IPv6: 2001:504:27:0:6:86f9::1/64
>>
>> Typo: 6 should be 0? 2001:504:27:0:0:86f9::1
>>
>> > Peering Contact:   peering@natesales.net
>> > Route Servers- YES
>> > BFD: No
>> >
>> > Welcome Aboard!
>> >
>>
>>
>> --
>> Richard
>>

--
Doug McIntyre                            <merlyn@iphouse.net>
                     ~.~ ipHouse ~.~
        Network Engineer/Provisioning/Jack of all Trades