- mice-discuss - lists.micemn.net

Re: Akamai Traffic on MICE

by David Farmer

It looks like Akamai has found a sweet spot they tend to do that, the link between the switches peaked up to about 850 and backed off and is hovering abut 650Mbps for the last hour or so. From what I've seen in the past for Amakai it will probably do that the rest of the day. On 5/19/11 07:23 CDT, David Farmer wrote: > The 10G Akamai stack at the University is having an affect. > > The University turned up routing from the GigaPOP to MICE on its 10G > link Tuesday around 8pm. The new paths were also announced to the Akamai > route collector around that time too. Akamai started using these new > paths around 1:30 in the afternoon on Wednesday. The University's 10G > link peaked a little over 1G around 9:30pm last night. The bottleneck is > the 1G link between the CNS 10G switch and the 4500. It was saturated > from about 6:30pm to 9:30pm at about 950Mbps. > > Some of us are organizing to rectify the situation ASAP. There are some > workarounds that could help in the very short-term, yet this morning, > and we are looking to get the new Juniper switches with 10G up-links > installed ASAP However, the earliest that can happen it this afternoon, > as the switches are down in Mankato with Jay. There is a plan to get > them up to 511 by mid-afternoon. > > Also I'll be watching the links and can modify our announcement to the > Akamai route collector if necessary. Things are going to be fluid today. > > I'll just say that this is the kind of problem I like to see, if you are > going to have to deal with any problem. That is the problem of over > succeeding. > -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 =============================================== ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 19, 2011

Re: Akamai Traffic on MICE

by Steve Howard

On 05/19/2011 07:58 AM, Mitch Elfstrand wrote: > SDN is willing to move the connection to alleviate the issue. Please let us know if we need to send someone to 511 to help with anything. > That sounds like this might be an ideal short-term fix. Feel free to plug into Gig 0/2 on the CNS switch. We didn't leave any optics down there, you will need to provide a Cisco (or compatible) SFP. Alternatively, you could consider doing a 10Gig connection. Your peak was almost 600Mbps last night! If you want to do 10Gig, you'll need X2 optics for the CNS switch. Let me know and I'll assign a 10Gig port. CNS will donate use of 10Gig LR optics to MICE for use in the CNS switch to connect to the Juniper switch. Unfortunately, those optics are in Bemidji. I will check to see if anybody here is going to the Cities today, if so I will send the optics with them, if not, I will overnight them to Mike Hemphill at FWR. (Mike, I hope that is OK with you). Thanks, Steve > Regards, > > Mitch Elfstrand | Director of Network Engineering > mitch.elfstrand(a)sdncommunications.com | 2900 W 10th St. | Sioux Falls, SD 57104 USA > Direct +1.605.978.3587 | Mobile +1.605.212.3392 | TF +1.800.247.1442 | Fax +1.605.334.4782 > > > > > -----Original Message----- > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Doug McIntyre > Sent: Thursday, May 19, 2011 7:54 AM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: Re: [MICE-DISCUSS] Akamai Traffic on MICE > > On Thu, May 19, 2011 at 07:23:48AM -0500, David Farmer wrote: >> Some of us are organizing to rectify the situation ASAP. There are >> some workarounds that could help in the very short-term... > Specificly one thing that could be done is if SDN could be moved from > the 4500 onto the 3560, and FWR could string another cross-connect > temporarily between the 3560 and the other fiber "uplink" port on the > 4500, we could change those two gig ports into an Etherchannel. > > This would move the biggest destination of the Akamai traffic closer > to the source, as well as preventing one endpoint from swamping the > interconnect.. > > Even if SDN could be moved to the 3560 would do a lot to alleviate the issue. > > -- > Doug McIntyre <merlyn(a)iphouse.net> > -- ipHouse/Goldengate/Bitstream/ProNS -- > Network Engineer/Provisioning/Jack of all Trades > > ######################################################################## > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > ***This message and any attachments are solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use or distribution of the information included in this message is prohibited -- Please immediately and permanently delete.*** > > ######################################################################## > > 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

May 19, 2011

Re: Akamai Traffic on MICE

by Mitch Elfstrand

SDN is willing to move the connection to alleviate the issue. Please let us know if we need to send someone to 511 to help with anything. Regards, Mitch Elfstrand | Director of Network Engineering mitch.elfstrand(a)sdncommunications.com | 2900 W 10th St. | Sioux Falls, SD 57104 USA Direct +1.605.978.3587 | Mobile +1.605.212.3392 | TF +1.800.247.1442 | Fax +1.605.334.4782 -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Doug McIntyre Sent: Thursday, May 19, 2011 7:54 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Akamai Traffic on MICE On Thu, May 19, 2011 at 07:23:48AM -0500, David Farmer wrote: > Some of us are organizing to rectify the situation ASAP. There are > some workarounds that could help in the very short-term... Specificly one thing that could be done is if SDN could be moved from the 4500 onto the 3560, and FWR could string another cross-connect temporarily between the 3560 and the other fiber "uplink" port on the 4500, we could change those two gig ports into an Etherchannel. This would move the biggest destination of the Akamai traffic closer to the source, as well as preventing one endpoint from swamping the interconnect.. Even if SDN could be moved to the 3560 would do a lot to alleviate the issue. -- Doug McIntyre <merlyn(a)iphouse.net> -- ipHouse/Goldengate/Bitstream/ProNS -- Network Engineer/Provisioning/Jack of all Trades ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ***This message and any attachments are solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use or distribution of the information included in this message is prohibited -- Please immediately and permanently delete.*** ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 19, 2011

Re: Akamai Traffic on MICE

by Doug McIntyre

On Thu, May 19, 2011 at 07:23:48AM -0500, David Farmer wrote: > Some of us are organizing to rectify the situation ASAP. There are > some workarounds that could help in the very short-term... Specificly one thing that could be done is if SDN could be moved from the 4500 onto the 3560, and FWR could string another cross-connect temporarily between the 3560 and the other fiber "uplink" port on the 4500, we could change those two gig ports into an Etherchannel. This would move the biggest destination of the Akamai traffic closer to the source, as well as preventing one endpoint from swamping the interconnect.. Even if SDN could be moved to the 3560 would do a lot to alleviate the issue. -- Doug McIntyre <merlyn(a)iphouse.net> -- ipHouse/Goldengate/Bitstream/ProNS -- Network Engineer/Provisioning/Jack of all Trades ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 19, 2011

Akamai Traffic on MICE

by David Farmer

The 10G Akamai stack at the University is having an affect. The University turned up routing from the GigaPOP to MICE on its 10G link Tuesday around 8pm. The new paths were also announced to the Akamai route collector around that time too. Akamai started using these new paths around 1:30 in the afternoon on Wednesday. The University's 10G link peaked a little over 1G around 9:30pm last night. The bottleneck is the 1G link between the CNS 10G switch and the 4500. It was saturated from about 6:30pm to 9:30pm at about 950Mbps. Some of us are organizing to rectify the situation ASAP. There are some workarounds that could help in the very short-term, yet this morning, and we are looking to get the new Juniper switches with 10G up-links installed ASAP However, the earliest that can happen it this afternoon, as the switches are down in Mankato with Jay. There is a plan to get them up to 511 by mid-afternoon. Also I'll be watching the links and can modify our announcement to the Akamai route collector if necessary. Things are going to be fluid today. I'll just say that this is the kind of problem I like to see, if you are going to have to deal with any problem. That is the problem of over succeeding. -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 =============================================== ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 19, 2011

Re: MICE Traffic

by Tom Drill

We can help with lead time. On Wed, May 18, 2011 at 10:24 PM, Jay Hanke <jayhanke(a)mankatonetworks.net>wrote: > We have seen a dramatic growth in traffic on the exchange. The GE link > between the CNS remote switch and the Main switch is running about > ~950 Mb/s. We're going to need to make some upgrades shortly to avoid > degrading services. Perhaps more quickly than originally planned. > > We may need some volunteers and stuff depending on the course of action. > > Jay > > ######################################################################## > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > -- MyTELEPATH | Tom Drill tdrill(a)mytelepath.com 11970 Portland Ave. Burnsville, MN 55337 952-400-6004 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 19, 2011

Re: MICE Traffic

by Jeremy Lumby

I would be happy to help out at 511 today if needed. -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Jay Hanke Sent: Wednesday, May 18, 2011 10:25 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] MICE Traffic We have seen a dramatic growth in traffic on the exchange. The GE link between the CNS remote switch and the Main switch is running about ~950 Mb/s. We're going to need to make some upgrades shortly to avoid degrading services. Perhaps more quickly than originally planned. We may need some volunteers and stuff depending on the course of action. Jay ######################################################################## 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

May 19, 2011

Re: Traffic between 10Gig & 1Gig Switches

by Owen DeLong

