While we're on the subject of peering, perhaps one of the admins can take a
stab at this one. I'm normally on a GCI connection which peers with
University of Alaska's network. Right now though I'm on a MTA line while
traveling, and I've noticed some strange routing: some traceroutes from MTA
to UA IP space stay all in Alaska and go through the MTA-GCI peering
circuits, while other traceroutes go down to Seattle and back up to Alaska.
It's almost as if not all of the UA BGP info is propagating......?
Examples:
to www.uaa.alaska.edu
http://www.pastey.net/137585
to www.uaf.edu
http://www.pastey.net/137586
to www.uas.alaska.edu
http://www.pastey.net/137587
to classes.uaf.edu
http://www.pastey.net/137588
to www.alaska.edu
http://www.pastey.net/137589
to uascentral.alaska.edu
http://www.pastey.net/137590
to uaonline.alaska.edu
http://www.pastey.net/137591
to www.pwscc.edu
http://www.pastey.net/137592
Ideas?
Scott
-- Scott A. Johnson scott.a.johnson@gmail.com http://scojo.us mobile: +1.907.240.2483 --------- To unsubscribe, send email to <aklug-request@aklug.org> with 'unsubscribe' in the message body.Received on Fri Jun 11 07:43:24 2010
This archive was generated by hypermail 2.1.8 : Fri Jun 11 2010 - 07:43:25 AKDT