http://keepass.info
Works great in a multi-user environment.
-Original Message-
From: Jay Nakamura [mailto:zeusda...@gmail.com]
Sent: Wednesday, November 18, 2009 19:57
To: NANOG
Subject: Password repository
Quick question, does anyone have software/combination of tools they
recommend
A free Netflow option is CUFlow, you can graph via AS/network/protocol.
http://www.columbia.edu/acis/networks/advanced/CUFlow
It is a bit outdated, but gets the job done here, as these details are
not mission critical for me.
-Original Message-
From: Stefan Fouant
Does anyone have a valid postmaster contact for Comcast? They are
currently blocking one of my mailservers, yet using the forms on their
site to request removal, they report that it is not blocked by them.
They are ignoring the actual content of my reports (such as the actual
error returned by
Customers thank me
I will not stoop much lower
Pay dirt for transit
-Original Message-
From: Murphy, Jay, DOH [mailto:jay.mur...@state.nm.us]
Sent: Monday, January 12, 2009 09:41
To: neal rauhauser; nanog@nanog.org
Subject: RE: Cogent Haiku v2.0
NANOG is too cool.
Rhyming with net
In general, announce what you are allocated from the RIR. The minimum
allocation from you will see is a /24.
A couple examples:
http://www.arin.net/reference/ip_blocks.html#ipv4
https://www.ripe.net/ripe/docs/ripe-ncc-managed-address-space.html
If you are allocated a /22, announce the /22. Do
For me, things appear to have cleared up this morning. Anyone else?
-Original Message-
From: Blake Pfankuch [mailto:[EMAIL PROTECTED]
Sent: Monday, December 08, 2008 22:19
To: Mike Lewinski; nanog@nanog.org
Subject: RE: Comcast DNS
Having paid attention to this thread, im having issues
Add Seattle/Washington to the list.
It's been a rough week with Comcast, with a state-wide outage last
Thursday morning as well.
-Original Message-
From: Mike Lewinski [mailto:[EMAIL PROTECTED]
Sent: Monday, December 08, 2008 20:48
To: nanog@nanog.org
Subject: Re: Comcast DNS
There are
Yes, all our traffic was dying over at UUNet, yet it was still being
announced it. It just came up before I could send anything to outages.
-Original Message-
From: Peter Beckman [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 12, 2008 13:48
To: nanog@nanog.org
Subject:
Hubs sure are fun...
I would trunk the ports you are monitoring, and run the port monitor on
the trunk port instead (one trunk port, one port per VLAN, plus one
span) which will help with your density. This is assuming the analysis
software you have can read the dot1q tags, but means you do not
This is all from netflow. The results are from two different routers.
IP packet size distribution (43046M total packets):
1-32 64 96 128 160 192 224 256 288 320 352 384 416 448
480
.000 .382 .077 .043 .022 .012 .011 .006 .007 .004 .004 .005 .003 .003
.003
512 544 576
Here is the reverse view from one of my systems on residential Comcast
in the Everett/Mill Creek area (source is 76.121.150.xxx):
Tracing route to 208.74.128.9 over a maximum of 30 hops
11 ms1 ms1 ms 192.168.254.254
2 *** Request timed out.
3 9 ms
11 matches
Mail list logo