On May 18, 2011, at 2:52 PM, Steve Howard wrote: > The traffic to/from the U shot up today. I'm guessing that is CDN related? > > The link between the CNS switch and the MICE switch shot up to ~850Mbps > today. Too bad that is only a single gig connection! > > It is great to have the traffic on the exchange, but we should probably > deal with this nearly saturated link fast. Here are a few possible > solutions: > > 1) Add another Gig connection. We'd probably need to pay FWR for a > cross-connect (CNS is paying for the first one) with this option; > > 2) Use one of the new Juniper switches with a 10Gig interface and > connect that to a 10Gig interface on the existing MICE 10Gig switch, > then move some of the 1Gig members over to those ports. This would > require purchase of 10Gig optics for the Juniper and the existing 10Gig > MICE switch; > > 3) Move some of the higher bandwidth MICE members to the 1Gig ports on > the 10Gig switch. Would this increase the FWR cross-connect charges > for those members if they are going from copper to fiber? > > 4) Encourage MICE members on the 1Gig switch to upgrade to a 10Gig > connection; > > 5) Ask the U to not advertise some of the members on the 1Gig switch to > CDNs (if that is the cause of the traffic load). This is a bummer if > you are one of the networks that gets left out. I really don't like > this option -- we are finally getting real traffic on the exchange and > then we'd be cutting back. > > What does everybody think? Any other suggestions? > To the extent that my input is useful, I encourage option 2. I believe this is the more scalable longer-term solution and does not represent a significantly higher cost than any of the others will in relatively short order. Owen ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 19, 2011

MICE Traffic

by Jay Hanke

We have seen a dramatic growth in traffic on the exchange. The GE link between the CNS remote switch and the Main switch is running about ~950 Mb/s. We're going to need to make some upgrades shortly to avoid degrading services. Perhaps more quickly than originally planned. We may need some volunteers and stuff depending on the course of action. Jay ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 19, 2011

Re: Traffic between 10Gig & 1Gig Switches

by Jay Hanke

On Wed, May 18, 2011 at 5:43 PM, Steve Howard <showard(a)paulbunyan.net> wrote: > What type? LX? Should be, I didn't pull them out to verify. James can you take a quick look at those? ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 18, 2011

Re: Traffic between 10Gig & 1Gig Switches

by Steve Howard

What type? LX? On 05/18/2011 05:27 PM, Jay Hanke wrote: >> Was I mistaken is reading the original donation note about the Juniper switches that Juniper included the 10GE uplink module or did it also include optics? > There are a couple of 10G SFP+ modules included along with the Juniper > switch. I don't think there were any 1 G optics. > > jay > > ######################################################################## > > 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

May 18, 2011

Re: Traffic between 10Gig & 1Gig Switches

by Jay Hanke

> Was I mistaken is reading the original donation note about the Juniper switches that Juniper included the 10GE uplink module or did it also include optics? There are a couple of 10G SFP+ modules included along with the Juniper switch. I don't think there were any 1 G optics. jay ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 18, 2011

Re: Traffic between 10Gig & 1Gig Switches

by Nevin Lyne

Guys >>2) Use one of the new Juniper switches with a 10Gig interface and >>connect that to a 10Gig interface on the existing MICE 10Gig switch, >>then move some of the 1Gig members over to those ports. This would >>require purchase of 10Gig optics for the Juniper and the existing 10Gig >>MICE switch; > > This will probably be happening. Was I mistaken is reading the original donation note about the Juniper switches that Juniper included the 10GE uplink module or did it also include optics? If it did not include one or both of those I would be willing to donate some money towards the uplink module & optics needed on both ends. -- Nevin Lyne -- Founder / Director of Technology -- EngineHosting.com -- 888-576-HOST or 612-234-8964 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 18, 2011

Re: Traffic between 10Gig & 1Gig Switches

by Mike Horwath

On 5/18/11 4:52 PM, "Steve Howard" <showard(a)PAULBUNYAN.NET> wrote: >The traffic to/from the U shot up today. I'm guessing that is CDN >related? > >The link between the CNS switch and the MICE switch shot up to ~850Mbps >today. Too bad that is only a single gig connection! Changing later when the 2 new switches go into place. >It is great to have the traffic on the exchange, but we should probably >deal with this nearly saturated link fast. Here are a few possible >solutions: > >1) Add another Gig connection. We'd probably need to pay FWR for a >cross-connect (CNS is paying for the first one) with this option; > >2) Use one of the new Juniper switches with a 10Gig interface and >connect that to a 10Gig interface on the existing MICE 10Gig switch, >then move some of the 1Gig members over to those ports. This would >require purchase of 10Gig optics for the Juniper and the existing 10Gig >MICE switch; This will probably be happening. >4) Encourage MICE members on the 1Gig switch to upgrade to a 10Gig >connection; Don't see how that helps. >5) Ask the U to not advertise some of the members on the 1Gig switch to >CDNs (if that is the cause of the traffic load). This is a bummer if >you are one of the networks that gets left out. I really don't like >this option -- we are finally getting real traffic on the exchange and >then we'd be cutting back. That'd be silly. -- Mike Horwath ipHouse - Welcome home! drechsau(a)iphouse.net The universe is an island, surrounded by whatever it is that surrounds universes. - Berkeley Fortune ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 18, 2011

Re: Traffic between 10Gig & 1Gig Switches

by Jeremy Lumby

Looking at the graphs, it is apparent that most of the traffic is going to one MICE member. I would believe that they would be inclined to want to move to a 10 gig link since it is really benefiting them, and since it is the same fiber cross connect, the only real cost would be the 10G optics. The second thing that is much more long term is I believe that the link between the switches should be 10Gig. This would not allow a single 1Gig member to do so much unexpected traffic that effects the exchange as a whole, and we would be able to watch trends, and adjust as needed before the situation became urgent. Jeremy -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Steve Howard Sent: Wednesday, May 18, 2011 4:52 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Traffic between 10Gig & 1Gig Switches The traffic to/from the U shot up today. I'm guessing that is CDN related? The link between the CNS switch and the MICE switch shot up to ~850Mbps today. Too bad that is only a single gig connection! It is great to have the traffic on the exchange, but we should probably deal with this nearly saturated link fast. Here are a few possible solutions: 1) Add another Gig connection. We'd probably need to pay FWR for a cross-connect (CNS is paying for the first one) with this option; 2) Use one of the new Juniper switches with a 10Gig interface and connect that to a 10Gig interface on the existing MICE 10Gig switch, then move some of the 1Gig members over to those ports. This would require purchase of 10Gig optics for the Juniper and the existing 10Gig MICE switch; 3) Move some of the higher bandwidth MICE members to the 1Gig ports on the 10Gig switch. Would this increase the FWR cross-connect charges for those members if they are going from copper to fiber? 4) Encourage MICE members on the 1Gig switch to upgrade to a 10Gig connection; 5) Ask the U to not advertise some of the members on the 1Gig switch to CDNs (if that is the cause of the traffic load). This is a bummer if you are one of the networks that gets left out. I really don't like this option -- we are finally getting real traffic on the exchange and then we'd be cutting back. What does everybody think? Any other suggestions? ######################################################################## 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

May 18, 2011

Re: Traffic between 10Gig & 1Gig Switches

by David Farmer

I looks like it is going to SDN and Airstream for the most part. There are two short term solutions; 1. move those to the CNS switch, I have Copper SFPs I can loan if necessary. 2. I can stop announcing those AS to the Akamai route collector. The longer term solution is to get the Juniper switches installed. On 5/18/11 16:52 CDT, Steve Howard wrote: > The traffic to/from the U shot up today. I'm guessing that is CDN related? > > The link between the CNS switch and the MICE switch shot up to ~850Mbps > today. Too bad that is only a single gig connection! > > It is great to have the traffic on the exchange, but we should probably > deal with this nearly saturated link fast. Here are a few possible > solutions: > > 1) Add another Gig connection. We'd probably need to pay FWR for a > cross-connect (CNS is paying for the first one) with this option; > > 2) Use one of the new Juniper switches with a 10Gig interface and > connect that to a 10Gig interface on the existing MICE 10Gig switch, > then move some of the 1Gig members over to those ports. This would > require purchase of 10Gig optics for the Juniper and the existing 10Gig > MICE switch; > > 3) Move some of the higher bandwidth MICE members to the 1Gig ports on > the 10Gig switch. Would this increase the FWR cross-connect charges > for those members if they are going from copper to fiber? > > 4) Encourage MICE members on the 1Gig switch to upgrade to a 10Gig > connection; > > 5) Ask the U to not advertise some of the members on the 1Gig switch to > CDNs (if that is the cause of the traffic load). This is a bummer if > you are one of the networks that gets left out. I really don't like > this option -- we are finally getting real traffic on the exchange and > then we'd be cutting back. > > What does everybody think? Any other suggestions? > > ######################################################################## > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 =============================================== ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 18, 2011

Traffic between 10Gig & 1Gig Switches

by Steve Howard

The traffic to/from the U shot up today. I'm guessing that is CDN related? The link between the CNS switch and the MICE switch shot up to ~850Mbps today. Too bad that is only a single gig connection! It is great to have the traffic on the exchange, but we should probably deal with this nearly saturated link fast. Here are a few possible solutions: 1) Add another Gig connection. We'd probably need to pay FWR for a cross-connect (CNS is paying for the first one) with this option; 2) Use one of the new Juniper switches with a 10Gig interface and connect that to a 10Gig interface on the existing MICE 10Gig switch, then move some of the 1Gig members over to those ports. This would require purchase of 10Gig optics for the Juniper and the existing 10Gig MICE switch; 3) Move some of the higher bandwidth MICE members to the 1Gig ports on the 10Gig switch. Would this increase the FWR cross-connect charges for those members if they are going from copper to fiber? 4) Encourage MICE members on the 1Gig switch to upgrade to a 10Gig connection; 5) Ask the U to not advertise some of the members on the 1Gig switch to CDNs (if that is the cause of the traffic load). This is a bummer if you are one of the networks that gets left out. I really don't like this option -- we are finally getting real traffic on the exchange and then we'd be cutting back. What does everybody think? Any other suggestions? ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 18, 2011

