- mice-discuss - lists.micemn.net

Re: NOCIX MICE Extension Proposal

by Michael Hare

To be clear my messages are NOT intended to be a downvote for the proposal, I’m just intending to foster discussion. I don't think https://www.micemn.net/technical.html needs major changes. Maybe change “Operators are responsible for the costs of operating their remote switch and the links to the core switch.” to “Operators are responsible for the costs of operating their remote switch and the links [TOWARDS] the core switch.” I think it's worthwhile acknowledging the distance to the proposed remote switch, the presumed lack of redundancy in the proposed backhaul. re: reliability: Is the lack of redundancy an accurate assumption, or would this be a protected wave? AS3128 has some experience in this area [AS3128 assists in operations of a 1000mi+ fiber ring for multistate research and education, including through Minneapolis and Minnesota] so I wanted to ack that in general with distance comes decreased reliability, and eBGP stability is important since topology changes lead to packet loss during convergence. I acknowledge we already have peers at MICE that are extensions out of Chicago [Google comes to mind]. I am also aware of the options that, for example, AS32621 provides in extending folks to Seattle IX as an opt-in value add, which is contrast to the ‘auto opt-in’ stance MICE route reflectors users enjoy. re: distance: based on geography or your home AS stance, this change could result in a longer RTT between some networks. AS3128 appears at exchanges other than MICE. But if you are in this club you are probably aware that you already have this potential problem and either you deal with it or not. Admittedly, our operations are less algorithmic and more reactionary. So if I were to focus discussions on either distance or reliability, I would focus more on reliability. Ultimately with MICE per-AS BGP community support, the publication of https://www.micemn.net/participants.html, and mailing list announcements of when new peers are brought onboard, AS3128 has all the tools it needs ==IF== we need to make a traffic engineer decision, which is great. If NOCIX comes onboard, I would welcome them and would have no intentions to proactively traffic engineer away from them via MICE. -Michael From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Aaron Wendel Sent: Saturday, January 29, 2022 9:46 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] NOCIX MICE Extension Proposal Our agreement with MN VOIP would be for transport from KC to Minneapolis. If the link became congested, we would order additional capacity. If MN VoIP could t provide it then we would get it someplace else. In the end, our intention is to be congestion free from KC to the MICE core. Aaron On Jan 29, 2022, at 12:30 PM, Michael Hare <000000097dab80c5-dmarc-request(a)lists.iphouse.net<mailto:000000097dab80c5-dmarc-request@lists.iphouse.net>> wrote: Hi- As I understand this will be an extension of an extension. It looks like this may be the second of that kind. If I understand this correctly the "South Front Networks Alberta Lea Remotes" switch hangs off of Minnesota VoIP? @ https://www.micemn.net/technical.html, I see "Operators are responsible for the costs of operating their remote switch and the links to the core switch. They must monitor their traffic levels and promptly add capacity to keep the links running congestion-free." My reading of above implies the current policy assumes a remote switch will connect to the MICE core directly. Perhaps we revisit the above language as it pertains to “the core switch”. -Michael From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>> On Behalf Of Richard Laager Sent: Friday, January 28, 2022 5:31 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> Subject: [MICE-DISCUSS] NOCIX MICE Extension Proposal For everyone's review and comment per our policy on remote switches: "As per the MICE remote switch policy this letter will serve as NOCIX’s intention to deploy, pending board approval, a MICE extension switch at the 1530 Swift facility at 1530 Swift St. North Kansas City, MO 64116. The purpose of this extension is to provide additional, low cost peering in the Kansas City and surrounding markets directly to the north-central US." See the attached PDF for full details. Richard ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Jan. 30, 2022

Re: NOCIX MICE Extension Proposal

by Aaron Wendel

Our agreement with MN VOIP would be for transport from KC to Minneapolis. If the link became congested, we would order additional capacity. If MN VoIP could t provide it then we would get it someplace else. In the end, our intention is to be congestion free from KC to the MICE core. Aaron > On Jan 29, 2022, at 12:30 PM, Michael Hare <000000097dab80c5-dmarc-request(a)lists.iphouse.net> wrote: > > > Hi- > > As I understand this will be an extension of an extension. It looks like this may be the second of that kind. If I understand this correctly the "South Front Networks Alberta Lea Remotes" switch hangs off of Minnesota VoIP? > > @ https://www.micemn.net/technical.html, I see "Operators are responsible for the costs of operating their remote switch and the links to the core switch. They must monitor their traffic levels and promptly add capacity to keep the links running congestion-free." > > My reading of above implies the current policy assumes a remote switch will connect to the MICE core directly. Perhaps we revisit the above language as it pertains to “the core switch”. > > -Michael > > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Richard Laager > Sent: Friday, January 28, 2022 5:31 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: [MICE-DISCUSS] NOCIX MICE Extension Proposal > > For everyone's review and comment per our policy on remote switches: > > "As per the MICE remote switch policy this letter will serve as NOCIX’s intention to deploy, pending board > approval, a MICE extension switch at the 1530 Swift facility at 1530 Swift St. North Kansas City, MO > 64116. The purpose of this extension is to provide additional, low cost peering in the Kansas City and > surrounding markets directly to the north-central US." > > See the attached PDF for full details. > > > Richard > > > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Jan. 30, 2022

Re: NOCIX MICE Extension Proposal

by Jay Hanke

