- dev - lists.frrouting.org

[cmaster-next] [PATCH 1/2] isisd: use a smaller #ifdef for isis_receive()
by Renato Westphal 29 Nov '16

29 Nov '16

There's no need to provide two definitions of the isis_receive() function (one for GNU_LINUX and the other for !GNU_LINUX). Both differ only slightly so it makes more sense to define isis_receive() just once and use a smaller #ifdef to account for these differences. This improves code readability. Signed-off-by: Renato Westphal <renato(a)opensourcerouting.org> --- isisd/isis_pdu.c | 40 ++++------------------------------------ 1 file changed, 4 insertions(+), 36 deletions(-) diff --git a/isisd/isis_pdu.c b/isisd/isis_pdu.c index 1dfb462..39d2df7 100644 --- a/isisd/isis_pdu.c +++ b/isisd/isis_pdu.c @@ -2139,7 +2139,6 @@ isis_handle_pdu (struct isis_circuit *circuit, u_char * ssnpa) return retval; } -#ifdef GNU_LINUX int isis_receive (struct thread *thread) { @@ -2153,10 +2152,11 @@ isis_receive (struct thread *thread) circuit = THREAD_ARG (thread); assert (circuit); + circuit->t_read = NULL; + isis_circuit_stream(circuit, &circuit->rcv_stream); retval = circuit->rx (circuit, ssnpa); - circuit->t_read = NULL; if (retval == ISIS_OK) retval = isis_handle_pdu (circuit, ssnpa); @@ -2166,52 +2166,20 @@ isis_receive (struct thread *thread) */ if (!circuit->is_passive) { +#ifdef GNU_LINUX THREAD_READ_ON (master, circuit->t_read, isis_receive, circuit, circuit->fd); - } - - return retval; -} - #else -int -isis_receive (struct thread *thread) -{ - struct isis_circuit *circuit; - u_char ssnpa[ETH_ALEN]; - int retval; - - /* - * Get the circuit - */ - circuit = THREAD_ARG (thread); - assert (circuit); - - circuit->t_read = NULL; - - isis_circuit_stream(circuit, &circuit->rcv_stream); - - retval = circuit->rx (circuit, ssnpa); - - if (retval == ISIS_OK) - retval = isis_handle_pdu (circuit, ssnpa); - - /* - * prepare for next packet. - */ - if (!circuit->is_passive) - { circuit->t_read = thread_add_timer_msec (master, isis_receive, circuit, listcount (circuit->area->circuit_list) * 100); +#endif } return retval; } -#endif - /* filling of the fixed isis header */ void fill_fixed_hdr (struct isis_fixed_hdr *hdr, u_char pdu_type) -- 1.9.1

1 1

[cmaster-next] please check your spam folders for list mails
by David Lamparter 28 Nov '16

28 Nov '16

Hi everyone, we've just noticed that some mails on this mailing list have gotten flagged down as spam. This is a widespread problem with mailing lists in regard to DKIM, DMARC and SPF anti-spam measures, i.e. in this case the SPF record for cumulusnetworks.com prohibits the mailing list from forwarding the mail, and in combination with DMARC that's sufficient for Google to put it into spam. There is no "good" workaround for this, and since this list is temporary and will hopefully be moved soon, there won't really be a fix. If you use Google Mail, please go to your spam folder and look for any mail that has "[cmaster-next]" in the Subject: line. I would hope the spam detection will remember the "this is not spam" click for future mails. There should have been 2 mails from Donald on the list, one Nov 25th, one today. These were the only ones I found in my spam folder, I hope I didn't miss anything else. Cheers, -David P.S.: I checked other subscriber domains on the list: - 6wind.com: no SPF - OK - opensourcerouting.org: no SPF - OK - labn.net: neutral SPF, but no DMARC - OK - us.ibm.com: soft SPF, but no DMARC - should be OK - orange.com: soft SPF, but no DMARC - should be OK - atcorp.com: hard SPF, but no DMARC - should be OK - cumulusnetworks.com: hard SPF + DMARC - PROBLEM :( I can write a script to auto-check this later for subscribers on the list, so at least they get a notification/warning.

1 0

[cmaster-next] Quick Update
by Donald Sharp 28 Nov '16

28 Nov '16

David and I had a video call to discuss details our preparation for a release: We are going to stop development on cmaster-next and merge it down into master on the opensourcerouting private repo. When we decide on a project name we are going to create the appropriately named repo and push the master branch into that. We are going to merge the licensing fixup branch into master. We are going to create a release candidate branch 2.0_rc or somesuch, David's choice of name. We are going to merge vtysh-grammar down into master for the development work. Why? because it is fundamentally changing the code base and let's bite the bullet early and often here. David is going to work on the modified Hacking file from the development document. donald

1 0

[Cmaster-next] new mailing list, also: deleting old branches
by David Lamparter 25 Nov '16

25 Nov '16

Hi everyone, as you can see there's now a mailing list. To post to it, send to: cmaster-next(a)lists.nox.tf (It's hosted on the same system as the patchwork.) Either way I wanted to remind/ask everyone to delete old branches when they're not needed anymore. I have deleted: cmaster-next-queue-20161011 cmaster-next-queue-20161012 cmaster-next-vtysh-fuckup cmaster-next-paul-cli (Not sure about others?) @Lou, I think we can delete all of these too, since it's merged? dev/labn/cmaster-next+prepvnc/v4 dev/labn/cmaster-next+vnc/v0 dev/labn/cmaster-next+vnc/v3 dev/labn/cmaster-next+vnc/v4 Cheers, David P.S.: As a quick reminder, here are some useful git commands: *** to find out the remote name of the OSR git in your clone: $ git remote -v | grep cumulus-private_quagga.git github_osr_cm git@github.com:opensourcerouting/cumulus-private_quagga.git (fetch) github_osr_cm git@github.com:opensourcerouting/cumulus-private_quagga.git (push) => It's "github_osr_cm" for me. *** to push a delete of branch onto github: $ git push github_osr_cm :cmaster-next-queue-20161011 (Note the ":" before the branch name) *** to "fetch deletes" (a normal pull won't delete your local copy) $ git remote prune github_osr_cm (This will remove your local copies of branches that were deleted on github.)

2 2