Steve Francis wrote:
Just as a head up - this sort of below should not be done on things
like web servers that support lots of concurrent connections - you'll
eat all your memory for sockets.
Unless you have something like FreeBSDĀ“s auto-tuning inflight window
stuff which
would allow large
There are two policy proposals coming up at ARIN that may be of
particular
interest to ISPs here that may not normally pay much attention to ARIN.
Actually, there are several policy proposals that may be
of particular interest to ISPs that may not normally
pay much attention to ARIN. For
135 is, indeed, blocked by Comcast.
What about ICMP (24.218.168.0 subnet) ? I was informed ports 135-139 and
were blocked only.
--
Brandon Ross AIM:
BrandonNR
Principal IP Engineer ICQ:
2269442
There was recently a thread regarding ability to access some SSL sites
from the AOL service, so I thought I'd sign up here and reach out.
If anyone has questions/problems regarding AOL's web access, please feel
free to contact me at [EMAIL PROTECTED] or on the office phone at
703-265-0906
There was recently a thread regarding ability to access some SSL sites
from the AOL service, so I thought I'd sign up here and reach out.
...and one of your peers was quickly helpful and pointed out the 172.***
addres issue that was staring us in the face.
Date: Tue, 30 Sep 2003 19:36:23 -0500
From: John Kristoff [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
On Tue, Sep 30, 2003 at 05:22:25PM -0700, Crist Clark wrote:
Wasn't this based upon the premise that gear should not return ICMP
errors as a result of ICMP packet input as a
Hello All,
Lacking Ren and MDR for planning this NANOG, Ren asked myself and David Koch
to hook up some unofficial events.
We have a few ideas and are wondering if anyone would be interested in the
following dates/times. Once we get a feel of when people are interested in
doing things, we'll
Anyone else seeing this:: (1sec+ delay to my idle DSL line across
sprintlink...)
traceroute is definitely taking an asymmetric path, since pings and tcp
connections are consistent 1sec plus RTT starting somewhere in seattle or
tacoma.tok? tokyo? Anyway before I start rattling this around
- Original Message -
From: Michael Loftis [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, October 01, 2003 2:47 PM
Subject: Massive sprintlink problems?
Anyone else seeing this:: (1sec+ delay to my idle DSL line across
sprintlink...)
traceroute is definitely taking an
I'm seeing this on my cable connection too.
([EMAIL PROTECTED]/pts/1:~) traceroute shell.wgops.com
traceroute to shell.wgops.com (66.92.192.108), 30 hops max, 38 byte packets
1 10.65.80.1 (10.65.80.1) 7.106 ms 11.420 ms 40.080 ms
2 srp4-0.chrlncsa-rtr4.carolina.rr.com (24.93.66.110) 6.847
According to speakeasy system status page (my DSL provider at the other end
there)... It seems though it's rather more widespread than what this
notice makes it out to be.
09/26/03 02:18:07 PM Seattle POP Packet Loss
Region : Seattle
E.T.A. : (none)
Services Affected : Some broadband
Judging by traceroutes to livejournal.com, which is hosted at Internap,
there are problems with Sprintlink after that hop to Toyko. I'm now hitting
Verio instead.
([EMAIL PROTECTED]/pts/1:~) traceroute shell.wgops.com
traceroute to shell.wgops.com (66.92.192.108), 30 hops max, 38 byte packets
.
.
| Type: Outage
| Purpose: Routing Issues
| Network: SL
| Ticket: 6505769
| Sprint Id: 16881
|
.
Can someone with a clue in ChoiceOnes IP operations contact me off list
please.
--
Robert Blayzor, BOFH
INOC, LLC
[EMAIL PROTECTED]
PGP: http://www.inoc.net/~dev/
Key fingerprint = A445 7D1E 3D4F A4EF 6875 21BB 1BAA 10FE 5748 CFE9
Quality assurance: A way to ensure you never deliver shoddy
Sue,
I know it's short notice, but, can we try and get someone from
ICANN to explain at Chicago why they haven't pulled Verisign's contracts
for malfeasance? Further, can we get someone from Verisign to explain
how Verisign plans to correct these actions and stop taking unilateral
Owen,
I know it's short notice, but, can we try and get someone from
ICANN to explain at Chicago why they haven't pulled Verisign's contracts
for malfeasance? Further, can we get someone from Verisign to explain
how Verisign plans to correct these actions and stop taking unilateral
Just passing this along - some of you may want to attend to voice your
opinion. - Russ
From: DCISOC [EMAIL PROTECTED]
Subject: DCISOC: SECSAC meeting on Verisign's Site Finder Service
This meeting, on one of the hottest Internet topics, will be held in
downtown D.C. next Tuesday. You're
17 matches
Mail list logo