There are currently two set up like this IIRC. SFN in Albert Lea and Compudyne in Duluth. Compudyne Duluth sits behind their remote in 511. I've always taken the congestion free requirement to be all the way to the core switch. Granted, two of the MICE remotes (CNS/MN VoIP) would be ranked nationally traffic wise if they were independent exchanges. :) On Sat, Jan 29, 2022 at 12:30 PM Michael Hare <000000097dab80c5-dmarc-request(a)lists.iphouse.net> wrote: > > Hi- > > > > As I understand this will be an extension of an extension. It looks like this may be the second of that kind. If I understand this correctly the "South Front Networks Alberta Lea Remotes" switch hangs off of Minnesota VoIP? > > > > @ https://www.micemn.net/technical.html, I see "Operators are responsible for the costs of operating their remote switch and the links to the core switch. They must monitor their traffic levels and promptly add capacity to keep the links running congestion-free." > > > > My reading of above implies the current policy assumes a remote switch will connect to the MICE core directly. Perhaps we revisit the above language as it pertains to “the core switch”. > > > > -Michael > > > > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Richard Laager > Sent: Friday, January 28, 2022 5:31 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: [MICE-DISCUSS] NOCIX MICE Extension Proposal > > > > For everyone's review and comment per our policy on remote switches: > > "As per the MICE remote switch policy this letter will serve as NOCIX’s intention to deploy, pending board > approval, a MICE extension switch at the 1530 Swift facility at 1530 Swift St. North Kansas City, MO > 64116. The purpose of this extension is to provide additional, low cost peering in the Kansas City and > surrounding markets directly to the north-central US." > > See the attached PDF for full details. > > Richard > > > > ________________________________ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > > ________________________________ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Jan. 29, 2022

Re: NOCIX MICE Extension Proposal

by Michael Hare

Hi- As I understand this will be an extension of an extension. It looks like this may be the second of that kind. If I understand this correctly the "South Front Networks Alberta Lea Remotes" switch hangs off of Minnesota VoIP? @ https://www.micemn.net/technical.html, I see "Operators are responsible for the costs of operating their remote switch and the links to the core switch. They must monitor their traffic levels and promptly add capacity to keep the links running congestion-free." My reading of above implies the current policy assumes a remote switch will connect to the MICE core directly. Perhaps we revisit the above language as it pertains to “the core switch”. -Michael From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Richard Laager Sent: Friday, January 28, 2022 5:31 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] NOCIX MICE Extension Proposal For everyone's review and comment per our policy on remote switches: "As per the MICE remote switch policy this letter will serve as NOCIX’s intention to deploy, pending board approval, a MICE extension switch at the 1530 Swift facility at 1530 Swift St. North Kansas City, MO 64116. The purpose of this extension is to provide additional, low cost peering in the Kansas City and surrounding markets directly to the north-central US." See the attached PDF for full details. Richard ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Jan. 29, 2022

Re: [EXTERNAL] [MICE-DISCUSS] NOCIX MICE Extension Proposal

by Kittel, Brady

Bullet point 7 is my favorite. :) ________________________________ From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of Richard Laager <rlaager(a)WIKTEL.COM> Sent: Friday, January 28, 2022 4:31:12 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Subject: [EXTERNAL] [MICE-DISCUSS] NOCIX MICE Extension Proposal CAUTION: This email originated from outside of HCMC. DO NOT CLICK links or open attachments unless you recognize the sender and know the content is safe. For everyone's review and comment per our policy on remote switches: "As per the MICE remote switch policy this letter will serve as NOCIX’s intention to deploy, pending board approval, a MICE extension switch at the 1530 Swift facility at 1530 Swift St. North Kansas City, MO 64116. The purpose of this extension is to provide additional, low cost peering in the Kansas City and surrounding markets directly to the north-central US." See the attached PDF for full details. Richard ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1<https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.ipho…>

Jan. 29, 2022

Re: Problems Reaching 206.108.255.164

by Justin Krejci

