Re: Data Center Installations

[Joe Greco]

> Wish there was Frys in the east=20

Micro Center is kind of like a less-insane Frys.

Always seem to be somewhat inconveniently located though.

... JG
-- 
Joe Greco - sol.net Network Services - Milwaukee, WI - http://www.sol.net
"We call it the 'one bite at the apple' rule. Give me one chance [and] then I
won't contact you again." - Direct Marketing Ass'n position on e-mail spam(CNN)
With 24 million small businesses in the US alone, that's way too many apples.

Re: Data Center Installations

[Joe Greco]

> I thought maybe there was a secret place to get cool data center layer 1 st=
> uff..

Yeah, it's called "inventory" ...  ;-)  Seriously, there's a reason why
it is common to maintain shelving in the data center, and/or storage 
lockers nearby.  The stuff you use and find usable isn't the same stuff 
that I use and find usable, and while I don't know about you, I'm too
cheap to pay top dollar for JIT style acquisition of the stuff I need,
even assuming that there was someplace local that sold it.  Easier to 
have it on-site.

As for acquiring the stuff in the first place?  Yeah, no good single
source.  We have a drawerful of current catalogs for various vendors,
such as:

ADI - low voltage distributors, often good pricing on bulk cable and 
UPS batteries

C&H Distributors- General industrial equipment, workbenches,
shelving, storage bins, etc.

CablesToGo  - KVM cables, PC and network cabling, power cords, etc

DigiKey - Mostly electronics parts and connectors

PI Manufacturing- All sorts of various inexpensive bits and pieces
for networks and PC's, cables, adapters, etc.

StayOnline  - More obscure stuff for the data center, such as C13-to-C14
power Y's

to mention some of the less-obvious ones, But these days there's a huge 
amount of purchasing that goes on entirely through online catalogs etc.

... JG
-- 
Joe Greco - sol.net Network Services - Milwaukee, WI - http://www.sol.net
"We call it the 'one bite at the apple' rule. Give me one chance [and] then I
won't contact you again." - Direct Marketing Ass'n position on e-mail spam(CNN)
With 24 million small businesses in the US alone, that's way too many apples.

Re: Could not send email to office 365

[Joe Abley]

On 2013-05-02, at 02:42, Cathy Almond  wrote:

> This may be a red herring, but I've heard of some dropping of DNS
> queries for the names within outlook.com domains where the queries are
> all coming from source port 53 (i.e. your recursive server doesn't use
> query source port randomization

... or there's a NAT or some other box in front of the recursive server which 
re-writes the source port...

> ).  Might be worth checking what the
> recursive server you're using is doing?
> 
> See https://www.dns-oarc.net/oarc/services/porttest


Joe

RE: Data Center Installations

[Jamie Bowden]

> From: Warren Bailey [mailto:wbai...@satelliteintelligencegroup.com]
> 
> Do any of you have a "go to" resource for materials used in installations? Tie
> wraps, cable management, blahblahblah?
> 
> I have found several places, but I'm curious to know what the nanog ninja's
> have to say.

I use Graybar for the most part.  If it's something small or easy, MicroCenter 
probably has it, but when I need a couple thousand feet of 
cat[5|5e|6|whatever], a bag of 500 cable ties, a box RJ-48s, etc., it's 
straight to Graybar.  If it's not already on the shelf they can get it quick 
and their pricing is pretty good.

-- 
Jamie Bowden(ja...@photon.com)
Sr. Sys. Admin. (703) 243-6613 x3848
Photon Research Associates
1616 Fort Myer Drive, Suite 1000
Arlington, VA 22209

Re: Google Public DNS Problems?

[Perry Lorier]

On 5/1/13 12:38 PM, Blair Trosper wrote:

> That's all well and good, but I certainly wouldn't expect "nslookup
> gmail.com " or for "nslookup google.com" to return
> SERVFAIL
>
>
Do you have traceroutes to 8.8.8.8 and 8.8.4.4?

Breakpoint 2013 Call For Papers

[cfp]

Breakpoint 2013 Call For Papers
Melbourne, Australia, October 24th-25th
Intercontinental Rialto
http://www.ruxconbreakpoint.com


.[x]. Introduction .[x].

 The Ruxcon team is pleased to announce Call For Papers for Breakpoint 2013.

 Breakpoint showcases the work of expert security researchers from around the
 world on a wide range of topics. This conference is organised by the Ruxcon 
 team and offers a specialised security conference to complement and lead into 
 the larger and more casual Ruxcon weekend conference. Breakpoint caters 
 towards security researchers and industry professionals alike, with a focus on 
 cutting edge security research.

 Breakpoint presents a great opportunity for our selected speakers to receive a
 complimentary trip to Australia and experience both the Breakpoint and Ruxcon 
 conferences, not to mention the great weather, awesome parties, and friendly 
 people. Melbourne is a city of many subcultures, personalities and styles. 
 Melbourne has a vibrant arts and music scene, eccentric cafes, intimate bars 
 and restaurants, and is known as Australia's cultural capital.


.[x]. Important Dates .[x].

 May 1  - Call For Presentations Open
 August 23  - Call For Presentations Close
 October 22-23  - Breakpoint Training
 October 24-25  - Breakpoint Conference
 October 26-27  - Ruxcon Conference


.[x]. Topic Scope .[x].

Topics of interest include, but are not limited to:

 o Mobile Device Security
 o Exploitation Techniques
 o Reverse Engineering
 o Vulnerability Discovery
 o Rootkit Development
 o Malware Analysis
 o Code Analysis
 o Virtualisation, Hypervisor Security
 o Cloud Security
 o Embedded Device Security
 o Hardware Security
 o Telecommunications Security
 o Wireless Network Security
 o Web Application Security
 o Law Enforcement Activities
 o Forensics
 o Threat Intelligence
 o You get the idea


.[x]. Submission Guidelines .[x].

 In order for us to process your submission we will require the following 
 information:

 1. Presentation title
 2. Detailed summary of your presentation material
 3. Name/Nickname
 4. Mobile phone number
 5. Brief personal biography
 6. Description of any demonstrations involved in presentation
 7. Information on where the presentation material has or will be presented 
before Breakpoint

 * Preference will be given to presentations that contain original research 
   that will be first presented at Breakpoint. 
 * As a general guideline, Breakpoint presentations are between 
   45 and 60 minutes, including question time. 

 If you have any questions about submissions, or would like to make a 
 submission, please send an email to b...@ruxconbreakpoint.com


.[x]. Speaker Benefits .[x].

 Speakers at Breakpoint will be entitled to the following benefits: 
   

 - A return economy airfare to Melbourne (total cost limit applies)
 - Three nights accommodation at the Intercontinental Rialto
 - Complimentary registration for Breakpoint and Ruxcon conferences
 - Invitation to all Breakpoint and Ruxcon parties
 - Unlock 'Presented on world's smallest continent' achievement

 * All speaker benefits apply to a single speaker per submission. 