WOW!!!

by David Farmer

Between 1:30 and 2:00 today Akamai started sending traffic to someone (or multiple someones) on MICE from our 10G connected stack of servers to the tune of about 800Mbps or more, and its still going. How full are the links between the switches? :) let me know if I need to do something on my side. http://perfsonar.northernlights.gigapop.net/gui/cacti/graph.php?action=view… FYI, those graphs are in MBytes/sec multiply by 8 for Mbps. COOL!!! -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 =============================================== ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 18, 2011

Bandwidth Testing Tool

by David Farmer

On 5/18/11 10:13 CDT, Doug McIntyre wrote: > On Wed, May 18, 2011 at 12:43:11AM -0500, David Farmer wrote: >> We are routing traffic now, IPv4 only for now. I need to clean up a >> number of route map issues for IPv6 before routing it. I should have >> that cleaned up tomorrow. > > Cool, looking good here. > > Nice to have sub millisec pings to the U of MN network. Here is a bandwidth testing tool you can use and tell you more than just round trip time. http://infotech-sv-62.ggnet.umn.edu:7123/ Check out the "More Details" and "Statistics" buttons too, lots of cool network engineer level details. -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 =============================================== ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 18, 2011

Re: UMN connected?

by Doug McIntyre

On Wed, May 18, 2011 at 12:43:11AM -0500, David Farmer wrote: > We are routing traffic now, IPv4 only for now. I need to clean up a > number of route map issues for IPv6 before routing it. I should have > that cleaned up tomorrow. Cool, looking good here. Nice to have sub millisec pings to the U of MN network. -- Doug McIntyre <merlyn(a)iphouse.net> -- ipHouse/Goldengate/Bitstream/ProNS -- Network Engineer/Provisioning/Jack of all Trades ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 18, 2011

Re: UMN connected?

by David Farmer

We are routing traffic now, IPv4 only for now. I need to clean up a number of route map issues for IPv6 before routing it. I should have that cleaned up tomorrow. On 5/16/11 17:19 CDT, Mike Horwath wrote: > On 5/16/11 5:16 PM, "David Farmer"<farmer(a)umn.edu> wrote: > >> Yes we are connected, I am waiting on change control before we start >> accepting any routes or start announcing any routes. I hope to have >> news tomorrow, when we plan to make it happen. Besides I needed bring >> up the peering sessions to get a better idea of the impact of the change >> and to do a little analysis. >> >> FYI, we will be adding to the MLPA approximately 427 IPv4 routes, not >> quite doubling the number of IPv4 routes, consisting of well over 3 >> million IPv4 addresses, more than doubling and probably tripling the >> number of IPv4 addresses available to the MLPA. That includes a couple >> of other local commercial peers we currently have, our 10G connected >> Akamai stack, and all of our GigaPOP Participants. I will be >> encouraging our commercial peers to connect directly to MICE in the >> future. > > I am excited! > -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 =============================================== ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 18, 2011

Re: MICE Presentation at Vaultas?

by John Unger

Jay Hanke is doing the presentation at our Grand Opening Celebration Event.. we have large scale bandwidth available for most any application. We did not have plans to broadcast the presentation but if someone is interested we have the available resources. Thanks, John A. Unger President 13033 Ridgedale Drive Suite 330 Minnetonka, MN 55305 D: 612.238.1601 C: 612.325-2909 john(a)vaultas.com Vaultas Alexandria, LLC 720 Hawthorne Street PO Box 546 Alexandria, MN 56308 D: 320.759.5800 Vaultas St Cloud, LLC 3701 18th Street South St Cloud, MN 56303 D: 320.443.6700 This message is intended only for the named recipient(s) and may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any misdirected transmission. If you received this message in error, please notify us immediately by telephone at 612.325.2909 and immediately delete this message from your system. If you are not the intended recipient, you must not use, disclose, distribute or copy any part of this message. -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Steve Howard Sent: Tuesday, May 17, 2011 11:02 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] MICE Presentation at Vaultas? Hello, I had an e-mail forwarded my way that indicates that MICE will be doing a presentation at John Unger's new data center in Alexandria next week. I'm curious, who is doing the presentation? What are the options to connect to MICE from Alexandria? Also, I was at an IPv6 presentation last week at the Tristate Operators Conference. The speaker asked about how many people were using IPv6. We were the only company that raised our hands. Sad. During the question/answer period I mentioned MICE and that you could get free IPv6 transit via Hurricane Electric if you are connected to MICE. Nobody indicated any interest. More sadness. At least they've now heard about MICE. Steve ######################################################################## 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

May 17, 2011

Re: Recruitment / Advertising to MICE

by Andrew Hoyos

I've got a contact at Qwest/CenturyLink from the InteropNet - I'll see what I can drum up. On May 11, 2011, at 9:03 PM, Frank Bulk wrote: > Are Comcast and CenturyLink/Qwest at 511 already? If so, I’m sure MICE members would have some contacts… > > Frank > > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Justin Krejci > Sent: Wednesday, May 11, 2011 7:44 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: [MICE-DISCUSS] Recruitment / Advertising to MICE > > Hello List, > > US Internet is in the process of getting connected to the network. In fact I plan to pop down to FWR this evening still and plug in the cross connect on my way home. > > In any case I only became aware of MICE thru unrelated discussions with WIN who mentioned it to me and passed me Jay's contact info which brings me to the subject at hand, is there any effort or interest in making a more official recruitment effort to get networks and providers to join up? I realize MICE is still pretty new and fresh but it strikes me it is only as useful as the networks that are participating. I think it would be great if we got Comcast and Qwest (CenturyLink, whatever) in particular to join up as they have big local networks in town. > > I also scanned some of the archives and was interested in the whole CDN participation idea. Any news on that at all with Akamai or others for that matter? Also are there any plans on the table for future UG meetings for MICE? > > > -Justin Krejci > > > 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

May 17, 2011

MICE Presentation at Vaultas?

by Steve Howard

Hello, I had an e-mail forwarded my way that indicates that MICE will be doing a presentation at John Unger's new data center in Alexandria next week. I'm curious, who is doing the presentation? What are the options to connect to MICE from Alexandria? Also, I was at an IPv6 presentation last week at the Tristate Operators Conference. The speaker asked about how many people were using IPv6. We were the only company that raised our hands. Sad. During the question/answer period I mentioned MICE and that you could get free IPv6 transit via Hurricane Electric if you are connected to MICE. Nobody indicated any interest. More sadness. At least they've now heard about MICE. Steve ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 17, 2011

Re: 2011 Q2 Steering Committee Election Results

by Owen DeLong

But you did skip the MICE UG meeting. :p Owen On May 16, 2011, at 6:04 PM, Reid Fishler wrote: > Still, I was there...and I stopped by 511... > On May 16, 2011 6:02 PM, "Mike Horwath" <drechsau(a)iphouse.net> wrote: > > > > On 5/16/11 7:38 PM, "Reid Fishler" <rfishler(a)HE.NET> wrote: > > > > >I was there for MNTE. > > > > I am not a telecomm. > > > > -- > > Mike Horwath ipHouse - Welcome home! drechsau(a)iphouse.net > > The universe is an island, surrounded by whatever it is > > that surrounds universes. - Berkeley Fortune > > > > ######################################################################## > > > > 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

May 17, 2011

Re: 2011 Q2 Steering Committee Election Results

by Reid Fishler

Still, I was there...and I stopped by 511... On May 16, 2011 6:02 PM, "Mike Horwath" <drechsau(a)iphouse.net> wrote: > > On 5/16/11 7:38 PM, "Reid Fishler" <rfishler(a)HE.NET> wrote: > > >I was there for MNTE. > > I am not a telecomm. > > -- > Mike Horwath ipHouse - Welcome home! drechsau(a)iphouse.net > The universe is an island, surrounded by whatever it is > that surrounds universes. - Berkeley Fortune > > ######################################################################## > > 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

May 17, 2011

Re: 2011 Q2 Steering Committee Election Results

by Mike Horwath

On 5/16/11 7:38 PM, "Reid Fishler" <rfishler(a)HE.NET> wrote: >I was there for MNTE. I am not a telecomm. -- Mike Horwath ipHouse - Welcome home! drechsau(a)iphouse.net The universe is an island, surrounded by whatever it is that surrounds universes. - Berkeley Fortune ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 17, 2011

Re: 2011 Q2 Steering Committee Election Results

by Reid Fishler

