March 2014 - Test - lists.nanog.org

Re: L6-20P -> L6-30R
by Larry Sheldon 19 Mar '14

19 Mar '14

On 3/19/2014 7:00 AM, Alex Rubenstein wrote: >>> Go look at any standard household lamp. It has a 5-15P on the end of >>> it, which could be plugged into an outlet rated for 20 amps (5-20R), >>> with 16 gauge lamp cord rated for 10 amps or less. >> >> Mine all seem to be NEMA 1-15P, some (most?) with 18 AWG wire. >> >> Have I been shortchanged? :) > > I wrote that too fast, you are absolutely right. > > But my point remains. Appliance/load wire size is often, and many times smaller than the ampacity of the circuit. > > Heck, how many times have you plugged in a 14 gauge extension cord to a 5-20R? I believe the thinking behind the standards is that the breaker is sized to protect the wiring to the receptacle or fixture. After that you are on your own. It is always safe to demand less current than the circuit is designed to provide. It is never save to deform connectors. Changing a receptacle to one of a lower capacity is safe, if confusing to those who follow you. If I operated a facility I would offer short adapters cords rather that changing the receptacle. > > > > -- 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

Customer Support Ticketing
by Paul Stewart 19 Mar '14

19 Mar '14

Hey folks…. We need a new customer ticketing system and I’m looking for input. I am still working on a scope document on everything we want to do with the new system. The most common problem I run across is that a system is either built for enterprise internal IT helpdesk or it is built like a CRM sales tracking system. We are an ISP among other things and are looking for a powerful and yet reasonable cost system to answer email inquiries, allow customers to open tickets via portal, mobile support, escalation/SLA support, and several other things. Solarwinds NPM integration would be a huge bonus but not a deal breaker. If anyone has a system that they have integrated with Ivue from NISC (our billing platform) I would be really interested in hearing more as well. So my question is meant high level. For those folks that are ISP’s supporting business customers (including managed customers) along with residential eyeball traffic what system(s) do you use and what do you like/dislike? I’ve looked so far at WHD (Solarwinds product), OTRS, RT, RemedyForce, ZenDesk, HappyFox, Kayako and several others. All of them so far would require a fair amount of configuration or modifications based on our still developing wish list. Also worth noting is that we have no full time development staff so hoping to find something that has a lot of promise and then work with the vendor to evolve it into what we feel we need. **This is not an invitation for sales folks to call on me** Thanks, Paul

11 10

Fusion Splicer
by Pui Edylie 19 Mar '14

19 Mar '14

Dear Member, Anyone can recommend a reliable and "affordable" fusion splicer please? Thanks!

4 4

Zabbix Template for Cisco 7606
by Shahab Vahabzadeh 19 Mar '14

19 Mar '14

Hi everybody, Any body has template for zabbix for Cisco 7606? I need: - In/Out interface traffic, uptime, cpu & memory utilization, temperatures, ... - Graph and Trigger Thanks -- Regards, Shahab Vahabzadeh, Network Engineer and System Administrator Cell Phone: +1 (415) 871 0742 PGP Key Fingerprint = 8E34 B335 D702 0CA7 5A81 C2EE 76A2 46C2 5367 BF90

1 0

Re: L6-20P -> L6-30R
by Larry Sheldon 18 Mar '14

18 Mar '14

On 3/18/2014 2:24 PM, Randy wrote: > I have a situation where a 208v/20A PDU (L6-20P) is supposedly hooked to > a 208v/30A circuit (L6-30R). Before I order the correct PDU's and whip > cords...sanity check...are connectors 'similar' enough that this is > possible (with force) or am I going to find we've actually got L6-20R's > on the provider side? > http://www.amazon.com/L6-20P-L6-30R-Locking-Power-Adapter/dp/B004W359W0 -- 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

NetBSD as a TimeCapsule?
by Atticus 18 Mar '14

18 Mar '14

Use avahi.

3 2

ATT Postmaster Contact
by Robert Webb 18 Mar '14

18 Mar '14

Anyone have a contact for postmaster at att.net? I have one user on an email list I send to and they are blocking for abuse. This list might get 15 email a month that go out. Filled out their "form" but would like to get this resolved in less than "2 days" as they state. Robert

3 3

Re: How to catch a cracker in the US?
by Larry Sheldon 17 Mar '14

17 Mar '14

On 3/17/2014 9:10 PM, shawn wilson wrote: > The point is that 'computer security' involves innovation as much as > is done at hacker spaces (which can be geared to hardware or computer > security or whatever). I think the difference you're trying to argue > is the legality and not the task or process. I think calling the > illegal form of the study of computer security "cracking", the legal > form "hacking" and people who are "cracking" who don't know what > they're doing "script kiddies" is irrelevant, useless, and causes > useless debates (that I started) like this. SSSSCOOOOOOOOORRRRRRE! -- 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

