Mexico

[Mehmet Akcin]

Hey there

I am looking for transit provider(s) who are small and connected networks
in Mexico city/Querétaro

Please contact me offlist if you can provide this service.

Mehmet
-- 
Mehmet
+1-424-298-1903

RE: Mexico

[Naslund, Steve]

You might want to check with a company called Transtelco.  They are an 
alternate fiber provider (outside of Telmex).

Steven Naslund
Chicago IL

From: NANOG  On Behalf Of Mehmet Akcin
Sent: Thursday, May 30, 2019 9:20 AM
To: nanog 
Subject: Mexico

Hi there

I am looking for dark fibre in several markets in México and waves from mexico 
city to LA and Dallas.

If you know someone in wholesale who can help, please contact me offlist

Thank you.

Mehmet
--
Mehmet
+1-424-298-1903

Mexico

[Mehmet Akcin]

Hi there

I am looking for dark fibre in several markets in México and waves from
mexico city to LA and Dallas.

If you know someone in wholesale who can help, please contact me offlist

Thank you.

Mehmet
-- 
Mehmet
+1-424-298-1903

USA to Mexico IXP Equipment Recommendations

[NJ]

Advice and/or suggestions wanted. Any input greatly appreciated.

*Scenario:*
We have run fiber from the USA to Mexico and have an exchange point in
place. Our fiber connections are dark and therefore we can use any
configuration we want on as many pairs as we want. Currently we have decided
to light two 100gig connections and they are piping across the border
already. We have 200gig going to Los Angeles (Wilshire Adjacent) and
are looking to the mexico interested community of network engineers to
identify how our peering point in Tijuana can be made to best service
the networks in the region (and abroad if they build in). Our IXP is
good, but we want to update/upgrade and put in a future-compatible
robust solution instead of what we have in there now. We are an open
IXP and are wondering how you would prefer to peer and what your
equipment recommendations are and why.  We're not afraid to spend
(some) money but we do want it to not be complete overkill however
should last at least 5 to 10 years before any upgrade would be
required. Also to note, we are running our own bandwidth over the
pipes as well so we would like to keep them separated.


*Norm*
A.A.S. R.A. Lifetime Member
*Archaeology, Astronautics and SETI Research Association*
SETI Project Lifetime Contributor

RE: Protocol 17 floods from Vietnam & Mexico?

[Matthew Smee]

Protocol 17 likely refers to UDP.

https://en.wikipedia.org/wiki/List_of_IP_protocol_numbers


-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Large Hadron Collider
Sent: Wednesday, 13 September 2017 11:08 AM
To: nanog@nanog.org
Subject: Protocol 17 floods from Vietnam & Mexico?

18:04:32.391082 IP 138-122-97-251.internet.static.ientc.mx >
umbrellix.net: ip-proto-17
18:04:32.391088 IP 138-122-97-251.internet.static.ientc.mx >
umbrellix.net: ip-proto-17
18:04:32.391110 IP 115.75.50.106.35180 > umbrellix.net.10454: UDP, bad length 
65500 > 1464
18:04:32.391145 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391152 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391158 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391164 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391170 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391176 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391182 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391188 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391194 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391199 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391205 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391211 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391217 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391223 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391229 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391234 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391248 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391255 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391261 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391266 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391272 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391278 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391284 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391289 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391295 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391313 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391319 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391325 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391331 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391336 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391342 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391348 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391354 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391367 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391374 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391379 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391385 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391391 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391396 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391402 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391408 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391414 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391420 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391426 IP 115.75.50.106 > umbrellix.net: ip-proto-17

Some stupidity has me wondering... protocol 17? Huh?


Is this some attempt to exploit me while at the same time flooding me at over 
800Mbit/s?


Needless to say, I've shut my computer down to avoid going over my data 
allowance.

Re: Protocol 17 floods from Vietnam & Mexico?

[i mawsog via NANOG]