I was there for MNTE. Reid On Mon, May 16, 2011 at 8:36 PM, Mike Horwath <drechsau(a)iphouse.net> wrote: > On 5/16/11 7:35 PM, "Reid Fishler" <rfishler(a)HE.NET> wrote: > >>I HAVE visited. I was just there! > > I didn't get an intro! > > Were you here for the turnup of the POP? > > -- > Mike Horwath ipHouse - Welcome home! drechsau(a)iphouse.net > The universe is an island, surrounded by whatever it is > that surrounds universes. - Berkeley Fortune > > ######################################################################## > > 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

May 17, 2011

Re: 2011 Q2 Steering Committee Election Results

by Mike Horwath

On 5/16/11 7:35 PM, "Reid Fishler" <rfishler(a)HE.NET> wrote: >I HAVE visited. I was just there! I didn't get an intro! Were you here for the turnup of the POP? -- Mike Horwath ipHouse - Welcome home! drechsau(a)iphouse.net The universe is an island, surrounded by whatever it is that surrounds universes. - Berkeley Fortune ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 17, 2011

Re: 2011 Q2 Steering Committee Election Results

by Reid Fishler

I HAVE visited. I was just there! Reid On Mon, May 16, 2011 at 8:33 PM, Mike Horwath <drechsau(a)iphouse.net> wrote: > On 5/16/11 7:20 PM, "Jay Hanke" <jayhanke(a)MANKATONETWORKS.NET> wrote: > >>Please congratulate Reid Fishler of Hurricane Electric as the new MICE >>Steering Committee Member! >> >>Next election is Fall-ish 2011. >> >>Congrats and welcome aboard! > > WHOOO! > > Now how do we get him to visit us... :) > > -- > Mike Horwath ipHouse - Welcome home! drechsau(a)iphouse.net > The universe is an island, surrounded by whatever it is > that surrounds universes. - Berkeley Fortune > > ######################################################################## > > 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

May 17, 2011

Re: 2011 Q2 Steering Committee Election Results

by Mike Horwath

On 5/16/11 7:20 PM, "Jay Hanke" <jayhanke(a)MANKATONETWORKS.NET> wrote: >Please congratulate Reid Fishler of Hurricane Electric as the new MICE >Steering Committee Member! > >Next election is Fall-ish 2011. > >Congrats and welcome aboard! WHOOO! Now how do we get him to visit us... :) -- Mike Horwath ipHouse - Welcome home! drechsau(a)iphouse.net The universe is an island, surrounded by whatever it is that surrounds universes. - Berkeley Fortune ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 17, 2011

2011 Q2 Steering Committee Election Results

by Jay Hanke

Please congratulate Reid Fishler of Hurricane Electric as the new MICE Steering Committee Member! Next election is Fall-ish 2011. Congrats and welcome aboard! Jay ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 17, 2011

Re: UMN connected?

by Mike Horwath

On 5/16/11 5:16 PM, "David Farmer" <farmer(a)umn.edu> wrote: >Yes we are connected, I am waiting on change control before we start >accepting any routes or start announcing any routes. I hope to have >news tomorrow, when we plan to make it happen. Besides I needed bring >up the peering sessions to get a better idea of the impact of the change >and to do a little analysis. > >FYI, we will be adding to the MLPA approximately 427 IPv4 routes, not >quite doubling the number of IPv4 routes, consisting of well over 3 >million IPv4 addresses, more than doubling and probably tripling the >number of IPv4 addresses available to the MLPA. That includes a couple >of other local commercial peers we currently have, our 10G connected >Akamai stack, and all of our GigaPOP Participants. I will be >encouraging our commercial peers to connect directly to MICE in the >future. I am excited! -- Mike Horwath ipHouse - Welcome home! drechsau(a)iphouse.net The universe is an island, surrounded by whatever it is that surrounds universes. - Berkeley Fortune ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 16, 2011

Re: UMN connected?

by David Farmer

Yes we are connected, I am waiting on change control before we start accepting any routes or start announcing any routes. I hope to have news tomorrow, when we plan to make it happen. Besides I needed bring up the peering sessions to get a better idea of the impact of the change and to do a little analysis. FYI, we will be adding to the MLPA approximately 427 IPv4 routes, not quite doubling the number of IPv4 routes, consisting of well over 3 million IPv4 addresses, more than doubling and probably tripling the number of IPv4 addresses available to the MLPA. That includes a couple of other local commercial peers we currently have, our 10G connected Akamai stack, and all of our GigaPOP Participants. I will be encouraging our commercial peers to connect directly to MICE in the future. On 5/16/11 14:54 CDT, Mike Horwath wrote: > Say it isn't so! > > Mr. Farmer, care to start pushing some routes out to MICE? > > ASN_57 BGP master up May13 Established > ... > Routes: 0 imported, 475 exported, 0 preferred > > Excited to see things change. > > -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 =============================================== ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 16, 2011

UMN connected?

by Mike Horwath

Say it isn't so! Mr. Farmer, care to start pushing some routes out to MICE? ASN_57 BGP master up May13 Established ... Routes: 0 imported, 475 exported, 0 preferred Excited to see things change. -- Mike Horwath ipHouse - Welcome home! drechsau(a)iphouse.net The universe is an island, surrounded by whatever it is that surrounds universes. - Berkeley Fortune ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 16, 2011

Re: Management IP address for new Juniper Switches?

by Doug McIntyre

On Mon, May 16, 2011 at 10:55:03AM -0500, Doug McIntyre wrote: > On Mon, May 16, 2011 at 10:47:45AM -0500, James Montz wrote: > > Mike et. al. @ IPHouse; > > > > As you were gracious enough to provide routable IP's (216.250.183.9/.10) to > > manage the existing MICE switches, If available, can we get an additional IP > > allocated for the new Juniper Swtich? > > Thats a /29 routed block. Gateway is 216.250.183.14. > So, take 216.250.183.11 & 216.250.183.12 I should mention that the current switches are totally within MICE IP address space. the 4503 is 69.147.218.254 The 3560E is 69.147.218.25 -- Doug McIntyre <merlyn(a)iphouse.net> -- ipHouse/Goldengate/Bitstream/ProNS -- Network Engineer/Provisioning/Jack of all Trades ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 16, 2011

Re: Management IP address for new Juniper Switches?

by Doug McIntyre

On Mon, May 16, 2011 at 10:47:45AM -0500, James Montz wrote: > Mike et. al. @ IPHouse; > > As you were gracious enough to provide routable IP's (216.250.183.9/.10) to > manage the existing MICE switches, If available, can we get an additional IP > allocated for the new Juniper Swtich? Thats a /29 routed block. Gateway is 216.250.183.14. So, take 216.250.183.11 & 216.250.183.12 -- Doug McIntyre <merlyn(a)iphouse.net> -- ipHouse/Goldengate/Bitstream/ProNS -- Network Engineer/Provisioning/Jack of all Trades ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 16, 2011

Management IP address for new Juniper Switches?

by James Montz

Mike et. al. @ IPHouse; As you were gracious enough to provide routable IP's (216.250.183.9/.10) to manage the existing MICE switches, If available, can we get an additional IP allocated for the new Juniper Swtich? --------------------------------------------------- *James C. Montz* Senior Consultant *Mankato Networks LLC* <http://www.mankatonetworks.net/>320 East Liberty Street <http://maps.google.com/maps?q=320+East+Liberty+Street%2CMankato%2CMN+56001&…>Mankato, MN 56001 *Phone:* *(320)-496-6689* *Email: jamesmontz(a)mankatonetworks.net* *Web: http://www.mankatonetworks.net Skype: james.montz* * http://www.linkedin.com/in/jmontz* ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 16, 2011

Re: Looking Glass / Route Server for MICE

by Mike Horwath

