I'm seeing odditiies when trying to traffic-engineering my way around an AS
3356-to-7922 performance issue.
I buy transit from 3356 and announce my /19 to 3356. I set traffic engineering
community 65000:7922 to supress announcement of it from 3356 to 7922.
When I do that, at route-server.newyork
On Tue, Sep 10, 2019 at 04:42:10PM +, Martijn Schmidt wrote:
> Hi Will,
>
> Unlike AS2914 which purely interconnects with AS7922, it seems that AS3356
> also has direct interconnections to the various Comcast subsidiary networks
> which are hidden from the DFZ through no-export communities..
We developed a web/mysql-based front-end that our noc uses for all DNS
ops, so the NOC never touches zone files directly. So it was easy to
just add a feature that provides additional syntax for ipv6 PTRs...
So for example in zone
0.0.0.0.d.c.b.a.8.B.D.0.1.0.0.2.ip6.arpa
we can enter
:
I use:
http://www.mastechpowersupply.com/dc-power-supply/switching-power-supply/volteq-power-supply-hy5020ex-50v-20a-over-voltage-over-current-protection/prod_61.html
The output is changable from positive to negative ground by moving the
shorting bar to ground from the - output to the + side.
If
On Thu, Apr 03, 2014 at 09:06:57PM -0700, George Herbert wrote:
> Sadly, right now that either means your own real clock, or WWV. The
> cellphone time is (as far as I know, for the networks I saw data on) all
> coming off GPS.
>
> Fortunately real clocks are coming way down in cost.
There are c
Cogent from various west coast USA locations seems to have trouble getting to
some Comcast ipv6 addresses:
Cogent LG Los Angeles to www.comcast6.net
traceroute to 2001:558:fe16:7:69:252:216:215 (2001:558:fe16:7:69:252:216:215),
30 hops max, 80 byte packets
1 2001:550:1:317::1 (2001:550:1:317::
We've run into an issue with a customer that has been confounding us for a few
months as we try to design what they need.
The customer has a location in the relative middle of nowhere that they are
trying to build a protected OC3 to. Ultimately, their traffic on it will be
packet data (IP/ether
On Thu, Sep 06, 2012 at 06:00:37PM +0100, Nick Hilliard wrote:
> Not sure if I see the problem here. Show them the bill for an OC3 service,
> and then show them the bill for the equivalent ethernet service. This
> usually works for me. If they want to pay for OC3 when there's no
> compelling rea
ght and sold wholesale this way too? Is there generally a
price
premium over the more normal client signals?
-Will Orton
We have an old Wiltel DS3 homed from their Anaheim POP... all traffic that's
not going to destinations on the old 7911 backbone seems to be backhauled to
Level3 in San Jose before getting anywhere else, like so:
1 (internal)
2 (internal)
3 (internal)
4 anhmca1wcx1-atm10-0-0.wcg.net (64.2
10 matches
Mail list logo