The port info is in the first  fragmented packet as was mentioned elsewhere.  
My guess is someone fragmenting large packets ( the mtu is set to  1464 or so). 
and  the host is receiving those fragment, but it not  reconstructing the 
packets.  If  it is possible to do a tcpdump/wireshark etc , then the content 
of the packets can be very easily observed .  
18:04:32.391082 IP 138-122-97-251.internet.static.ientc.mx > 
umbrellix.net: ip-proto-17
18:04:32.391088 IP 138-122-97-251.internet.static.ientc.mx > 
umbrellix.net: ip-proto-17
18:04:32.391110 IP 115.75.50.106.35180 > umbrellix.net.10454: UDP, bad 
length 65500 > 1464
18:04:32.391145 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391152 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391158 IP 115.75.50.106 > umbrellix.net: ip-proto-17



  From: Christopher Morrow <morrowc.li...@gmail.com>
 To: Krunal Shah <ks...@primustel.ca> 
Cc: "nanog@nanog.org" <nanog@nanog.org>
 Sent: Wednesday, September 13, 2017 7:59 AM
 Subject: Re: Protocol 17 floods from Vietnam & Mexico?
   
On Wed, Sep 13, 2017 at 9:59 AM, Krunal Shah <ks...@primustel.ca> wrote:

> It might be spoofed source IPs
>
>
if you are seeing large fragmented udp packets.. it's almost always not
spoofed.
or historically speaking anyway it's not been spoofed.

There are cases with dns reflection that include spoofing, but by the time
you see the large packet .. that's not spoofed it's coming from the dns
server talking to you, why it's talking to you is due to spoofing, but
that's outside (most times) your span of control.


>
> Krunal Shah
>
>
>
>
>
>
> -Original Message-
> From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Mark Andrews
> Sent: Tuesday, September 12, 2017 10:45 PM
> To: Large Hadron Collider
> Cc: nanog@nanog.org
> Subject: Re: Protocol 17 floods from Vietnam & Mexico?
>
>
> In message <08ed2903-c81c-aa2e-cd04-4fa117840...@gmx.com>, Large Hadron
> Collider writes:
> > Yes, I'm being UDP flooded. I worked that out by grepping /etc/protocols.
> >
> >
> > On 12/09/2017 18:24, Matt Harris wrote:
> > > Protocol 17 is UDP.  UDP is pretty common on the internet. Not sure
> > > why source and destination ports aren't being shown by your tool
> > > there, might be malformed UDP packets designed to obscure themselves
> > > from or otherwise evade some intrusion detection or firewall systems.
>
> No ports are listed because they are not the initial fragment of the UDP
> packet.  Only the initial fragment that contains the UDP header has the
> ports reported.
>
> Mark
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                INTERNET: ma...@isc.org
>
>
>
> 
> This electronic message contains information from Primus Management ULC
> ("PRIMUS") , which may be legally privileged and confidential. The
> information is intended to be for the use of the individual(s) or entity
> named above. If you are not the intended recipient, be aware that any
> disclosure, copying, distribution or use of the contents of this
> information is prohibited. If you have received this electronic message in
> error, please notify us by telephone or e-mail (to the number or address
> above) immediately. Any views, opinions or advice expressed in this
> electronic message are not necessarily the views, opinions or advice of
> PRIMUS. It is the responsibility of the recipient to ensure that any
> attachments are virus free and PRIMUS bears no responsibility for any loss
> or damage arising in any way from the use thereof.The term "PRIMUS"
> includes its affiliates.
> 
> Pour la version en français de ce message, veuillez voir
> http://www.primustel.ca/fr/legal/cs.htm
>
>

   

Re: Protocol 17 floods from Vietnam & Mexico?

[Christopher Morrow]

On Wed, Sep 13, 2017 at 9:59 AM, Krunal Shah <ks...@primustel.ca> wrote:

> It might be spoofed source IPs
>
>
if you are seeing large fragmented udp packets.. it's almost always not
spoofed.
or historically speaking anyway it's not been spoofed.

There are cases with dns reflection that include spoofing, but by the time
you see the large packet .. that's not spoofed it's coming from the dns
server talking to you, why it's talking to you is due to spoofing, but
that's outside (most times) your span of control.