On 5/13/11 2:12 PM, "James Montz" <jamesmontz(a)MANKATONETWORKS.NET> wrote: >If you look at the command output by the DE-ICX... It looks like the >Cisco show ip gbp summary command, that is not the BIRD command. >So it looks like their looking glass is pulling route data froma Cisco L3 >device. > >It IS possible to pull the data from the BIRD command, however, this >involves allowing PHP execute() on the web server, requiring some >"hackery" That isn't hackery. Though custom code sucks to maintain. And bird really wants root to access the socket so that requires more work as well. But for those that wanna see things <now>: > sudo birdc show route primary BIRD 1.2.4 ready. 204.9.232.0/22 via 69.147.218.100 on bce1 [ASN_53480 May12] * (100) [AS4497i] 216.222.160.0/19 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS11796i] 216.226.80.0/20 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS11796i] 216.226.80.0/24 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS11796i] 64.73.101.0/24 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS23301i] 64.33.192.0/20 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS11796i] 208.157.160.0/19 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS11796i] 208.157.160.0/24 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS11796i] 208.74.240.0/21 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS40328i] 208.74.240.0/22 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS40328i] 205.149.144.0/20 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS14371i] 64.179.128.0/20 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS6304i] 64.251.160.0/19 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS6580i] 64.251.160.0/20 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS6580i] 206.176.0.0/20 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS11736i] 68.69.64.0/19 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS6580i] 208.71.216.0/21 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS20014i] 64.73.112.0/20 via 69.147.218.26 on bce1 [ASN_3599 May12] * (100) [AS3599i] 69.168.240.0/20 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS20283i] 209.94.191.0/24 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS26527i] 63.81.108.0/23 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS25967i] 204.17.145.0/24 via 69.147.218.26 on bce1 [ASN_3599 May12] * (100) [AS3599i] 198.199.195.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS10551i] 151.159.240.0/20 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS11602i] 64.179.144.0/21 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS6304i] 64.251.176.0/20 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS6580i] 69.174.224.0/20 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS30055i] 206.176.16.0/20 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14263i] 64.33.228.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.234.80.0/20 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS25967i] 64.33.229.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 64.33.230.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 64.33.231.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 67.217.4.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 64.33.224.0/19 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 64.33.224.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 91.220.15.0/24 via 69.147.218.26 on bce1 [ASN_3599 May12] * (100) [AS51818i] 64.33.225.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 67.217.2.0/23 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 64.33.226.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 64.33.227.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 64.33.236.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 64.33.238.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 64.33.239.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 151.159.192.0/20 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS11602i] 64.179.160.0/20 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS6304i] 64.33.233.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 173.240.64.0/20 via 69.147.218.26 on bce1 [ASN_3599 May12] * (100) [AS3599i] 64.33.234.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 206.176.32.0/19 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14263i] 64.33.244.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 64.33.245.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 64.33.246.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 151.159.216.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS11602i] 67.217.20.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 67.220.0.0/19 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS10242i] 64.33.240.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 69.4.96.0/19 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS11796i] 67.217.18.0/23 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 74.51.176.0/20 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS30055i] 64.33.243.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 151.159.220.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS33189i] 64.33.252.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 64.33.254.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 151.159.208.0/21 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS11602i] 67.217.28.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 204.120.16.0/20 via 69.147.218.103 on bce1 [ASN_30032 May12] * (100) [AS30032i] 64.33.249.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS18817i] 64.33.250.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576?] 205.213.166.0/23 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS22066i] 12.36.220.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS16954i] 66.115.206.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.115.207.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS18817i] 66.44.176.0/20 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS23430i] 66.115.205.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 64.17.64.0/23 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 64.33.128.0/18 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS11796i] 66.115.202.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 68.168.160.0/19 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS10242i] 66.115.203.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 64.17.66.0/23 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 24.56.190.0/23 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 66.115.201.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 67.209.64.0/19 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS11796i] 66.115.198.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.115.199.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.206.48.0/20 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS14703i] 66.115.197.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 198.233.41.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14439i] 64.17.74.0/23 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 66.115.192.0/18 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.115.192.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 206.176.64.0/18 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14263i] 66.44.162.0/24 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS23430i] 24.56.168.0/23 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 205.215.193.0/24 via 69.147.218.11 on bce1 [ASN_32621 May12] * (100) [AS32621i] 192.236.32.0/19 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS11736i] 66.115.223.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 209.240.64.0/19 via 69.147.218.3 on bce1 [ASN_7753 May12] * (100) [AS7753i] 66.44.160.0/23 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS23430i] 66.115.220.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.44.166.0/24 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS23430i] 24.54.148.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 66.44.164.0/23 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS23430i] 138.247.0.0/16 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS23122i] 24.54.152.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 66.115.214.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.115.212.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.115.213.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 198.49.94.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS14371i] 204.153.244.0/22 via 69.147.218.3 on bce1 [ASN_7753 May12] * (100) [AS7753i] 66.115.211.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.115.209.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.38.32.0/21 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS23430i] 68.65.32.0/19 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS11796i] 75.102.179.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.115.238.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 75.102.178.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 204.239.17.0/24 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS23301i] 66.44.144.0/20 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS23430i] 75.102.177.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.115.236.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.115.236.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 199.21.240.0/21 via 69.147.218.101 on bce1 [ASN_47096 May12] * (100) [AS47096i] 75.102.176.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 64.73.0.0/17 via 69.147.218.26 on bce1 [ASN_3599 May12] * (100) [AS3599i] 75.102.183.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.115.234.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 75.102.182.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.115.235.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.17.96.0/19 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS26860i] 66.17.96.0/20 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS26860i] 24.54.166.0/23 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 75.102.181.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 75.102.180.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 204.15.152.0/21 via 69.147.218.100 on bce1 [ASN_53480 May12] * (100) [AS4497i] 24.56.144.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 64.90.64.0/19 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS20283i] 75.102.187.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.115.230.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 64.246.240.0/20 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS14159i] 75.102.186.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 75.102.185.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 75.102.184.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.115.229.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 151.159.128.0/18 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS11602i] 24.56.148.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 75.102.191.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.115.226.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS18817i] 75.102.190.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 75.102.189.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 74.117.240.0/21 via 69.147.218.103 on bce1 [ASN_30032 May12] * (100) [AS30032i] 75.102.188.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.115.225.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS18817i] 75.102.163.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 207.108.15.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS10551i] 75.102.162.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 208.132.177.0/24 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS25714i] 199.36.37.0/24 via 69.147.218.26 on bce1 [ASN_3599 May12] * (100) [AS3599i] 75.102.161.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.115.252.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.44.129.0/24 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS23430i] 204.86.231.0/24 via 69.147.218.26 on bce1 [ASN_3599 May12] * (100) [AS3599i] 75.102.160.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 75.102.167.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 204.251.84.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 75.102.166.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 75.102.165.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.115.248.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 75.102.164.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 207.190.64.0/18 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS11796i] 199.36.47.0/24 via 69.147.218.26 on bce1 [ASN_3599 May12] * (100) [AS3599i] 75.102.171.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 75.102.170.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 75.102.169.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 38.126.164.0/23 via 69.147.218.9 on bce1 [ASN_46131 May12] * (100) [AS46131i] 75.102.168.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 75.102.175.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 75.102.174.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 38.126.163.0/24 via 69.147.218.100 on bce1 [ASN_53480 May12] * (100) [AS53480?] 75.102.173.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 75.102.172.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.45.236.0/24 via 69.147.218.11 on bce1 [ASN_32621 May12] * (100) [AS32621i] 216.106.240.0/21 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576?] 66.199.222.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873?] 24.236.40.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 216.250.176.0/20 via 69.147.218.3 on bce1 [ASN_7753 May12] * (100) [AS7753i] 66.199.223.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 66.199.221.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 66.199.218.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 24.236.44.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 66.187.40.0/21 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS14703i] 66.199.216.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 207.126.176.0/20 via 69.147.218.26 on bce1 [ASN_3599 May12] * (100) [AS46814i] 66.199.217.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 216.106.248.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576?] 66.199.214.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 204.252.180.0/22 via 69.147.218.100 on bce1 [ASN_53480 May12] * (100) [AS4497i] 206.107.235.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS15157i] 66.199.215.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 66.187.36.0/22 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS14703i] 66.199.212.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 206.209.0.0/20 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS11736i] 216.106.252.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576?] 192.135.80.0/24 via 69.147.218.26 on bce1 [ASN_3599 May12] * (100) [AS3599?] 66.199.211.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873?] 66.187.32.0/22 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS14703i] 66.199.208.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 66.199.209.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 216.106.224.0/20 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.106.224.0/21 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.199.206.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 64.202.248.0/24 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS10242i] 216.250.160.0/20 via 69.147.218.3 on bce1 [ASN_7753 May12] * (100) [AS7753i] 216.250.160.0/19 via 69.147.218.3 on bce1 [ASN_7753 May12] * (100) [AS7753i] 69.77.224.0/19 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS6580i] 64.202.249.0/24 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS10242i] 66.199.204.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 74.221.172.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 96.2.251.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS46432i] 66.199.205.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 66.199.202.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 24.236.60.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 216.243.128.0/18 via 69.147.218.3 on bce1 [ASN_7753 May12] * (100) [AS7753i] 66.199.200.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 74.221.168.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 66.199.201.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 216.250.167.0/24 via 69.147.218.3 on bce1 [ASN_7753 May12] * (100) [AS40851?] 216.16.0.0/17 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS6304i] 216.106.232.0/21 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 198.177.154.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS22215i] 66.199.198.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 64.202.240.0/24 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS10242i] 66.199.199.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 64.202.241.0/24 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS10242i] 66.199.196.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 64.202.242.0/24 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS10242i] 74.221.164.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 65.125.46.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS22206i] 66.199.197.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 64.202.243.0/24 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS10242i] 216.17.0.0/19 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS10242i] 68.170.112.0/20 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS20283i] 66.199.194.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 64.202.244.0/24 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS10242i] 66.199.195.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 66.199.192.0/19 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 66.199.192.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 64.202.246.0/24 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS10242i] 74.221.160.0/20 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955i] 66.199.193.0/24 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873i] 64.202.247.0/24 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS10242i] 66.35.110.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 24.49.124.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 216.106.208.0/21 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.35.111.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 209.169.212.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 209.212.32.0/20 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS20283i] 206.55.176.0/20 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS10242i] 96.2.203.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS46890?] 66.35.109.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 24.49.120.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 209.169.208.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 199.3.109.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS15157i] 96.2.207.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS40568i] 199.3.108.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS15157i] 66.35.102.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 24.49.116.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 216.106.216.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 68.235.64.0/18 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS14371i] 68.235.64.0/19 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS14371i] 205.185.128.0/19 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS40328i] 205.185.128.0/20 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS40328i] 198.180.188.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS7773i] 96.47.112.0/20 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS11796i] 24.49.112.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 216.106.220.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.189.128.0/20 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS32609i] 68.234.64.0/20 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS11796i] 66.35.96.0/19 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955i] 66.35.96.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 66.35.96.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 98.159.176.0/20 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576?] 209.169.218.0/23 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 216.106.192.0/18 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.106.192.0/21 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 69.77.192.0/18 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS6580i] 69.77.192.0/19 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS6580i] 50.93.244.0/22 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS10242i] 209.169.198.0/23 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 209.169.192.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 65.240.52.0/22 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS25714i] 66.35.120.0/21 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 66.35.118.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 216.106.200.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 63.171.43.0/24 via 69.147.218.103 on bce1 [ASN_30032 May12] * (100) [AS30032i] 208.254.144.0/23 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS25967i] 66.35.116.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 66.35.117.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 67.107.84.0/22 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS25714i] 216.17.32.0/19 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS10242i] 66.35.114.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 216.106.204.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 209.169.200.0/23 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 66.35.112.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 50.93.248.0/21 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS10242i] 98.143.224.0/20 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS11796i] 66.35.113.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 208.53.196.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 208.72.48.0/22 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21873?] 66.231.30.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.254.224.0/20 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS6304i] 209.62.232.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS32719i] 65.165.20.0/23 via 69.147.218.103 on bce1 [ASN_30032 May12] * (100) [AS30032i] 66.231.31.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 206.51.193.0/24 via 69.147.218.101 on bce1 [ASN_47096 May12] * (100) [AS47096i] 209.62.234.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS32719i] 66.231.29.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 24.52.12.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 208.53.192.0/18 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 208.53.192.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.231.26.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.249.248.0/21 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576?] 208.53.193.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 208.53.194.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.231.24.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 209.62.238.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS32719i] 208.53.204.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 209.62.225.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS32719i] 66.231.22.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.249.244.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576?] 216.70.9.0/24 via 69.147.218.101 on bce1 [ASN_47096 May12] * (100) [AS47096i] 69.147.192.0/20 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS11796i] 205.173.176.0/21 via 69.147.218.26 on bce1 [ASN_3599 May12] * (100) [AS3599i] 208.53.206.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 164.154.0.0/16 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS7773i] 205.173.181.0/24 via 69.147.218.26 on bce1 [ASN_3599 May12] * (100) [AS3599i] 216.249.240.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 208.53.201.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS18817i] 209.62.228.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS32719i] 216.70.13.0/24 via 69.147.218.101 on bce1 [ASN_47096 May12] * (100) [AS47096i] 205.173.180.0/24 via 69.147.218.26 on bce1 [ASN_3599 May12] * (100) [AS3599i] 66.173.59.0/24 via 69.147.218.9 on bce1 [ASN_46131 May12] * (100) [AS46131i] 66.231.19.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 208.53.202.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.231.16.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.249.242.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 208.53.203.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.231.17.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 24.52.24.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 64.72.176.0/20 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS6304i] 216.249.236.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.254.240.0/20 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS6304i] 209.62.248.0/21 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS32719i] 216.70.17.0/24 via 69.147.218.101 on bce1 [ASN_47096 May12] * (100) [AS47096i] 69.147.216.0/23 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS26527i] 66.231.15.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS18817i] 66.231.12.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 69.147.218.0/24 via 69.147.218.103 on bce1 [ASN_30032 May12] * (100) [AS30032?] 66.231.13.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 24.52.28.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 208.53.208.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.249.232.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 208.53.209.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.231.11.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.70.22.0/24 via 69.147.218.101 on bce1 [ASN_47096 May12] * (100) [AS47096i] 198.204.32.0/20 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS16714i] 66.231.8.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 208.53.211.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.231.9.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 24.52.16.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 208.53.220.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS36013i] 216.235.172.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS32719i] 216.249.228.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 208.53.221.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 69.147.208.0/21 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS11796i] 208.53.222.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 209.62.243.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS32719i] 216.70.26.0/24 via 69.147.218.101 on bce1 [ASN_47096 May12] * (100) [AS47096i] 216.70.27.0/24 via 69.147.218.101 on bce1 [ASN_47096 May12] * (100) [AS47096i] 216.17.64.0/19 via 69.147.218.19 on bce1 [ASN_10242 May12] * (100) [AS10242i] 208.53.216.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 209.62.245.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS32719i] 216.70.28.0/24 via 69.147.218.101 on bce1 [ASN_47096 May12] * (100) [AS47096i] 66.231.2.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.249.224.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 209.62.244.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS32719i] 216.70.29.0/24 via 69.147.218.101 on bce1 [ASN_47096 May12] * (100) [AS47096i] 216.249.225.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.231.0.0/19 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.249.226.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.249.227.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 204.52.252.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14263i] 24.52.40.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 208.53.228.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576?] 64.68.176.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 66.128.162.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.173.22.0/24 via 69.147.218.9 on bce1 [ASN_46131 May12] * (100) [AS46131i] 216.249.220.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 64.68.177.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 216.249.221.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS46623i] 208.53.230.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576?] 66.128.160.0/19 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.249.222.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.128.161.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576?] 208.53.224.0/20 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 208.53.224.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576?] 64.68.180.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 64.73.128.0/18 via 69.147.218.26 on bce1 [ASN_3599 May12] * (100) [AS3599i] 66.128.166.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.249.216.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.249.217.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS40568i] 208.53.226.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576?] 66.128.164.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.249.218.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 64.68.184.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955i] 66.128.170.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 137.216.0.0/16 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS11607i] 208.53.238.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576?] 64.68.186.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955i] 216.249.214.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 199.115.224.0/22 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS14159i] 151.159.0.0/17 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS11602i] 24.52.36.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 208.53.232.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576?] 64.68.188.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 66.128.174.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.249.208.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.128.175.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 209.191.192.0/19 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS14371i] 216.249.209.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 208.53.234.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576?] 64.68.190.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 216.249.210.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576?] 64.68.191.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 66.128.173.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.249.211.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 24.52.56.0/21 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 208.53.244.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 64.68.160.0/19 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955i] 208.53.246.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 206.71.32.0/20 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14263i] 66.128.176.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 12.155.146.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS16954i] 198.180.229.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS22851i] 208.53.240.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.128.182.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.249.200.0/21 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 65.61.64.0/19 via 69.147.218.50 on bce1 [ASN_32609 May12] * (100) [AS21730i] 64.68.166.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955i] 66.128.180.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 208.53.252.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 192.55.228.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS11736i] 64.68.168.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 216.249.196.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 208.53.253.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.128.187.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 173.245.128.0/20 via 69.147.218.10 on bce1 [ASN_11796 May12] * (100) [AS11796i] 208.53.254.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 64.68.170.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 66.128.184.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.249.198.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 64.68.171.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 24.52.52.0/22 via 69.147.218.42 on bce1 [ASN_11055 May12] * (100) [AS11055i] 208.53.248.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS25732i] 66.128.190.0/23 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS18817i] 216.249.192.0/18 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 216.249.192.0/22 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 208.53.249.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 64.68.173.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 208.53.250.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 66.128.188.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 208.53.251.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS13576i] 64.68.175.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS14955?] 66.128.189.0/24 via 69.147.218.49 on bce1 [ASN_13576 01:14] * (100) [AS18817i] And the very large IPv6 table... > sudo birdc6 show route primary BIRD 1.2.4 ready. 2001:4980::/32 via 2607:fe10:ffff::3 on bce1 [ASN_7753 May12] * (100) [AS7753i] 2605:8400::/32 via 2607:fe10:ffff::19 on bce1 [ASN_10242 May12] * (100) [AS10242i] 2607:fba0::/32 via 2607:fe10:ffff::50 on bce1 [ASN_32609 May12] * (100) [AS30055i] 2607:fcb0::/32 via 2607:fe10:ffff::50 on bce1 [ASN_32609 May12] * (100) [AS14371i] :) This only shows the multilateral peering that is set up - bilateral stuff will not be seen via this interface...ever. ie: HE is bilateral only, TDS is bilateral only. (7753 is ipHouse, 10242 is USI, 32609 is CNS with 2 /32s - I now feel inadequate) -- Mike Horwath ipHouse - Welcome home! drechsau(a)iphouse.net The universe is an island, surrounded by whatever it is that surrounds universes. - Berkeley Fortune ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 13, 2011