Great that it is sorted. For future reference one can reliably look up MICE IP address assignments on the MICE website participants page: https://micemn.net/participants.html Usually PeeringDB is accurate but I consider the MICE page to be fully authoritative on this matter. ________________________________ From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of Joshua Eckert <JoshuaEckert(a)CLTEL.COM> Sent: Friday, January 28, 2022 3:36 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Problems Reaching 206.108.255.164 I can ping IP Pathways and they ping us so we should be good. Thanks! Joshua Eckert | Systems Administrator CL Tel | 107 N 4th St. | Clear Lake, IA 50428 P: 641-357-2111 | F: 641-357-8800 www.cltel.com<http://www.cltel.com> | www.facebook.com/cltel<http://www.facebook.com/cltel> -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay Hanke Sent: Friday, January 28, 2022 3:35 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Problems Reaching 206.108.255.164 SECURITY NOTICE: This is an email from an EXTERNAL source. If it appears to be from an internal source please notify the CLTEL JCIT team immediately. Please exercise caution and DO NOT open attachments or click links from unknown senders or in unexpected emails. ________________________________ There was a hung entry in the config. I cleared it. Can you confirm? On Fri, Jan 28, 2022 at 3:27 PM Joshua Eckert <JoshuaEckert(a)cltel.com> wrote: > > We tried on both our sides and neither could get a response. > > > > Joshua Eckert | Systems Administrator > CL Tel | 107 N 4th St. | Clear Lake, IA 50428 > P: 641-357-2111 | F: 641-357-8800 > www.cltel.com<http://www.cltel.com> | www.facebook.com/cltel<http://www.facebook.com/cltel> > > -----Original Message----- > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay > Hanke > Sent: Friday, January 28, 2022 3:21 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: Re: [MICE-DISCUSS] Problems Reaching 206.108.255.164 > > SECURITY NOTICE: This is an email from an EXTERNAL source. If it appears to be from an internal source please notify the CLTEL JCIT team immediately. Please exercise caution and DO NOT open attachments or click links from unknown senders or in unexpected emails. > ________________________________ > > > I cleared mac on the remote switch can you check again? > > I can clear the 100G one as well if that doesn't work. > > On Fri, Jan 28, 2022 at 3:12 PM Joshua Eckert <JoshuaEckert(a)cltel.com> wrote: > > > > We did, and we checked with IP Pathways and the mac address in our arp was correct. > > > > > > > > Joshua Eckert | Systems Administrator CL Tel | 107 N 4th St. | Clear > > Lake, IA 50428 > > P: 641-357-2111 | F: 641-357-8800 > > www.cltel.com<http://www.cltel.com> | www.facebook.com/cltel<http://www.facebook.com/cltel> > > > > -----Original Message----- > > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay > > Hanke > > Sent: Friday, January 28, 2022 3:09 PM > > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > > Subject: Re: [MICE-DISCUSS] Problems Reaching 206.108.255.164 > > > > SECURITY NOTICE: This is an email from an EXTERNAL source. If it appears to be from an internal source please notify the CLTEL JCIT team immediately. Please exercise caution and DO NOT open attachments or click links from unknown senders or in unexpected emails. > > ________________________________ > > > > > > Have you cleared your arp cache on your router? > > > > On Fri, Jan 28, 2022 at 3:00 PM Joshua Eckert <JoshuaEckert(a)cltel.com> wrote: > > > > > > We can't get a response from 206.108.255.164, we're using 206.108.255.139 as the source IP. Other IPs in this subnet are responding. > > > > > > > > > > > > Joshua Eckert | Systems Administrator CL Tel | 107 N 4th St. | > > > Clear Lake, IA 50428 > > > P: 641-357-2111 | F: 641-357-8800 > > > www.cltel.com<http://www.cltel.com> | www.facebook.com/cltel<http://www.facebook.com/cltel> > > > > > > -----Original Message----- > > > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of > > > Jay Hanke > > > Sent: Friday, January 28, 2022 2:51 PM > > > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > > > Subject: Re: [MICE-DISCUSS] Problems Reaching 206.108.255.164 > > > > > > SECURITY NOTICE: This is an email from an EXTERNAL source. If it appears to be from an internal source please notify the CLTEL JCIT team immediately. Please exercise caution and DO NOT open attachments or click links from unknown senders or in unexpected emails. > > > ________________________________ > > > > > > > > > We're seeing the next hop available from Davenport (via the Albert > > > Lea > > > remote) > > > > > > jayhanke@SFN-IA-Davenport-BDR1> ping 206.108.255.164 PING > > > 206.108.255.164 (206.108.255.164): 56 data bytes > > > 64 bytes from 206.108.255.164: icmp_seq=0 ttl=64 time=14.733 ms > > > 64 bytes from 206.108.255.164: icmp_seq=1 ttl=64 time=20.584 ms > > > 64 bytes from 206.108.255.164: icmp_seq=2 ttl=64 time=14.928 ms > > > 64 bytes from 206.108.255.164: icmp_seq=3 ttl=64 time=15.388 ms > > > 64 bytes from 206.108.255.164: icmp_seq=4 ttl=64 time=19.997 ms > > > 64 bytes from 206.108.255.164: icmp_seq=5 ttl=64 time=90.039 ms > > > 64 bytes from 206.108.255.164: icmp_seq=6 ttl=64 time=16.737 ms > > > 64 bytes from 206.108.255.164: icmp_seq=7 ttl=64 time=14.910 ms > > > 64 bytes from 206.108.255.164: icmp_seq=8 ttl=64 time=14.660 ms > > > 64 bytes from 206.108.255.164: icmp_seq=9 ttl=64 time=15.294 ms > > > 64 bytes from 206.108.255.164: icmp_seq=10 ttl=64 time=14.717 ms > > > 64 bytes from 206.108.255.164: icmp_seq=11 ttl=64 time=15.642 ms > > > 64 bytes from 206.108.255.164: icmp_seq=12 ttl=64 time=15.244 ms > > > ^C > > > --- 206.108.255.164 ping statistics --- > > > 13 packets transmitted, 13 packets received, 0% packet loss > > > round-trip min/avg/max/stddev = 14.660/21.759/90.039/19.801 ms > > > > > > jayhanke@SFN-IA-Davenport-BDR1> > > > > > > UPN had circuit issues yesterday in the Urbandale area that affected this connection. I believe this has been resolved. > > > > > > On Fri, Jan 28, 2022 at 2:49 PM Jeremy Lumby <jlumby(a)mnvoip.com> wrote: > > > > > > > > Can you traceroute to the next hop past it? I can ping 206.108.255.164 however one thing to keep in mind is that the MICE subnet is not publically routed so to successfully ping 206.108.255.164 you will need to be logged into your MICE connected router so that it uses your MICE interface IP as the source address. > > > > > > > > > > > > Jeremy Lumby > > > > Minnesota VoIP > > > > 9217 17th Ave S #216 > > > > Bloomington, MN 55425 > > > > M: 612-355-7740 > > > > D: 612-392-6814 > > > > F: 952-873-7425 > > > > jlumby(a)mnvoip.com > > > > > > > > > > > > > > > > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On > > > > Behalf Of Joshua Eckert > > > > Sent: Friday, January 28, 2022 2:32 PM > > > > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > > > > Subject: [MICE-DISCUSS] Problems Reaching 206.108.255.164 > > > > > > > > We are having problems reaching 206.108.255.164. We found out this afternoon after a customer stated they were having problems reaching their company's server that has an IP in a subnet that looks like it is using that this IP as its next hop. > > > > > > > > B 199.201.120.0/24 [20/0] via 206.108.255.164, 20:24:51 > > > > > > > > Has anyone else had problems reaching this 206.108.255.164? I fairly new here, so I don't know if this is the right place to put these questions, if not please let me know. > > > > > > > > Thanks! > > > > > > > > > > > > > > > > > > > > > > > > > > > > Joshua Eckert | Systems Administrator CL Tel | 107 N 4th St. | > > > > Clear Lake, IA 50428 > > > > P: 641-357-2111 | F: 641-357-8800 www.cltel.com<http://www.cltel.com> | > > > > www.facebook.com/cltel<http://www.facebook.com/cltel> > > > > > > > > CONFIDENTIALITY NOTICE. This e-mail and any files transmitted with it are the property of Clear Lake Independent Telephone Company and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to which this e-mail is addressed. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Unless stated to the contrary, any opinions or comments are personal to the writer and do not represent the official view of the company. If you are not the named recipient, please contact the sender by reply e-mail and delete this message immediately from your computer. > > > > > > > > ________________________________________ > > > > To unsubscribe from the MICE-DISCUSS list, click the following link: > > > > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > > > > > > > > > > > -- > > > Jay Hanke, President > > > South Front Networks > > > jayhanke(a)southfront.io > > > Phone 612-204-0000 > > > CONFIDENTIALITY NOTICE. This e-mail and any files transmitted with it are the property of Clear Lake Independent Telephone Company and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to which this e-mail is addressed. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Unless stated to the contrary, any opinions or comments are personal to the writer and do not represent the official view of the company. If you are not the named recipient, please contact the sender by reply e-mail and delete this message immediately from your computer. > > > > > > > > -- > > Jay Hanke, President > > South Front Networks > > jayhanke(a)southfront.io > > Phone 612-204-0000 > > CONFIDENTIALITY NOTICE. This e-mail and any files transmitted with it are the property of Clear Lake Independent Telephone Company and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to which this e-mail is addressed. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Unless stated to the contrary, any opinions or comments are personal to the writer and do not represent the official view of the company. If you are not the named recipient, please contact the sender by reply e-mail and delete this message immediately from your computer. > > > > -- > Jay Hanke, President > South Front Networks > jayhanke(a)southfront.io > Phone 612-204-0000 > CONFIDENTIALITY NOTICE. This e-mail and any files transmitted with it are the property of Clear Lake Independent Telephone Company and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to which this e-mail is addressed. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Unless stated to the contrary, any opinions or comments are personal to the writer and do not represent the official view of the company. If you are not the named recipient, please contact the sender by reply e-mail and delete this message immediately from your computer. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000 CONFIDENTIALITY NOTICE. This e-mail and any files transmitted with it are the property of Clear Lake Independent Telephone Company and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to which this e-mail is addressed. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Unless stated to the contrary, any opinions or comments are personal to the writer and do not represent the official view of the company. If you are not the named recipient, please contact the sender by reply e-mail and delete this message immediately from your computer.

