My experience with Juniper has been mixed, experience with 12.X and 13.X made
me wonder if I had a poor understanding of how to do a proper decode or if
Juniper's implementation itself had issues as I would often get incomplete
results.
We've now grab over XML and have been pleased with that ch
I'm not against the theory of what is being proposed, but I was surprised to
see little discussion of this announcement on list.
Upon examination on my view of the DFZ from AS3128 I see over 400 upstream
routes falling into this category, mostly in the 64512 - 65534 range. Based on
our flow ba
Couldn't one make the same argument with respect to filtering private ASNs from
the global table? Unlike filtering of RFC1918 and the like a private ASN in
the path isn't likely to leak RFC1918 like traffic, yet I believe several major
ISPs have done just that. This topic was discussed ~1 year
While attempting to focus on ISPs there is still [unbelievably] a vendor
support issue. You may consider this a procurement failure, but the
fact remains that some products [Cisco me3400e] have yet to implement
support.
-Michael
On 8/9/2011 9:24 AM, Nick Hilliard wrote:
On 09/08/2011 14:47,
nt on entry. Fine, that is their choice. There are other
vendors offering 4 byte ASN in simliar products at or near this price
point and we'll probably have to move to them.
-Michael
On 8/9/2011 10:38 AM, Nick Hilliard wrote:
On 09/08/2011 15:45, Michael Hare wrote:
While attempting to foc
On 8/10/2011 8:46 PM, William Herrin wrote:
On Wed, Aug 10, 2011 at 9:32 PM, Owen DeLong wrote:
Someday, I expect the pantry to have a barcode reader on it connected back
a computer setup for the kitchen someday. Most of us already use barcode
readers when we shop so its not a big step to home
You seem to have accidentally put an 'R' between your E and X ;)
On 9/14/2011 4:05 PM, Scott Weeks wrote:
--- brandon.galbra...@gmail.com wrote:
From: Brandon Galbraith
Juniper: Who needs to waste time with pathetic marketing videos when you're
gear just works.
---
AS2381 has also received them, we are no further along in this than you are.
On 1/19/2012 2:59 PM, Jay Hennigan wrote:
We have received three emails from the US Department of Justice Victim
Notification System to our ARIN POC address advising us that we may be
the victim of a crime. Headers loo
Martin-
I represent a statewide educational network running Juniper gear that is a
quasi-enterprise. I think efforts depend on size and type of network. We are
testing an approach that involves;
1) whitelisting known local resolvers, well behaved cloud DNS resolvers.
2) on ingress, policing
Saku-
> In internal network, instead of having a default route in iBGP or IGP,
> you should have the same loopback address in every full DFZ router and
> advertise that loopback in IGP. Then non fullDFZ routers should static
> route default to that loopback, always reaching IGP closest full DFZ
>
Mark (and others),
I used to run loose uRPF on peering/transit links for AS3128 because I used to
think that tightening the screws was always the "right thing to do".
I instrumented at 60s granularity with vendor J uRPF drop counters on these
links. Drops during steady state [bgp converged]
Re: Adam's advice about IOS/XR SNMP access to VRF, while this experience may be
a bit dated [IOS XR 5.x], in production we have used "snmp-server community-map
$x context $y". I will say we weren't pleased, we noticed that context
switches didn't work well. For example if our poller tried to s
Paul-
You said: "... would decide to configure MPLS paths between Chicago and distant
international locations ..."
AS3128 runs MPLS and it's probable someone might correct me here, but for a IGP
backbone area I think it's common for there to be a full mesh of LSPs via
either LDP, RSVP, SR etc.
John-
This is little consolation, but at AS3128, I see the same thing to our
downstream at times, claiming to come from both 13335 and 15169 often
simultaneously at the tune of 25Kpps , "assuming it's not spoofed", which is
pragmatically impossible to prove for me given our indirect relationshi
x27;s an interesting comment about DNSSEC that I hadn't considered.
-Michael
From: Damian Menscher
Sent: Monday, December 4, 2023 12:21 PM
To: Michael Hare
Cc: John R. Levine ; nanog@nanog.org
Subject: Re: What are these Google IPs hammering on my DNS server?
Google Public DNS (8.8.8.8) attemp
15 matches
Mail list logo