Re: Looking Glass / Route Server for MICE

by James Montz

If you look at the command output by the DE-ICX... It looks like the Cisco show ip gbp summary command, that is not the BIRD command. So it looks like their looking glass is pulling route data froma Cisco L3 device. It IS possible to pull the data from the BIRD command, however, this involves allowing PHP execute() on the web server, requiring some "hackery" --------------------------------------------------- *James C. Montz* Senior Consultant *Mankato Networks LLC* <http://www.mankatonetworks.net/>320 East Liberty Street <http://maps.google.com/maps?q=320+East+Liberty+Street%2CMankato%2CMN+56001&…>Mankato, MN 56001 *Phone:* *(320)-496-6689* *Email: jamesmontz(a)mankatonetworks.net* *Web: http://www.mankatonetworks.net Skype: james.montz* * http://www.linkedin.com/in/jmontz* On Fri, May 13, 2011 at 2:01 PM, Jay Hanke <jayhanke(a)mankatonetworks.net>wrote: > > We have 12K routes? :) > > > > Oh right, HE.... (just kidding, I am poking fun) > > The switch role is L2 in our current config. So we're really going to > use about 50 entries in the mac-address-table and enough routes to > manage the box. > > > Code? > > James, didn't we talk to someone from DE-CIX back in the formative > stages? They might be able to help us out. > > Jay > > ######################################################################## > > 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