Jan. 28, 2022

NOCIX MICE Extension Proposal

by Richard Laager

For everyone's review and comment per our policy on remote switches: "As per the MICE remote switch policy this letter will serve as NOCIX’s intention to deploy, pending board approval, a MICE extension switch at the 1530 Swift facility at 1530 Swift St. North Kansas City, MO 64116. The purpose of this extension is to provide additional, low cost peering in the Kansas City and surrounding markets directly to the north-central US." See the attached PDF for full details. Richard

Jan. 28, 2022

Re: Problems Reaching 206.108.255.164

by Joshua Eckert

I can ping IP Pathways and they ping us so we should be good. Thanks! Joshua Eckert | Systems Administrator CL Tel | 107 N 4th St. | Clear Lake, IA 50428 P: 641-357-2111 | F: 641-357-8800 www.cltel.com | www.facebook.com/cltel -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay Hanke Sent: Friday, January 28, 2022 3:35 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Problems Reaching 206.108.255.164 SECURITY NOTICE: This is an email from an EXTERNAL source. If it appears to be from an internal source please notify the CLTEL JCIT team immediately. Please exercise caution and DO NOT open attachments or click links from unknown senders or in unexpected emails. ________________________________ There was a hung entry in the config. I cleared it. Can you confirm? On Fri, Jan 28, 2022 at 3:27 PM Joshua Eckert <JoshuaEckert(a)cltel.com> wrote: > > We tried on both our sides and neither could get a response. > > > > Joshua Eckert | Systems Administrator > CL Tel | 107 N 4th St. | Clear Lake, IA 50428 > P: 641-357-2111 | F: 641-357-8800 > www.cltel.com | www.facebook.com/cltel > > -----Original Message----- > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay > Hanke > Sent: Friday, January 28, 2022 3:21 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: Re: [MICE-DISCUSS] Problems Reaching 206.108.255.164 > > SECURITY NOTICE: This is an email from an EXTERNAL source. If it appears to be from an internal source please notify the CLTEL JCIT team immediately. Please exercise caution and DO NOT open attachments or click links from unknown senders or in unexpected emails. > ________________________________ > > > I cleared mac on the remote switch can you check again? > > I can clear the 100G one as well if that doesn't work. > > On Fri, Jan 28, 2022 at 3:12 PM Joshua Eckert <JoshuaEckert(a)cltel.com> wrote: > > > > We did, and we checked with IP Pathways and the mac address in our arp was correct. > > > > > > > > Joshua Eckert | Systems Administrator CL Tel | 107 N 4th St. | Clear > > Lake, IA 50428 > > P: 641-357-2111 | F: 641-357-8800 > > www.cltel.com | www.facebook.com/cltel > > > > -----Original Message----- > > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay > > Hanke > > Sent: Friday, January 28, 2022 3:09 PM > > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > > Subject: Re: [MICE-DISCUSS] Problems Reaching 206.108.255.164 > > > > SECURITY NOTICE: This is an email from an EXTERNAL source. If it appears to be from an internal source please notify the CLTEL JCIT team immediately. Please exercise caution and DO NOT open attachments or click links from unknown senders or in unexpected emails. > > ________________________________ > > > > > > Have you cleared your arp cache on your router? > > > > On Fri, Jan 28, 2022 at 3:00 PM Joshua Eckert <JoshuaEckert(a)cltel.com> wrote: > > > > > > We can't get a response from 206.108.255.164, we're using 206.108.255.139 as the source IP. Other IPs in this subnet are responding. > > > > > > > > > > > > Joshua Eckert | Systems Administrator CL Tel | 107 N 4th St. | > > > Clear Lake, IA 50428 > > > P: 641-357-2111 | F: 641-357-8800 > > > www.cltel.com | www.facebook.com/cltel > > > > > > -----Original Message----- > > > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of > > > Jay Hanke > > > Sent: Friday, January 28, 2022 2:51 PM > > > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > > > Subject: Re: [MICE-DISCUSS] Problems Reaching 206.108.255.164 > > > > > > SECURITY NOTICE: This is an email from an EXTERNAL source. If it appears to be from an internal source please notify the CLTEL JCIT team immediately. Please exercise caution and DO NOT open attachments or click links from unknown senders or in unexpected emails. > > > ________________________________ > > > > > > > > > We're seeing the next hop available from Davenport (via the Albert > > > Lea > > > remote) > > > > > > jayhanke@SFN-IA-Davenport-BDR1> ping 206.108.255.164 PING > > > 206.108.255.164 (206.108.255.164): 56 data bytes > > > 64 bytes from 206.108.255.164: icmp_seq=0 ttl=64 time=14.733 ms > > > 64 bytes from 206.108.255.164: icmp_seq=1 ttl=64 time=20.584 ms > > > 64 bytes from 206.108.255.164: icmp_seq=2 ttl=64 time=14.928 ms > > > 64 bytes from 206.108.255.164: icmp_seq=3 ttl=64 time=15.388 ms > > > 64 bytes from 206.108.255.164: icmp_seq=4 ttl=64 time=19.997 ms > > > 64 bytes from 206.108.255.164: icmp_seq=5 ttl=64 time=90.039 ms > > > 64 bytes from 206.108.255.164: icmp_seq=6 ttl=64 time=16.737 ms > > > 64 bytes from 206.108.255.164: icmp_seq=7 ttl=64 time=14.910 ms > > > 64 bytes from 206.108.255.164: icmp_seq=8 ttl=64 time=14.660 ms > > > 64 bytes from 206.108.255.164: icmp_seq=9 ttl=64 time=15.294 ms > > > 64 bytes from 206.108.255.164: icmp_seq=10 ttl=64 time=14.717 ms > > > 64 bytes from 206.108.255.164: icmp_seq=11 ttl=64 time=15.642 ms > > > 64 bytes from 206.108.255.164: icmp_seq=12 ttl=64 time=15.244 ms > > > ^C > > > --- 206.108.255.164 ping statistics --- > > > 13 packets transmitted, 13 packets received, 0% packet loss > > > round-trip min/avg/max/stddev = 14.660/21.759/90.039/19.801 ms > > > > > > jayhanke@SFN-IA-Davenport-BDR1> > > > > > > UPN had circuit issues yesterday in the Urbandale area that affected this connection. I believe this has been resolved. > > > > > > On Fri, Jan 28, 2022 at 2:49 PM Jeremy Lumby <jlumby(a)mnvoip.com> wrote: > > > > > > > > Can you traceroute to the next hop past it? I can ping 206.108.255.164 however one thing to keep in mind is that the MICE subnet is not publically routed so to successfully ping 206.108.255.164 you will need to be logged into your MICE connected router so that it uses your MICE interface IP as the source address. > > > > > > > > > > > > Jeremy Lumby > > > > Minnesota VoIP > > > > 9217 17th Ave S #216 > > > > Bloomington, MN 55425 > > > > M: 612-355-7740 > > > > D: 612-392-6814 > > > > F: 952-873-7425 > > > > jlumby(a)mnvoip.com > > > > > > > > > > > > > > > > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On > > > > Behalf Of Joshua Eckert > > > > Sent: Friday, January 28, 2022 2:32 PM > > > > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > > > > Subject: [MICE-DISCUSS] Problems Reaching 206.108.255.164 > > > > > > > > We are having problems reaching 206.108.255.164. We found out this afternoon after a customer stated they were having problems reaching their company's server that has an IP in a subnet that looks like it is using that this IP as its next hop. > > > > > > > > B 199.201.120.0/24 [20/0] via 206.108.255.164, 20:24:51 > > > > > > > > Has anyone else had problems reaching this 206.108.255.164? I fairly new here, so I don't know if this is the right place to put these questions, if not please let me know. > > > > > > > > Thanks! > > > > > > > > > > > > > > > > > > > > > > > > > > > > Joshua Eckert | Systems Administrator CL Tel | 107 N 4th St. | > > > > Clear Lake, IA 50428 > > > > P: 641-357-2111 | F: 641-357-8800 www.cltel.com | > > > > www.facebook.com/cltel > > > > > > > > CONFIDENTIALITY NOTICE. This e-mail and any files transmitted with it are the property of Clear Lake Independent Telephone Company and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to which this e-mail is addressed. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Unless stated to the contrary, any opinions or comments are personal to the writer and do not represent the official view of the company. If you are not the named recipient, please contact the sender by reply e-mail and delete this message immediately from your computer. > > > > > > > > ________________________________________ > > > > To unsubscribe from the MICE-DISCUSS list, click the following link: > > > > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > > > > > > > > > > > -- > > > Jay Hanke, President > > > South Front Networks > > > jayhanke(a)southfront.io > > > Phone 612-204-0000 > > > CONFIDENTIALITY NOTICE. This e-mail and any files transmitted with it are the property of Clear Lake Independent Telephone Company and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to which this e-mail is addressed. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Unless stated to the contrary, any opinions or comments are personal to the writer and do not represent the official view of the company. If you are not the named recipient, please contact the sender by reply e-mail and delete this message immediately from your computer. > > > > > > > > -- > > Jay Hanke, President > > South Front Networks > > jayhanke(a)southfront.io > > Phone 612-204-0000 > > CONFIDENTIALITY NOTICE. This e-mail and any files transmitted with it are the property of Clear Lake Independent Telephone Company and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to which this e-mail is addressed. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Unless stated to the contrary, any opinions or comments are personal to the writer and do not represent the official view of the company. If you are not the named recipient, please contact the sender by reply e-mail and delete this message immediately from your computer. > > > > -- > Jay Hanke, President > South Front Networks > jayhanke(a)southfront.io > Phone 612-204-0000 > CONFIDENTIALITY NOTICE. This e-mail and any files transmitted with it are the property of Clear Lake Independent Telephone Company and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to which this e-mail is addressed. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Unless stated to the contrary, any opinions or comments are personal to the writer and do not represent the official view of the company. If you are not the named recipient, please contact the sender by reply e-mail and delete this message immediately from your computer. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000 CONFIDENTIALITY NOTICE. This e-mail and any files transmitted with it are the property of Clear Lake Independent Telephone Company and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to which this e-mail is addressed. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Unless stated to the contrary, any opinions or comments are personal to the writer and do not represent the official view of the company. If you are not the named recipient, please contact the sender by reply e-mail and delete this message immediately from your computer.