.[x]. Contact .[x]. 

 If you have any questions or inqueries, contact us at:

 * Email:   b...@ruxconbreakpoint.com
 * Twitter: @ruxconbpx

RE: Data Center Installations

[Blake Pfankuch - Mailing List]

Along this same line of questioning... favorite Velcro?  I used to get spools 
of about 500 8 inch strips for a reasonable amount however the vendor went out 
of business.  The cloth tabs are nice, but then end up getting in the way...

Thanks,
Blake

-Original Message-
From: Otis L. Surratt, Jr. [mailto:o...@ocosa.com] 
Sent: Wednesday, May 1, 2013 1:40 PM
To: Warren Bailey; nanog@nanog.org
Subject: RE: Data Center Installations

-Original Message-
From: Warren Bailey [mailto:wbai...@satelliteintelligencegroup.com]
Sent: Wednesday, May 01, 2013 2:24 PM
To: nanog@nanog.org
Subject: Data Center Installations

>Do any of you have a "go to" resource for materials used in
installations? Tie wraps, cable management, blahblahblah?
>
>I have found several places, but I'm curious to know what the nanog
ninja's have to say.
>
>//warren

We've used both CSC and Graybar, more frequently CSC better deals in our case.
For very nice affordable Cat 5e/6A patch cords iofast.com we've never purchased 
a patch from anywhere else since we found them.

RE: Data Center Installations

[Blake Pfankuch - Mailing List]

We have been going with rolls and cut to fit, however looking for something 
precut that way we don't end up with a NOC monkey putting a 18 inch piece of 
Velcro on 4 cat5 cables...  I do have pictures... If they only get 8 inch 
strips, it helps keep things cleaner, and then leave the cut to fit to the 
people who have "engineer" in their title.

Mike, I was looking at them as well and will add them to the list to pay 
attention to.  Thanks, for the suggestion, I will order a roll and have a look.

Thanks,
Blake

From: Mike Lyon [mailto:mike.l...@gmail.com]
Sent: Wednesday, May 1, 2013 5:33 PM
To: Otis L. Surratt, Jr.
Cc: Blake Pfankuch - Mailing List; Warren Bailey; NANOG
Subject: Re: Data Center Installations

For bulk velcro, I found Uline to be fairly cheap.

On Wed, May 1, 2013 at 4:30 PM, Otis L. Surratt, Jr. 
mailto:o...@ocosa.com>> wrote:
-Original Message-
From: Blake Pfankuch - Mailing List
[mailto:blake.mailingl...@pfankuch.me]
Sent: Wednesday, May 01, 2013 6:18 PM
To: Otis L. Surratt, Jr.; Warren Bailey; nanog@nanog.org
Subject: RE: Data Center Installations

>Along this same line of questioning... favorite Velcro?  I used to get
spools of about 500 8 inch strips for a reasonable amount however the
vendor went out of business.  The cloth tabs are nice, but then end >up
getting in the way...
>
>Thanks,
>Blake

You should be able to get a roll from Graybar. Never checked with CSC
for that. We bought a large roll from Graybar and simply cut what we
need. It's not precut and pretty but it works.



--
Mike Lyon
408-621-4826
mike.l...@gmail.com

http://www.linkedin.com/in/mlyon

Problem reaching Wikipedia (AS43821) via Tele2

[Israel G. Lugo]

Hello,

Anyone else having problems reaching Wikipedia?

I can't reach AS43821 (Wikimedia RIPE) from within the Portuguese NREN
(AS1930), via Cogent (AS174) -> Tele2 (AS1257):

traceroute to en.wikipedia.org (91.198.174.225), 30 hops max, 60 byte
packets
 1  Router3.10GE.Lisboa.fccn.pt (193.136.1.89) [AS1930]  0.953 ms
 2  ROUTER10.10GE.Lisboa.fccn.pt (193.137.0.8) [AS1930]  0.939 ms
 3  ROUTER4.10GE.Lisboa.fccn.pt (193.137.0.20) [AS1930]  1.000 ms
 4  fccn.mx2.lis.pt.geant.net (62.40.124.97) [AS20965]  1.000 ms
 5  xe-2-3-0.rt1.mad.es.geant.net (62.40.98.107) [AS20965]  13.926 ms
 6  as2.rt1.gen.ch.geant2.net (62.40.112.25) [AS20965]  37.882 ms
 7  ae3.mx1.gen.ch.geant.net (62.40.112.14) [AS20965]  37.874 ms
 8  ae1.mx1.fra.de.geant.net (62.40.98.109) [AS20965]  44.154 ms
 9  ae4.rt1.fra.de.geant.net (62.40.98.135) [AS20965]  43.935 ms
10  te0-4-0-2.mag21.fra03.atlas.cogentco.com (149.6.42.73) [AS174] 
44.842 ms
11  fra36-peer-1.xe-1-2-0-unit0.tele2.net (130.244.200.41) [AS1257] 
44.368 ms
12  fra36-core-1.bundle-ether2.tele2.net (130.244.64.186) [AS1257] 
44.977 ms
13  *
14  ams13-peer-1.ae0-unit0.tele2.net (130.244.53.123) [AS1257]  50.299 ms
15  *
16  *
17  *
18  *
19  *
20  *

Tele2's traceroute server (http://services.tele2net.at/traceroute.html)
reaches the same IP without problems:

1 213.90.34.4 (213.90.34.4) 0.268 ms 0.124 ms 0.151 ms
2 213.90.1.20 (213.90.1.20) 0.430 ms 0.382 ms 0.303 ms
3 wat1-15-93.net.uta.at (62.218.15.93) 0.497 ms 0.368 ms 0.387 ms
4 c76wmode1-tengigE4-1.net.uta.at (212.152.192.206) 0.644 ms 0.572 ms
0.599 ms
5 wen1-core-2.tengige0-0-1-1.tele2.net (130.244.205.57) 0.836 ms 0.874
ms 0.737 ms
6 fra36-core-1.bundle-ether7.tele2.net (130.244.206.28) 13.683 ms 13.472
ms 13.817 ms
7 ams-core-2.bundle-ether4.tele2.net (130.244.64.201) 20.421 ms 20.482
ms 20.762 ms
8 ams13-peer-1.ae0-unit0.tele2.net (130.244.53.123) 19.972 ms 19.936 ms
19.962 ms
9 ge-2-5.br1-knams.wikimedia.org (130.244.6.250) 20.727 ms 20.641 ms
20.660 ms
10 wikipedia-lb.esams.wikimedia.org (91.198.174.225) 20.610 ms 20.539 ms
20.615 ms

Trying from $HOME_ISP, via AS6453 (Globe) -> AS1299 (Telia) works fine.

