 |
 |
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 <[log in to unmask]> 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 > [log in to unmask] > > > > From: MICE Discuss [mailto:[log in to unmask]] On Behalf Of Joshua Eckert > Sent: Friday, January 28, 2022 2:32 PM > To: [log in to unmask] > 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 [log in to unmask] Phone 612-204-0000