>
> Krunal Shah
>
>
>
>
>
>
> -Original Message-
> From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Mark Andrews
> Sent: Tuesday, September 12, 2017 10:45 PM
> To: Large Hadron Collider
> Cc: nanog@nanog.org
> Subject: Re: Protocol 17 floods from Vietnam & Mexico?
>
>
> In message <08ed2903-c81c-aa2e-cd04-4fa117840...@gmx.com>, Large Hadron
> Collider writes:
> > Yes, I'm being UDP flooded. I worked that out by grepping /etc/protocols.
> >
> >
> > On 12/09/2017 18:24, Matt Harris wrote:
> > > Protocol 17 is UDP.  UDP is pretty common on the internet. Not sure
> > > why source and destination ports aren't being shown by your tool
> > > there, might be malformed UDP packets designed to obscure themselves
> > > from or otherwise evade some intrusion detection or firewall systems.
>
> No ports are listed because they are not the initial fragment of the UDP
> packet.  Only the initial fragment that contains the UDP header has the
> ports reported.
>
> Mark
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
>
>
>
> 
> This electronic message contains information from Primus Management ULC
> ("PRIMUS") , which may be legally privileged and confidential. The
> information is intended to be for the use of the individual(s) or entity
> named above. If you are not the intended recipient, be aware that any
> disclosure, copying, distribution or use of the contents of this
> information is prohibited. If you have received this electronic message in
> error, please notify us by telephone or e-mail (to the number or address
> above) immediately. Any views, opinions or advice expressed in this
> electronic message are not necessarily the views, opinions or advice of
> PRIMUS. It is the responsibility of the recipient to ensure that any
> attachments are virus free and PRIMUS bears no responsibility for any loss
> or damage arising in any way from the use thereof.The term "PRIMUS"
> includes its affiliates.
> 
> Pour la version en français de ce message, veuillez voir
> http://www.primustel.ca/fr/legal/cs.htm
>
>

RE: Protocol 17 floods from Vietnam & Mexico?

[Krunal Shah]

It might be spoofed source IPs


Krunal Shah






-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Mark Andrews
Sent: Tuesday, September 12, 2017 10:45 PM
To: Large Hadron Collider
Cc: nanog@nanog.org
Subject: Re: Protocol 17 floods from Vietnam & Mexico?


In message <08ed2903-c81c-aa2e-cd04-4fa117840...@gmx.com>, Large Hadron 
Collider writes:
> Yes, I'm being UDP flooded. I worked that out by grepping /etc/protocols.
>
>
> On 12/09/2017 18:24, Matt Harris wrote:
> > Protocol 17 is UDP.  UDP is pretty common on the internet. Not sure
> > why source and destination ports aren't being shown by your tool
> > there, might be malformed UDP packets designed to obscure themselves
> > from or otherwise evade some intrusion detection or firewall systems.

No ports are listed because they are not the initial fragment of the UDP 
packet.  Only the initial fragment that contains the UDP header has the ports 
reported.

Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org




This electronic message contains information from Primus Management ULC 
("PRIMUS") , which may be legally privileged and confidential. The information 
is intended to be for the use of the individual(s) or entity named above. If 
you are not the intended recipient, be aware that any disclosure, copying, 
distribution or use of the contents of this information is prohibited. If you 
have received this electronic message in error, please notify us by telephone 
or e-mail (to the number or address above) immediately. Any views, opinions or 
advice expressed in this electronic message are not necessarily the views, 
opinions or advice of PRIMUS. It is the responsibility of the recipient to 
ensure that any attachments are virus free and PRIMUS bears no responsibility 
for any loss or damage arising in any way from the use thereof.The term 
"PRIMUS" includes its affiliates.

Pour la version en français de ce message, veuillez voir
http://www.primustel.ca/fr/legal/cs.htm

Re: Protocol 17 floods from Vietnam & Mexico?

[Mark Andrews]

In message <08ed2903-c81c-aa2e-cd04-4fa117840...@gmx.com>, Large Hadron 
Collider writes:
> Yes, I'm being UDP flooded. I worked that out by grepping /etc/protocols.
> 
> 
> On 12/09/2017 18:24, Matt Harris wrote:
> > Protocol 17 is UDP.  UDP is pretty common on the internet. Not sure 
> > why source and destination ports aren't being shown by your tool 
> > there, might be malformed UDP packets designed to obscure themselves 
> > from or otherwise evade some intrusion detection or firewall systems.

No ports are listed because they are not the initial fragment of
the UDP packet.  Only the initial fragment that contains the UDP
header has the ports reported.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org

Re: Protocol 17 floods from Vietnam & Mexico?

[Large Hadron Collider]

Yes, I'm being UDP flooded. I worked that out by grepping /etc/protocols.