Regards,
Israel G. Lugo

Re: Google Public DNS Problems?

[Jay Ashworth]

- Original Message -
> From: "Perry Lorier" 

> On 5/1/13 12:38 PM, Blair Trosper wrote:
> 
> > That's all well and good, but I certainly wouldn't expect "nslookup
> > gmail.com " or for "nslookup google.com" to return
> > SERVFAIL

> Do you have traceroutes to 8.8.8.8 and 8.8.4.4?

Is that actually pertinent?

8.8 and 8.4 aren't *public zone servers* for Google's commercial domains,
are they?  I have been assuming they were only open recursive resolver
nameservers...

Cheers,
-- jra
-- 
Jay R. Ashworth  Baylink   j...@baylink.com
Designer The Things I Think   RFC 2100
Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII
St Petersburg FL USA   #natog  +1 727 647 1274

Re: Google Public DNS Problems?

[Christopher Morrow]

On Thu, May 2, 2013 at 10:32 AM, Jay Ashworth  wrote:

> - Original Message -
> > From: "Perry Lorier" 
>
> > On 5/1/13 12:38 PM, Blair Trosper wrote:
> >
> > > That's all well and good, but I certainly wouldn't expect "nslookup
> > > gmail.com " or for "nslookup google.com" to return
> > > SERVFAIL
>
> > Do you have traceroutes to 8.8.8.8 and 8.8.4.4?
>
> Is that actually pertinent?
>
> 8.8 and 8.4 aren't *public zone servers* for Google's commercial domains,
> are they?  I have been assuming they were only open recursive resolver
> nameservers...
>
>
I think perry's question is: "Can you show me which networks you traversed
and which instance of the service you were talking to at the time of the
problem?" (or 'now' if the problem is persisting)

Re: Google Public DNS Problems?

[Jay Ashworth]

- Original Message -
> From: "Christopher Morrow" 

> On Thu, May 2, 2013 at 10:32 AM, Jay Ashworth  wrote:
> 
> > - Original Message -
> > > From: "Perry Lorier" 
> >
> > > On 5/1/13 12:38 PM, Blair Trosper wrote:
> > >
> > > > That's all well and good, but I certainly wouldn't expect "nslookup
> > > > gmail.com " or for "nslookup google.com" to
> > > > return SERVFAIL
> >
> > > Do you have traceroutes to 8.8.8.8 and 8.8.4.4?
> >
> > Is that actually pertinent?
> >
> > 8.8 and 8.4 aren't *public zone servers* for Google's commercial domains,
> > are they? I have been assuming they were only open recursive resolver
> > nameservers...

> I think perry's question is: "Can you show me which networks you traversed
> and which instance of the service you were talking to at the time of
> the problem?" (or 'now' if the problem is persisting)

Sure, Chris.

But since Perry's problem is *inability to resolve names in google's
public zones*, the *path to the ZONE servers* is the thing diagnostics
would require a trace to, no?

If 8.8.8.8 doesn't *answer* for "google.com" (and no one's told me it
has), then how you get there is irrelevant.

Cheers,
-- jra
-- 
Jay R. Ashworth  Baylink   j...@baylink.com
Designer The Things I Think   RFC 2100
Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII
St Petersburg FL USA   #natog  +1 727 647 1274

Re: Google Public DNS Problems?

[Joe Abley]

On 2013-05-02, at 11:51, Jay Ashworth  wrote:

> But since Perry's problem is *inability to resolve names in google's
> public zones*, the *path to the ZONE servers* is the thing diagnostics
> would require a trace to, no?

Blair's problem, I think. Perry was just being helpful. Blair's point was that 
if Google DNS is not able to resolve Google domains, then you know something is 
wrong.

> If 8.8.8.8 doesn't *answer* for "google.com" (and no one's told me it
> has), then how you get there is irrelevant.

Well, if you're trying to troubleshoot the performance or functionality of a 
service that is deployed using anycast, knowing what anycast node is giving 
problems is pretty useful. I say this as someone who has to help troubleshoot 
problems with anycast DNS services pretty regularly.

Since there's no obvious way (in the draft-jabley-dnsop-anycast-mapping sense) 
to identify a Google DNS anycast node in-band, traceroute and RTT are pretty 
much what we're left with.


Joe

Re: Google Public DNS Problems?

[Charles Gucker]

Joe,

 That's not entirely true.You can easily do lookup for
whoami.akamai.net and it will return the unicast address for the node
in question (provided the local resolver is able to do the
resolution).This is a frequent lookup that I do when I don't know
what actual anycast node I'm using.


charles



On Thu, May 2, 2013 at 11:55 AM, Joe Abley  wrote:
>
> On 2013-05-02, at 11:51, Jay Ashworth  wrote:
>
>> But since Perry's problem is *inability to resolve names in google's
>> public zones*, the *path to the ZONE servers* is the thing diagnostics
>> would require a trace to, no?
>
> Blair's problem, I think. Perry was just being helpful. Blair's point was 
> that if Google DNS is not able to resolve Google domains, then you know 
> something is wrong.
>
>> If 8.8.8.8 doesn't *answer* for "google.com" (and no one's told me it
>> has), then how you get there is irrelevant.
>
> Well, if you're trying to troubleshoot the performance or functionality of a 
> service that is deployed using anycast, knowing what anycast node is giving 
> problems is pretty useful. I say this as someone who has to help troubleshoot 
> problems with anycast DNS services pretty regularly.
>
> Since there's no obvious way (in the draft-jabley-dnsop-anycast-mapping 
> sense) to identify a Google DNS anycast node in-band, traceroute and RTT are 
> pretty much what we're left with.
>
>
> Joe

Re: Google Public DNS Problems?

[Christopher Morrow]

On Thu, May 2, 2013 at 11:51 AM, Jay Ashworth  wrote:

> - Original Message -
> > From: "Christopher Morrow" 
>
> > On Thu, May 2, 2013 at 10:32 AM, Jay Ashworth  wrote:
> >
> > > - Original Message -
> > > > From: "Perry Lorier" 
> > >
> > > > On 5/1/13 12:38 PM, Blair Trosper wrote:
> > > >
> > > > > That's all well and good, but I certainly wouldn't expect "nslookup
> > > > > gmail.com " or for "nslookup google.com" to
> > > > > return SERVFAIL
> > >
> > > > Do you have traceroutes to 8.8.8.8 and 8.8.4.4?
> > >
> > > Is that actually pertinent?
> > >
> > > 8.8 and 8.4 aren't *public zone servers* for Google's commercial
> domains,
> > > are they? I have been assuming they were only open recursive resolver
> > > nameservers...
>
> > I think perry's question is: "Can you show me which networks you
> traversed
> > and which instance of the service you were talking to at the time of
> > the problem?" (or 'now' if the problem is persisting)
>
> Sure, Chris.
>
> But since Perry's problem is *inability to resolve names in google's
>

