Re: OLD root server IP addresses through history
On Wed, 4 Jun 2008, [EMAIL PROTECTED] wrote: On Mon, Jun 02, 2008 at 02:53:26PM -0400, Sean Donelan wrote: http://www.donelan.com/dnstimeline.html 1 Jun 1990 NIC.DDN.MIL 26.0.0.73 root service ends (last "original" root server) it would much more helpful to have citations for your dates. Most of the dates came from the Namedroppers mailing list archives. A few came from other mailing lists or newspaper articles at the time. But my actual question, which I neglected to include, Is Net-26 still seeing queries to the 26.0.0.73 root after 18 years?
Re: OLD root server IP addresses through history
Sean Donelan wrote: But my actual question, which I neglected to include, Is Net-26 still seeing queries to the 26.0.0.73 root after 18 years? 26/8 doesn't appear in the routing table. so unless it's getting queries from inside the dod all those packets should fall on the floor the first time they hit a router without default.
Re: OLD root server IP addresses through history
On Wed, Jun 04, 2008 at 10:20:33AM -0400, Sean Donelan wrote: > On Wed, 4 Jun 2008, [EMAIL PROTECTED] wrote: > >On Mon, Jun 02, 2008 at 02:53:26PM -0400, Sean Donelan wrote: > >> > >> > >>http://www.donelan.com/dnstimeline.html > >> > >>1 Jun 1990 > >>NIC.DDN.MIL 26.0.0.73 root service ends (last "original" root server) > > > > > > it would much more helpful to have citations for your > > dates. > > Most of the dates came from the Namedroppers mailing list archives. A few > came from other mailing lists or newspaper articles at the time. > > But my actual question, which I neglected to include, Is Net-26 still > seeing queries to the 26.0.0.73 root after 18 years? i can see net 26, but will have to get an answer from someone else. --bill
AT&T Outage?
I'm getting 100% packet loss out of NYC heading to Comcast.. anyone else seeing anything? ___ Phillip S. Loveless DRS Power & Control Technologies 21 South Street Danbury, CT 06810 <>
AT&T Outage?
Update: 4 785 ms 245 ms 781 ms gbr5.n54ny.ip.att.net [12.123.202.130] 5 756 ms 759 ms 787 ms tbr1.n54ny.ip.att.net [12.122.11.9] 6 *** Request timed out. 7 729 ms 737 ms 699 ms 64.212.107.97 8 *** Request timed out. 9 682 ms 688 ms 331 ms COMCAST-IP-SERVICES-LLC-New-York.TenGigabitEther et9-2.ar4.NYC1.gblx.net [64.213.77.218] 10 667 ms 673 ms 674 ms te-0-1-0-0-crs01.plainfield.nj.panjde.comcast.ne [68.85.192.37] 11 *** Request timed out. 12 710 ms 696 ms 709 ms te-1-1-ur02.mtlaurel.nj.panjde.comcast.net [68.8 .192.42] 13 *** Request timed out. 14 *** Request timed out. 15 *** Request timed out. ___ Phillip S. Loveless
RE: AT&T Outage?
Same coming out of the mid-west also. 4 12.122.96.5 584 msec 788 msec 784 msec 5 192.205.34.62 816 msec 632 msec 616 msec 6 ae-15-51.car1.Atlanta2.Level3.net (4.68.103.10) 712 msec 808 msec 860 msec 7 COMCAST-IP.car1.Atlanta2.Level3.net (4.71.252.6) 784 msec 840 msec 784 msec 8 pos-0-8-0-0-cr01.mclean.va.ibone.comcast.net (68.86.85.70) 736 msec 820 msec 784 msec 9 pos-0-0-0-0-cr01.philadelphia.pa.ibone.comcast.net (68.86.85.6) 796 msec 844 msec 852 msec 10 be-40-crs01.401nbroadst.pa.panjde.comcast.net (68.86.208.33) 872 msec 804 ms ec 696 msec 11 pos-0-7-0-0-crs01.ivyland.pa.panjde.comcast.net (68.85.192.202) 748 msec 824 msec * 12 te-0-1-0-0-crs01.plainfield.nj.panjde.comcast.net (68.85.192.37) 700 msec 74 0 msec 784 msec 13 te-1-1-ur01.mtlaurel.nj.panjde.comcast.net (68.85.192.38) 824 msec 848 msec 864 msec 14 te-1-1-ur02.mtlaurel.nj.panjde.comcast.net (68.85.192.42) 800 msec 768 msec 716 msec 15 te-1-1-ur01.arneysmount.nj.panjde.comcast.net (68.85.192.46) 680 msec 692 ms ec 828 msec 16 GE-0-1-ubr01.arneysmount.nj.panjde.comcast.net (68.86.223.118) 824 msec 800 msec 816 msec 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * -Original Message- From: Loveless, Phillip S. [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 04, 2008 12:28 PM To: [EMAIL PROTECTED] Subject: AT&T Outage? Update: 4 785 ms 245 ms 781 ms gbr5.n54ny.ip.att.net [12.123.202.130] 5 756 ms 759 ms 787 ms tbr1.n54ny.ip.att.net [12.122.11.9] 6 *** Request timed out. 7 729 ms 737 ms 699 ms 64.212.107.97 8 *** Request timed out. 9 682 ms 688 ms 331 ms COMCAST-IP-SERVICES-LLC-New-York.TenGigabitEther et9-2.ar4.NYC1.gblx.net [64.213.77.218] 10 667 ms 673 ms 674 ms te-0-1-0-0-crs01.plainfield.nj.panjde.comcast.ne [68.85.192.37] 11 *** Request timed out. 12 710 ms 696 ms 709 ms te-1-1-ur02.mtlaurel.nj.panjde.comcast.net [68.8 .192.42] 13 *** Request timed out. 14 *** Request timed out. 15 *** Request timed out. ___ Phillip S. Loveless
Re: amazonaws.com?
On Thu, May 29, 2008 at 06:08:47AM -0700, Joel Jaeggli wrote: > Dorn Hetzel wrote: > >There is a really huge difference in the ease with which payment from a > >credit card can be reversed if fraudulent, and the amount of effort > >necessary to reverse a wire transfer. I won't go so far as to say that > >reversing a wire transfer is impossible, but I would claim it's many orders > >of magnitude harder than the credit card reversal. > > To paraphrase one of my colleagues from the user interaction world: > > "The key to offering a compelling service is minimising > transaction hassles." > > I encourage all my competitors to implement inconvenient hard to use > payment methods I do too. If all of your competitors uniformly make it just enough harder for Bad Actors to rent servers from which to Act Bad, then we'll *know* where it's coming from, and what to do about it -- and why (you wanted to make more money). See also "Tragedy Of The Commons". Cheers, -- jra -- Jay R. Ashworth[EMAIL PROTECTED] Designer+-Internetworking--+-+RFC 2100 Ashworth & Associates | Best Practices Wiki | | '87 e24 St Petersburg FL USA+-http://bestpractices.wikia.com-+ +1 727 647 1274 If you can read this... thank a system administrator. Or two. --me
Re: amazonaws.com?
On Thu, May 29, 2008 at 11:10:40AM -0700, Joel Jaeggli wrote: > Barry Shein wrote: > > > Equating port 25 use with domestic terrorism is specious. > > > > > > Ammonium nitrate requires requires some care in handling regardless of > > > your intentions,see for exmple the oppau or texas city disasters. > > > >And how different is that from the million+ strong zombie botnets? Who > >owns (not pwns) those zombie'd systems and what were their intentions? > > Well let's see. The texas city disaster is/was considered the worst > industrial accident in american history. 581 people killed by an > explosive yield of about 2 kilotons. The secondary effects includes > fires in many of the chemical facilities in Galveston and a swath of > destruction that reached up to 40 miles inland... > > http://www.local1259iaff.org/disaster.html > > So no, I don't think internet attached hosts can casually equated with > the destructive potential of a pile of fertilizer at least not in the > context described. One word: SCADA. Yes, in point of fact, I think it *is* reasonable to evaluate potential threats to "just some PCs getting pwned" in terms of physical damage on grander scales. It's not just about spam, or fraudulent credit charges. Cheers, -- jra -- Jay R. Ashworth[EMAIL PROTECTED] Designer+-Internetworking--+-+RFC 2100 Ashworth & Associates | Best Practices Wiki | | '87 e24 St Petersburg FL USA+-http://bestpractices.wikia.com-+ +1 727 647 1274 If you can read this... thank a system administrator. Or two. --me
RE: AT&T Outage?
> Same coming out of the mid-west also. Not seeing anything unusual here in S.E CT (att adsl going to Comcast business cable acct.). 1 2 ms10 ms 2 ms 172.16.34.250 2 1 ms<1 ms<1 ms 69.183.133.206 3 8 ms 8 ms 8 ms se1-l0.mrdnct.sbcglobal.net [204.60.4.38] 4 8 ms 9 ms 8 ms dist1-vlan60.mrdnct.sbcglobal.net [66.159.184.226] 545 ms24 ms15 ms bb1-10g2-0.mrdnct.sbcglobal.net [151.164.92.147] 688 ms98 ms 147 ms 151.164.94.255 7 100 ms52 ms13 ms asn3356-level3.eqnwnj.sbcglobal.net [151.164.89.250] 816 ms18 ms17 ms ae-31-53.ebr1.newark1.level3.net [4.68.99.94] 914 ms17 ms17 ms ae-2.ebr1.newyork1.level3.net [4.69.132.97] 1024 ms19 ms16 ms ae-71-71.csw2.newyork1.level3.net [4.69.134.70] 1113 ms13 ms13 ms ae-2-79.edge1.newyork2.level3.net [4.68.16.75] 1214 ms28 ms13 ms comcast-ip.edge1.newyork2.level3.net [4.71.184.2] 1316 ms17 ms17 ms te-3-3-ar01.chartford.ct.hartford.comcast.net [68.86.90.66] 1417 ms17 ms17 ms po-10-ar01.berlin.ct.hartford.comcast.net [68.87.146.30] 1517 ms17 ms17 ms te-9-1-ur01.middletown.ct.hartford.comcast.net [68.87.182.50] 1618 ms17 ms18 ms te-9-1-ur01.killingworth.ct.hartford.comcast.net [68.87.182.46] 1718 ms18 ms28 ms te-9-1-ur01.clinton.ct.hartford.comcast.net [68.87.182.42] 1819 ms20 ms20 ms te-8-1-ur01.groton.ct.hartford.comcast.net [68.87.182.21] 1919 ms19 ms26 ms te-9-1-ur01.nstonington.ct.hartford.comcast.net [68.87.182.25] 2019 ms19 ms20 ms te-9-1-ur01.norwich.ct.hartford.comcast.net [68.86.231.166] 21 * 1533 ms 2871 ms 75-144-196-61-connecticut.hfc.comcastbusiness.net [75.144.196.61] ya, our end point is a tad saturated but not my problem yet. ;) ~JasonG --
RE: Power/temperature monitoring
Frank, We have had good luck with a device called TemPager (http://tempager.com/). Our specific device is used for SNMP temperature monitoring, but they also make a device that includes the ability to humidity, power, flood, room entry, etc. etc. Hope that is helpful, Josh - - - - Joshua Fiske '03, '04 Network and Security Engineer Clarkson University, Office of Information Technology (315) 268-6722 -- Fax: (315) 268-6570 GPG Key: http://clarkson.edu/~jfiske/jfiske_pub.asc [EMAIL PROTECTED] CONFIDENTIALITY: This e-mail (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this e-mail in error, please notify the sender and delete this e-mail from your system. -Original Message- From: Frank Bulk [mailto:[EMAIL PROTECTED] Sent: Fri 5/30/2008 10:58 AM To: nanog@nanog.org Subject: Power/temperature monitoring Hopefully monitoring the status of a network is on-topic. I'm looking for temperature and power monitoring unit to install in some remote BWA cabinets. We had two incidents where we lost power in a town and we weren't aware of it until the backup batter drained to empty, and another situation where the cabinet became too cold. Because these cabinets are less than 19" wide and just 3-5" deep, I need something quite small. I did find one product but it requires four components (unit with built-in temperature sensor, adapter, and AC power sensor, plus power supply) Perhaps there's someone on this list who has gone down this road and can point me to a good product. Required: - temperature sensor - 110 VAC power monitoring (on/off, not necessarily current) - Ethernet interface (at least SNMP, Web GUI and Optional: - fed via 12 VDC power - 12 VDC power monitoring (current) - humidity sensor Frank
