That honestly is what my experience used to be but this has not been my
observation recently, even when we as a large NSP provide all detail and
literally ask about possible bugs.
From: NANOG On Behalf Of Joel Esler
Sent: Thursday, March 7, 2024 11:46 AM
To: Pascal Masha
Cc: nanog
Subject: Re
I've always been a little less harsh than What Jared mentions, but my theory is
like within say 5-7 ms is probably reasonable as long as the endpoint is closer
than the next major IX both are present on. I don't really know what folks
think they are getting by peering across the world. I t
As a decent sized north American ISP I think I need totally agree with this
post.There simply is not any economically justifiable reason to collect
customer data, doing so is expensive, and unless you are trying to traffic
shape like a cell carrier has zero economic benefit. In our case
I'm also willing to try and fit in a few real CO tours around the event if
people are so inclined. We operate the ILEC territory to both the north and
east of the venue and it is somewhat unique as it is former GTE territory and
not bell system.
I also recommend the telecom museum.
-Ori
Honestly, the only way I’ve found to fix this is completely fill it with
subscribers off a BNG and give support a script about what to tell customers.
I’ve had folks literally get the wrong TV channels because we assign unused
blocks in Portland Oregon out of our parent large aggrigates and the
20 KW should easily cover the 9KW you could max draw with your strip heat. It
is super uncommon to have even peak loads over 20 KW in a house. Even your
peak day was only an average of 6 KW.
You might need some load shedding just to keep the big stuff from coming on all
at once but that is
When working with ILECs it is important to differentiate what must be offered
via ICAs and what is offered commercially. We for example sell a ton
commercially but effectively none through our interconnection agreements
anymore.
(we being Ziply Fiber in WA/OR/ID/MT)
From: NANOG On Behalf Of
I told my wife that she is my critical load as such I like to treat our place
like a datacenter. House wide UPS for all lights and all bedroom and office
outlets, large generator system, ATS and lots of fuel. Last time I was at a
nanog and the power went out she chuckled when I told her it w
Yes, most grounding out now that utilities do for work is all phases to one
another, to the neutral and to the ground.
From: NANOG On Behalf Of Mel Beckman
Sent: Monday, August 30, 2021 10:59 AM
To: Aaron C. de Bruyn
Cc: NANOG Operators' Group
Subject: Re: Reminder: Never connect a generator t
Unless you have storage, you are using the utility for services. It is no
realistic to assume that they will do net metering forever, it simply does not
allow them to fund the distribution network.
I honestly think the current rates for solar in-feed at places like Hawaiian
electric are more
We are seeing the peak spread out… we carry mostly pacific northwest
residential networks… we are also seeing new, slightly higher evening peaks.
From: NANOG On Behalf Of Rishi Singh
Sent: Friday, March 13, 2020 8:25 AM
To: Jared Mauch
Cc: nanog@nanog.org
Subject: Re: AT&T is suspending broa
Did you happen to have this contact? I have a couple of CIDR blocks still
having this problem.
The blocks involved all seem right on the main geolocation blocks.
John
From: NANOG On Behalf Of Cassidy B. Larson
Sent: Tuesday, November 12, 2019 3:54 PM
To: Michael Crapse
Cc: nanog@nanog.org
S
We were looking at them for the same role as well, P router makes a lot of
sense in places where the network comes together (for us often ahead of CMTS
boxes etc) but routing is still required due to many paths being available.
We are using juniper ACX5000s for this as well currently.
Hi j...@vanoppen.com if you need me or anything from 11404 in general.
-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Rod Beck
Sent: Sunday, April 16, 2017 9:40 AM
To: nanog@nanog.org
Subject: John Van Oppen - Wave Broadband
If John is on the list
That is awesome!
-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Dorian Kim
Sent: Sunday, February 14, 2016 3:25 AM
To: Jared Geiger
Cc: nanog@nanog.org
Subject: Re: NTT Charles
AS2914 has a tradition of bidding farewell to technical team members who
move on
Not that we could tell, it was a really annoying location to fix and we saw
lots of traffic show up from customers that were multi-homed between us and the
affected carriers (L3 and integra), likely amazon saw the same issues we did.
RFO I heard was fiber cut on an island in the Columbia river.
seems pretty real to me, I know we (AS11404) mark to zero on ingress... I
think that is the typical case otherwise people would just tag their flood
style ddos traffic as max and try to take out everything.
John
From: NANOG [nanog-boun...@nanog.org] on
Dead here at AS11404 from all locations where we PNI or public peer...
must be bad over there, v4 dies at their edge, v6 makes it in but no page loads.
John
cogent is well known not to filter in any useful way... in terms of sources
that should not be there, we see the same thing (or did the last time I looked).
John van Oppen
Spectrum Networks
Direct: 206-973-8302
Main: 206-973-8300
From: NANOG [nanog
We gave up and went to ASR9ks but that that was also a pretty big budget
upgrade...
-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Simon Lockhart
Sent: Tuesday, July 29, 2014 3:57 PM
To: Corey Touchet
Cc: nanog@nanog.org
Subject: Re: Upgrade Path Options from
The choice for ISPs at larger scale is peering or caching, peering is cheaper
than caching as power is not as cheap as you think as well as the requirement
to have two of everything for failover if you do caches (ie can't have my
transits or more likely my backhaul blow up if the caches go away)
Let's just dispel this, internet bandwidth is not a very significant cost for
access networks when compared to moving the data internally and maintaining the
last mile access. That being said, incremental usage can drive huge capex,
almost always in the very expensive last mile.
Most of our c
FIB is not the same as RIB...
Perfectly happy 6509, many paths, only one full table in the FIB:
BGP router identifier XXX , local AS number 11404
BGP table version is 40916063, main routing table version 40916063
494649 network entries using 71229456 bytes of memory
886903 path entries using 7095
On the sup 720 they become unshared if you carve v4 away from the default
separately, that is why I carve the other two instead.
PM
To: John van Oppen
Cc: nanog@nanog.org
Subject: Re: FW: Getting pretty close to default IPv4 route maximum for
6500/7600routers.
John, great point!
Regardless, shouldn't need more than 626K to make it to v6 and we wont need as
many for v6. That was one of the problems that v6 was design
It is generally much better to do the following:
mls cef maximum-routes ipv6 90
mls cef maximum-routes ip-multicast 1
This will leave v4 and mpls in one big pool, puts v6 to something useful for
quite a while and steals all of the multicast space which is not really used on
most deployments.
The westin is for all affective purposes connected to the building where the
conference is. It would be the closest, the others are a bit further, blocks
are very long in Bellevue so keep that in mind when looking at the maps.
-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.
, 2014 10:56 AM
To: John van Oppen; 'mark.ti...@seacom.mu'; nanog@nanog.org
Subject: Re: Experiences with IPv6 and Routing Efficiency
On 1/18/14, 10:30 AM, John van Oppen wrote:
> This is exactly what pushed us into 6PE... it was the only way to make
> performance similar to v
This is exactly what pushed us into 6PE... it was the only way to make
performance similar to v4 from a routing standpoint.
John @ AS11404
To be honest, that is the problem with most smaller ISPs, their uplinks are not
all 10G... The only way to have users who reliably get high speed tests is to
make sure one does not have 1G upstream links but obviously for a smaller
provider that would not be an option.
I think this is why our
Yep, that would be us. :) Lots of 100/100 and 1g/1g home Ethernet connections
around the Seattle area. :)
Joe was a great guy, we miss him still, one of the nicest guys I knew.
John van Oppen
Spectrum Networks
Direct: 206-973-8302
Main: 206-973-8300
Perhaps I am missing something from your advantage list, but why would you want
to exchange routing information with a network to which you don't have a
connection due to a local failure?I think you are attempting to abstract
routing from the underlying physical infrastructure a bit too much
an account is not required at least at the locations in Seattle, but an account
gets you access to the best prices if you buy in quantity.
John - AS11404
From: Carlos Alcantar [car...@race.com]
Sent: Friday, May 31, 2013 3:37 PM
To: nanog@nanog.org
Subjec
I remember it too... I had a ticket get escalated from our support group in
about 2003 of a customer who could not get any internet access... they had XP
and had been assigned a .0 IP out of a /23 we were using for a specific pop.
That /23 came out of 64.0.0.0/8 so it was clearly a bit more
I have ended up excluding .0 and .255 from our DHCP pools in larger than /24
subents due to this exact issue in the past... It is a PITA. I wish people
would update filters.
John
It probably should be noted that AS3356's local pref heirarchy is as follows:
Highest: customers of 3356
Next highest: customers of 3549
Lowest: peers
This does not really seem odd at all, and is probably what I would do if I
owned two separate networks that were going to take a long time to mer
I know we dislike BGP on small connections (even though we do it), it is an
extra administrative hassle that tends to be the most work on the smallest
connections.Customers with multiple 10Gs tend to have small numbers of BGP
related tickets than customers with a single fastE, given that, I
We have cogent in the mix, and I do have to say one gets what one pays for...
They are a no redundancy, no extra capacity kind of shop... This often is
noticeable when they have fiber cuts or equipment failures, it also results in
a lot more service affecting maintenance than our other prov
from Level3's looking glass (it sure looks like l3 is reaching the prefix in
this email via AS701 as would be expected):
BGP routing table entry for 173.79.0.0/16
Paths: (2 available, best #2)
701 19262
AS-path translation: { ALTERNET VZGNI-TRANSIT }
edge2.Dallas3 (metric 3827)
Orig
We saw the issues on the AS209 backbone as well from our vantage point here in
Seattle but we also show a circuit we have down (that rides Qwest) between
Yakima, WA and Spokane, WA. The outage corresponds to the IP issues so I
would think that it is probably the same cut affecting both the wav
We actually have a lot of the old gigabeam radios in service, they are faster
than the published specs of the airfiber links (1G full duplex vs 750 mbit/sec
fd) and lower latency due to their very simplistic design. To be honest,
from a network engineering standpoint, the gigabeams were conv
All -
I was noticing that it appears from our Seattle-based full route feed from
cogent that they may have de-peered AS4134 (or vise-versa)... anyone know
anything about this?We noticed this recently in a shift of traffic away
from cogent for traffic to and from china telecom... Now cog
Here is my little table for 128.0.0.0/21 based on our upstreams:
AS7922: Yes
AS174: No
AS2914: Yes
AS3257: Yes
AS2914: Yes
AS2828: No
AS209: Yes
John @ AS11404
We saw several customers go away this morning as well. Our network itself is
cisco so we did not see anything directly.
John van Oppen
@ AS11404.
-Original Message-
From: Tom Hill [mailto:t...@ninjabadger.net]
Sent: Monday, November 07, 2011 7:09 AM
To: nanog@nanog.org
Subject: Re
nd none of them had ever really had an issue with
this policy in terms of keeping customers. I agree with Ricky's current
comment on this thread, blocking is unfortunately necessary on the modern
consumer portions of the internet.
Thanks,
John van Oppen
-Original Message-
Fr
That does not seem to be unique to nanog.
-Original Message-
From: Brett Watson [mailto:br...@the-watsons.org]
Sent: Thursday, October 06, 2011 4:58 PM
To: nanog@nanog.org
Subject: Not operational, but related to the attendees in Philly
I'm getting a rash of emails (as are some of my co
That comment about wholesale prices is not actually quite true here in the
northwest where avoiding BPA actually sometimes results in cheaper power (ie
grant, douglas and chelan counties whoes PUDs own their own dams and are
obligated to service their customer and as non-profits actually sell to
We had a cow break down a door to a remote microwave site once...now we are
the proud owners of a generator backed electric fence at that site...Rural
physical plant issues are almost always entertaining. :)
John
-Original Message-
From: Eric J Esslinger [mailto:eesslin...@fpu
you a AS7922 sales contact if you need it, just hit me up off
list... they also have a good list of info on peeringdb for people to contact.
Thanks,
John van Oppen
Spectrum Networks AS 11404
-Original Message-
From: Oscar Caraig [mailto:oscarcar...@safe-mail.net]
Sent: Friday, Sept
i have seen many udp/80 floods as well... pretty common.
John van Oppen
Spectrum Networks / AS11404
From: Dobbins, Roland [rdobb...@arbor.net]
Sent: Tuesday, September 06, 2011 1:00 AM
To: North American Network Operators' Group
Subject: Re: DDoS
I was wondering the same thing... we have v6 enabled to about 700 users in
our native Ethernet to the home deployment here in Seattle.Unfortunately,
user routers don't seem to often support v6 resulting in only about 2-8% of
users in most buildings using it, and most of those are just peop
Why does it matter what his position is? Sounds like they had a forged LOA
from the customer and that they fixed the issue when they found out about it.
I am not sure you can ask too much more from a network operator, the best
thing we can hope for are companies that will cancel customers i
>>>I'd be happy if https://newnog.org/join.php loaded a page instead of an SSL
>>>error.
Good to see that you have working v6 connectivity. :)This is being worked
on now, it is ironically only broken in v6.
John
Yep...Seeing serious issues from our office here at AS11404, we are peered
directly and all looks good at the IP layer but all of us who wanted to
procrastinate here at the office are having trouble getting page loads to
complete. Oddly, no noc tickets yet.
John
-Original Message
GFCI breakers are very common, the slightly less common version are arc fault
breakers which are starting to show up more as well.
GFCI breakers are often required on large services, most large (new) 480v
services I have seen (1000A and larger) a have Ground fault breakers, in fact I
have seen
It is probably worth nothing that a 3-phase input in Europe is actually 240/415
volt Y (for every panel I have seen in Germany at least, even the places I have
lived there had 240/415 three phase). The normal 240v single phase outlet
circuits were the phase to neutral voltage. Obviously Euro
We saw further evidence of this on paths traversing global crossing to a
customer last night.I don't know about others but we are intending to make
some efforts to move traffic other places, this type of repeated failure is
just terrible, especially since they still continue to announce rout
I am on the technology committee of the college I attended (Whitman) and they
currently have a 200 mbit/sec via gigE link for a campus of just under 2000 and
every building has at least 1X gigE into their backbone.They are in a rural
area (walla walla, wa) but they don't generally have more
I would say for most of our customers, especially in the hosting space, a
"class C" is a /24, they just don't know networking at all and build their
hosting lans using /24s for each vlan.
Very few of the requests that we get are submitted using CIDR notation.
Personally, I think this is a big
. As of now though
we are seeing the issue as fixed and turned up GBLX again.
Thanks,
John
-Original Message-
From: Heath Jones [mailto:hj1...@gmail.com]
Sent: Thursday, October 07, 2010 9:22 AM
To: John van Oppen
Cc: Thomas Schmid; nanog@nanog.org
Subject: Re: reachability problems
: Thursday, October 07, 2010 9:24 AM
To: John van Oppen
Cc: Thomas Schmid; nanog@nanog.org
Subject: Re: reachability problems Europe->US?
It seemed from the symptoms OP was seeing, that Qwest was the issue.
Has GLBX reported to you that they are having a fault? If not, perhaps
try tagging your expor
to be black-holing
roughly 1/4 of what we were sending them.
Thanks,
John van Oppen
Spectrum Networks / AS 11404
-Original Message-
From: Thomas Schmid [mailto:sch...@dfn.de]
Sent: Thursday, October 07, 2010 6:10 AM
To: Heath Jones
Cc: nanog@nanog.org
Subject: Re: reachability problems E
The only way in which I can see facebook as required for operations is when one
is hosting apps that must interact with the facbook API. Facebook is a site
we keep an eye on from our NOC simply because it is important to a lot our
larger transit customers due to them having apps that require
We get people calling our noc numbers pretty often trying to report abuse for
other people's networks... that is always fun
John van Oppen / AS11404
-Original Message-
From: Randy Bush [mailto:ra...@psg.com]
Sent: Wednesday, October 06, 2010 3:16 PM
To: Matthew Huff
Cc: &#x
available "soon" and will replace the current tunneled options
they have.
Thanks,
John van Oppen
Spectrum Networks (AS11404)
-Original Message-
From: Jared Mauch [mailto:ja...@puck.nether.net]
Sent: Wednesday, March 10, 2010 11:19 AM
To: Charles Mills
Cc: NANOG list
Subject: Re: IP
The best OTDR data I have ever gotten prior to signing an agreement for strands
is the readings from another pair on the same route.That being said most
dark fiber agreements have some sort of minimum performance specifications in
them.
John van Oppen
Spectrum Networks LLC
Direct
I think that is a pretty standard procedure. We generally give our
users 12 hours to remove the content before we null-route the IP...
The only time this does not apply is with active spam sources, simple
and quite effective.
Thanks,
John van Oppen
Spectrum Networks LLC
Direct: 206.973.8302
No BGP looking glass but there is a traceroute gateway in AS702:
http://zelfservice.nl.uu.net/netwerk/pops/trace.uunet
John van Oppen
Spectrum Networks LLC
Direct: 206.973.8302
Main: 206.973.8300
Website: http://spectrumnetworks.us
-Original Message-
From: R. Scott Evans [mailto:na
XO has been offering a product lately that is all routes except level3
and sprint which leads me to believe that they pay both of those
peers...
John van Oppen
Spectrum Networks LLC
Direct: 206.973.8302
Main: 206.973.8300
Website: http://spectrumnetworks.us
-Original Message-
From
To come up with an accurate recommendation one really needs to know your
budget, on that distance speeds up to 1 gbit/sec are possible if you
spend enough on the radios...Do you have some cost and desired
throughput parameters to guide everyone's recommendations?
-Original Message-
Fr
NTT (2914) and GBLX (3549) both do native v6... most everyone else on
the tier1 list does tunnels. :(
There are some nice tier2 networks who do native v6, tiscali and he.net
come to mind.
-John
-Original Message-
From: Paul Timmins [mailto:p...@telcodata.us]
Sent: Thursday, June 11,
h are
geostationary):
http://en.wikipedia.org/wiki/Geostationary_orbit
perhaps further comments can go to the discussion pages on Wikipedia
since I would wager a very small number of us push any serious number of
bits via satellite.
John van Oppen
Spectrum Networks LLC
Direct: 206.973.8302
Main: 206.973
Because it gave you the IP of ns1 & ns2.push.mobi in the additional section?
Looks like a pretty normal answer for a TLD server.
John van Oppen
Spectrum Networks LLC
206.973.8302 (Direct)
206.973.8300 (main office)
-Original Message-
From: Anton Zimm [mailto:anton.z...@gmail
I agree, spamhaus has always been great.
We were on a few feedback loops and senderbase.org did not show much for that
subnet... anyway solved now.Got the ex-customer's other ISP to block the
announcement since we killed it a while ago, also removed the SWIP. ;)
John van
We had complaints about our entire ASN being listed too, due to a bunch of
infected hosts in a sub-allocated /23 (out of our nearly /16 of space). The
best part is they don't bother to report the abuse, they just block the entire
ASN, not terribly productive.
John van Oppen
Spectrum Net
interested in.
Thanks,
John van Oppen
Spectrum Networks LLC (AS11404)
Direct: 206.973.8302
Main: 206.973.8300
Website: http://spectrumnetworks.us
-Original Message-
From: Kai Chen [mailto:kch...@eecs.northwestern.edu]
Sent: Tuesday, March 31, 2009 7:56 PM
To: na...@merit.edu
Subject
thus I never purchased that service when looking into it.
On the peering/transit side, the guys at national (AS7922) are really
professional (albeit a bit overworked). Our peering link to them is
awesome for getting rid of Comcast user complaints. :)
John van Oppen
Spectrum Networks LLC
of our customers speaking BGP had no issue just three out of
about 25.
What do people think is a reasonable maximum as-path length to enforce
at ones edge?
John van Oppen
Spectrum Networks LLC
Direct: 206.973.8302
Main: 206.973.8300
Website: http://spectrumnetworks.us
-Original Message
ref 50, valid, internal, best
Community: 11404:1000 11404:1040
agg2-sea-A>
John van Oppen
Spectrum Networks LLC
Direct: 206.973.8302
Main: 206.973.8300
Website: http://spectrumnetworks.us
-Original Message-
From: Andy Davidson [mailto:a...@nosignal.org]
Sent: Monday, Febru
500
John van Oppen
Spectrum Networks LLC
Direct: 206.973.8302
Main: 206.973.8300
Website: http://spectrumnetworks.us
-Original Message-
From: Matt Liotta [mailto:mlio...@r337.com]
Sent: Monday, February 16, 2009 8:55 AM
To: nanog@nanog.org
Subject: anyone else seeing very long AS
were paths that worked, they were just wrong and we ended up just
throwing a prefix-list on that peer.
The thing is, one basically has to trust one's transit providers which
don't always filter well. Given this trusting one's peers at least
some-what does not seem too out the
indicated. It was a good advertisement for having spare capacity
handy.
John van Oppen
Spectrum Networks LLC / AS11404
-Original Message-
From: Scott Weeks [mailto:sur...@mauigateway.com]
Sent: Tuesday, January 20, 2009 10:28 AM
To: nanog@nanog.org
Subject: Re: Inauguration
would cancel them just due to the lack of RADB support but at
least they have no uRPF filters so I have taken to just doing batch
prefix-list updates with them every few months as my sanity-saving
solution.
John van Oppen
Spectrum Networks LLC
Direct: 206.973.8302
Main: 206.973.8300
Website:
RTG is a great solution for 95th percentile if you are building your own
system since it puts everything into an SQL database and comes with a
nice php front end to start with.
John van Oppen
Spectrum Networks LLC
206.973.8302 (Direct)
206.973.8300 (main office)
-Original Message
allocations were all
originated from downstream ASNs from our network.
If anyone has an engineering contact at cogent (ie not the support
contact) I would love to talk to them as it seems support department
front-end is the problem and not necessarily cogent's actual policies.
Thanks,
John van
to avoid the arguments with the support monkeys.
I should note that this is actually the second time I have had this
issue (the last time was with one of our customers and their cogent
connection) even though we only turned up our service recently.
John van Oppen
AS11404
I know I have experienced the engineering department there as well, the
best one was when they wanted paper documentation for every route I
asked to have in our filters... (and they were incapable of using
RADB). It was especially odd since we have > 80 of our own peers and
three other transit p
pricing at larger commits either (I won't buy cogent if they don't at
least match the terms of our cheapest large-network transit provider).
:)
John van Oppen
Spectrum Networks LLC
206.973.8302 (Direct)
206.973.8300 (main office)
-Original Message-
From: manolo [mailto:[EMAIL PROT
88 matches
Mail list logo