s/perry/blair/


> public zones*, the *path to the ZONE servers* is the thing diagnostics
> would require a trace to, no?
>

I think, from some troubleshooting with blair yesterday he was having some
odd problems with queries to google-public-dns (gdns), where everything he
asked came up servfail. I wasn't able to repro this, which was annoying ;(
We (perry/others) were interested in verifying that something odd wasn't
happening between blair and the server answering his question(s)...


>
> If 8.8.8.8 doesn't *answer* for "google.com" (and no one's told me it
> has), then how you get there is irrelevant.
>
>
8.8.8.8 is just an open resolver... oh, jabley replied as well (alway a
cogent reply from him)


> Cheers,
> -- jra
> --
> Jay R. Ashworth  Baylink
> j...@baylink.com
> Designer The Things I Think   RFC
> 2100
> Ashworth & Associates http://baylink.pitas.com 2000 Land
> Rover DII
> St Petersburg FL USA   #natog  +1 727 647
> 1274
>
>

Re: Google Public DNS Problems?

[Joe Abley]

On 2013-05-02, at 11:59, Charles Gucker  wrote:

> That's not entirely true.You can easily do lookup for
> whoami.akamai.net and it will return the unicast address for the node
> in question (provided the local resolver is able to do the
> resolution).This is a frequent lookup that I do when I don't know
> what actual anycast node I'm using.

Using 8.8.8.8 to tell me about whoami.akamai.net tells me what Akamai 
authoritative server Google last used to answer that query.

If I can rely upon there being an Akamai auth server every place there's a 
Google 8.8.8.8 server, then that does seem fun and useful for identifying the 
Google node I'm using. Is that the case?

(If I ask 8.8.8.8, which is somewhere 30ms from Toronto, about 
identity.l.root-servers.org/IN/TXT then the answer I get just now is "Paris, 
France". L-Root and Google/8.8.8.8 are not colocated. So the usefulness of this 
technique in general to identify Google nodes depends on deployment 
assumptions.)


Joe

Re: Google Public DNS Problems?

[Joe Abley]

On 2013-05-02, at 12:10, Joe Abley  wrote:

> On 2013-05-02, at 11:59, Charles Gucker  wrote:
> 
>>That's not entirely true.You can easily do lookup for
>> whoami.akamai.net and it will return the unicast address for the node
>> in question (provided the local resolver is able to do the
>> resolution).This is a frequent lookup that I do when I don't know
>> what actual anycast node I'm using.
> 
> Using 8.8.8.8 to tell me about whoami.akamai.net tells me what Akamai 
> authoritative server Google last used to answer that query.

Oh, now that I poke at it, it seems like whoami.akamai.net is telling me about 
the address of the resolver I used, rather than the address of the akamai node 
I hit.

Never mind, I understand now :-)


Joe

Re: Could not send email to office 365

[JoeSox]

Our Technical Support is reporting a big jump in Outlook connectivity
issues about 5-10 minutes ago.
Our resolvers are testing fine.
--
Thanks, Joe


On Thu, May 2, 2013 at 4:53 AM, Joe Abley  wrote:

>
> On 2013-05-02, at 02:42, Cathy Almond  wrote:
>
> > This may be a red herring, but I've heard of some dropping of DNS
> > queries for the names within outlook.com domains where the queries are
> > all coming from source port 53 (i.e. your recursive server doesn't use
> > query source port randomization
>
> ... or there's a NAT or some other box in front of the recursive server
> which re-writes the source port...
>
> > ).  Might be worth checking what the
> > recursive server you're using is doing?
> >
> > See https://www.dns-oarc.net/oarc/services/porttest
>
>
> Joe
>

Re: Problem reaching Wikipedia (AS43821) via Tele2

[Grant Ridder]

Looks like ge-2-5.br1-knams.wikimedia.org (130.244.6.250) is filtering you 
somehow.

Grant 

Sent from my iPhone

On May 2, 2013, at 9:01 AM, "Israel G. Lugo"  wrote:

> Hello,
> 
> Anyone else having problems reaching Wikipedia?
> 
> I can't reach AS43821 (Wikimedia RIPE) from within the Portuguese NREN
> (AS1930), via Cogent (AS174) -> Tele2 (AS1257):
> 
> traceroute to en.wikipedia.org (91.198.174.225), 30 hops max, 60 byte
> packets
> 1  Router3.10GE.Lisboa.fccn.pt (193.136.1.89) [AS1930]  0.953 ms
> 2  ROUTER10.10GE.Lisboa.fccn.pt (193.137.0.8) [AS1930]  0.939 ms
> 3  ROUTER4.10GE.Lisboa.fccn.pt (193.137.0.20) [AS1930]  1.000 ms
> 4  fccn.mx2.lis.pt.geant.net (62.40.124.97) [AS20965]  1.000 ms
> 5  xe-2-3-0.rt1.mad.es.geant.net (62.40.98.107) [AS20965]  13.926 ms
> 6  as2.rt1.gen.ch.geant2.net (62.40.112.25) [AS20965]  37.882 ms
> 7  ae3.mx1.gen.ch.geant.net (62.40.112.14) [AS20965]  37.874 ms
> 8  ae1.mx1.fra.de.geant.net (62.40.98.109) [AS20965]  44.154 ms
> 9  ae4.rt1.fra.de.geant.net (62.40.98.135) [AS20965]  43.935 ms
> 10  te0-4-0-2.mag21.fra03.atlas.cogentco.com (149.6.42.73) [AS174] 
> 44.842 ms
> 11  fra36-peer-1.xe-1-2-0-unit0.tele2.net (130.244.200.41) [AS1257] 
> 44.368 ms
> 12  fra36-core-1.bundle-ether2.tele2.net (130.244.64.186) [AS1257] 
> 44.977 ms
> 13  *
> 14  ams13-peer-1.ae0-unit0.tele2.net (130.244.53.123) [AS1257]  50.299 ms
> 15  *
> 16  *
> 17  *
> 18  *
> 19  *
> 20  *
> 
> Tele2's traceroute server (http://services.tele2net.at/traceroute.html)
> reaches the same IP without problems:
> 
> 1 213.90.34.4 (213.90.34.4) 0.268 ms 0.124 ms 0.151 ms
> 2 213.90.1.20 (213.90.1.20) 0.430 ms 0.382 ms 0.303 ms
> 3 wat1-15-93.net.uta.at (62.218.15.93) 0.497 ms 0.368 ms 0.387 ms
> 4 c76wmode1-tengigE4-1.net.uta.at (212.152.192.206) 0.644 ms 0.572 ms
> 0.599 ms
> 5 wen1-core-2.tengige0-0-1-1.tele2.net (130.244.205.57) 0.836 ms 0.874
> ms 0.737 ms
> 6 fra36-core-1.bundle-ether7.tele2.net (130.244.206.28) 13.683 ms 13.472
> ms 13.817 ms
> 7 ams-core-2.bundle-ether4.tele2.net (130.244.64.201) 20.421 ms 20.482
> ms 20.762 ms
> 8 ams13-peer-1.ae0-unit0.tele2.net (130.244.53.123) 19.972 ms 19.936 ms
> 19.962 ms
> 9 ge-2-5.br1-knams.wikimedia.org (130.244.6.250) 20.727 ms 20.641 ms
> 20.660 ms
> 10 wikipedia-lb.esams.wikimedia.org (91.198.174.225) 20.610 ms 20.539 ms
> 20.615 ms
> 
> Trying from $HOME_ISP, via AS6453 (Globe) -> AS1299 (Telia) works fine.
> 
> Regards,
> Israel G. Lugo
> 
> 