Re: How to catch a cracker in the US?
by Larry Sheldon 17 Mar '14

17 Mar '14

On 3/13/2014 8:22 AM, Sholes, Joshua wrote: > On 3/13/14, 12:35 AM, "shawn wilson" <ag4ve.us(a)gmail.com> wrote: >> A note on terminology - whether you know what you're doing, actually break >> into a system, or obtain a thumb drive with data that you weren't supposed >> to have - it has the same end so I'd refer to it by the same term - >> hacking. Trying to differentiate terms based on skill, target, or data >> type is kinda dumb. > > If one came up in this field with a mentor who was old school, or if one > is old school oneself, one tends use the original (as I understand it) > definitions--a "cracker" breaks security or obtains data unlawfully, a > "hacker" is someone who likes ethically playing (in the "joyful > exploration" sense) with complicated systems. > > People who are culturally younger tend use "hacker", as you are doing, for > the former and as far as I can tell no specific term for the latter. > > If you ask me, this is something of a cultural loss. Not sure I can agree with that. I have been in this game for a very long time, but for most of it in places where the world's population cleaved neatly into two parts: "Authorized Users" who could be identified by the facts that they had ID cards, Badges, and knew the door code; and "trespassers" who were all others. Then you new kids came along and (pointlessly, in my opinion) divided the later group into the two described above. -- 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)

4 4

Last Call and Draft program for RIPE 68
by Filiz Yilmaz 17 Mar '14

17 Mar '14

Dear Colleagues, A list of currently accepted RIPE 68 presentations is now published at: https://ripe68.ripe.net/programme/meeting-plan/draft/ There are still few slots remaining for a final RIPE 68 programme and RIPE Programme Committee will accept new proposals until 6 April 2014. This is our last call for you to submit your proposals. Kind regards Filiz Yilmaz Chair, RIPE Programme Committee Begin forwarded message: > From: Filiz Yilmaz <koalafil(a)gmail.com> > Subject: Call for Presentations RIPE 68 > Date: 19 Nov 2013 19:04:34 GMT+1 > To: ripe-list(a)ripe.net, "nanog(a)nanog.org" <nanog(a)nanog.org> > Cc: "pc(a)ripe.net Committee" <pc(a)ripe.net> > > > Dear colleagues, > > Please find the CFP for RIPE 68 below or at https://ripe68.ripe.net/submit-topic/cfp/. > > The deadline for submissions is 2 March 2014. > Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. > > Kind regards > > Filiz Yilmaz > RIPE PC Chair > http://www.ripe.net/ripe/meetings/ripe-meetings/pc > > > --------------------- > > Call for Presentations > > A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. > > RIPE 68 will take place from 12 – 16 May 2014 in Warsaw, Poland. > > The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary session presentations, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 68. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: > > • IPv6 deployment > • Managing IPv4 scarcity in operations > • Commercial transactions of IPv4 addresses > • Data centre technologies > • Network and DNS operations > • Internet governance and regulatory practices > • Network and routing security > • Content delivery > • Internet peering and mobile data exchange > > Submissions > > RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and not attempt a product demonstration. > > The RIPE PC accepts proposals for different presentation formats, including plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. See the full descriptions of these formats at > https://ripe68.ripe.net/submit-topic/presentation-formats/ > > Presenters who are proposing a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. > > In addition to presentations selected in advance for the plenary, the RIPE PC also offers several time slots for “lightning talks”, which are selected immediately before or during the conference. > > The following general requirements apply: > > - Proposals for plenary session presentations, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 2 March 2014, using the meeting submission system at https://ripe68.ripe.net/submit-topic/guidelines/. Proposals submitted after this date will be considered on a space-available basis. > > - Lightning talks should also be submitted using the meeting submission system (https://ripe68.ripe.net/submit-topic/submission-form/) and can be submitted just days before the RIPE Meeting starts or even during the meeting week. The allocation of lightning talk slots will be announced in short notice – in some cases on the same day but often one day prior to the relevant session. > > - Presenters should indicate how much time they will require. > See more information on time slot allocations per presentation format at https://ripe68.ripe.net/submit-topic/presentation-formats/ > > - Proposals for talks will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panelists, presenters and moderators. > > - Due to potential technical issues, it is expected that most, if not all, presenters/panelists will be physically present at the RIPE Meeting. > > If you have any questions or requests concerning content submissions, please email pc [at] ripe [dot] net. > > --------------------- > >

1 0