On 12/09/2017 18:24, Matt Harris wrote:
Protocol 17 is UDP.  UDP is pretty common on the internet. Not sure 
why source and destination ports aren't being shown by your tool 
there, might be malformed UDP packets designed to obscure themselves 
from or otherwise evade some intrusion detection or firewall systems.



On Tue, Sep 12, 2017 at 8:08 PM, Large Hadron Collider 
> 
wrote:


18:04:32.391082 IP 138-122-97-251.internet.static.ientc.mx
 > umbrellix.net
: ip-proto-17
18:04:32.391088 IP 138-122-97-251.internet.static.ientc.mx
 > umbrellix.net
: ip-proto-17
18:04:32.391110 IP 115.75.50.106.35180 > umbrellix.net.10454: UDP,
bad length 65500 > 1464
18:04:32.391145 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391152 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391158 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391164 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391170 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391176 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391182 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391188 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391194 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391199 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391205 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391211 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391217 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391223 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391229 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391234 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391248 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391255 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391261 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391266 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391272 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391278 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391284 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391289 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391295 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391313 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391319 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391325 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391331 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391336 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391342 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391348 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391354 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391367 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391374 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391379 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391385 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391391 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391396 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391402 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391408 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391414 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391420 IP 115.75.50.106 > umbrellix.net
: ip-proto-17
18:04:32.391426 IP 

Re: Protocol 17 floods from Vietnam & Mexico?

[Mark Andrews]

Protocol 17 == UDP.  These are just very big (65500 byte) UDP packets
which have been fragmented.  Somebody need to teach that packet
analyser that UDP packets can be this big over IPv4 and bigger still
if you are using IPv6 jumbo packets.

Mark

In message <1bf07b56-f71c-1fec-bfd2-386a67c2b...@gmx.com>, Large Hadron 
Collider writes:
> 18:04:32.391082 IP 138-122-97-251.internet.static.ientc.mx > 
> umbrellix.net: ip-proto-17
> 18:04:32.391088 IP 138-122-97-251.internet.static.ientc.mx > 
> umbrellix.net: ip-proto-17
> 18:04:32.391110 IP 115.75.50.106.35180 > umbrellix.net.10454: UDP, bad 
> length 65500 > 1464
> 18:04:32.391145 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391152 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391158 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391164 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391170 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391176 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391182 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391188 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391194 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391199 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391205 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391211 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391217 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391223 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391229 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391234 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391248 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391255 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391261 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391266 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391272 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391278 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391284 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391289 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391295 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391313 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391319 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391325 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391331 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391336 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391342 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391348 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391354 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391367 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391374 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391379 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391385 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391391 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391396 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391402 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391408 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391414 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391420 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 18:04:32.391426 IP 115.75.50.106 > umbrellix.net: ip-proto-17
> 
> Some stupidity has me wondering... protocol 17? Huh?
> 
> 
> Is this some attempt to exploit me while at the same time flooding me at 
> over 800Mbit/s?
> 
> 
> Needless to say, I've shut my computer down to avoid going over my data 
> allowance.
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org

Protocol 17 floods from Vietnam & Mexico?

[Large Hadron Collider]

18:04:32.391082 IP 138-122-97-251.internet.static.ientc.mx > 
umbrellix.net: ip-proto-17
18:04:32.391088 IP 138-122-97-251.internet.static.ientc.mx > 
umbrellix.net: ip-proto-17
18:04:32.391110 IP 115.75.50.106.35180 > umbrellix.net.10454: UDP, bad 
length 65500 > 1464

18:04:32.391145 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391152 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391158 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391164 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391170 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391176 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391182 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391188 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391194 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391199 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391205 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391211 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391217 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391223 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391229 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391234 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391248 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391255 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391261 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391266 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391272 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391278 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391284 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391289 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391295 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391313 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391319 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391325 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391331 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391336 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391342 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391348 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391354 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391367 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391374 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391379 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391385 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391391 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391396 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391402 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391408 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391414 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391420 IP 115.75.50.106 > umbrellix.net: ip-proto-17
18:04:32.391426 IP 115.75.50.106 > umbrellix.net: ip-proto-17

Some stupidity has me wondering... protocol 17? Huh?


Is this some attempt to exploit me while at the same time flooding me at 
over 800Mbit/s?



Needless to say, I've shut my computer down to avoid going over my data 
allowance.

dedicated server providers in Mexico?

[Carlos Kamtha]

Hi everyone, 