BGP Route Recorder suggestions

[Ben Bartsch]

Hi all:

I am curious what you RENs out there are using for BGP (and IGP) route
recording.  We did a demo of Packet Design's Route Explorer.  While I loved
the functionality and ease of use, we simply can not afford it.  I am
attracted to iBGPlay since we use the BGPlayer at routeviews all the time,
but I can't seem to get a privacy statement from the software authors.

Any other (cheap) route recorders out there?  Any recommendations on what
y'all are using that you like / don't like?

Thanks in advance for any input.

-ben

whoami.akamai.net [was: Google Public DNS Problems?]

[Patrick W. Gilmore]

On May 02, 2013, at 12:12 , Joe Abley  wrote:
> On 2013-05-02, at 12:10, Joe Abley  wrote:
>> On 2013-05-02, at 11:59, Charles Gucker  wrote:

>>>   That's not entirely true.You can easily do lookup for
>>> whoami.akamai.net and it will return the unicast address for the node
>>> in question (provided the local resolver is able to do the
>>> resolution).This is a frequent lookup that I do when I don't know
>>> what actual anycast node I'm using.
>> 
>> Using 8.8.8.8 to tell me about whoami.akamai.net tells me what Akamai 
>> authoritative server Google last used to answer that query.
> 
> Oh, now that I poke at it, it seems like whoami.akamai.net is telling me 
> about the address of the resolver I used, rather than the address of the 
> akamai node I hit.
> 
> Never mind, I understand now :-)

For clarity: Looking up the hostname "whoami.akamai.net" will return the IP 
address in the source field of the packet (DNS query) which reached the 
authoritative name server for Akamai.net.

We use this to look for forwarding or proxying, which is frequently unknown / 
invisible to the end user.

It has the side-effect that querying against an anycast server (e.g. 
208.67.222.222 or 8.8.8.8) will show the unicast address of the anycast node 
which forwarded to our servers.

In case anyone is wondering, we do not do any special logging or watching of 
this hostname. It is logged for a short time on the local hard drive the same 
as any other DNS query, but unless someone actually looks, we will not notice 
if you query for it. So feel free to use it for your own purposes as much as 
you like. We have a bit of spare DNS capacity. :)

-- 
TTFN,
patrick

Re: whoami.akamai.net [was: Google Public DNS Problems?]

[Constantine A. Murenin]

On 2 May 2013 11:12, Patrick W. Gilmore  wrote:
> On May 02, 2013, at 12:12 , Joe Abley  wrote:
>> On 2013-05-02, at 12:10, Joe Abley  wrote:
>>> On 2013-05-02, at 11:59, Charles Gucker  wrote:
>
   That's not entirely true.You can easily do lookup for
 whoami.akamai.net and it will return the unicast address for the node
 in question (provided the local resolver is able to do the
 resolution).This is a frequent lookup that I do when I don't know
 what actual anycast node I'm using.
>>>
>>> Using 8.8.8.8 to tell me about whoami.akamai.net tells me what Akamai 
>>> authoritative server Google last used to answer that query.
>>
>> Oh, now that I poke at it, it seems like whoami.akamai.net is telling me 
>> about the address of the resolver I used, rather than the address of the 
>> akamai node I hit.
>>
>> Never mind, I understand now :-)
>
> For clarity: Looking up the hostname "whoami.akamai.net" will return the IP 
> address in the source field of the packet (DNS query) which reached the 
> authoritative name server for Akamai.net.
>
> We use this to look for forwarding or proxying, which is frequently unknown / 
> invisible to the end user.
>
> It has the side-effect that querying against an anycast server (e.g. 
> 208.67.222.222 or 8.8.8.8) will show the unicast address of the anycast node 
> which forwarded to our servers.
>
> In case anyone is wondering, we do not do any special logging or watching of 
> this hostname. It is logged for a short time on the local hard drive the same 
> as any other DNS query, but unless someone actually looks, we will not notice 
> if you query for it. So feel free to use it for your own purposes as much as 
> you like. We have a bit of spare DNS capacity. :)


No IPv6 at akamai.net, huh? :p

Cns# host whoami.akamai.net
whoami.akamai.net has address 216.66.80.30
Cns# host 216.66.80.30
30.80.66.216.in-addr.arpa domain name pointer tserv1.fra1.he.net.
Cns#

Does anyone run a DNS whoami that's IPv6-ready?

C.

Re: whoami.akamai.net [was: Google Public DNS Problems?]

[Patrick W. Gilmore]

On May 02, 2013, at 14:42 , "Constantine A. Murenin"  wrote:
> On 2 May 2013 11:12, Patrick W. Gilmore  wrote:

>> For clarity: Looking up the hostname "whoami.akamai.net" will return the IP 
>> address in the source field of the packet (DNS query) which reached the 
>> authoritative name server for Akamai.net.
>> 
>> We use this to look for forwarding or proxying, which is frequently unknown 
>> / invisible to the end user.
>> 
>> It has the side-effect that querying against an anycast server (e.g. 
>> 208.67.222.222 or 8.8.8.8) will show the unicast address of the anycast node 
>> which forwarded to our servers.
>> 
>> In case anyone is wondering, we do not do any special logging or watching of 
>> this hostname. It is logged for a short time on the local hard drive the 
>> same as any other DNS query, but unless someone actually looks, we will not 
>> notice if you query for it. So feel free to use it for your own purposes as 
>> much as you like. We have a bit of spare DNS capacity. :)
> 
> No IPv6 at akamai.net, huh? :p

No, sorry. We're working on it.

Of course, v6 is available on most other Akamai products.

And if someone wants to pay us for v6 on whomai. :)

-- 
TTFN,
patrick


> Cns# host whoami.akamai.net
> whoami.akamai.net has address 216.66.80.30
> Cns# host 216.66.80.30
> 30.80.66.216.in-addr.arpa domain name pointer tserv1.fra1.he.net.
> Cns#
> 
> Does anyone run a DNS whoami that's IPv6-ready?
> 
> C.
> 

