cancel
Showing results for 
Search instead for 
Did you mean: 
Create a Post
Highlighted

About those mysterious R77.20 builds...

So, we all know and see those mysterious R77.20 builds uploaded lately and because I am "brave" enough I decided to give them a try:

 

1. Build 990172984 code named "private build"

Boots really slow! It actually reboots few times in a row until it finally gives up and ends with a peculiar message in /var/log/messages about configuring WiFi on a Wired appliance. Once it boots it works well until load average goes above 3.00 at which time either sfwd process will crash or cluster fail-over will happen. The interesting thing here is that R&D incorporated some kind of logic to interrupt endless reboots. Nice.

 

2. Build 990172993 code named "Private fix"

This one fixes the reboot-loop bug and is the first build ever that was able to survive 3.00+ load average test. The only problem is that above such load averages all site-to-site VPN tunnels die but this is more like side effect of the fact that they all run on the already overloaded core 0. This build is also pretty efficient in memory consumption. The only very minor issue I found is that it will sometime fail to connect to SNMP socket on boot.

 

3. Build 990173003 code named "customer fix"

This build... (btw, notice we reached 3000 builds milestone) just works! 

 

4. Build 990173004 code named "private customer build"

This one was released today and I am going to give it a try tomorrow....

---

So, if you have the guts give them a try. 😉

2 Replies
Employee+
Employee+

Re: About those mysterious R77.20 builds...

Hi

they are not mysterious, they are simply private fixes for specific customer issues (based on the latest Jumbo)

if you don't have a problem, i don't see any value in installing them.

once we will release a new R77.20 firmware (soon) - all these fixes will be included. and we will let you know.

 

thanks

 

 

Re: About those mysterious R77.20 builds...

Thanx for the update. The only problem I had was the one described by me above. And I am happy latest published build solved it as it was very annoying.