Subject: RARE user and assistance email list
List archive
- From: "Tim Chown via groups.io" <>
- To: "" <>, "" <>
- Cc: "" <>, Bruno Rijsman <>, "Jeffrey (Zhaohui) Zhang" <>, Jeff Tantsura <>, Jordan Head <>, "" <>, Mariano Scazzariello <>, famfo <>, "" <>, "" <>, "" <>
- Subject: Re: [RARE-users] [freertr] RIFT interop in IETF118 hackathon?
- Date: Mon, 2 Oct 2023 08:27:40 +0000
- Accept-language: en-GB, en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=jisc.ac.uk; dmarc=pass action=none header.from=jisc.ac.uk; dkim=pass header.d=jisc.ac.uk; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=D1okfavseb5KegJLoTN+gLqu3gIPLMrWBOKYpe7YRHE=; b=cPSzXXSAnFIK0cC/r2tCLckLKArxHin1XCYpOss+aQ66mPLlFvX+shxpAE+WgoSd9FraBte6ti7PxlYxbDmolU+kD/uCFAfspJmC1bs6GdPd8MAfgQS5gzUssUQP2yG7yAJ6poSCr1HrHF0aETCylIi/37rSJV34UO4lmep38Bh3r39HExau5SFESdyYlw8WvdXNlOg41QHkF3MYxLmPt/DL/oZmFZpTyHZdHMSnjXtdKbhvewlbibnljrtQbWaFiV+MHED16iDzUWQQ8e4g63hHid9K34nrLp3jMLWPSSnH68pxlt5HR68gPEcVr1g8CzjNujneAXTux4pIMJ8GXw==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=CLtACzTMURX2OjRBfLmtUtXT1doV5UoJAP6zyzAEawIQV0WNJuXjfidt9CAd9dMeQz5w+7q88w2hExuo3/r1UuOcphW7SEfRIU0wNYuUIDYE/vKdmMMAPUrW+U3wmZeBE7qP4vtsjHo95K1W2tHxiPgFMJrr5o7aejwTAgYMGo6oUxwYJ1dzmogNx6vAPdEi9WI3UjSNAJD/MG7AWzftwdDjqbfGsxGwsNmPTbit2SzDrRceNt9bYKCv74wg5y3Beq76ANICW6ES6fNzN8BP3o5RLZb1rrIhA/E47W9B4/QGQsxV8UvGD0RJCqOK2T+wDCu1raVuY+JjvSDsKh116w==
- List-id: <freertr.groups.io>
- Mailing-list: list ; contact
Hi,
The Prague hackathon details are now all up at https://www.ietf.org/how/runningcode/hackathons/118-hackathon/.
Tim
On 1 Oct 2023, at 10:48, Antoni Przygienda via groups.io <> wrote:
I don’t remember having some pdf stored. You implemented some LIEs/hello stuff and then I think we pinged each other with themMpls-sr is doable. No real demand I see for the moment from customers here. If anything folks run SRMPLSoUDP in DC towards the DCI and that’s a pretty good technology in terms of simplicity, solving usecases they haveMost interesting work right now iw the new KV update Jordan is on and DF+ rift extensions that are starting. And multicast would be great since the joined tree (s) could be used for lots other clever stuff 😉
- Tony
Juniper Business Use Only
From: mc36 <>
Date: Sunday, 1 October 2023 at 11:24
To: Antoni Przygienda <>, Bruno Rijsman <>, <>
Cc: Jeffrey (Zhaohui) Zhang <>, Jeff Tantsura <>, Jordan Head <>, <>, Mariano Scazzariello <>, famfo <>, <>, <>, <>
Subject: Re: [freertr] RIFT interop in IETF118 hackathon?
[External Email. Be cautious of content]
last but not least, back to the bits, do you (jeff, prz) have the 1 year old pdfs about the interop or do i have to recreate it?! XDDDDDD
moreover whats with ipv6, we already ship it, and whats with the rift+mpls-sr draft, please?!
br,
cs
On 10/1/23 11:21, mc36 wrote:
> so its not c-tac, j-tac, z-tac, etc..... its foss, our tac is groups.io, that is, the p2mp publicity right?!....
>
> On 10/1/23 11:20, mc36 wrote:
>> ok straightening the english, foss is good to get pushed, but does not likes p2p in general....
>>
>> just do not shrinken the lists like we also dont remove your ext-asdfasdfsa management mail distributions....
>>
>> if not intentionally, then untentionally, these are written to the disks then wiped securely 10-15 years later on a raid10zzz replacement.... bruhh....
>>
>> br,
>>
>> cs
>>
>>
>>
>>
>> On 10/1/23 11:13, mc36 wrote:
>>> +to, the 2 affected lists, dn42.dev is a 1000ish test ebgp internet, v4 v6 equally....
>>>
>>> freertr is a node there providing mcast ripe route beacons (ietf world tour) etc services there for fun....
>>>
>>> br,
>>>
>>> cs
>>>
>>>
>>>
>>> On 10/1/23 11:09, mc36 wrote:
>>>> sooo i mean fix your ebgps in the 1st place, instead....
>>>>
>>>> not u but in generally speaking... its the same what "the-routing-beacons" are measuring 0-24 on the clearnets,
>>>>
>>>> what ietf shittests for decades, etc....
>>>>
>>>> bruhh.....
>>>>
>>>>
>>>>
>>>>
>>>> -------- Forwarded Message --------
>>>> Subject: Re: Fwd: Re: [dn42] DN42 Mailing List - Digest #191
>>>> Date: Sun, 1 Oct 2023 11:05:28 +0200
>>>> From:
>>>> To: jrb0001 <>,
>>>>
>>>>
>>>> maaaaan, the guy wrote that he had the issues in their networks... noone except he had it... ibgp, loops... looolz.... XDDDDDDD
>>>>
>>>> On 10/1/23 10:26, jrb0001 wrote:
>>>> > I am not surprised that we have way more issues than clearnet. dn42 is a network for learning and experimenting after all. If people learn something by accidentally
>>>> creating ghosts, then that's perfectly fine. But we definitely have a huge issue with long term maintenance (people loosing interest but forget to disconnect their stuff and
>>>> return the resources). But I have no idea how to solve this and working around it by disconnecting somebody is a huge effort, if it is even possible at all.
>>>> >
>>>> > Am 01.10.23 um 09:44 schrieb :
>>>> >> most importantly, the results, that is, 5% of the times the prefixes ghosted back.... :(
>>>> >>
>>>> >> p4deb-dn42>
>>>> >> p4deb-dn42>show ipv4 ghosthunt 24 status
>>>> >> info userReader.cmdEnter:userReader.java:1175 command p4deb-dn42>show ipv4 ghosthunt 24 status from console
>>>> >> category curr times ago last
>>>> >> execute true 177275 00:00:00 2023-10-01 09:44:01
>>>> >> advertise false 14399 01:33:01 2023-10-01 08:10:59
>>>> >> withdraw true 162876 00:00:00 2023-10-01 09:44:01
>>>> >> ghost false 0 never 1970-01-01 01:00:00
>>>> >> pass true 177227 00:00:00 2023-10-01 09:44:01
>>>> >> attrib err 0 0 never 1970-01-01 01:00:00
>>>> >> attrib ok 0 14399 01:33:00 2023-10-01 08:11:00
>>>> >>
>>>> >> p4deb-dn42>show ipv4 ghosthunt 42 status
>>>> >> info userReader.cmdEnter:userReader.java:1175 command p4deb-dn42>show ipv4 ghosthunt 42 status from console
>>>> >> category curr times ago last
>>>> >> execute true 177276 00:00:00 2023-10-01 09:44:02
>>>> >> advertise false 14399 01:33:02 2023-10-01 08:10:59
>>>> >> withdraw true 162877 00:00:00 2023-10-01 09:44:02
>>>> >> ghost false 10103 01:33:02 2023-10-01 08:10:59
>>>> >> pass true 76501 00:00:00 2023-10-01 09:44:02
>>>> >> attrib err 0 0 never 1970-01-01 01:00:00
>>>> >> attrib ok 0 0 never 1970-01-01 01:00:00
>>>> >>
>>>> >> p4deb-dn42>
>>>> >> p4deb-dn42>
>>>> >> p4deb-dn42>
>>>> >> p4deb-dn42>
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >> On 10/1/23 09:16, wrote:
>>>> >>> hihi,
>>>> >>>
>>>> >>> can u please send this message in?! seemingly im moderated not just on irc but on the lists also....
>>>> >>>
>>>> >>> moreover, whats with our 1/2 peerings please? it seems down for month now... :)
>>>> >>>
>>>> >>> 4242421955 - nop-mnt
>>>> >>>
>>>> >>> cs
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> p4deb#show ipv4 bgp 42 summary
>>>> >>> neighbor as ready learn
>>>> sent uptime
>>>> >>> 172.21.83.90 4242422308 yes 657 507 2d0h
>>>> >>> 172.23.215.168 4242420119 yes 650 620 2d0h
>>>> >>> 172.23.215.170 4242420119 no 0 0 00:00:00
>>>> >>> 172.23.236.56 76190 yes 644 234 1d16h
>>>> >>>
>>>> >>> p4deb#show ipv4 route dn42 172.23.215.170 | include interf
>>>> >>> alt0 interface tunnel929
>>>> >>>
>>>> >>> p4deb#show running-config interface tunnel929
>>>> >>> interface tunnel929
>>>> >>> description jrb0001 nl1
>>>> >>> tunnel key 21955
>>>> >>> tunnel vrf inet
>>>> >>> tunnel protection tun929
>>>> >>> tunnel source sdn1
>>>> >>> tunnel destination 2001:19f0:5001:36ad:5400:2ff:fe17:ed2e
>>>> >>> tunnel mode wireguard
>>>> >>> vrf forwarding dn42
>>>> >>> ipv4 address 172.23.215.171 255.255.255.254
>>>> >>> ipv6 address fd40:cc1e:c0de::131 ffff:ffff:ffff:ffff:ffff:ffff:ffff:fff0
>>>> >>> ipv6 prefix-suppress
>>>> >>> template template42
>>>> >>> no shutdown
>>>> >>> exit
>>>> >>> !
>>>> >>>
>>>> >>> p4deb#
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> -------- Forwarded Message --------
>>>> >>> Subject: Re: [dn42] DN42 Mailing List - Digest #191
>>>> >>> Date: Sun, 1 Oct 2023 08:50:39 +0200
>>>> >>> From:
>>>> >>> To: <>
>>>> >>>
>>>> >>> mornin' hawkins,
>>>> >>>
>>>> >>> in hope your n0twork does _not_ floods/stucks on the prefixes alone, that would be the 1st to stop doing...
>>>> >>>
>>>> >>> i personally consider each of the below extreme as dn42 tends to be way heavier meshed than anything else...
>>>> >>>
>>>> >>> i personally run a ghosthunter service in dn42 also, it have much more hits than anything else...
>>>> >>>
>>>> >>> route measures withdrawal 2 hours on the clearnets, here it tends to 3-4 hours and still alarms weekly..
>>>> >>>
>>>> >>> https://urldefense.com/v3/__https://wiki.dn42.dev/gollum/commit/8184b44bb711c8e8876518a89a106a70bb84d0c4__;!!NEt6yMaO-gk!Fk002HobEosSSvmAU3SkpBVOxun6RklVupSK9PDrFAP1E45omWXvcE61HoVtRkordW8qwA$
>>>> >>>
>>>> >>> if you mrt/bmp just this asn then you can see the prefixes preiodically appearing, disappearing...
>>>> >>>
>>>> >>> from this info you can have the guesstimate to blame a set of asns... the more the observers the sharpen the guesstimation....
>>>> >>>
>>>> >>> fun fact i run this in production clearnet also with a different set of prefixes do advertised publicly,
>>>> >>>
>>>> >>> not a single alarmings seen and it usually withdrawals in 15-30 minutes at least, depending on the observed period....
>>>> >>>
>>>> >>> path attributes are a different thing, packet delivery per ip protocols or inner markings (gre's inner protocol type marker) are yet another question.....
>>>> >>>
>>>> >>> ps: the timestamps below are in Z+0100(cet)+-leapseconds (the original ".mil." cctlds' default timezone 4 short:)
>>>> >>>
>>>> >>> br,
>>>> >>>
>>>> >>> cs
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> p4deb>show ipv4 bgp 42 unicast pathlen 10-1111
>>>> >>> 2023-10-01 08:38:07
>>>> >>> prefix hop metric aspath
>>>> >>> 10.127.134.0/26 172.23.215.168 20/100/0/0 4242420119 4242422601 4242422825 4242422092 4242421288 4242421331 4242421298 4242423618
>>>> 4242423947 4242421817 4242422032 4201272032
>>>> >>> 10.127.134.128/25 172.23.215.168 20/100/0/0 4242420119 4242422601 4242422825 4242422092 4242421288 4242421331 4242421298 4242423618 4242423947
>>>> 4242421817 4242422032 4201272032
>>>> >>> 10.127.134.192/26 172.23.215.168 20/100/0/0 4242420119 4242422601 4242422825 4242422092 4242421288 4242421331 4242421298 4242423618 4242423947
>>>> 4242421817 4242422032 4201272032
>>>> >>> 172.20.39.80/28 172.23.215.168 20/100/0/0 4242420119 4242422601 4242422825 4242422092 4242421123 4242423088 4242421331 4242421298
>>>> 4242423618 4242423947 4242422189 4242421350
>>>> >>> 172.20.128.80/29 172.23.215.168 20/100/0/0 4242420119 4242422601 4242422825 4242422092 4242423088 4242421331 4242421298 4242423618
>>>> 4242423947 4242421080 4242421588 4242422668
>>>> >>> 172.20.209.64/26 172.23.215.168 20/100/0/0 4242420119 4242422601 4242422825 4242422092 4242423088 4242421123 4242422633 4242421123
>>>> 4242423668 4242423914 4242423947
>>>> >>> 172.20.209.80/29 172.23.236.56 20/100/0/0 76190 64719 4242422825 4242422092 4242423914 4242421888 4242421123 4242422633 4242421123
>>>> 4242423088 4242420212 4242421817 4242423947
>>>> >>> 172.20.209.96/29 172.23.215.168 20/100/0/0 4242420119 4242422601 4242422825 4242422092 4242423088 4242420458 4242421080 4242421123
>>>> 4242422633 4242423914 4242423668 4242421123 4242423618 4242423947
>>>> >>> 172.20.209.120/29 172.23.215.168 20/100/0/0 4242420119 4242422601 4242422825 4242422092 4242423088 4242420458 4242421080 4242421123 4242422633
>>>> 4242423914 4242423668 4242421123 4242423618 4242423947
>>>> >>> 172.23.0.80/32 172.23.215.168 20/100/0/0 4242420119 4242423088 4242422825 4242422092 4242421722 4242422633 4242421123
>>>> 4242422225 4242423947 4242422601
>>>> >>>
>>>> >>> p4deb>show ipv6 bgp 42 unicast pathlen 10-1111
>>>> >>> 2023-10-01 08:38:11
>>>> >>> prefix hop
>>>> metric aspath
>>>> >>> fd10:127:64:fffc::/64 fd40:cc1e:c0de::282 20/100/0/0 4242422308 4242423914 4242420604 4201270016 4201270016 4201270016 4201270016 4201270016 4201270016
>>>> 4201270016
>>>> >>>
>>>> >>> p4deb>show ipv4 bgp 42 unicast asmid 4242423947
>>>> >>> 2023-10-01 08:38:26
>>>> >>> prefix hop metric aspath
>>>> >>> 10.127.134.0/26 172.23.215.168 20/100/0/0 4242420119 4242422601 4242422825 4242422092 4242421288 4242421331 4242421298 4242423618
>>>> 4242423947 4242421817 4242422032 4201272032
>>>> >>> 10.127.134.128/25 172.23.215.168 20/100/0/0 4242420119 4242422601 4242422825 4242422092 4242421288 4242421331 4242421298 4242423618 4242423947
>>>> 4242421817 4242422032 4201272032
>>>> >>> 10.127.134.192/26 172.23.215.168 20/100/0/0 4242420119 4242422601 4242422825 4242422092 4242421288 4242421331 4242421298 4242423618 4242423947
>>>> 4242421817 4242422032 4201272032
>>>> >>> 172.20.39.80/28 172.23.215.168 20/100/0/0 4242420119 4242422601 4242422825 4242422092 4242421123 4242423088 4242421331 4242421298
>>>> 4242423618 4242423947 4242422189 4242421350
>>>> >>> 172.20.128.80/29 172.23.215.168 20/100/0/0 4242420119 4242422601 4242422825 4242422092 4242423088 4242421331 4242421298 4242423618
>>>> 4242423947 4242421080 4242421588 4242422668
>>>> >>> 172.23.0.80/32 172.23.215.168 20/100/0/0 4242420119 4242423088 4242422825 4242422092 4242421722 4242422633 4242421123
>>>> 4242422225 4242423947 4242422601
>>>> >>> 172.23.114.96/27 172.23.236.56 20/100/0/0 76190 4242422092 4242422825 4242422601 64719 4242423947 4242423088 4242421757
>>>> >>>
>>>> >>> p4deb>show ipv4 bgp 42 unicast asend 4242423947
>>>> >>> 2023-10-01 08:38:31
>>>> >>> prefix hop metric aspath
>>>> >>> 172.20.209.64/26 172.23.215.168 20/100/0/0 4242420119 4242422601 4242422825 4242422092 4242423088 4242421123 4242422633 4242421123
>>>> 4242423668 4242423914 4242423947
>>>> >>> 172.20.209.80/29 172.23.236.56 20/100/0/0 76190 64719 4242422825 4242422092 4242423914 4242421888 4242421123 4242422633 4242421123
>>>> 4242423088 4242420212 4242421817 4242423947
>>>> >>> 172.20.209.88/29 172.23.215.168 20/100/0/0 4242420119 4242422601 4242422825 4242422092 4242423088 4242423947
>>>> >>> 172.20.209.96/29 172.23.215.168 20/100/0/0 4242420119 4242422601 4242422825 4242422092 4242423088 4242420458 4242421080 4242421123
>>>> 4242422633 4242423914 4242423668 4242421123 4242423618 4242423947
>>>> >>> 172.20.209.120/29 172.23.215.168 20/100/0/0 4242420119 4242422601 4242422825 4242422092 4242423088 4242420458 4242421080 4242421123 4242422633
>>>> 4242423914 4242423668 4242421123 4242423618 4242423947
>>>> >>>
>>>> >>> p4deb>show ipv4 bgp 42 unicast asbeg 4242423947
>>>> >>> 2023-10-01 08:38:35
>>>> >>> prefix hop metric aspath
>>>> >>>
>>>> >>> p4deb>show ipv4 bgp 42 unicast database 172.20.209.96/29
>>>> >>> 2023-10-01 08:38:49
>>>> >>> id category value
>>>> >>>
>>>> vrf dn42:4
>>>> >>> ipver 4
>>>> >>>
>>>> rd 0:0
>>>> >>> original rd 0:0
>>>> >>> prefix
>>>> 172.20.209.96/29
>>>> >>> prefix network 172.20.209.96
>>>> >>> prefix broadcast 172.20.209.103
>>>> >>> prefix wildcard ::7
>>>> >>> prefix netmask ffff:ffff:ffff:ffff:ffff:ffff:ffff:fff8
>>>> >>>
>>>> nlri n/a
>>>> >>> alternates 2
>>>> >>> alternate #0 candidate=true best=true
>>>> >>> alt0 type bgp4 42
>>>> >>> alt0 source 172.23.215.168
>>>> >>> alt0 validity 0
>>>> >>> alt0 only to customer 0
>>>> >>> alt0 segrout index 0
>>>> >>> alt0 segrout old base 0
>>>> >>> alt0 segrout base 0
>>>> >>> alt0 segrout size 0
>>>> >>> alt0 segrout offset 0
>>>> >>> alt0 segrout prefix null
>>>> >>> alt0 bier index 0
>>>> >>> alt0 bier old base 0
>>>> >>> alt0 bier base 0
>>>> >>> alt0 bier range 0
>>>> >>> alt0 bier size 0-32
>>>> >>> alt0 updated 2023-10-01 05:22:48 (03:16:00 ago)
>>>> >>> alt0 version 74042
>>>> >>> alt0 distance 20
>>>> >>> alt0 metric 0
>>>> >>> alt0 ident 0
>>>> >>> alt0 hops 0
>>>> >>> alt0 interface null
>>>> >>> alt0 table null
>>>> >>> alt0 nexthop 172.23.215.168
>>>> >>> alt0 original nexthop null
>>>> >>> alt0 tag 0
>>>> >>> alt0 origin type 0
>>>> >>> alt0 local preference 100
>>>> >>> alt0 evpn label*16 0
>>>> >>> alt0 attribute as 0
>>>> >>> alt0 attribute value n/a
>>>> >>> alt0 tunnel type 0
>>>> >>> alt0 tunnel value n/a
>>>> >>> alt0 link state n/a
>>>> >>> alt0 pmsi type 0
>>>> >>> alt0 pmsi label*16 0
>>>> >>> alt0 pmsi tunnel n/a
>>>> >>> alt0 accumulated igp 0
>>>> >>> alt0 bandwidth 0
>>>> >>> alt0 atomic aggregator false
>>>> >>> alt0 aggregator as 0
>>>> >>> alt0 aggregator router null
>>>> >>> alt0 originator null
>>>> >>> alt0 cluster list
>>>> >>> alt0 aspath 4242420119 4242422601 4242422825 4242422092
>>>> 4242423088 4242420458 4242421080 4242421123 4242422633 4242423914 4242423668 4242421123 4242423618 4242423947
>>>> >>> alt0 asname as#4242420119 as#4242422601 as#4242422825
>>>> as#4242422092 as#4242423088 as#4242420458 as#4242421080 as#4242421123 as#4242422633 as#4242423914 as#4242423668 as#4242421123 as#4242423618 as#4242423947
>>>> >>> alt0 asinfo as#4242420119 as#4242422601 as#4242422825
>>>> as#4242422092 as#4242423088 as#4242420458 as#4242421080 as#4242421123 as#4242422633 as#4242423914 as#4242423668 as#4242421123 as#4242423618 as#4242423947
>>>> >>> alt0 path length 14
>>>> >>> alt0 standard community 64511:52 64511:1156
>>>> >>> alt0 extended community
>>>> >>> alt0 large community 4242420119:1000:2 4242420119:2000:2 4242421080:101:51 4242421080:103:39 4242422092:110:195 4242422092:120:197
>>>> 4242422601:120:9 4242422601:140:42 4242422633:101:51 4242422633:103:34 4242423088:1:204 4242423618:160:1156 4242423914:100:41
>>>> >>> alt0 internal source 4
>>>> >>> alt0 local label null
>>>> >>> alt0 remote label
>>>> >>> alternate #1 candidate=true best=false
>>>> >>> alt1 type bgp4 42
>>>> >>> alt1 source 172.23.236.56
>>>> >>> alt1 validity 0
>>>> >>> alt1 only to customer 0
>>>> >>> alt1 segrout index 0
>>>> >>> alt1 segrout old base 0
>>>> >>> alt1 segrout base 0
>>>> >>> alt1 segrout size 0
>>>> >>> alt1 segrout offset 0
>>>> >>> alt1 segrout prefix null
>>>> >>> alt1 bier index 0
>>>> >>> alt1 bier old base 0
>>>> >>> alt1 bier base 0
>>>> >>> alt1 bier range 0
>>>> >>> alt1 bier size 0-32
>>>> >>> alt1 updated 2023-10-01 05:22:48 (03:16:00 ago)
>>>> >>> alt1 version 74042
>>>> >>> alt1 distance 20
>>>> >>> alt1 metric 0
>>>> >>> alt1 ident 0
>>>> >>> alt1 hops 0
>>>> >>> alt1 interface null
>>>> >>> alt1 table null
>>>> >>> alt1 nexthop 172.23.236.56
>>>> >>> alt1 original nexthop null
>>>> >>> alt1 tag 0
>>>> >>> alt1 origin type 0
>>>> >>> alt1 local preference 100
>>>> >>> alt1 evpn label*16 0
>>>> >>> alt1 attribute as 0
>>>> >>> alt1 attribute value n/a
>>>> >>> alt1 tunnel type 0
>>>> >>> alt1 tunnel value n/a
>>>> >>> alt1 link state n/a
>>>> >>> alt1 pmsi type 0
>>>> >>> alt1 pmsi label*16 0
>>>> >>> alt1 pmsi tunnel n/a
>>>> >>> alt1 accumulated igp 0
>>>> >>> alt1 bandwidth 0
>>>> >>> alt1 atomic aggregator false
>>>> >>> alt1 aggregator as 0
>>>> >>> alt1 aggregator router null
>>>> >>> alt1 originator null
>>>> >>> alt1 cluster list
>>>> >>> alt1 aspath 76190 64719 4242422825 4242422092 4242423088
>>>> 4242420458 4242421080 4242421123 4242422633 4242423914 4242423668 4242421123 4242423618 4242423947
>>>> >>> alt1 asname as#76190 as#64719 as#4242422825 as#4242422092
>>>> as#4242423088 as#4242420458 as#4242421080 as#4242421123 as#4242422633 as#4242423914 as#4242423668 as#4242421123 as#4242423618 as#4242423947
>>>> >>> alt1 asinfo as#76190 as#64719 as#4242422825 as#4242422092
>>>> as#4242423088 as#4242420458 as#4242421080 as#4242421123 as#4242422633 as#4242423914 as#4242423668 as#4242421123 as#4242423618 as#4242423947
>>>> >>> alt1 path length 14
>>>> >>> alt1 standard community 64511:5 64511:23 64511:33 64511:52 64511:1156
>>>> >>> alt1 extended community
>>>> >>> alt1 large community 4242421080:101:51 4242421080:103:39 4242422092:110:195 4242422092:120:197 4242422633:101:51 4242422633:103:34
>>>> 4242423088:1:204 4242423618:160:1156 4242423914:100:41
>>>> >>> alt1 internal source 4
>>>> >>> alt1 local label null
>>>> >>> alt1 remote label
>>>> >>> counter tx=0(0) rx=0(0)
>>>> drp=0(0)
>>>> >>> lastio input never
>>>> ago, output never ago, drop never ago
>>>> >>> hardware counter null
>>>> >>>
>>>> >>> p4deb>
>>>> >>> p4deb>attach vdc dn42
>>>> >>>
>>>> >>> escape character is ascii0x03.
>>>> >>>
>>>> >>> p4deb-dn42>
>>>> >>> p4deb-dn42>
>>>> >>> p4deb-dn42>show startup-config ghost
>>>> >>> 2023-10-01 08:48:41
>>>> >>> time-map ghosts
>>>> >>> time-zone CET
>>>> >>> sequence 10 action permit
>>>> >>> sequence 10 match hour 0
>>>> >>> sequence 10 match minute 1-10
>>>> >>> sequence 20 action permit
>>>> >>> sequence 20 match hour 2
>>>> >>> sequence 20 match minute 1-10
>>>> >>> sequence 30 action permit
>>>> >>> sequence 30 match hour 4
>>>> >>> sequence 30 match minute 1-10
>>>> >>> sequence 40 action permit
>>>> >>> sequence 40 match hour 6
>>>> >>> sequence 40 match minute 1-10
>>>> >>> sequence 50 action permit
>>>> >>> sequence 50 match hour 8
>>>> >>> sequence 50 match minute 1-10
>>>> >>> sequence 60 action permit
>>>> >>> sequence 60 match hour 10
>>>> >>> sequence 60 match minute 1-10
>>>> >>> sequence 70 action permit
>>>> >>> sequence 70 match hour 12
>>>> >>> sequence 70 match minute 1-10
>>>> >>> sequence 80 action permit
>>>> >>> sequence 80 match hour 14
>>>> >>> sequence 80 match minute 1-10
>>>> >>> sequence 90 action permit
>>>> >>> sequence 90 match hour 16
>>>> >>> sequence 90 match minute 1-10
>>>> >>> sequence 100 action permit
>>>> >>> sequence 100 match hour 18
>>>> >>> sequence 100 match minute 1-10
>>>> >>> sequence 110 action permit
>>>> >>> sequence 110 match hour 20
>>>> >>> sequence 110 match minute 1-10
>>>> >>> sequence 120 action permit
>>>> >>> sequence 120 match hour 22
>>>> >>> sequence 120 match minute 1-10
>>>> >>> sequence 130 action permit
>>>> >>> sequence 130 match hour 24
>>>> >>> sequence 130 match minute 1-10
>>>> >>> exit
>>>> >>> route-policy ghosts
>>>> >>> sequence 10 set aspath 4242421933
>>>> >>> sequence 20 pass
>>>> >>> exit
>>>> >>> router ghosthunt4 24
>>>> >>> description ipv4 prefix generator
>>>> >>> vrf dn42
>>>> >>> prefix 172.21.100.24/29
>>>> >>> nexthop 172.23.199.110
>>>> >>> range ghosts
>>>> >>> grace 2000 2000
>>>> >>> send-policy ghosts
>>>> >>> ignore label
>>>> >>> mode originator
>>>> >>> start
>>>> >>> exit
>>>> >>> router ghosthunt4 42
>>>> >>> description ipv4 prefix verifier
>>>> >>> vrf dn42
>>>> >>> prefix 172.21.100.24/29
>>>> >>> nexthop 172.23.199.110
>>>> >>> range ghosts
>>>> >>> grace 180000 3600000
>>>> >>> lookup router bgp6 42
>>>> >>> send-policy ghosts
>>>> >>> ignore nexthop origin locpref distance aspath stdcomm extcomm aggregate lrgcomm empty
>>>> >>> start
>>>> >>> exit
>>>> >>> router ghosthunt6 24
>>>> >>> description ipv6 prefix generator
>>>> >>> vrf dn42
>>>> >>> prefix fd40:e3b7:1d77:1234::/64
>>>> >>> nexthop fd40:cc1e:c0de::fffe
>>>> >>> range ghosts
>>>> >>> grace 2000 2000
>>>> >>> send-policy ghosts
>>>> >>> ignore label
>>>> >>> mode originator
>>>> >>> start
>>>> >>> exit
>>>> >>> router ghosthunt6 42
>>>> >>> description ipv6 prefix verifier
>>>> >>> vrf dn42
>>>> >>> prefix fd40:e3b7:1d77:1234::/64
>>>> >>> nexthop fd40:cc1e:c0de::fffe
>>>> >>> range ghosts
>>>> >>> grace 180000 3600000
>>>> >>> lookup router bgp6 42
>>>> >>> send-policy ghosts
>>>> >>> ignore nexthop origin locpref distance aspath stdcomm extcomm aggregate lrgcomm empty
>>>> >>> start
>>>> >>> exit
>>>> >>> check ghost4
>>>> >>> command show ipv4 ghosthunt 42 status | hide time
>>>> >>> require-text category;curr;
>>>> >>> require-text execute;true;
>>>> >>> require-text advertise;false;
>>>> >>> require-text withdraw;true;
>>>> >>> require-text ghost;false;
>>>> >>> require-text pass;true;
>>>> >>> require-text attrib err;0;
>>>> >>> require-text attrib ok;0;
>>>> >>> exit
>>>> >>> check ghost6
>>>> >>> command show ipv6 ghosthunt 42 status | hide time
>>>> >>> require-text category;curr;
>>>> >>> require-text execute;true;
>>>> >>> require-text advertise;false;
>>>> >>> require-text withdraw;true;
>>>> >>> require-text ghost;false;
>>>> >>> require-text pass;true;
>>>> >>> require-text attrib err;0;
>>>> >>> require-text attrib ok;0;
>>>> >>> exit
>>>> >>> sensor ghosts4
>>>> >>> path ghosts/peer/peer
>>>> >>> prefix freertr-ghosts
>>>> >>> prepend ghosts_ipv4_
>>>> >>> command show ipv4 ghosthunt 42 status
>>>> >>> name 0 category=
>>>> >>> key name ghosts/peer
>>>> >>> column 2 name count
>>>> >>> exit
>>>> >>> sensor ghosts6
>>>> >>> path ghosts/peer/peer
>>>> >>> prefix freertr-ghosts
>>>> >>> prepend ghosts_ipv6_
>>>> >>> command show ipv6 ghosthunt 42 status
>>>> >>> name 0 category=
>>>> >>> key name ghosts/peer
>>>> >>> column 2 name count
>>>> >>> exit
>>>> >>>
>>>> >>> p4deb-dn42>
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> On 10/1/23 08:01, wrote:
>>>> >>>> Groups.io <https://urldefense.com/v3/__https://groups.io/__;!!NEt6yMaO-gk!Fk002HobEosSSvmAU3SkpBVOxun6RklVupSK9PDrFAP1E45omWXvcE61HoVtRkoO2LWNZA$ >
>>>> >>>>
>>>> >>>> This is a digest for DN42 Mailing List <https://urldefense.com/v3/__https://groups.io/g/dn42/topics__;!!NEt6yMaO-gk!Fk002HobEosSSvmAU3SkpBVOxun6RklVupSK9PDrFAP1E45omWXvcE61HoVtRkrfTEbGrA$ >. View all your groups.io groups, and edit your subscriptions, here <https://urldefense.com/v3/__https://groups.io__;!!NEt6yMaO-gk!Fk002HobEosSSvmAU3SkpBVOxun6RklVupSK9PDrFAP1E45omWXvcE61HoVtRkr5nPannw$ >.
>>>> >>>> Do not reply to this email. To reply to a message, click the Reply link under the message.
>>>> >>>>
>>>> >>>> Topics in this digest:
>>>> >>>> .
>>>> >>>>
>>>> >>>> 1. #dn42 #Routing Please help inspecting ghost routes retained on DN42 network with extremely long AS Path <#523> #dn42 #Routing
>>>> >>>>
>>>> >>>> messages:
>>>> >>>> .
>>>> >>>>
>>>> >>>> 1a.
>>>> >>>> *#dn42 #Routing Please help inspecting ghost routes retained on DN42 network with extremely long AS Path* #dn42 #Routing
>>>> >>>> From: Hawkins Sherpherd
>>>> >>>> Date: Sun, 01 Oct 2023 04:37:05 UTC
>>>> >>>>
>>>> >>>> Recently, my network become uncanny, it keep making loop for some prefixies between iBGP neighbors, some of nodes send large amount of prefixies (even more than total
>>>> amount the DN42 network able to reach) to iBGP neighbors. To avoid my network failure keep affecting DN42 network, around 12:00 this day, I shutdown all external peering to
>>>> stop this influence. But it seems didn't help, I can see my prefixies still exists on DN42 network with extremely long AS path, those prefixies affected by my network failure
>>>> having same issue, too.
>>>> >>>> Please, if anyone see any route traverses 4242423947 or with extremely long AS path, it would be great help to DN42 if you can check these routes did or didn't go wrong
>>>> in your network.
>>>> >>>>
>>>> >>>> View/Reply Online <https://urldefense.com/v3/__https://groups.io/g/dn42/message/523__;!!NEt6yMaO-gk!Fk002HobEosSSvmAU3SkpBVOxun6RklVupSK9PDrFAP1E45omWXvcE61HoVtRkr-D64ckA$ > | Reply To Group
>>>> <>
>>>> | Mute Topic <https://urldefense.com/v3/__https://groups.io/mt/101687198/4791281__;!!NEt6yMaO-gk!Fk002HobEosSSvmAU3SkpBVOxun6RklVupSK9PDrFAP1E45omWXvcE61HoVtRkofojp9Uw$ > | Mute #dn42 <https://urldefense.com/v3/__https://groups.io/mk?hashtag=dn42&subid=8585920__;!!NEt6yMaO-gk!Fk002HobEosSSvmAU3SkpBVOxun6RklVupSK9PDrFAP1E45omWXvcE61HoVtRkqBpLNfXw$ > | Mute #Routing
>>>> <https://urldefense.com/v3/__https://groups.io/mk?hashtag=Routing&subid=8585920__;!!NEt6yMaO-gk!Fk002HobEosSSvmAU3SkpBVOxun6RklVupSK9PDrFAP1E45omWXvcE61HoVtRkofR_gANg$ > | Top ^ <#topics> | New Topic <https://urldefense.com/v3/__https://groups.io/g/dn42/post__;!!NEt6yMaO-gk!Fk002HobEosSSvmAU3SkpBVOxun6RklVupSK9PDrFAP1E45omWXvcE61HoVtRkoG5UQwfg$ >
>>>> >>>>
>>>> >>>> - The DN42 Mailing List
>>>> >>>>
>>>> >>>> Groups.io <https://urldefense.com/v3/__https://groups.io/__;!!NEt6yMaO-gk!Fk002HobEosSSvmAU3SkpBVOxun6RklVupSK9PDrFAP1E45omWXvcE61HoVtRkoO2LWNZA$> 2023 Groups.io<https://urldefense.com/v3/__https://groups.io/__;!!NEt6yMaO-gk!Fk002HobEosSSvmAU3SkpBVOxun6RklVupSK9PDrFAP1E45omWXvcE61HoVtRkoO2LWNZA$ >
>>>> >>>>
>>>> >>>> You are receiving this email because you are subscribed to <https://urldefense.com/v3/__https://groups.io/g/dn42__;!!NEt6yMaO-gk!Fk002HobEosSSvmAU3SkpBVOxun6RklVupSK9PDrFAP1E45omWXvcE61HoVtRkrWAu0_7w$ > via . You can unsubscribe here
>>>> <https://urldefense.com/v3/__https://groups.io/g/dn42/leave/8585920/4791281/1339920448/xyzzy__;!!NEt6yMaO-gk!Fk002HobEosSSvmAU3SkpBVOxun6RklVupSK9PDrFAP1E45omWXvcE61HoVtRkrCCmRVSg$ >.
>>>> >>>>
>>>>
>>>>
>>>>
>>>>
>>>> On 10/1/23 11:06, mc36 wrote:
>>>>> tldr pebkac issues, dont feed the trolley...
>>>>>
>>>>> "not-i" was who put up on an endless thread 2nd i shut down the ebgp peer who wrote the mails...
>>>>>
>>>>> as in a devvies hats, do i had anything i needed to modify on friday evening?
>>>>>
>>>>> i mean on the bits or was just about the bits of the bits?! (u chittychattyGPTing, again?!)
>>>>>
>>>>> like the sitin-sitout tps-reports cover sheets meetings within the * meetings?! :)
>>>>>
>>>>>
>>>>>
>>>>> On 10/1/23 10:50, Antoni Przygienda wrote:
>>>>>> Hey hey, have fun. Great you both in good shape to look for another corner of the end of the world
>>>>>> Your implementation is pretty well understood by good amount of folks around by now so we can fix/add/muck around with it easily, I ll pull it up to newest schema etc
>>>>>> (rift draft stable since forever now waiting for the 2^nd AD to get through it so we finallyu hit publish queue)
>>>>>>
>>>>>> Csaba had something as well I think he ran against our daemon even but I don t know where he stands these day with it
>>>>>>
>>>>>> --- tony
>>>>>>
>>>>>> *
>>>>>> *
>>>>>>
>>>>>> *
>>>>>>
>>>>>> Juniper Business Use Only
>>>>>>
>>>>>> From: *Bruno Rijsman <>
>>>>>> *Date: *Saturday, 30 September 2023 at 02:08
>>>>>> *To: *Antoni Przygienda <>
>>>>>> *Cc: *Jeffrey (Zhaohui) Zhang <>, Jeff Tantsura <>, Jordan Head <>,
>>>>>> <>, mc36 <>
>>>>>> *Subject: *Re: RIFT interop in IETF118 hackathon?
>>>>>>
>>>>>> *[External Email. Be cautious of content]*
>>>>>>
>>>>>> Hi Everyone,
>>>>>>
>>>>>> That is very exciting news that there is another RIFT implementation which will be interop tested against my implementation at the IETF 118 Hackathon.
>>>>>>
>>>>>> I would love to actively participate myself, but unfortunately I won t be able to make it.
>>>>>>
>>>>>> Starting October 14, my wife and I will be going on a long two-month expedition in the Nepal Himalaya with zero Internet access or computer access for the entire two months.
>>>>>>
>>>>>> I will be back online somewhere about mid to late December and at that time I will happily look at any pull requests for schema updates other other fixes that came out of the
>>>>>> interop testing.
>>>>>>
>>>>>> Enjoy the hackathon!
>>>>>>
>>>>>> Bruno
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sep 30, 2023, at 3:12 AM, Antoni Przygienda <> wrote:
>>>>>>
>>>>>> So (especially at Sandy) the requirements would be to have suppor for the .yaml file format and run either the odd or even nodes. This can be easily tested
>>>>>> against Bruno ;s
>>>>>> implementation/framework that can be easily extended to test that.
>>>>>>
>>>>>> Once we have that in place we can test any matrix of 2 implementations.
>>>>>>
>>>>>> I ll update Bruno s open source to newest spec/schema so we re all in line.
>>>>>>
>>>>>> Goals AFAIS
>>>>>>
>>>>>> 1. Bring up adjacency v4 (would be good to do v6 as well) with fixed level config
>>>>>> 2. Bring up adjacencies with ZTP, in one case ToF node, other case without ToF flag
>>>>>> 3. Exchange TIEs until databases coherent between the nodes
>>>>>> 4. Verify routing tables (if implementation allows)
>>>>>> 5. Test leaf flag if implementation allows
>>>>>>
>>>>>> Once that is all in place we can go and start breaking links and test disaggregation (Bruno s framework has that included and implementation needs to pass
>>>>>> that first against
>>>>>> his testframework before other combinations I would say)
>>>>>>
>>>>>> Folks can chime in with what they want to try, what they have to test
>>>>>>
>>>>>> * Tony
>>>>>>
>>>>>> Juniper Business Use Only
>>>>>>
>>>>>> *From:*Jeffrey (Zhaohui) Zhang < <>>
>>>>>> *Date:*Friday, 29 September 2023 at 17:48
>>>>>> *To:*Jeff Tantsura < <>>
>>>>>> *Cc:*Antoni Przygienda < <>>, Jordan Head < <>>,
>>>>>> <><<>>
>>>>>> *Subject:*RE: RIFT interop in IETF118 hackathon?
>>>>>>
>>>>>> You re right.
>>>>>>
>>>>>> Juniper Business Use Only
>>>>>>
>>>>>> *From:*Jeff Tantsura < <>>
>>>>>> *Sent:*Friday, September 29, 2023 11:40 AM
>>>>>> *To:*Jeffrey (Zhaohui) Zhang < <>>
>>>>>> *Cc:*Antoni Przygienda < <>>; Jordan Head < <>>;
>>>>>> <><<>>
>>>>>> *Subject:*Re: RIFT interop in IETF118 hackathon?
>>>>>>
>>>>>> *[External Email. Be cautious of content]*
>>>>>>
>>>>>> No, FreeRTR is a different code base, sorry, I didn t realize ZTE is in.
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Jeff
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sep 29, 2023, at 08:33, Jeffrey (Zhaohui) Zhang <<>> wrote:
>>>>>>
>>>>>>
>>>>>> FreeRTR is Bruno?
>>>>>>
>>>>>> ZTE is all in.
>>>>>>
>>>>>> Jeffrey
>>>>>>
>>>>>> Juniper Business Use Only
>>>>>>
>>>>>> *From:*Jeff Tantsura <<>>
>>>>>> *Sent:*Friday, September 29, 2023 11:32 AM
>>>>>> *To:*Antoni Przygienda < <>>
>>>>>> *Cc:*Jeffrey (Zhaohui) Zhang <<>>; Jordan Head <
>>>>>> <>>;
>>>>>> <><<>>
>>>>>> *Subject:*Re: RIFT interop in IETF118 hackathon?
>>>>>>
>>>>>> *[External Email. Be cautious of content]*
>>>>>>
>>>>>> So, practically would be Junos + Bruno + FreeRTR?
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Jeff
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sep 29, 2023, at 00:54, Antoni Przygienda < <>> wrote:
>>>>>>
>>>>>>
>>>>>> And I would tell them to plug into Bruno s framework where e thing gets tested against Bruno framework. I.e. an
>>>>>> implementation has to run bunch nodes and connect based
>>>>>> on yaml on either red or black nodes in the yaml
>>>>>>
>>>>>> This will allow to run any 2 implementaton combination against each other
>>>>>>
>>>>>> Juniper Business Use Only
>>>>>>
>>>>>> *From:*Jeffrey (Zhaohui) Zhang <<>>
>>>>>> *Date:*Friday, 29 September 2023 at 05:19
>>>>>> *To:*'Jeff Tantsura' <<>>, Antoni Przygienda <
>>>>>> <>>, Jordan Head
>>>>>> < <>>,
>>>>>> <>< <>>
>>>>>> *Subject:*RIFT interop in IETF118 hackathon?
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Did we talk about that? We may have but I forgot about that entirely, though we did give Juniper's RIFT image to ZTE for interop
>>>>>> testing.
>>>>>>
>>>>>> Besides Juniper, ZTE and FreeRTR, who else has the implementation?
>>>>>>
>>>>>> Jeffrey
>>>>>>
>>>>>> Juniper Business Use Only
>>>>>>
>>>
>>>
>>>
>>>
>>>
>
>
>
>
>
_._,_._,_
Groups.io Links:
You receive all messages sent to this group.
View/Reply Online (#2072) |
|
|
Mute This Topic
| New Topic
Your Subscription |
|
Unsubscribe
[]
_._,_._,_
- Re: [RARE-users] [freertr] RIFT interop in IETF118 hackathon?, Antoni Przygienda via groups.io, 10/01/2023
- Re: [RARE-users] [freertr] RIFT interop in IETF118 hackathon?, Tim Chown via groups.io, 10/02/2023
- Message not available
- Re: [RARE-users] [freertr] RIFT interop in IETF118 hackathon?, Tim Chown via groups.io, 10/02/2023
- Message not available
- Re: [RARE-users] [freertr] RIFT interop in IETF118 hackathon?, Tim Chown via groups.io, 10/02/2023
Archive powered by MHonArc 2.6.24.