Re: whoami.akamai.net [was: Google Public DNS Problems?]

[Christopher Morrow]

On Thu, May 2, 2013 at 2:12 PM, Patrick W. Gilmore wrote:

> On May 02, 2013, at 12:12 , Joe Abley  wrote:
> > On 2013-05-02, at 12:10, Joe Abley  wrote:
> >> On 2013-05-02, at 11:59, Charles Gucker  wrote:
>
> >>>   That's not entirely true.You can easily do lookup for
> >>> whoami.akamai.net and it will return the unicast address for the node
> >>> in question (provided the local resolver is able to do the
> >>> resolution).This is a frequent lookup that I do when I don't know
> >>> what actual anycast node I'm using.
> >>
> >> Using 8.8.8.8 to tell me about whoami.akamai.net tells me what Akamai
> authoritative server Google last used to answer that query.
> >
> > Oh, now that I poke at it, it seems like whoami.akamai.net is telling
> me about the address of the resolver I used, rather than the address of the
> akamai node I hit.
> >
> > Never mind, I understand now :-)
>
> For clarity: Looking up the hostname "whoami.akamai.net" will return the
> IP address in the source field of the packet (DNS query) which reached the
> authoritative name server for Akamai.net.
>
> We use this to look for forwarding or proxying, which is frequently
> unknown / invisible to the end user.
>
> It has the side-effect that querying against an anycast server (e.g.
> 208.67.222.222 or 8.8.8.8) will show the unicast address of the anycast
> node which forwarded to our servers.
>
>
'the unicast address of the exit for upstream/cache-fill lookups' .. since
the topology behind the anycast node isn't necessarily:
internet -> anycast-ip -|host|- unicast-ip ...

there could be some networking between |host| and the outside world, or
other things going on.

anyway... nit-picking-aside, cool that there's a way to figure this sort of
thing out :)
google has a similar method, which I can't find today :( 

Louisiana Optical Network Initiative

[John D Caffery]

I am sending this query on behalf of the University of New Orleans.  For the 
past couple of weeks users on their campus are unable to get logged on to the 
Capital One Online Banking Secure Portal to do their online banking.  The UNO 
AS number is 23666 and LONI, which I am part of, is their internet provider, AS 
number 32440.  None of our other Louisiana Participants seem to have an issue 
getting there and every test I do from other locations in our network are 
successful.  Users can get to the https://onlinebanking.capitalone.com site but 
after putting in their login credentials the site simply times out.

Capital One peers with both Verizon and AT&T but when I go to the above site it 
is via Verizon.

Does anyone know of or have this issue also?  I have a ticket open with Verizon 
but have yet to get a response.  I was speaking with a representative from 
Capital One but after leaving several voice mails I have yet to get a call back.

Thank you in advance for anyone's assistance,

John Caffery
Information Technology Consultant
Louisiana Optical Network Initiative - LONI
O  225.578.7263
C   225.252.3046
www.loni.org

Google Security Contact

[J. Oquendo]

Can someone put me in touch with someone "up there" in the
security realm at Google? (sorry for the noise)

-- 
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
J. Oquendo
SGFA, SGFE, C|EH, CNDA, CHFI, OSCP, CPT, RWSP, GREM

"Where ignorance is our master, there is no possibility of
real peace" - Dalai Lama

42B0 5A53 6505 6638 44BB  3943 2BF7 D83F 210A 95AF
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2BF7D83F210A95AF

[NANOG-announce] NANOG 58 Updates

[Betty Burke]

Colleagues:

NANOG 58 is fast approaching!  NANOGers will be meeting June 3 – 5, 2013 in
New Orleans, LA.

Do not delay, be sure to register for NANOG
58and take advantage
of early
Bird Registration which ends on May 10, 2013  (non-member $450, member
$425, student $100).

As you register for NANOG 58, be sure to reserve your hotel room at
theRoosevelt New Orleans
Hotel,
the room
block is almost full and the NANOG room rate will expire at 5 PM CT on May
10, 2013.

For meeting information be sure to visit the NANOG 58
Highlightspage,
and check-out the NANOG
Topic List and Preliminary Agenda
.

The NANOG Program Committee  received a
number of great submissions and are
very close to posting the tentative agenda.  NANOG 58 will once again
showcase a program packed
with great content.

If you are interested in a NANOG Sponsorship, contact our Development
Committee by emailing
market...@nanog.org.

We look forward to a great meeting and seeing you in New Orleans.

Should you have any questions, please direct them to nanog-supp...@nanog.org
.


Sincerely,

Betty

-- 
Betty Burke
NANOG Executive Director
48377 Fremont Boulevard, Suite 117
Fremont, CA 94538
Tel: +1 510 492 4030
___
NANOG-announce mailing list
nanog-annou...@mailman.nanog.org
http://mailman.nanog.org/mailman/listinfo/nanog-announce

Re: Google Security Contact

[Damian Menscher]

In general security vulnerabilities in applications should be reported
following the links at http://www.google.com/about/appsecurity/  For abuse
issues, there are usually links within the products.

If your question isn't covered by any of that, I can probably help.  Feel
free to ping me off-list.

Damian
-- 
Damian Menscher :: Security Reliability Engineer :: Google


On Thu, May 2, 2013 at 12:40 PM, J. Oquendo  wrote:

>
> Can someone put me in touch with someone "up there" in the
> security realm at Google? (sorry for the noise)
>
> --
> =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
> J. Oquendo
> SGFA, SGFE, C|EH, CNDA, CHFI, OSCP, CPT, RWSP, GREM
>
> "Where ignorance is our master, there is no possibility of
> real peace" - Dalai Lama
>
> 42B0 5A53 6505 6638 44BB  3943 2BF7 D83F 210A 95AF
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2BF7D83F210A95AF
>
>

Re: Louisiana Optical Network Initiative

[Thomas Cannon]

Hijacked DNS to steal login credentials perhaps?

-tc

On May 2, 2013, at 10:35 AM, John D Caffery  wrote:

> I am sending this query on behalf of the University of New Orleans.  For the 
> past couple of weeks users on their campus are unable to get logged on to the 
> Capital One Online Banking Secure Portal to do their online banking.  The UNO 
> AS number is 23666 and LONI, which I am part of, is their internet provider, 
> AS number 32440.  None of our other Louisiana Participants seem to have an 
> issue getting there and every test I do from other locations in our network 
> are successful.  Users can get to the https://onlinebanking.capitalone.com 
> site but after putting in their login credentials the site simply times out.
> 
> Capital One peers with both Verizon and AT&T but when I go to the above site 
> it is via Verizon.
> 
> Does anyone know of or have this issue also?  I have a ticket open with 
> Verizon but have yet to get a response.  I was speaking with a representative 
> from Capital One but after leaving several voice mails I have yet to get a 
> call back.
> 
> Thank you in advance for anyone's assistance,
> 
> John Caffery
> Information Technology Consultant
> Louisiana Optical Network Initiative - LONI
> O  225.578.7263
> C   225.252.3046
> www.loni.org
> 
> 