May 13, 2011

Re: Looking Glass / Route Server for MICE

by Jay Hanke

> We have 12K routes? :) > > Oh right, HE.... (just kidding, I am poking fun) The switch role is L2 in our current config. So we're really going to use about 50 entries in the mac-address-table and enough routes to manage the box. > Code? James, didn't we talk to someone from DE-CIX back in the formative stages? They might be able to help us out. Jay ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 13, 2011

Re: Looking Glass / Route Server for MICE

by Mike Horwath

On 5/13/11 12:25 PM, "Jay Hanke" <jayhanke(a)MANKATONETWORKS.NET> wrote: >On Fri, May 13, 2011 at 11:53 AM, Owen DeLong <owend(a)he.net> wrote: >> If the Juniper systems are stackable EX series switches, then, they will >> not take a full BGP table. > >Very True. The FIB limit on the ex4200 is about 12k and there isn't a >huge amount of memory for a RIB. We have 12K routes? :) Oh right, HE.... (just kidding, I am poking fun) >It looks like DE-CIX might have already rolled a solution for bird. > >http://lg.de-cix.net/ Code? -- Mike Horwath ipHouse - Welcome home! drechsau(a)iphouse.net The universe is an island, surrounded by whatever it is that surrounds universes. - Berkeley Fortune ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 13, 2011

Re: Looking Glass / Route Server for MICE

by Jay Hanke

On Fri, May 13, 2011 at 11:53 AM, Owen DeLong <owend(a)he.net> wrote: > If the Juniper systems are stackable EX series switches, then, they will > not take a full BGP table. Very True. The FIB limit on the ex4200 is about 12k and there isn't a huge amount of memory for a RIB. It looks like DE-CIX might have already rolled a solution for bird. http://lg.de-cix.net/ jay ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 13, 2011

Re: Looking Glass / Route Server for MICE

by Owen DeLong

If the Juniper systems are stackable EX series switches, then, they will not take a full BGP table. Owen On May 13, 2011, at 9:12 AM, Mike Horwath wrote: > On 5/13/11 11:09 AM, "Justin Krejci" <jkrejci(a)USINTERNET.COM> wrote: > >> On Fri, 2011-05-13 at 15:46 +0000, Mike Horwath wrote: >>> On 5/13/11 10:43 AM, "Justin Krejci" <jkrejci(a)USINTERNET.COM> wrote: >>> >>>> On Fri, 2011-05-13 at 15:11 +0000, Mike Horwath wrote: >>>>> On 5/12/11 6:57 PM, "Justin Krejci" <jkrejci(a)USINTERNET.COM> wrote: >>>>> >>>>>> As I understand it there is currently no public looking glass or >>> route >>>>>> server for MICE users or the public in general. Any interest in >>> setting >>>>>> something up? I could donate a server or some time to the cause. >>> They >>>>> are >>>>>> quite useful in troubleshooting routing issues or network changes. >>>>> >>>>> You are correct, there isn't. >>>>> >>>>> This could easily run on the system that handles the statistics >>> easily >>>>> enough, just I have no idea how I would tie bird into a LG setup. >>>>> >>>> >>>> Looks like using its CLI will not be immediately compatible with most >>>> (all?) LG tools out there which are seemingly mostly geared around >>>> Cisco, Juniper, and Zebra/Quagga systems it seems. Unless someone knows >>>> of a really great and flexible LG app. >>> >>> Yah, that was my finding as well. >>> >>>> Perhaps a small C/J router could peer up with the two servers to suck >>> in >>>> the routes and be used as the LG source and as a publicly telnet >>>> accessible route server as well. >>> >>> There will be a Juniper in place soon - once that is done, we can look >>> at >>> putting it into the 'route' subsystem (this is *not* a requirement for >>> operation of the peering point, in fact, it could create other issues if >>> something breaks) but we could then query that for data. >> >> If there will be a Juniper router already going into the network anyways >> that would certainly work I should think. Then it can be polled by the >> existing stats server you mentioned. > > ...for a looking glass system. > > (finishing your sentence :) > >>>> >>>> ALso OpenBSD has a good bgp daemon with their own bgplg toools (web and >>>> cli) included. >>> >>>> http://www.openbsd.org/cgi-bin/man.cgi?query=bgp&sektion=0&manpath=OpenB >>>> SD >>>> +Current&arch=amd64&apropos=1&format=html >>> >>> We aren't using OpenBSD anywhere though...we are using BIRD. >> >> A small OpenBSD server, even a small Soekris style box, can still suck >> up a read-only copy of the routes from the route servers via BGP. No >> real maintenance or overhead once its up and running. The only real >> difference between something like this and using a C/J would be that >> OBSD has all of the tools built in already, so it's a matter of >> convenience and the general dependable security of an OBSD system. I >> have a such Soekris box with a flash drive I could donate to the cause >> as I've been looking for something to do with it besides accessorize my >> desk. I only mention this as an option as I have used OBSD for a long >> time and am familiar with it and it would meet the needs from what I can >> see. > > Sorry, I was being flippant with my comment. > > I'll be direct: no hackery > > When the new Juniper systems are in place, hopefully they are licensed for > BGP, and if that is the case, we can query that with a looking glass > system and use the current stats server to handle this. > > If this does *not* happen then we need to research another solution. > Additional hardware should *not* be needed at all. > > -- > Mike Horwath ipHouse - Welcome home! drechsau(a)iphouse.net > The universe is an island, surrounded by whatever it is > that surrounds universes. - Berkeley Fortune > > ######################################################################## > > 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

May 13, 2011

Re: Looking Glass / Route Server for MICE

by Owen DeLong

Another option would be to run an instance of quagga on the BIRD box and peer it with the BIRD instance in receive-only mode. Then you could do the LG stuff against that. Owen On May 13, 2011, at 9:09 AM, Justin Krejci wrote: > On Fri, 2011-05-13 at 15:46 +0000, Mike Horwath wrote: >> On 5/13/11 10:43 AM, "Justin Krejci" <jkrejci(a)USINTERNET.COM> wrote: >> >>> On Fri, 2011-05-13 at 15:11 +0000, Mike Horwath wrote: >>>> On 5/12/11 6:57 PM, "Justin Krejci" <jkrejci(a)USINTERNET.COM> wrote: >>>> >>>>> As I understand it there is currently no public looking glass or route >>>>> server for MICE users or the public in general. Any interest in setting >>>>> something up? I could donate a server or some time to the cause. They >>>> are >>>>> quite useful in troubleshooting routing issues or network changes. >>>> >>>> You are correct, there isn't. >>>> >>>> This could easily run on the system that handles the statistics easily >>>> enough, just I have no idea how I would tie bird into a LG setup. >>>> >>> >>> Looks like using its CLI will not be immediately compatible with most >>> (all?) LG tools out there which are seemingly mostly geared around >>> Cisco, Juniper, and Zebra/Quagga systems it seems. Unless someone knows >>> of a really great and flexible LG app. >> >> Yah, that was my finding as well. >> >>> Perhaps a small C/J router could peer up with the two servers to suck in >>> the routes and be used as the LG source and as a publicly telnet >>> accessible route server as well. >> >> There will be a Juniper in place soon - once that is done, we can look at >> putting it into the 'route' subsystem (this is *not* a requirement for >> operation of the peering point, in fact, it could create other issues if >> something breaks) but we could then query that for data. > > If there will be a Juniper router already going into the network anyways > that would certainly work I should think. Then it can be polled by the > existing stats server you mentioned. > >>> >>> ALso OpenBSD has a good bgp daemon with their own bgplg toools (web and >>> cli) included. >>> http://www.openbsd.org/cgi-bin/man.cgi?query=bgp&sektion=0&manpath=OpenBSD >>> +Current&arch=amd64&apropos=1&format=html >> >> We aren't using OpenBSD anywhere though...we are using BIRD. > > A small OpenBSD server, even a small Soekris style box, can still suck > up a read-only copy of the routes from the route servers via BGP. No > real maintenance or overhead once its up and running. The only real > difference between something like this and using a C/J would be that > OBSD has all of the tools built in already, so it's a matter of > convenience and the general dependable security of an OBSD system. I > have a such Soekris box with a flash drive I could donate to the cause > as I've been looking for something to do with it besides accessorize my > desk. I only mention this as an option as I have used OBSD for a long > time and am familiar with it and it would meet the needs from what I can > see. > > ######################################################################## > > 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

May 13, 2011

Re: Looking Glass / Route Server for MICE

by Mike Horwath

