October 2001 - Test - lists.nanog.org

Unix Timestamp
by Brandon Handeland 23 Oct '01

23 Oct '01

Does anyone have a formula to convert a unix time stamp into the current time? I know it is January 1st, 1970, in UTC format. Just need some example code. I'm trying to export some data from a HP/UX box into a MSSQL database and need to use the timestamp feature of MSSQL. Thanks ---------------------------------------------------------------------- Brandon Handeland Brandon(a)wyoming.com Senior Network Engineer wyoming.com NOC (307) 857-1092 ----------------------------------------------------------------------

11 11

DVMRP tunnel to the MBONE (seeking MBONE end)
by Joe Abley 23 Oct '01

23 Oct '01

Wanted: one DVMRP tunnel to the MBONE. Router terminating tunnel on my side is well-connected, in MFN colo in Reston, VA. Anybody feel like hooking me up? Direct replies would be good. Thanks!

1 0

Fwd: Call for Volunteers: IAB/IETF Nominating Committee
by RJ Atkinson 23 Oct '01

23 Oct '01

If NANOG folks want the IETF to have good operator input, then operationally minded folks need to volunteer for the IETF nominating committee. The NomCom is responsible for nominating IAB and IESG members. Last year's NomCom had a nicely rounded participation from developers, network operators, and corporate users. If you are qualified to be on IETF NomCom, please consider volunteering. There is less than 1 week left, so if you are interested and haven't sent in your email to the special email address yet, please do so now. Speaking just for myself. Ran rja(a)inet.org >From: tytso(a)mit.edu >To: IETF-Announce: ; >Subject: Call for Volunteers: IAB/IETF Nominating Committee (2nd call) >Date: Thu, 11 Oct 2001 15:57:24 -0400 >Sender: scoya(a)cnri.reston.va.us > > >Many thanks to those members of the IETF community who have volunteered >to serve on the IAB/IESG Nominating committee. The list of those people >who have volunteered can be found at: > > http://thunk.org/tytso/nomcom-volunteers.html > >If you believe you have volunteered, but you cannot find your name on >this list, please send me e-mail so I can look into it. > >If you have not yet volunteered, please consider doing so. In order to >be eligible to serve on the Nominating Committee, you must have attended >at least 2 of the last 3 IETF's. > >The time commitment will range from 3-5 hours a week from November to >January, and will consist of weekly teleconferences plus time spent >interviewing and reading e-mail from prospective candidates as well as >working group chairs and other IETF participants. This is a significant >time commitment, but participation by IETF volunteers is critical if we >are to select the best leadership for our community. So I encourage all >eligible volunteers who feel that they can offer their time and efforts >to respond. > >To volunteer please send e-mail to the following e-mail address: > > nomcom-volunteer(a)thunk.org > >A list of those people who have volunteered and who have been confirmed >by the Secretariat as having attended at least two of the last three >IETF meetings can be found at: > > http://www.thunk.org/tytso/nomcom-volunteers.html > >The deadline for volunteering to serve on the Nominating Committee is >5pm EDT, October 29, 2001. > >Based on the list of those who have volunteered, we will run the >selection process and announce the results the week of October 29, 2001. >Ten (10) NomCom voting members will be chosen from the pool of >volunteers according to the procedure described by Donald Eastlake in >RFC 2777, "Publicly Verifiable Nomcom Random Selection". The source of >randomness will be based on the number of shares traded of 12 stocks >selected by the NomCom chair on October 30, 2001. > >The official number of shares traded (denoted in 000s) will be drawn >from the October 31, 2000 Wall Street Journal which reports the sales >figures from the previous day - October 30, 2001. If trading in any >stock is suspended, then the number of shares traded will be taken from >the first day prior to October 30, 2001 where the number of shares >traded in that stock was non-zero. > >Thank you, > > Theodore Ts'o > tytso(a)mit.edu

1 0

Re: [NEWS] FBI To Require ISPs To Reconfigure E-mail Systems (fwd)
by Paul Vixie 23 Oct '01

23 Oct '01

Not picking on anyone in particular but just plucking an example at ~random: > Funny you should mention that, as I think we are about to find out. It's possible that the feds are going about this in the wrong way. Rather than seeking ways to expose that wrongness if any, we ought to be putting our effort into figuring out what they're trying to do and then making a recommendation (or several) as to how to actually get it done. Put your shoulder to this wheel, folks. Or find someplace else to live. (There's a four year sunset provision in the law they're passing tonight.)

8 9

Re: Unix Timestamp
by rs＠seastrom.com 22 Oct '01

22 Oct '01