Re: Louisiana Optical Network Initiative

[Paul Ferguson]

John,

Can you provide the prefixes in question off-list?

Thanks,

- ferg (not at Capital One, but can perhaps assist here)


> On May 2, 2013, at 10:35 AM, John D Caffery  wrote:
>
>> I am sending this query on behalf of the University of New Orleans.  For the 
>> past couple of weeks users on their campus are unable to get logged on to 
>> the Capital One Online Banking Secure Portal to do their online banking.  
>> The UNO AS number is 23666 and LONI, which I am part of, is their internet 
>> provider, AS number 32440.  None of our other Louisiana Participants seem to 
>> have an issue getting there and every test I do from other locations in our 
>> network are successful.  Users can get to the 
>> https://onlinebanking.capitalone.com site but after putting in their login 
>> credentials the site simply times out.
>>
>> Capital One peers with both Verizon and AT&T but when I go to the above site 
>> it is via Verizon.
>>
>> Does anyone know of or have this issue also?  I have a ticket open with 
>> Verizon but have yet to get a response.  I was speaking with a 
>> representative from Capital One but after leaving several voice mails I have 
>> yet to get a call back.
>>
>> Thank you in advance for anyone's assistance,
>>
>> John Caffery
>> Information Technology Consultant
>> Louisiana Optical Network Initiative - LONI
>> O  225.578.7263
>> C   225.252.3046
>> www.loni.org
>>
>>
>
>



--
"Fergie", a.k.a. Paul Ferguson
 fergdawgster(at)gmail.com

RE: Louisiana Optical Network Initiative

[Eric Wieling]

Blocking ICMP packet-too-big packets (or other ICMP which might break PMTU) on 
your firewall, perhaps?

-Original Message-
From: Thomas Cannon [mailto:tcan...@beatsmusic.com] 
Sent: Thursday, May 02, 2013 5:55 PM
To: John D Caffery
Cc: nanog@nanog.org
Subject: Re: Louisiana Optical Network Initiative


Hijacked DNS to steal login credentials perhaps?

-tc

On May 2, 2013, at 10:35 AM, John D Caffery  wrote:

> I am sending this query on behalf of the University of New Orleans.  For the 
> past couple of weeks users on their campus are unable to get logged on to the 
> Capital One Online Banking Secure Portal to do their online banking.  The UNO 
> AS number is 23666 and LONI, which I am part of, is their internet provider, 
> AS number 32440.  None of our other Louisiana Participants seem to have an 
> issue getting there and every test I do from other locations in our network 
> are successful.  Users can get to the https://onlinebanking.capitalone.com 
> site but after putting in their login credentials the site simply times out.
> 
> Capital One peers with both Verizon and AT&T but when I go to the above site 
> it is via Verizon.
> 
> Does anyone know of or have this issue also?  I have a ticket open with 
> Verizon but have yet to get a response.  I was speaking with a representative 
> from Capital One but after leaving several voice mails I have yet to get a 
> call back.
> 
> Thank you in advance for anyone's assistance,
> 
> John Caffery
> Information Technology Consultant
> Louisiana Optical Network Initiative - LONI O  225.578.7263
> C   225.252.3046
> www.loni.org
> 
> 

Re: whoami.akamai.net [was: Google Public DNS Problems?]

[Cameron Daniel]

On 2013-05-03 4:57 am, Christopher Morrow wrote:
anyway... nit-picking-aside, cool that there's a way to figure this 
sort of

thing out :)
google has a similar method, which I can't find today :( 


dig -t txt o-o.myaddr.l.google.com

Re: whoami.akamai.net [was: Google Public DNS Problems?]

[Constantine A. Murenin]

On 2 May 2013 15:41, Cameron Daniel  wrote:
> On 2013-05-03 4:57 am, Christopher Morrow wrote:
>>
>> anyway... nit-picking-aside, cool that there's a way to figure this sort
>> of
>> thing out :)
>> google has a similar method, which I can't find today :( > webcrawler!!!>
>
>
> dig -t txt o-o.myaddr.l.google.com

That's cool, but still no IPv6.

Cns#  dig -t txt o-o.myaddr.l.google.com

; <<>> DiG 9.4.2-P2 <<>> -t txt o-o.myaddr.l.google.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53188
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;o-o.myaddr.l.google.com.   IN  TXT

;; ANSWER SECTION:
o-o.myaddr.l.google.com. 60 IN  TXT "216.66.80.30"

;; Query time: 9 msec
;; SERVER: 2001:470:20::2#53(2001:470:20::2)
;; WHEN: Thu May  2 15:46:22 2013
;; MSG SIZE  rcvd: 66

Cns#

Re: Louisiana Optical Network Initiative

[Paul Ferguson]

Hang on -- University of New Orleans's AS is 23666?

Looks like "SISTELINDO-AS-ID PT Sistelindo Mitralintas":

http://www.cidr-report.org/cgi-bin/as-report?as=as23666

?

- ferg

On Thu, May 2, 2013 at 3:22 PM, Paul Ferguson  wrote:

> John,
>
> Can you provide the prefixes in question off-list?
>
> Thanks,
>
> - ferg (not at Capital One, but can perhaps assist here)
>
>
>> On May 2, 2013, at 10:35 AM, John D Caffery  wrote:
>>
>>> I am sending this query on behalf of the University of New Orleans.  For 
>>> the past couple of weeks users on their campus are unable to get logged on 
>>> to the Capital One Online Banking Secure Portal to do their online banking. 
>>>  The UNO AS number is 23666 and LONI, which I am part of, is their internet 
>>> provider, AS number 32440.  None of our other Louisiana Participants seem 
>>> to have an issue getting there and every test I do from other locations in 
>>> our network are successful.  Users can get to the 
>>> https://onlinebanking.capitalone.com site but after putting in their login 
>>> credentials the site simply times out.
>>>
>>> Capital One peers with both Verizon and AT&T but when I go to the above 
>>> site it is via Verizon.
>>>
>>> Does anyone know of or have this issue also?  I have a ticket open with 
>>> Verizon but have yet to get a response.  I was speaking with a 
>>> representative from Capital One but after leaving several voice mails I 
>>> have yet to get a call back.
>>>
>>> Thank you in advance for anyone's assistance,
>>>
>>> John Caffery
>>> Information Technology Consultant
>>> Louisiana Optical Network Initiative - LONI
>>> O  225.578.7263
>>> C   225.252.3046
>>> www.loni.org
>>>
>>>
>>
>>
>
>


