- mice-discuss - lists.micemn.net

Re: Problems Reaching 206.108.255.164

by Jay Hanke

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

Jan. 28, 2022

Re: Problems Reaching 206.108.255.164

by Joshua Eckert

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.

Jan. 28, 2022

Re: Problems Reaching 206.108.255.164

by Jay Hanke

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

Jan. 28, 2022

Re: Problems Reaching 206.108.255.164

by Joshua Eckert

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.

Jan. 28, 2022

Re: Problems Reaching 206.108.255.164

by Jay Hanke

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

Jan. 28, 2022

Re: Problems Reaching 206.108.255.164

by Jeremy Lumby

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

Jan. 28, 2022

Re: Problems Reaching 206.108.255.164

by Richard Laager

That IP is IP Pathways. They just moved from one SouthFront Networks remote switch to the other. So maybe that's related. On 1/28/22 14:32, Joshua Eckert wrote: > > 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 4^th 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 > <http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1> > -- Richard

Jan. 28, 2022

Problems Reaching 206.108.255.164

by Joshua Eckert

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! [cid:image001.png@01D81453.D1E9A120] 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.

Jan. 28, 2022

IP Pathways Port Move

by Jay Hanke

IP Pathways has moved from SFN Remote Ethernet 8 to SFN 100G Remote Ethernet7/2 -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Jan. 27, 2022

MPW Port Move

by Jay Hanke

MPW has been moved from SFN Remote Ethernet12 to SFN 100G Remote Ethernet6/1 -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Jan. 27, 2022