Jan. 28, 2022

Re: Problems Reaching 206.108.255.164

by Jay Hanke

There was a hung entry in the config. I cleared it. Can you confirm? On Fri, Jan 28, 2022 at 3:27 PM Joshua Eckert <JoshuaEckert(a)cltel.com> wrote: > > We tried on both our sides and neither could get a response. > > > > Joshua Eckert | Systems Administrator > CL Tel | 107 N 4th St. | Clear Lake, IA 50428 > P: 641-357-2111 | F: 641-357-8800 > www.cltel.com | www.facebook.com/cltel > > -----Original Message----- > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay Hanke > Sent: Friday, January 28, 2022 3:21 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: Re: [MICE-DISCUSS] Problems Reaching 206.108.255.164 > > SECURITY NOTICE: This is an email from an EXTERNAL source. If it appears to be from an internal source please notify the CLTEL JCIT team immediately. Please exercise caution and DO NOT open attachments or click links from unknown senders or in unexpected emails. > ________________________________ > > > I cleared mac on the remote switch can you check again? > > I can clear the 100G one as well if that doesn't work. > > On Fri, Jan 28, 2022 at 3:12 PM Joshua Eckert <JoshuaEckert(a)cltel.com> wrote: > > > > We did, and we checked with IP Pathways and the mac address in our arp was correct. > > > > > > > > Joshua Eckert | Systems Administrator > > CL Tel | 107 N 4th St. | Clear Lake, IA 50428 > > P: 641-357-2111 | F: 641-357-8800 > > www.cltel.com | www.facebook.com/cltel > > > > -----Original Message----- > > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay > > Hanke > > Sent: Friday, January 28, 2022 3:09 PM > > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > > Subject: Re: [MICE-DISCUSS] Problems Reaching 206.108.255.164 > > > > SECURITY NOTICE: This is an email from an EXTERNAL source. If it appears to be from an internal source please notify the CLTEL JCIT team immediately. Please exercise caution and DO NOT open attachments or click links from unknown senders or in unexpected emails. > > ________________________________ > > > > > > Have you cleared your arp cache on your router? > > > > On Fri, Jan 28, 2022 at 3:00 PM Joshua Eckert <JoshuaEckert(a)cltel.com> wrote: > > > > > > We can't get a response from 206.108.255.164, we're using 206.108.255.139 as the source IP. Other IPs in this subnet are responding. > > > > > > > > > > > > Joshua Eckert | Systems Administrator CL Tel | 107 N 4th St. | Clear > > > Lake, IA 50428 > > > P: 641-357-2111 | F: 641-357-8800 > > > www.cltel.com | www.facebook.com/cltel > > > > > > -----Original Message----- > > > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay > > > Hanke > > > Sent: Friday, January 28, 2022 2:51 PM > > > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > > > Subject: Re: [MICE-DISCUSS] Problems Reaching 206.108.255.164 > > > > > > SECURITY NOTICE: This is an email from an EXTERNAL source. If it appears to be from an internal source please notify the CLTEL JCIT team immediately. Please exercise caution and DO NOT open attachments or click links from unknown senders or in unexpected emails. > > > ________________________________ > > > > > > > > > We're seeing the next hop available from Davenport (via the Albert > > > Lea > > > remote) > > > > > > jayhanke@SFN-IA-Davenport-BDR1> ping 206.108.255.164 PING > > > 206.108.255.164 (206.108.255.164): 56 data bytes > > > 64 bytes from 206.108.255.164: icmp_seq=0 ttl=64 time=14.733 ms > > > 64 bytes from 206.108.255.164: icmp_seq=1 ttl=64 time=20.584 ms > > > 64 bytes from 206.108.255.164: icmp_seq=2 ttl=64 time=14.928 ms > > > 64 bytes from 206.108.255.164: icmp_seq=3 ttl=64 time=15.388 ms > > > 64 bytes from 206.108.255.164: icmp_seq=4 ttl=64 time=19.997 ms > > > 64 bytes from 206.108.255.164: icmp_seq=5 ttl=64 time=90.039 ms > > > 64 bytes from 206.108.255.164: icmp_seq=6 ttl=64 time=16.737 ms > > > 64 bytes from 206.108.255.164: icmp_seq=7 ttl=64 time=14.910 ms > > > 64 bytes from 206.108.255.164: icmp_seq=8 ttl=64 time=14.660 ms > > > 64 bytes from 206.108.255.164: icmp_seq=9 ttl=64 time=15.294 ms > > > 64 bytes from 206.108.255.164: icmp_seq=10 ttl=64 time=14.717 ms > > > 64 bytes from 206.108.255.164: icmp_seq=11 ttl=64 time=15.642 ms > > > 64 bytes from 206.108.255.164: icmp_seq=12 ttl=64 time=15.244 ms ^C > > > --- 206.108.255.164 ping statistics --- > > > 13 packets transmitted, 13 packets received, 0% packet loss > > > round-trip min/avg/max/stddev = 14.660/21.759/90.039/19.801 ms > > > > > > jayhanke@SFN-IA-Davenport-BDR1> > > > > > > UPN had circuit issues yesterday in the Urbandale area that affected this connection. I believe this has been resolved. > > > > > > On Fri, Jan 28, 2022 at 2:49 PM Jeremy Lumby <jlumby(a)mnvoip.com> wrote: > > > > > > > > Can you traceroute to the next hop past it? I can ping 206.108.255.164 however one thing to keep in mind is that the MICE subnet is not publically routed so to successfully ping 206.108.255.164 you will need to be logged into your MICE connected router so that it uses your MICE interface IP as the source address. > > > > > > > > > > > > Jeremy Lumby > > > > Minnesota VoIP > > > > 9217 17th Ave S #216 > > > > Bloomington, MN 55425 > > > > M: 612-355-7740 > > > > D: 612-392-6814 > > > > F: 952-873-7425 > > > > jlumby(a)mnvoip.com > > > > > > > > > > > > > > > > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On > > > > Behalf Of Joshua Eckert > > > > Sent: Friday, January 28, 2022 2:32 PM > > > > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > > > > Subject: [MICE-DISCUSS] Problems Reaching 206.108.255.164 > > > > > > > > We are having problems reaching 206.108.255.164. We found out this afternoon after a customer stated they were having problems reaching their company's server that has an IP in a subnet that looks like it is using that this IP as its next hop. > > > > > > > > B 199.201.120.0/24 [20/0] via 206.108.255.164, 20:24:51 > > > > > > > > Has anyone else had problems reaching this 206.108.255.164? I fairly new here, so I don't know if this is the right place to put these questions, if not please let me know. > > > > > > > > Thanks! > > > > > > > > > > > > > > > > > > > > > > > > > > > > Joshua Eckert | Systems Administrator CL Tel | 107 N 4th St. | > > > > Clear Lake, IA 50428 > > > > P: 641-357-2111 | F: 641-357-8800 > > > > www.cltel.com | www.facebook.com/cltel > > > > > > > > CONFIDENTIALITY NOTICE. This e-mail and any files transmitted with it are the property of Clear Lake Independent Telephone Company and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to which this e-mail is addressed. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Unless stated to the contrary, any opinions or comments are personal to the writer and do not represent the official view of the company. If you are not the named recipient, please contact the sender by reply e-mail and delete this message immediately from your computer. > > > > > > > > ________________________________________ > > > > To unsubscribe from the MICE-DISCUSS list, click the following link: > > > > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > > > > > > > > > > > -- > > > Jay Hanke, President > > > South Front Networks > > > jayhanke(a)southfront.io > > > Phone 612-204-0000 > > > CONFIDENTIALITY NOTICE. This e-mail and any files transmitted with it are the property of Clear Lake Independent Telephone Company and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to which this e-mail is addressed. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Unless stated to the contrary, any opinions or comments are personal to the writer and do not represent the official view of the company. If you are not the named recipient, please contact the sender by reply e-mail and delete this message immediately from your computer. > > > > > > > > -- > > Jay Hanke, President > > South Front Networks > > jayhanke(a)southfront.io > > Phone 612-204-0000 > > CONFIDENTIALITY NOTICE. This e-mail and any files transmitted with it are the property of Clear Lake Independent Telephone Company and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to which this e-mail is addressed. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Unless stated to the contrary, any opinions or comments are personal to the writer and do not represent the official view of the company. If you are not the named recipient, please contact the sender by reply e-mail and delete this message immediately from your computer. > > > > -- > Jay Hanke, President > South Front Networks > jayhanke(a)southfront.io > Phone 612-204-0000 > CONFIDENTIALITY NOTICE. This e-mail and any files transmitted with it are the property of Clear Lake Independent Telephone Company and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to which this e-mail is addressed. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Unless stated to the contrary, any opinions or comments are personal to the writer and do not represent the official view of the company. If you are not the named recipient, please contact the sender by reply e-mail and delete this message immediately from your computer. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Jan. 28, 2022