Brandon Handeland <Brandon(a)wyoming.com> writes: > Does anyone have a formula to convert a unix time stamp into the > current time? I know it is January 1st, 1970, in UTC format. Just > need some example code. > > I'm trying to export some data from a HP/UX box into a MSSQL database and > need to use the timestamp feature of MSSQL. The best code I've seen for this (and which knows about most variants of the timestamp seen in the wild) was written by Steve Bellovin et al, and can be found in the inn distribution in lib/parsedate.y ---Rob

2 1

Re: Unix Timestamp
by Steven M. Bellovin 22 Oct '01

22 Oct '01

In message <87elnvtsdd.fsf(a)valhalla.seastrom.com>, Robert E. Seastrom writes: > > >Brandon Handeland <Brandon(a)wyoming.com> writes: > >> Does anyone have a formula to convert a unix time stamp into the >> current time? I know it is January 1st, 1970, in UTC format. Just >> need some example code. >> >> I'm trying to export some data from a HP/UX box into a MSSQL database and >> need to use the timestamp feature of MSSQL. > >The best code I've seen for this (and which knows about most variants >of the timestamp seen in the wild) was written by Steve Bellovin et >al, and can be found in the inn distribution in lib/parsedate.y Thanks -- but I think that my code performs the inverse function. That is, it converts lots of different time formats *into* Unix time. Also, so much of the code was rewritten by others in the mid-1990's that I'm not sure it's fair to call it mine any more. (My code was written in 1979, when 'int' was a 16-bit datatype, 'long' didn't exist, and the yacc stack was composed of 16-bit values only -- all of which are why it needed to be rewritten... As a fringe benefit, my original code not only had y2k issues, it refused to convert any dates after 2000.) --Steve Bellovin, http://www.research.att.com/~smb Full text of "Firewalls" book now at http://www.wilyhacker.com

1 0

Re: Unix Timestamp
by Steven M. Bellovin 22 Oct '01

22 Oct '01

In message <5.1.0.14.2.20011022123839.05490760(a)calamity.wyoming.com>, Brandon H andeland writes: > >Does anyone have a formula to convert a unix time stamp into the current time? > >I know it is January 1st, 1970, in UTC format. Just need some example code. > >I'm trying to export some data from a HP/UX box into a MSSQL database and >need to use the timestamp feature of MSSQL. > How accurate does your conversion need to be? Do you need timezones? Daylight time? On any Unix system, including the open-source clones, grab a copy of ctime.c; its job is to do exactly that. If you want to approximate the answer -- well, there are 86400 seconds/day, and either 365 or 366 days/year. The remaind when dividing by 86400 is the number of seconds into the current day, in UTC. --Steve Bellovin, http://www.research.att.com/~smb Full text of "Firewalls" book now at http://www.wilyhacker.com

1 0

mae-west problems (AS8251)
by MarcoH 22 Oct '01

22 Oct '01

We (AS 8251) are having problems with the announcements one of our upstreams is making on mae-west. From the 2 prefixes they announce for us, 1 is working fine and the other is unreachable. If somebody who`s peering with Carrier1 at mae-west would be so kind to see if there are any differences in the annoucements for 62.216.0.0/19 and 195.64.64.0/19 I would be thankfull. 62.216.0.0/19 is the one working, traffic for 195.64.64.0/19 drops at mea-west. We`re also working directly with C1 to sort things out, but any usefull information is welcome. MarcoH Cistron Internet BV (Netherlands)

1 0

Nanog 23 questons
by Lucy E. Lynch 22 Oct '01

22 Oct '01

Notes: send questions to: questions(a)nanog.org the archive is here: http://darkwing.uoregon.edu/~llynch/nanog23/ Please use a keyword in your subject related to the talk you're addressing. Use the keyword tech: for technical feeedback please. Lucy E. Lynch Academic User Services Computing Center University of Oregon llynch(a)darkwing.uoregon.edu (541) 346-1774 Cell: (541) 912-7998 5419127998(a)mobile.att.net

1 0

Fwd: Re: NetSol's PGP auth ... and the road not taken
by Rodney Thayer 22 Oct '01

22 Oct '01

>From: Leo Bicknell <bicknell(a)ufp.org> > >On Mon, Oct 22, 2001 at 12:24:17AM -0700, Joe Rhett wrote: > > Don't waste your time. We had PGP auth working for the last 6 years. It > > will slow down any change you want to make by 3-5 days. Around 30% will get > > rejected for no reason whatsoever, and much more fun stuff. > >I find these comments interesting. I have been using PGP auth for >a number of years and found it to work just fine. From the PGP implementor community, we've seen reports that the NetSol use of PGP has had issues in the past, things being garbled or lost, other sorts of things. The implication was that there were issues with the PGP implementation they were using. I've heard multiple stories of people having less-than-sound customer service experiences with this mechanism.

1 0