On Sat, Jul 19, 2008 at 08:26:33PM +0100, [EMAIL PROTECTED] wrote:
> Sounds like he's used to used IRC, not mailing lists. There used to
> be an IRC channel where a lot of NANOG folks hung out. Anyone care to
> publicize the channel name and which IRC network carries it?
I was invited to it once,
On Sat Jul 19, 2008 at 08:44:31PM +0100, [EMAIL PROTECTED] wrote:
> Is there a place where frontline
> network operators hang out, where it is not frowned upon to
> ask operational questions about events in progress?
There are many. I suspect some are more public than others (but I don't have
a l
> > Sounds like he's used to used IRC, not mailing lists.
> > There used to be an IRC channel where a lot of NANOG folks
> hung out.
> > Anyone care to publicize the channel name and which IRC network
> > carries it?
> from the nanog mailing list...
> Sent: Tuesday, June 22, 2004 12:17 PM
> >
[EMAIL PROTECTED] wrote:
Anyone from sbcglobal out there? i'm seeing a routing
loop. Please
contact me off list thanks.
What did your upstream transit supplier advise before you
escalated this to the global audience at NANOG?
This is the second time in 24hrs you have
[EMAIL PROTECTED] wrote:
Sounds like he's used to used IRC, not mailing lists.
There used to be an IRC channel where a lot of NANOG
folks hung out. Anyone care to publicize the channel
name and which IRC network carries it?
--Michael Dillon
from the nanog mailing list...
From: "Tim Brown" <>
> > Anyone from sbcglobal out there? i'm seeing a routing
> loop. Please
> > contact me off list thanks.
> What did your upstream transit supplier advise before you
> escalated this to the global audience at NANOG?
> This is the second time in 24hrs you have requested
> assistance here whic
Aaron Glenn wrote:
I think it should be clear to those posting here as a last ditch
effort that they should certainly outline the steps they've already
taken -- basically justifying their post to NANOG: "I tried X, waited
Y, got Z, and now I'm here"
To give an example:
http://mailman.nanog.or
On Fri, Jul 18, 2008 at 3:56 PM, Paul Wall <[EMAIL PROTECTED]> wrote:
> I think that's precisely the problem, that the issue could not have
> been handled "though other methods".
I think it should be clear to those posting here as a last ditch
effort that they should certainly outline the steps th
I think that's precisely the problem, that the issue could not have
been handled "though other methods".
I agree NANOG is not a replacement for NOCs, but what about when the
NOCs are utterly useless and the issue is global in scope?
Given the parties involved, I'd like to think that Logan tried t
What did your upstream transit supplier advise before you escalated this to
the global audience at NANOG?
This is the second time in 24hrs you have requested assistance here which
could have been handled via other methods.
-ren
On Fri, Jul 18, 2008 at 1:30 PM, Logan Rawlins <[EMAIL PROTECTED]>
wro
Think this may be an ongoing issue... Last night out here in the bay
area, myself and many other SBC/ATT users were experiencing random
blackholed networks. Total PITA!
-Mike
On Fri, Jul 18, 2008 at 10:33 AM, Justin Ream <[EMAIL PROTECTED]> wrote:
> Hey we got one too - we're having problems thr
Hey we got one too - we're having problems through Level 3.
Hop IP Address Hostname ASN Network Name % Loss Min Latency Latency Avg
Latency Max Latency Std Dev
1 192.168.1.1 192.168.1.1 0 0.37 0.47 0.67 0.06
2 192.168.1.254 192.168.1.254 0 0.66 0.76 1.1 0.07
3 216.31.131.253 s1p20.
12 matches
Mail list logo