Re: Problems Reaching 206.108.255.164

by Joshua Eckert

We tried on both our sides and neither could get a response. Joshua Eckert | Systems Administrator CL Tel | 107 N 4th St. | Clear Lake, IA 50428 P: 641-357-2111 | F: 641-357-8800 www.cltel.com | www.facebook.com/cltel -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay Hanke Sent: Friday, January 28, 2022 3:21 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Problems Reaching 206.108.255.164 SECURITY NOTICE: This is an email from an EXTERNAL source. If it appears to be from an internal source please notify the CLTEL JCIT team immediately. Please exercise caution and DO NOT open attachments or click links from unknown senders or in unexpected emails. ________________________________ I cleared mac on the remote switch can you check again? I can clear the 100G one as well if that doesn't work. On Fri, Jan 28, 2022 at 3:12 PM Joshua Eckert <JoshuaEckert(a)cltel.com> wrote: > > We did, and we checked with IP Pathways and the mac address in our arp was correct. > > > > Joshua Eckert | Systems Administrator > CL Tel | 107 N 4th St. | Clear Lake, IA 50428 > P: 641-357-2111 | F: 641-357-8800 > www.cltel.com | www.facebook.com/cltel > > -----Original Message----- > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay > Hanke > Sent: Friday, January 28, 2022 3:09 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: Re: [MICE-DISCUSS] Problems Reaching 206.108.255.164 > > SECURITY NOTICE: This is an email from an EXTERNAL source. If it appears to be from an internal source please notify the CLTEL JCIT team immediately. Please exercise caution and DO NOT open attachments or click links from unknown senders or in unexpected emails. > ________________________________ > > > Have you cleared your arp cache on your router? > > On Fri, Jan 28, 2022 at 3:00 PM Joshua Eckert <JoshuaEckert(a)cltel.com> wrote: > > > > We can't get a response from 206.108.255.164, we're using 206.108.255.139 as the source IP. Other IPs in this subnet are responding. > > > > > > > > Joshua Eckert | Systems Administrator CL Tel | 107 N 4th St. | Clear > > Lake, IA 50428 > > P: 641-357-2111 | F: 641-357-8800 > > www.cltel.com | www.facebook.com/cltel > > > > -----Original Message----- > > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jay > > Hanke > > Sent: Friday, January 28, 2022 2:51 PM > > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > > Subject: Re: [MICE-DISCUSS] Problems Reaching 206.108.255.164 > > > > SECURITY NOTICE: This is an email from an EXTERNAL source. If it appears to be from an internal source please notify the CLTEL JCIT team immediately. Please exercise caution and DO NOT open attachments or click links from unknown senders or in unexpected emails. > > ________________________________ > > > > > > We're seeing the next hop available from Davenport (via the Albert > > Lea > > remote) > > > > jayhanke@SFN-IA-Davenport-BDR1> ping 206.108.255.164 PING > > 206.108.255.164 (206.108.255.164): 56 data bytes > > 64 bytes from 206.108.255.164: icmp_seq=0 ttl=64 time=14.733 ms > > 64 bytes from 206.108.255.164: icmp_seq=1 ttl=64 time=20.584 ms > > 64 bytes from 206.108.255.164: icmp_seq=2 ttl=64 time=14.928 ms > > 64 bytes from 206.108.255.164: icmp_seq=3 ttl=64 time=15.388 ms > > 64 bytes from 206.108.255.164: icmp_seq=4 ttl=64 time=19.997 ms > > 64 bytes from 206.108.255.164: icmp_seq=5 ttl=64 time=90.039 ms > > 64 bytes from 206.108.255.164: icmp_seq=6 ttl=64 time=16.737 ms > > 64 bytes from 206.108.255.164: icmp_seq=7 ttl=64 time=14.910 ms > > 64 bytes from 206.108.255.164: icmp_seq=8 ttl=64 time=14.660 ms > > 64 bytes from 206.108.255.164: icmp_seq=9 ttl=64 time=15.294 ms > > 64 bytes from 206.108.255.164: icmp_seq=10 ttl=64 time=14.717 ms > > 64 bytes from 206.108.255.164: icmp_seq=11 ttl=64 time=15.642 ms > > 64 bytes from 206.108.255.164: icmp_seq=12 ttl=64 time=15.244 ms ^C > > --- 206.108.255.164 ping statistics --- > > 13 packets transmitted, 13 packets received, 0% packet loss > > round-trip min/avg/max/stddev = 14.660/21.759/90.039/19.801 ms > > > > jayhanke@SFN-IA-Davenport-BDR1> > > > > UPN had circuit issues yesterday in the Urbandale area that affected this connection. I believe this has been resolved. > > > > On Fri, Jan 28, 2022 at 2:49 PM Jeremy Lumby <jlumby(a)mnvoip.com> wrote: > > > > > > Can you traceroute to the next hop past it? I can ping 206.108.255.164 however one thing to keep in mind is that the MICE subnet is not publically routed so to successfully ping 206.108.255.164 you will need to be logged into your MICE connected router so that it uses your MICE interface IP as the source address. > > > > > > > > > Jeremy Lumby > > > Minnesota VoIP > > > 9217 17th Ave S #216 > > > Bloomington, MN 55425 > > > M: 612-355-7740 > > > D: 612-392-6814 > > > F: 952-873-7425 > > > jlumby(a)mnvoip.com > > > > > > > > > > > > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On > > > Behalf Of Joshua Eckert > > > Sent: Friday, January 28, 2022 2:32 PM > > > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > > > Subject: [MICE-DISCUSS] Problems Reaching 206.108.255.164 > > > > > > We are having problems reaching 206.108.255.164. We found out this afternoon after a customer stated they were having problems reaching their company's server that has an IP in a subnet that looks like it is using that this IP as its next hop. > > > > > > B 199.201.120.0/24 [20/0] via 206.108.255.164, 20:24:51 > > > > > > Has anyone else had problems reaching this 206.108.255.164? I fairly new here, so I don't know if this is the right place to put these questions, if not please let me know. > > > > > > Thanks! > > > > > > > > > > > > > > > > > > > > > Joshua Eckert | Systems Administrator CL Tel | 107 N 4th St. | > > > Clear Lake, IA 50428 > > > P: 641-357-2111 | F: 641-357-8800 > > > www.cltel.com | www.facebook.com/cltel > > > > > > CONFIDENTIALITY NOTICE. This e-mail and any files transmitted with it are the property of Clear Lake Independent Telephone Company and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to which this e-mail is addressed. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Unless stated to the contrary, any opinions or comments are personal to the writer and do not represent the official view of the company. If you are not the named recipient, please contact the sender by reply e-mail and delete this message immediately from your computer. > > > > > > ________________________________________ > > > To unsubscribe from the MICE-DISCUSS list, click the following link: > > > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > > > > > > > -- > > Jay Hanke, President > > South Front Networks > > jayhanke(a)southfront.io > > Phone 612-204-0000 > > CONFIDENTIALITY NOTICE. This e-mail and any files transmitted with it are the property of Clear Lake Independent Telephone Company and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to which this e-mail is addressed. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Unless stated to the contrary, any opinions or comments are personal to the writer and do not represent the official view of the company. If you are not the named recipient, please contact the sender by reply e-mail and delete this message immediately from your computer. > > > > -- > Jay Hanke, President > South Front Networks > jayhanke(a)southfront.io > Phone 612-204-0000 > CONFIDENTIALITY NOTICE. This e-mail and any files transmitted with it are the property of Clear Lake Independent Telephone Company and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to which this e-mail is addressed. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Unless stated to the contrary, any opinions or comments are personal to the writer and do not represent the official view of the company. If you are not the named recipient, please contact the sender by reply e-mail and delete this message immediately from your computer. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000 CONFIDENTIALITY NOTICE. This e-mail and any files transmitted with it are the property of Clear Lake Independent Telephone Company and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to which this e-mail is addressed. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Unless stated to the contrary, any opinions or comments are personal to the writer and do not represent the official view of the company. If you are not the named recipient, please contact the sender by reply e-mail and delete this message immediately from your computer.

Jan. 28, 2022