Please Welcome Nate Sales to MICE!
Name: Nate Sales Port: MN VoIP Remote ASN: 34553 IPv4: 206.108.255.166/24 IPv6: 2001:504:27:0:6:86f9::1/64 Peering Contact: peering@natesales.net Route Servers- YES BFD: No Welcome Aboard! -- Jay Hanke, President South Front Networks jayhanke@southfront.io Phone 612-204-0000
This will be port E19 @1Gig on my extension switch -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Jay Hanke Sent: Wednesday, May 27, 2020 9:35 AM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Please Welcome Nate Sales to MICE! Name: Nate Sales Port: MN VoIP Remote ASN: 34553 IPv4: 206.108.255.166/24 IPv6: 2001:504:27:0:6:86f9::1/64 Peering Contact: peering@natesales.net Route Servers- YES BFD: No Welcome Aboard! -- Jay Hanke, President South Front Networks jayhanke@southfront.io Phone 612-204-0000
On Wed, May 27, 2020 at 09:35:15AM -0500, 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 Peering Contact: peering@natesales.net Route Servers- YES BFD: No
They've been setup in the route servers now. -- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
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
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
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
Ok, got it. I've updated the sessions to the correct address so you're free to push the config. Nate On Thu, May 28, 2020, 9:22 AM Doug McIntyre <merlyn@iphouse.net> wrote:
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
Thanks. I've got the changes in, although your router IPv6 addresses don't seem to have changed yet. (ie. I can ping6 2001:504:27:0:6:86f9::1, but I can't ping6 2001:504:27:0:0:86f9::1 On Thu, May 28, 2020 at 09:27:13AM -0700, Nate Sales wrote:
Ok, got it. I've updated the sessions to the correct address so you're free to push the config.
Nate
On Thu, May 28, 2020, 9:22 AM Doug McIntyre <merlyn@iphouse.net> wrote:
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
-- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
Oops, I committed the session update but not the address assignment. Established now. Thanks! On Thu, May 28, 2020 at 9:31 AM Doug McIntyre <merlyn@iphouse.net> wrote:
Thanks. I've got the changes in, although your router IPv6 addresses don't seem to have changed yet.
(ie. I can ping6 2001:504:27:0:6:86f9::1, but I can't ping6 2001:504:27:0:0:86f9::1
On Thu, May 28, 2020 at 09:27:13AM -0700, Nate Sales wrote:
Ok, got it. I've updated the sessions to the correct address so you're free to push the config.
Nate
On Thu, May 28, 2020, 9:22 AM Doug McIntyre <merlyn@iphouse.net> wrote:
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
-- Doug McIntyre <merlyn@iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades
participants (5)
-
Doug McIntyre -
Jay Hanke -
Jeremy Lumby -
Nate Sales -
Richard Laager