I am currently not happy with out MX server provider, and so, inquiring 
with anyone that can give a recommendation based on experience? 

I found this list via google. 

http://www.webhostingsearch.com/dedicated-server/mexico.php

I wondering if anyone can speak to any of the providers on this list
(outside of 1n1). offlist..

Feedback as always greatly appreciated. 

Cheers, 

Carlos. 

Re: dedicated server providers in Mexico?

[Jason Canady]

I have no experience with dedicated hosting providers in Mexico, but 
that list is incorrect.  I know that Steadfast does not have servers 
located in Mexico.  I believe other providers are also incorrectly listed.


You should search for providers on Web Hosting Talk, 
http://www.webhostingtalk.com


Regards,

Jason

On 4/29/14, 2:06 PM, Carlos Kamtha wrote:

Hi everyone,

I am currently not happy with out MX server provider, and so, inquiring
with anyone that can give a recommendation based on experience?

I found this list via google.

http://www.webhostingsearch.com/dedicated-server/mexico.php

I wondering if anyone can speak to any of the providers on this list
(outside of 1n1). offlist..

Feedback as always greatly appreciated.

Cheers,

Carlos.

Re: dedicated server providers in Mexico?

[Paul Norton]

RedIT

--
Paul Norton


Carlos Kamtha wrote:

Hi everyone,

I am currently not happy with out MX server provider, and so, inquiring
with anyone that can give a recommendation based on experience?

I found this list via google.

http://www.webhostingsearch.com/dedicated-server/mexico.php

I wondering if anyone can speak to any of the providers on this list
(outside of 1n1). offlist..

Feedback as always greatly appreciated.

Cheers,

Carlos.

Contacts at ISPs in Mexico?

[Anne P. Mitchell, Esq.]

Are there any Mexico ISPs on the list or does anybody here have any contacts at 
any Mexican ISPs?

Thank you,

Anne

Anne P. Mitchell, Attorney at Law
Author: Section 6 of the CAN-SPAM Act of 2003
CEO/President: Institute for Social Internet Public Policy
Providers: SuretyMail Email Accreditation
Member: California Bar Cyberspace Law Committee

Re: Contacts at ISPs in Mexico?

[James Bensley]

You might have better luck asking at LACNOG;
https://mail.lacnic.net/mailman/listinfo/lacnog


Cheers,
James.

Re: Brasil/Mexico/Argentina connectivity

[Eduardo Casarero]

El jueves, 15 de noviembre de 2012 01:05:37 p.m., Jima escribió:

On Wednesday, November 14th, 2012, Olivier CALVANO wrote:

I am search one or more carrier for connect 3 sites in Brasil, Mexico
and Argentina to one of our pop
in USA or Spain.


  I don't deal with it directly, but my employer has used MPLS offerings
from (in alphabetical order) BT, Level 3/Global Crossing, and Verizon in
a number of countries.  I suspect any of the three have access in all of
the countries listed.  I imagine there are others, but those are the ones
that sprung to mind.

  Jima




I think Level3 is your best, as L3 bought Globalcrossing. Here in 
Argentina L3 has heavy weight in the carriers market, also in Brazil. 
What i dont know is in Mexico.

Re: Brasil/Mexico/Argentina connectivity

[Jima]

On Wednesday, November 14th, 2012, Olivier CALVANO wrote:
 I am search one or more carrier for connect 3 sites in Brasil, Mexico
 and Argentina to one of our pop
 in USA or Spain.

 I don't deal with it directly, but my employer has used MPLS offerings
from (in alphabetical order) BT, Level 3/Global Crossing, and Verizon in
a number of countries.  I suspect any of the three have access in all of
the countries listed.  I imagine there are others, but those are the ones
that sprung to mind.

 Jima

Re: Brasil/Mexico/Argentina connectivity

[alejandroacostaalamo]

Hi Jima,
   I can help you contacting BT if you need so.

Alejandro,



--Mensaje original--
De: Jima
Para: nanog@nanog.org
Asunto: Re: Brasil/Mexico/Argentina connectivity
Enviado: 15 nov, 2012 11:35

On Wednesday, November 14th, 2012, Olivier CALVANO wrote:
 I am search one or more carrier for connect 3 sites in Brasil, Mexico
 and Argentina to one of our pop
 in USA or Spain.

 I don't deal with it directly, but my employer has used MPLS offerings
