Hi,
in the IETF transport area there are discussions on DSCP interconnection
between networks. It's quite common that operators clear (bleach) the DSCP
codepoints when receiving packets from other operators, turning everything
into BE (best effort) traffic. Historically CS1 has been proposed
On 2/Jul/15 09:14, Mikael Abrahamsson wrote:
>
>
> It would be great if there could be an operational document as well,
> giving recommendations on how to configure the above, and it would be
> great if it could be done with lots of operator input into the matter.
Given that some networks don'
Then again, maybe my tinfoil hat is too tight.
Recent history would seem to indicate that, if anything, most of us were
skimping a bit on tinfoil.
That said, the recent cuts in CA have received a lot of attention and
passed into the mainstream media; that seems, imho, a bit too public for
t
I've referenced article 645 before, but you have to look at anything
upstream or downstream of the PDU as well, as the system as a whole needs
to be within standards.
On Wed, Jul 1, 2015 at 11:42 AM, William Herrin wrote:
> Hi Folks,
>
> Do you know of any regulations, standards or publications
Really, it's got to be something dead stupid. Hoping to borrow 5
minutes of someone's time. Replies on or off list are fine.
I've reduced it to a simple config:
BIRD:
protocol bgp {
description "ExaBGP-local";
local as 12345;
allow local as 1;
neighbor 10.0.0.2 as 12345;
next hop keep;
FYI, if the static is moved up within the neighbor definition, it works.
So this is an Exa related issue/feature and not a problem with BIRD.
I'll move the noise to the Exa list if needed.
~Randy
On 07/02/2015 9:13 am, Randy wrote:
Really, it's got to be something dead stupid. Hoping to b
Exactly… It’s not an issue, it’s expected behavior.
If you move the static up within the neighbor definition, it becomes an Anchor
Route and Exa knows you want it announced.
If you leave it in the static routes section, then you either need a
redistribution policy from static to bgp (not recomm
I think you overestimated exabgp's dead simplicity.
After some more testing, I found moving the route higher in the config
file (before the neighbor definition rather than inside it), it
propagates. So order matters more than anything. You have to define
routes either BEFORE or WITHIN neig
To demonstrate -- order is everything -- this works:
group gixlg {
hold-time 180;
local-as 12345;
router-id 10.0.0.2;
family {
ipv4 unicast;
}
static {
route 1.2.3.4/32 next-hop 4.3.2.1;
}
neighbor 10.0.0.1 {
router-id 10.0.0.2;
local-ad
On Wed 2015-Jul-01 17:02:13 +0200, Mark Tinka wrote:
On 1/Jul/15 16:54, Nick Hilliard wrote:
you probably want to ignore more rpsl constructs and depend solely on
as-sets, aut-nums and route/route6 objects. RPSL is not going to live up
to your expectations.
Honestly, I'm ambivalent about
On Wed, Jul 1, 2015 at 1:02 PM, Keith Medcalf wrote:
> No-Such-Agency typically taps communication lines by
> "back-hoe accident" of some sort on the path they are
> interested in tapping. Then again, maybe my tinfoil hat is too tight.
I'm gonna go with "too tight."
My main reason is that there'
Sluggish Internet via TWC and Sprint 3G/4G in Marina Del Rey area. Any
outages reported?
Regards,
David
UUCP.
Someone had to mention it. So I did. And BITNET I guess.
--
-Barry Shein
The World | b...@theworld.com | http://www.TheWorld.com
Purveyors to the Trade | Voice: 800-THE-WRLD| Dial-Up: US, PR, Canada
Software Tool & Die| Public Access Internet
Hello Randy,
The current configuration parser is currently progressive: what exists
when the neighbor is created (or in the neighbor group) is what will be
associated (which is not really ideal) hence why I have passed the last
three weeks totally rewriting it in view of version 4.0. This is s
After being down since early May 2014, www.att.net is now back up over IPv6
since 7:29 pm U.S. Central.
Sites that we track that were up but remain down over IPv6 are
www.charter.com, www.dnssec.comcast.net, and www.globalcrossing.com.
Frank
John Curran gets a quote; NBC gets the etymology of "IPv4" wrong.
Just keep them away from Jim Fleming.
http://www.nbcnews.com/news/us-news/internet-now-officially-too-big-ip-addresses-run-out-n386081
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2/Jul/15 19:48, Hugo Slabbert wrote:
>
>
> Jeebuz; you accept /128s? Perhaps "le 24 & le 48"?
Yes, that was a typo - /48 :-).
Mark.
-BEGIN PGP SIGNATURE-
iQIcBAEBCAAGBQJVlixgAAoJEGcZuYTeKm+GLRQP/2HjuqFJW+pzhuH9qSbltl1D
hz//dUVzJnG
17 matches
Mail list logo
