community strings for Reliance Globalcom
does anybody have the community strings for Reliance Globalcom
On Thu, Jan 12, 2012 at 2:57 PM, Philip Lavine <source_route@yahoo.com> wrote:
does anybody have the community strings for Reliance Globalcom
You might check to see if they left the default "public" read-only string in place, but I highly doubt it. Most people are pretty careful to pick at least somewhat hard to guess community strings, and to ACL them off from external querying. Matt
Additionally, http://ubs.flagtel.com/lg Their looking glass. You can do basic traceroute and BGP from here. On Fri, Jan 13, 2012 at 4:36 AM, Matthew Petach <mpetach@netflight.com>wrote:
On Thu, Jan 12, 2012 at 2:57 PM, Philip Lavine <source_route@yahoo.com> wrote:
does anybody have the community strings for Reliance Globalcom
You might check to see if they left the default "public" read-only string in place, but I highly doubt it. Most people are pretty careful to pick at least somewhat hard to guess community strings, and to ACL them off from external querying.
Matt
-- Anurag Bhatia anuragbhatia.com or simply - http://[2001:470:26:78f::5] if you are on IPv6 connected network! Twitter: @anurag_bhatia <https://twitter.com/#!/anurag_bhatia>
I could be wrong, but I think OP was requesting for BGP communities. I don't think he was asking for their SNMP community strings - I've never heard of a situation where a provider would allow their customers to poll their routers via SNMP. Or did I miss something? Stefan Fouant JNCIE-SEC, JNCIE-SP, JNCIE-ER, JNCI Technical Trainer, Juniper Networks Follow us on Twitter @JuniperEducate Sent from my iPad On Jan 12, 2012, at 6:06 PM, Matthew Petach <mpetach@netflight.com> wrote:
On Thu, Jan 12, 2012 at 2:57 PM, Philip Lavine <source_route@yahoo.com> wrote:
does anybody have the community strings for Reliance Globalcom
You might check to see if they left the default "public" read-only string in place, but I highly doubt it. Most people are pretty careful to pick at least somewhat hard to guess community strings, and to ACL them off from external querying.
Matt
nail on the head. I need the XXXX:XXXX notation for the BGP preference. I need to be able to set a provider as a backup, for example: qwest would be 209:70 ________________________________ From: Stefan Fouant <sfouant@shortestpathfirst.net> To: Matthew Petach <mpetach@netflight.com> Cc: Philip Lavine <source_route@yahoo.com>; "nanog@nanog.org" <nanog@nanog.org> Sent: Friday, January 13, 2012 6:41 AM Subject: Re: community strings for Reliance Globalcom I could be wrong, but I think OP was requesting for BGP communities. I don't think he was asking for their SNMP community strings - I've never heard of a situation where a provider would allow their customers to poll their routers via SNMP. Or did I miss something? Stefan Fouant JNCIE-SEC, JNCIE-SP, JNCIE-ER, JNCI Technical Trainer, Juniper Networks Follow us on Twitter @JuniperEducate Sent from my iPad On Jan 12, 2012, at 6:06 PM, Matthew Petach <mpetach@netflight.com> wrote:
On Thu, Jan 12, 2012 at 2:57 PM, Philip Lavine <source_route@yahoo.com> wrote:
does anybody have the community strings for Reliance Globalcom
You might check to see if they left the default "public" read-only string in place, but I highly doubt it. Most people are pretty careful to pick at least somewhat hard to guess community strings, and to ACL them off from external querying.
Matt
Here's the info from their IRR: remarks: Communities applied at ingress remarks: ======================================================= remarks: 15412:1xxx PoP remarks: 15412:1101 New York remarks: 15412:1201 Los Angeles remarks: 15412:1202 Palo Alto remarks: 15412:1301 Tokyo remarks: 15412:1311 Hong Kong remarks: 15412:1316 Singapore remarks: 15412:1321 Seoul remarks: 15412:1331 Singapore remarks: 15412:1341 Taipei remarks: 15412:1401 Cairo remarks: 15412:1411 Bahrain remarks: 15412:1402 Alexandria remarks: 15412:1412 Jeddah remarks: 15412:1413 Al Khobar remarks: 15412:1414 Dubai remarks: 15412:1415 Doha remarks: 15412:1431 Mumbai remarks: 15412:1432 Chennai remarks: 15412:1501 London remarks: 15412:1511 Paris remarks: 15412:1521 Madrid remarks: 15412:1531 Frankfurt remarks: 15412:1514 Amsterdam remarks: ======================================================= remarks: 15412:7xx Customer remarks: 15412:701 Aggregate remarks: 15412:702 Statically Routed remarks: 15412:703 BGP Routed remarks: 15412:705 BGP Routed (Suppress MED to upstreams) remarks: ======================================================= remarks: 15412:8xx Peer remarks: 15412:800 PRIVATE PEER remarks: 15412:801 PAIX remarks: 15412:802 NYIIX remarks: 15412:803 JPIX remarks: 15412:804 KINX remarks: 15412:805 HKIX remarks: 15412:806 LINX remarks: 15412:807 SFINX remarks: 15412:808 LAIX remarks: 15412:809 AMSIX remarks: 15412:810 DECIX remarks: 15412:813 JPNAP remarks: 15412:814 EQUINIX ASHBURN VA remarks: 15412:815 EQUINIX SINGAPORE remarks: 15412:816 EQUINIX TOKYO remarks: 15412:817 ANY2 remarks: 15412:820 EQUINIX PARIS remarks: 15412:821 EQUINIX HONG KONG remarks: ======================================================= remarks: 15412:9xx Upstream remarks: 15412:902 LEVEL3 AS3356<http://bgp.he.net/AS3356>remarks: 15412:903 NTT/VERIO AS2914 <http://bgp.he.net/AS2914> remarks: ======================================================= remarks: BGP Communities available to customers for traffic engineering remarks: ======================================================= remarks: Modify LocalPref remarks: remarks: 15412:80 = 80 remarks: 15412:200 = 200 (e.g. backup link) remarks: 15412:300 = 300 remarks: Default (Customer/Transit/Peer) = 250/100/100 remarks: ======================================================= remarks: Suppression/Prepend remarks: ======================================================= remarks: 15412:4100 Do not announce to any upstream remarks: ======================================================= remarks: 15412:4120 Do not announce to LEVEL3 AS3356 <http://bgp.he.net/AS3356> remarks: 15412:4121 Prepend 15412 to LEVEL3 AS3356 <http://bgp.he.net/AS3356>remarks: 15412:4122 Prepend 15412 15412 to LEVEL3 AS3356 <http://bgp.he.net/AS3356> remarks: ======================================================= remarks: 15412:4130 Do not announce to NTT/Verio AS2914 <http://bgp.he.net/AS2914> remarks: 15412:4131 Prepend 15412 to NTT/Verio AS2914 <http://bgp.he.net/AS2914>remarks: 15412:4132 Prepend 15412 15412 to NTT/Verio AS2914 <http://bgp.he.net/AS2914> remarks: ======================================================= remarks: 15412:4500 Do not announce to FLAG peers remarks: ======================================================= remarks: 15412:4510 Do not announce to PAIX Peers remarks: 15412:4511 Prepend 15412 to PAIX Peers remarks: 15412:4512 Prepend 15412 15412 to PAIX Peers remarks: ======================================================= remarks: 15412:4520 Do not announce to NYIIX Peers remarks: 15412:4521 Prepend 15412 to NYIIX Peers remarks: 15412:4522 Prepend 15412 15412 to NYIIX Peers remarks: ======================================================= remarks: 15412:4530 Do not announce to JPIX Peers remarks: 15412:4531 Prepend 15412 to JPIX Peers remarks: 15412:4532 Prepend 15412 15412 to JPIX Peers remarks: ======================================================= remarks: 15412:4540 Do not announce to KINX Peers remarks: 15412:4541 Prepend 15412 to KINX Peers remarks: 15412:4542 Prepend 15412 15412 to KINX Peers remarks: ======================================================= remarks: 15412:4550 Do not announce to HKIX Peers remarks: 15412:4551 Prepend 15412 to HKIX Peers remarks: 15412:4552 Prepend 15412 15412 to HKIX Peers remarks: ======================================================= remarks: 15412:4560 Do not announce to LINX Peers remarks: 15412:4561 Prepend 15412 to LINX Peers remarks: 15412:4562 Prepend 15412 15412 to LINX Peers remarks: ======================================================= remarks: 15412:4570 Do not announce to SFINX Peers remarks: 15412:4571 Prepend 15412 to SFINX Peers remarks: 15412:4572 Prepend 15412 15412 to SFINX Peers remarks: ======================================================= remarks: 15412:4580 Do not announce to LAIX Peers remarks: 15412:4581 Prepend 15412 to LAIX Peers remarks: 15412:4582 Prepend 15412 15412 to LAIX Peers remarks: ======================================================= remarks: 15412:4590 Do not announce to DECIX Peers remarks: 15412:4591 Prepend 15412 to DECIX Peers remarks: 15412:4592 Prepend 15412 15412 to DECIX Peers remarks: ======================================================= remarks: 15412:4600 Do not announce to AMSIX Peers remarks: 15412:4601 Prepend 15412 to AMSIX Peers remarks: 15412:4602 Prepend 15412 15412 to AMSIX Peers remarks: ======================================================= remarks: 15412:4610 Do not announce to EQUINIX ASHBURN peers remarks: 15412:4611 Prepend 15412 to EQUINIX ASHBURN peers remarks: 15412:4612 Prepend 15412 15412 to EQUINIX ASHBURN peers remarks: ======================================================= remarks: 15412:4620 Do not announce to JPNAP peers remarks: 15412:4621 Prepend 15412 to JPNAP peers remarks: 15412:4622 Prepend 15412 15412 to JPNAP peers remarks: ======================================================= remarks: 15412:4640 Do not announce to EQUINIX SINGAPORE peers remarks: 15412:4641 Prepend 15412 to EQUINIX SINGAPORE peers remarks: 15412:4642 Prepend 15412 15412 to EQUINIX SINGAPORE peers remarks: ======================================================= remarks: 15412:4660 Do not announce to EQUINIX TOKYO peers remarks: 15412:4661 Prepend 15412 to EQUINIX TOKYO peers remarks: 15412:4662 Prepend 15412 15412 to EQUINIX TOKYO peers remarks: ======================================================= remarks: 15412:4670 Do not announce to ANY2 peers remarks: 15412:4671 Prepend 15412 to ANY2 peers remarks: 15412:4672 Prepend 15412 15412 to ANY2 peers remarks: ======================================================= remarks: 15412:4700 Do not announce to EQUINIX PARIS peers remarks: 15412:4701 Prepend 15412 to EQUINIX PARIS peers remarks: 15412:4702 Prepend 15412 15412 to EQUINIX PARIS peers Hope that will help you. On Fri, Jan 13, 2012 at 8:27 PM, Philip Lavine <source_route@yahoo.com>wrote:
nail on the head. I need the XXXX:XXXX notation for the BGP preference. I need to be able to set a provider as a backup, for example: qwest would be 209:70
________________________________ From: Stefan Fouant <sfouant@shortestpathfirst.net> To: Matthew Petach <mpetach@netflight.com> Cc: Philip Lavine <source_route@yahoo.com>; "nanog@nanog.org" < nanog@nanog.org> Sent: Friday, January 13, 2012 6:41 AM Subject: Re: community strings for Reliance Globalcom
I could be wrong, but I think OP was requesting for BGP communities. I don't think he was asking for their SNMP community strings - I've never heard of a situation where a provider would allow their customers to poll their routers via SNMP.
Or did I miss something?
Stefan Fouant JNCIE-SEC, JNCIE-SP, JNCIE-ER, JNCI Technical Trainer, Juniper Networks
Follow us on Twitter @JuniperEducate
Sent from my iPad
On Jan 12, 2012, at 6:06 PM, Matthew Petach <mpetach@netflight.com> wrote:
On Thu, Jan 12, 2012 at 2:57 PM, Philip Lavine <source_route@yahoo.com> wrote:
does anybody have the community strings for Reliance Globalcom
You might check to see if they left the default "public" read-only string in place, but I highly doubt it. Most people are pretty careful to pick at least somewhat hard to guess community strings, and to ACL them off from external querying.
Matt
-- Anurag Bhatia anuragbhatia.com or simply - http://[2001:470:26:78f::5] if you are on IPv6 connected network! Twitter: @anurag_bhatia <https://twitter.com/#!/anurag_bhatia>
On Fri, Jan 13, 2012 at 6:41 AM, Stefan Fouant <sfouant@shortestpathfirst.net> wrote:
I could be wrong, but I think OP was requesting for BGP communities. I don't think he was asking for their SNMP community strings - I've never heard of a situation where a provider would allow their customers to poll their routers via SNMP.
Or did I miss something?
Sorry--I was knee-deep in digging through IPv6 OIDs, so my brain was all awash with SNMP community strings when I saw the post. You're right, in retrospect BGP communities made more sense. Apologies for the confusion. Matt
Stefan Fouant JNCIE-SEC, JNCIE-SP, JNCIE-ER, JNCI Technical Trainer, Juniper Networks
Follow us on Twitter @JuniperEducate
Sent from my iPad
On Jan 12, 2012, at 6:06 PM, Matthew Petach <mpetach@netflight.com> wrote:
On Thu, Jan 12, 2012 at 2:57 PM, Philip Lavine <source_route@yahoo.com> wrote:
does anybody have the community strings for Reliance Globalcom
You might check to see if they left the default "public" read-only string in place, but I highly doubt it. Most people are pretty careful to pick at least somewhat hard to guess community strings, and to ACL them off from external querying.
Matt
Not sure how up to date this is, but I believe this is what you are looking for: http://www.onesc.net/communities/as15412/ Cheers, Stefan Fouant JNCIE-SEC, JNCIE-SP, JNCIE-ER, JNCI Technical Trainer, Juniper Networks Follow us on Twitter @JuniperEducate Sent from my iPad On Jan 12, 2012, at 5:57 PM, Philip Lavine <source_route@yahoo.com> wrote:
does anybody have the community strings for Reliance Globalcom
participants (4)
-
Anurag Bhatia -
Matthew Petach -
Philip Lavine -
Stefan Fouant