--
"Fergie", a.k.a. Paul Ferguson
 fergdawgster(at)gmail.com

Re: whoami.akamai.net [was: Google Public DNS Problems?]

[Valdis . Kletnieks]

On Thu, 02 May 2013 15:48:08 -0700, "Constantine A. Murenin" said:
> On 2 May 2013 15:41, Cameron Daniel  wrote:

> > dig -t txt o-o.myaddr.l.google.com
>
> That's cool, but still no IPv6.

> o-o.myaddr.l.google.com. 60 IN  TXT "216.66.80.30"

You're complaining that there's no IPv6 data in a *descriptive TXT* record?

Man, if that's the biggest IPv6 issue we have, we're on easy street. :)


pgpQNOaBEodbs.pgp
Description: PGP signature

Re: Louisiana Optical Network Initiative

[joel jaeggli]

On 5/2/13 3:54 PM, Paul Ferguson wrote:

Hang on -- University of New Orleans's AS is 23666?

http://bgp.he.net/AS26333

Looks like "SISTELINDO-AS-ID PT Sistelindo Mitralintas":

http://www.cidr-report.org/cgi-bin/as-report?as=as23666

?

- ferg

On Thu, May 2, 2013 at 3:22 PM, Paul Ferguson  wrote:


John,

Can you provide the prefixes in question off-list?

Thanks,

- ferg (not at Capital One, but can perhaps assist here)



On May 2, 2013, at 10:35 AM, John D Caffery  wrote:


I am sending this query on behalf of the University of New Orleans.  For the 
past couple of weeks users on their campus are unable to get logged on to the 
Capital One Online Banking Secure Portal to do their online banking.  The UNO 
AS number is 23666 and LONI, which I am part of, is their internet provider, AS 
number 32440.  None of our other Louisiana Participants seem to have an issue 
getting there and every test I do from other locations in our network are 
successful.  Users can get to the https://onlinebanking.capitalone.com site but 
after putting in their login credentials the site simply times out.

Capital One peers with both Verizon and AT&T but when I go to the above site it 
is via Verizon.

Does anyone know of or have this issue also?  I have a ticket open with Verizon 
but have yet to get a response.  I was speaking with a representative from 
Capital One but after leaving several voice mails I have yet to get a call back.

Thank you in advance for anyone's assistance,

John Caffery
Information Technology Consultant
Louisiana Optical Network Initiative - LONI
O  225.578.7263
C   225.252.3046
www.loni.org








--
"Fergie", a.k.a. Paul Ferguson
  fergdawgster(at)gmail.com

Re: Louisiana Optical Network Initiative

[Warren Bailey]

AS26333
Country: US
Registration Date: 2002-08-22
Registrar: arin
Owner: UNONET - University of New Orleans




On 5/2/13 3:54 PM, "Paul Ferguson"  wrote:

>Hang on -- University of New Orleans's AS is 23666?
>
>Looks like "SISTELINDO-AS-ID PT Sistelindo Mitralintas":
>
>http://www.cidr-report.org/cgi-bin/as-report?as=as23666
>
>?
>
>- ferg
>
>On Thu, May 2, 2013 at 3:22 PM, Paul Ferguson 
>wrote:
>
>> John,
>>
>> Can you provide the prefixes in question off-list?
>>
>> Thanks,
>>
>> - ferg (not at Capital One, but can perhaps assist here)
>>
>>
>>> On May 2, 2013, at 10:35 AM, John D Caffery  wrote:
>>>
 I am sending this query on behalf of the University of New Orleans.
For the past couple of weeks users on their campus are unable to get
logged on to the Capital One Online Banking Secure Portal to do their
online banking.  The UNO AS number is 23666 and LONI, which I am part
of, is their internet provider, AS number 32440.  None of our other
Louisiana Participants seem to have an issue getting there and every
test I do from other locations in our network are successful.  Users
can get to the https://onlinebanking.capitalone.com site but after
putting in their login credentials the site simply times out.

 Capital One peers with both Verizon and AT&T but when I go to the
above site it is via Verizon.

 Does anyone know of or have this issue also?  I have a ticket open
with Verizon but have yet to get a response.  I was speaking with a
representative from Capital One but after leaving several voice mails
I have yet to get a call back.

 Thank you in advance for anyone's assistance,

 John Caffery
 Information Technology Consultant
 Louisiana Optical Network Initiative - LONI
 O  225.578.7263
 C   225.252.3046
 www.loni.org


>>>
>>>
>>
>>
>
>
>--
>"Fergie", a.k.a. Paul Ferguson
> fergdawgster(at)gmail.com
>
>

Re: Louisiana Optical Network Initiative

[David Walker]

On 03/05/2013, John D Caffery  wrote:
> The UNO AS number is 23666 ...

26333 right?

Re: Louisiana Optical Network Initiative

[Paul Ferguson]

In the original message, he said 23666

- ferg

On Thu, May 2, 2013 at 4:59 PM, David Walker  wrote:
> On 03/05/2013, John D Caffery  wrote:
>> The UNO AS number is 23666 ...
>
> 26333 right?
>



-- 
"Fergie", a.k.a. Paul Ferguson
 fergdawgster(at)gmail.com

Re: Louisiana Optical Network Initiative

[Warren Bailey]

I'm not even cool enough to have an As number, so I'll be in my hole if anyone 
needs me.. ;)


Sent from my T-Mobile 4G LTE Device



 Original message 
From: Paul Ferguson 
Date: 05/02/2013 5:08 PM (GMT-08:00)
To: David Walker 
Cc: nanog@nanog.org
Subject: Re: Louisiana Optical Network Initiative


In the original message, he said 23666

- ferg

On Thu, May 2, 2013 at 4:59 PM, David Walker  wrote:
> On 03/05/2013, John D Caffery  wrote:
>> The UNO AS number is 23666 ...
>
> 26333 right?
>



--
"Fergie", a.k.a. Paul Ferguson
 fergdawgster(at)gmail.com

Re: Louisiana Optical Network Initiative

[Valdis . Kletnieks]

On Thu, 02 May 2013 17:05:36 -0700, Paul Ferguson said:
> In the original message, he said 23666

But 'whois as23666' points at Indonesia, not Louisiana, so I suspect
some transcription errors have crept into the process...



pgpru6LP5k5hK.pgp
Description: PGP signature

Re: Louisiana Optical Network Initiative

[Paul Ferguson]

Ya think? :-)

- ferg

On Thu, May 2, 2013 at 7:45 PM,   wrote:

> On Thu, 02 May 2013 17:05:36 -0700, Paul Ferguson said:
>> In the original message, he said 23666
>
> But 'whois as23666' points at Indonesia, not Louisiana, so I suspect
> some transcription errors have crept into the process...
>



--
"Fergie", a.k.a. Paul Ferguson
 fergdawgster(at)gmail.com