Rare project developers

[mc36 <>]

so

"
wget freertr.org/rtr.zip
unzip zzz.zip
cd src
./c.sh
./tw.sh rout-bgp521.tst pcap r4 eth1
" --- now gave me the attached pcap... good to see that now it dissects... 
packet #17, #18...

much easier to read except the magics (?) like why it became unknown?.... :)

seeked also into the rfc, imho im right here?

(tbh, i have the feeling, that 2021-12 was too early for my skills, and maybe 
others are earlier implementers?!... :)

my google also failed me to find the mentioned pdf about the 'slides', an url 
would be nice from you, please....



but, im still scratching my head on things like why the cicd went crazy about 
the yesterday commit??? any help highly appreciated that.... :)

6he update will pass tomorrow imho against the big vendors as i already 
started using it internally (inf.nop.hu) and niif.hu updates 10am

today (telnet lg.hbone.hu to see this on the full table plus the local ix's 
blackhole /32s, plus the geant mdvpn, etc....:),

then slowly the whole lab, including frederic daily morning schedule... and 
so on.... not to mention my dn42.dev (telnet sandbox.freertr.org) peering box 
and internal bgp (lg.nop.hu)

so what i saw is that r1 refused the prefix from r4, according the config, i 
think thats a way better behavior than the 100% success rate???

regrading the frr help, so basically i just meant the core lines like 
remote-as and the role.... im asking as the frr docs now confused

me a little bit, it seems an industry standard split here, and as we test 
against intop9-frr.htm, im also happy revert the yesterday changes...

but i have the feeling i should not, just wait for the cicd to fail and then 
fix the test case then.... :)

thanks,
cs




On 4/29/23 00:14, mc36 wrote:
> On 4/28/23 23:46, mc36 wrote:
> > also git 3 dots to spot the auto-shitload when you do edit the project's 
> > default todo.txt instead of the issue tracker...
>
> https://github.com/rare-freertr/freeRtr/blob/master/changelog.txt#L12322

Attachment: slot0log-r4-eth1.pcap
Description: application/vnd.tcpdump.pcap