from (in alphabetical order) BT, Level 3/Global Crossing, and Verizon in
a number of countries.  I suspect any of the three have access in all of
the countries listed.  I imagine there are others, but those are the ones
that sprung to mind.

 Jima




Este mensaje ha sido enviado gracias al servicio BlackBerry de Movilnet

Brasil/Mexico/Argentina connectivity

[Olivier CALVANO]

Hi

I am search one or more carrier for connect 3 sites in Brasil, Mexico
and Argentina to one of our pop
in USA or Spain.

if you have a name and contact ;=)

best regards
Olivier

Mexico City IP/Ethernet/Wave/Fiber/Colo/IXP etc...

[Tim Durack]

I'm looking for connectivity options in the Mexico City area. Initial
impressions suggest Mexico has a fairly closed market. That being
said:
Who offers good IP/BGP connectivity in and around Mexico City?Who
offers good Ethernet connectivity in and around Mexico City?Who offers
wave/fiber services in and around Mexico City.Where are the colo/IXPs
located?
Feedback on or off-list appreciated. I'm not looking for a salesman.
Thanks,
-- 
Tim:

Re: Mexico?

[Bradley Huffaker]

LACNIC http://lacnic.net/en/index.html

On Thu, Oct 27, 2011 at 11:24:54PM -0400, Ryan Finnesey wrote:
 If I want to get a block of IP's issued for a network within Mexico who do I
 talk with?  I have been told arin does not cover Mexico.  It was my
 understand arin covers North America.
 
  
 
 Cheers
 
 Ryan
 
  

-- 
true liberty is the right to be wrong

Re: Mexico?

[Carlos Martinez-Cagnazzo]

Mexico-based networks get their IP blocks (v4 and v6) from NIC Mexico
(http://www.nic.mx). NIC Mexico and NIC Brasil are the two NIRs within
LACNIC's service area.

regards

Carlos


On Fri, Oct 28, 2011 at 1:24 AM, Ryan Finnesey rfinne...@gmail.com wrote:
 If I want to get a block of IP's issued for a network within Mexico who do I
 talk with?  I have been told arin does not cover Mexico.  It was my
 understand arin covers North America.



 Cheers

 Ryan







-- 
--
=
Carlos M. Martinez-Cagnazzo
http://www.labs.lacnic.net
=

Mexico?

[Ryan Finnesey]

If I want to get a block of IP's issued for a network within Mexico who do I
talk with?  I have been told arin does not cover Mexico.  It was my
understand arin covers North America.

 

Cheers

Ryan

 

Re: Mexico?

[John Curran]

On Oct 28, 2011, at 3:24 AM, Ryan Finnesey wrote:

 If I want to get a block of IP's issued for a network within Mexico who do I
 talk with?  I have been told arin does not cover Mexico.  It was my
 understand arin covers North America.

Hi Ryan - 
   
  ARIN used to cover the entire global minus the RIPE NCC and 
  APNIC regions. When LACNIC was formed, it made sense to have
  ARIN handle Canada and US from NA, and have LACNIC handle Mexico.

  Look into www.lacnic.net and also www.nic.mx (NIC Mexico)

Thanks!
/John

John Curran
President and CEO
ARIN

Re: Mexico?

[Joel jaeggli]

On 10/27/11 20:24 , Ryan Finnesey wrote:
 If I want to get a block of IP's issued for a network within Mexico who do I
 talk with?  I have been told arin does not cover Mexico.  It was my
 understand arin covers North America.

mexico moved to the lacnic region with the formation of the lacnic rir.
NIC mexico was deeply involved if not instrumental in the formation of
lacnic.




  
 
 Cheers
 
 Ryan
 
  
 

Re: Mexico?

[Daniel Espejel]

Hi Ryan...well, a late response, but actually you should take a look in
the www.lacnic.net (Latin-america's RIR) and www.nic.mx (Network
Information Center of Mexico) webpages and contact someone there to
get all the information you need in order to obtain a IP addresses block.
Regards



 If I want to get a block of IP's issued for a network within Mexico who do I
 talk with?  I have been told arin does not cover Mexico.  It was my
 understand arin covers North America.



-- 
Daniel Espejel Pérez
Técnico Académico
D.G.T.I.C. - U.N.A.M.
GT-IPv6 CLARA / GT-IPv6 U.N.A.M.