- Test - lists.nanog.org

Atlanta - Patch Cables
by Bobby Lacey 25 Feb '14

25 Feb '14

In Atlanta doing an install for a client this weekend and it appears that the fiber/ethernet patch cables won't be delivered in time from supplier. Would anyone know of a good resource for patch cables (both fiber and ethernet) in the metro area? Just wondering if there are any other resources for these? Frys? Offlist please. Thank you! Bobby

2 1

Re: out of band management gear
by Larry Sheldon 25 Feb '14

25 Feb '14

On 2/24/2014 7:59 AM, Vinny_Abello(a)Dell.com wrote: > Dell - Internal Use - Confidential You sent me this by mistake. I have deleted all of the instances of it that know of. Why does the NANOG forwarder forward these things? -- Requiescas in pace o email Two identifying characteristics of System Administrators: Ex turpi causa non oritur actio Infallibility, and the ability to learn from their mistakes. (Adapted from Stephen Pinker)

1 0

Miami Dade County Public School VPN
by Mario Eirea 24 Feb '14

24 Feb '14

Will someone in MDCPS ITS please contact me off list regarding serious VPN disconnection issues that have been plaguing us for the past week? Thank you, Mario Eirea IT Department Layer 8 Solutions 7701 W 26th Ave Unit 2 Hialeah, FL 33016-5603 25.892545°, -80.335783° U.S.A., Earth , Solar System, Milky Way, Local Group, Universe [https://charterschoolit.com/1up_micro.png] [http://charterschoolit.com/layer8_micro.png]

1 0

The somewhat illegal fix for NTP attacks
by Baldur Norddahl 24 Feb '14

24 Feb '14

Hi The following would probably be illegal so do not actually do this. But what if... there are just 4 billion IPv4 addresses. Scanning that address-space for open NTP is trivially done in a few hours. Abusing these servers for reflection attack is as trivial, hence the problem. How can we get the responsible parties to fix their NTP servers? Answer: DDoS them. With their own service. Or it could be a DDoS defense. As a victim of an ongoing NTP reflection attack, you know exactly the IP-addresses of the vulnerable NTP servers used to attack you. Make them stop by sending back forged NTP packets, so they use up their available bandwidth to DDoS each other instead of you. This could even be automated. If you let them attack their next-hop as discovered by traceroute, it might not even be illegal or harmful. They will only bring down their own link, do no more harm to the internet at large and they can fix it by stopping the NTP service. If they are part of an ongoing DDoS attack it is just self defence to shut them down in the least harmful way possible. Regards, Baldur

6 5

out of band management gear
by Hank Disuko 24 Feb '14

24 Feb '14

Hi folks, I wonder if anyone has good experiences to share with out-of-band hardware? I'm looking for a good OOB hardware vendor. I need to manage my routers/switches/firewalls in a datacenter located overseas, and I'm looking to setup a good serial console server via an OOB link. I've been looking at Lantronix, OpenGear, Raritan...but they all seem to have the same basic features. I'm having trouble really differentiating them. I'm interested in analog modem, cellular options for my OOB link. Or even a secondary internet circuit either wired or wifi if the DC has that option available. Any good suggestions or experiences with a current OOB solution out there? What are you doing for your OOB management? thanks,Hank

17 17

Re: Filter NTP traffic by packet size?
by Brandon Butterworth 24 Feb '14

24 Feb '14

> > What is the business model for the IX? Unauthorized filtering of > > incoming traffic risks collateral damage and outing exchange members > > seems problematic. > > I never proposed for them to filter. What is missing is filtering at IXP not by IXP. Most transits have blackhole communities so you can drop the DoS through them but peers usually do not. You end up shutting peering so your transit will drop it for you, not ideal. We could agree per peer to do the same but with route servers and lots of peers a standard for community and acceptance of it would be handy. Obviously there is risk in doing this with (lots of) peers as they tend to be prefix limited, not address filtered. brandon

1 0

RE: Filter NTP traffic by packet size?
by Phil Bedard 23 Feb '14

23 Feb '14

On Sun, 23 Feb 2014, Chris Laffin wrote: > Ive talked to some major peering exchanges and they refuse to take any action. Possibly if the requests come from many peering participants it will be taken more seriously? If only there was more focus on the BCP38 offenders who are the real root cause of this problem, I would be more happy. I would be more impressed if the IXes would start to use their sFlow capabilities to find out what IX ports the NTP queries are coming to backtrace the traffic to the BCP38 offendors than try to block the NTP packets resulting from these src address forged queries. -- Mikael Abrahamsson email: swmike(a)swm.pp.se

1 0

[5350-5470 MHz]
by bmanning＠vacation.karoshi.com 23 Feb '14

23 Feb '14

if you have comments or feedback.... ----- Forwarded message from "Julie N" ----- Date: Wed, 19 Feb 2014 21:34:51 +0000 Subject: 5350-5470 MHz Dear Members, As you know, we have been actively engaged in the International Telecommunication Union's (ITU) Joint Task Group (JTG) studies to consider additional spectrum allocations to the mobile service for terrestrial mobile broadband applications and identification of frequency bands for International Mobile Telecommunications (IMT) at the 2015 World Radiocommunication Conference (WRC-15). The United States is currently considering 5350-5470 MHz for Unlicensed National Information Infrastructure (U-NII) devices radio local area networks (RLANs). We are working with NTIA, FCC, federal agencies and industry to ensure that the necessary analyses are completed and interference avoidance or mitigation techniques are developed and demonstrated in time to resolve concerns and to develop international support for a U.S. position. I am attaching a letter from Ambassador Sepulveda containing important information about this band and our commitment to working with you to mobilize spectrum for wireless broadband. I look forward to working with you on this and many other important WRC-15 issues. Best regards, Julie This email is UNCLASSIFIED. ----- End forwarded message -----

1 0

Gmail throttling?
by Eduardo A. Suárez 22 Feb '14

22 Feb '14

Hi, some of our users have forwarded the email to Gmail and Gmail now are complaining that this is bulk mail and delaying it. We have SPF, DKIM, DMARC, even SRS to try these things do not happen :( Anyone know if there is any new policy in Gmail about that? Above all, the message refers to a non-existent URI! >>> RSET 250 2.1.5 Flushed v69si8136768yhd.33 - gsmtp <xxxx(a)gmail.com>... Using cached ESMTP connection to gmail-smtp-in.l.google.com. via esmtp... >>> MAIL From:<xxx(a)example.com> SIZE=150374 BODY=8BITMIME 250 2.1.0 OK v69si8136768yhd.33 - gsmtp >>> RCPT To:<xxxx(a)gmail.com> >>> DATA 250 2.1.5 OK v69si8136768yhd.33 - gsmtp 354 Go ahead v69si8136768yhd.33 - gsmtp >>> . 421-4.7.0 [163.10.4.2 15] Our system has detected an unusual rate of 421-4.7.0 unsolicited mail originating from your IP address. To protect our 421-4.7.0 users from spam, mail sent from your IP address has been temporarily 421-4.7.0 rate limited. Please visit http://www.google.com/mail/help/bulk_mail. 421 4.7.0 html to review our Bulk Email Senders Guidelines. v69si8136768yhd.33 - gsmtp >>> QUIT Eduardo.- -- Eduardo A. Suarez Facultad de Ciencias Astronómicas y Geofísicas - UNLP FCAG: (0221)-4236593 int. 172/Cel: (0221)-15-4557542/Casa: (0221)-4526589 ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

5 4

NANOG 61 - Bellevue - Call For Presentations is open!
by Greg Dendy 22 Feb '14

22 Feb '14

NANOG Community- I hope everyone enjoyed NANOG 60, NANOG’s largest attended winter meeting. Fresh off a great meeting, and post our NANOG Icelanta Reception, we are ready start the process for NANOG 61 in Bellevue. NANOG 61 will be NANOG’s 20th year serving the network operator community and helping to make the Internet better. If you have a topic you'd like to speak about, the program committee would love to consider it. Please read http://www.nanog.org/meetings/nanog61/callforpresentations for more information. We will continue with the Monday-Wednesday format, with Tracks on Monday and Wednesday afternoons and Tutorials to be scheduled on Tuesday morning. The program will begin on Monday morning at 10:00AM followed by our popular Newcomers Lunch. The exact schedule layout can be found at http://www.nanog.org/meetings/nanog60/preagenda, please take this into account as you plan travel. If you wish to submit a presentation, please keep these important dates in mind: * Presentation Abstracts and Draft Slides Due: April 7, 2014 * Slides Due: May 5, 2014 * Topic List Posted: April 21, 2014 * Agenda Published: May 12, 2014 Please submit your materials to http://pc.nanog.org<http://pc.nanog.org/>. Looking forward to seeing everyone in Bellevue! Thanks, Greg Dendy Chair, NANOG Program Committee

1 0