On 5/13/11 11:09 AM, "Justin Krejci" <jkrejci(a)USINTERNET.COM> wrote: >On Fri, 2011-05-13 at 15:46 +0000, Mike Horwath wrote: >> On 5/13/11 10:43 AM, "Justin Krejci" <jkrejci(a)USINTERNET.COM> wrote: >> >> >On Fri, 2011-05-13 at 15:11 +0000, Mike Horwath wrote: >> >> On 5/12/11 6:57 PM, "Justin Krejci" <jkrejci(a)USINTERNET.COM> wrote: >> >> >> >> >As I understand it there is currently no public looking glass or >>route >> >> >server for MICE users or the public in general. Any interest in >>setting >> >> >something up? I could donate a server or some time to the cause. >>They >> >>are >> >> >quite useful in troubleshooting routing issues or network changes. >> >> >> >> You are correct, there isn't. >> >> >> >> This could easily run on the system that handles the statistics >>easily >> >> enough, just I have no idea how I would tie bird into a LG setup. >> >> >> > >> >Looks like using its CLI will not be immediately compatible with most >> >(all?) LG tools out there which are seemingly mostly geared around >> >Cisco, Juniper, and Zebra/Quagga systems it seems. Unless someone knows >> >of a really great and flexible LG app. >> >> Yah, that was my finding as well. >> >> >Perhaps a small C/J router could peer up with the two servers to suck >>in >> >the routes and be used as the LG source and as a publicly telnet >> >accessible route server as well. >> >> There will be a Juniper in place soon - once that is done, we can look >>at >> putting it into the 'route' subsystem (this is *not* a requirement for >> operation of the peering point, in fact, it could create other issues if >> something breaks) but we could then query that for data. > >If there will be a Juniper router already going into the network anyways >that would certainly work I should think. Then it can be polled by the >existing stats server you mentioned. ...for a looking glass system. (finishing your sentence :) >> > >> >ALso OpenBSD has a good bgp daemon with their own bgplg toools (web and >> >cli) included. >> >>>http://www.openbsd.org/cgi-bin/man.cgi?query=bgp&sektion=0&manpath=OpenB >>>SD >> >+Current&arch=amd64&apropos=1&format=html >> >> We aren't using OpenBSD anywhere though...we are using BIRD. > >A small OpenBSD server, even a small Soekris style box, can still suck >up a read-only copy of the routes from the route servers via BGP. No >real maintenance or overhead once its up and running. The only real >difference between something like this and using a C/J would be that >OBSD has all of the tools built in already, so it's a matter of >convenience and the general dependable security of an OBSD system. I >have a such Soekris box with a flash drive I could donate to the cause >as I've been looking for something to do with it besides accessorize my >desk. I only mention this as an option as I have used OBSD for a long >time and am familiar with it and it would meet the needs from what I can >see. Sorry, I was being flippant with my comment. I'll be direct: no hackery When the new Juniper systems are in place, hopefully they are licensed for BGP, and if that is the case, we can query that with a looking glass system and use the current stats server to handle this. If this does *not* happen then we need to research another solution. Additional hardware should *not* be needed at all. -- Mike Horwath ipHouse - Welcome home! drechsau(a)iphouse.net The universe is an island, surrounded by whatever it is that surrounds universes. - Berkeley Fortune ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 13, 2011

Re: Looking Glass / Route Server for MICE

by Justin Krejci

On Fri, 2011-05-13 at 15:46 +0000, Mike Horwath wrote: > On 5/13/11 10:43 AM, "Justin Krejci" <jkrejci(a)USINTERNET.COM> wrote: > > >On Fri, 2011-05-13 at 15:11 +0000, Mike Horwath wrote: > >> On 5/12/11 6:57 PM, "Justin Krejci" <jkrejci(a)USINTERNET.COM> wrote: > >> > >> >As I understand it there is currently no public looking glass or route > >> >server for MICE users or the public in general. Any interest in setting > >> >something up? I could donate a server or some time to the cause. They > >>are > >> >quite useful in troubleshooting routing issues or network changes. > >> > >> You are correct, there isn't. > >> > >> This could easily run on the system that handles the statistics easily > >> enough, just I have no idea how I would tie bird into a LG setup. > >> > > > >Looks like using its CLI will not be immediately compatible with most > >(all?) LG tools out there which are seemingly mostly geared around > >Cisco, Juniper, and Zebra/Quagga systems it seems. Unless someone knows > >of a really great and flexible LG app. > > Yah, that was my finding as well. > > >Perhaps a small C/J router could peer up with the two servers to suck in > >the routes and be used as the LG source and as a publicly telnet > >accessible route server as well. > > There will be a Juniper in place soon - once that is done, we can look at > putting it into the 'route' subsystem (this is *not* a requirement for > operation of the peering point, in fact, it could create other issues if > something breaks) but we could then query that for data. If there will be a Juniper router already going into the network anyways that would certainly work I should think. Then it can be polled by the existing stats server you mentioned. > > > >ALso OpenBSD has a good bgp daemon with their own bgplg toools (web and > >cli) included. > >http://www.openbsd.org/cgi-bin/man.cgi?query=bgp&sektion=0&manpath=OpenBSD > >+Current&arch=amd64&apropos=1&format=html > > We aren't using OpenBSD anywhere though...we are using BIRD. A small OpenBSD server, even a small Soekris style box, can still suck up a read-only copy of the routes from the route servers via BGP. No real maintenance or overhead once its up and running. The only real difference between something like this and using a C/J would be that OBSD has all of the tools built in already, so it's a matter of convenience and the general dependable security of an OBSD system. I have a such Soekris box with a flash drive I could donate to the cause as I've been looking for something to do with it besides accessorize my desk. I only mention this as an option as I have used OBSD for a long time and am familiar with it and it would meet the needs from what I can see. ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 13, 2011

Re: Looking Glass / Route Server for MICE

by Mike Horwath

On 5/13/11 10:43 AM, "Justin Krejci" <jkrejci(a)USINTERNET.COM> wrote: >On Fri, 2011-05-13 at 15:11 +0000, Mike Horwath wrote: >> On 5/12/11 6:57 PM, "Justin Krejci" <jkrejci(a)USINTERNET.COM> wrote: >> >> >As I understand it there is currently no public looking glass or route >> >server for MICE users or the public in general. Any interest in setting >> >something up? I could donate a server or some time to the cause. They >>are >> >quite useful in troubleshooting routing issues or network changes. >> >> You are correct, there isn't. >> >> This could easily run on the system that handles the statistics easily >> enough, just I have no idea how I would tie bird into a LG setup. >> > >Looks like using its CLI will not be immediately compatible with most >(all?) LG tools out there which are seemingly mostly geared around >Cisco, Juniper, and Zebra/Quagga systems it seems. Unless someone knows >of a really great and flexible LG app. Yah, that was my finding as well. >Perhaps a small C/J router could peer up with the two servers to suck in >the routes and be used as the LG source and as a publicly telnet >accessible route server as well. There will be a Juniper in place soon - once that is done, we can look at putting it into the 'route' subsystem (this is *not* a requirement for operation of the peering point, in fact, it could create other issues if something breaks) but we could then query that for data. > >ALso OpenBSD has a good bgp daemon with their own bgplg toools (web and >cli) included. >http://www.openbsd.org/cgi-bin/man.cgi?query=bgp&sektion=0&manpath=OpenBSD >+Current&arch=amd64&apropos=1&format=html We aren't using OpenBSD anywhere though...we are using BIRD. -- Mike Horwath ipHouse - Welcome home! drechsau(a)iphouse.net The universe is an island, surrounded by whatever it is that surrounds universes. - Berkeley Fortune ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 13, 2011

Re: Looking Glass / Route Server for MICE

by Justin Krejci

On Fri, 2011-05-13 at 15:11 +0000, Mike Horwath wrote: > On 5/12/11 6:57 PM, "Justin Krejci" <jkrejci(a)USINTERNET.COM> wrote: > > >As I understand it there is currently no public looking glass or route > >server for MICE users or the public in general. Any interest in setting > >something up? I could donate a server or some time to the cause. They are > >quite useful in troubleshooting routing issues or network changes. > > You are correct, there isn't. > > This could easily run on the system that handles the statistics easily > enough, just I have no idea how I would tie bird into a LG setup. > Looks like using its CLI will not be immediately compatible with most (all?) LG tools out there which are seemingly mostly geared around Cisco, Juniper, and Zebra/Quagga systems it seems. Unless someone knows of a really great and flexible LG app. Perhaps a small C/J router could peer up with the two servers to suck in the routes and be used as the LG source and as a publicly telnet accessible route server as well. ALso OpenBSD has a good bgp daemon with their own bgplg toools (web and cli) included. http://www.openbsd.org/cgi-bin/man.cgi?query=bgp&sektion=0&manpath=OpenBSD+… ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 13, 2011

Re: Looking Glass / Route Server for MICE

by Mike Horwath

On 5/12/11 6:57 PM, "Justin Krejci" <jkrejci(a)USINTERNET.COM> wrote: >As I understand it there is currently no public looking glass or route >server for MICE users or the public in general. Any interest in setting >something up? I could donate a server or some time to the cause. They are >quite useful in troubleshooting routing issues or network changes. You are correct, there isn't. This could easily run on the system that handles the statistics easily enough, just I have no idea how I would tie bird into a LG setup. -- Mike Horwath ipHouse - Welcome home! drechsau(a)iphouse.net The universe is an island, surrounded by whatever it is that surrounds universes. - Berkeley Fortune ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 13, 2011