Routing in SMB Device 1550

[Sanjay_S]

Hi All,

We recently faced issues with the routing in the SMB device. We had issues adding routes in it. When i add a route 10.0.0.0/9 for example it updates as a inactive route for it and then create 10.0.0.0/16 route as active one. And only 10.0.0.0/16 works. Not able to add any routes apart from standard subnets such as /8, /16, /24, /32. Is there any limitation as such? Or anything i am missing?

Regards,

Sanjay S

[PhoneBoy]

How precisely are you adding the route and what is the precise topology?
I'm not aware of any specific limitations here, though there does appear to be a relevant bug that is fixed in R80.20.15: SMB-14380
See: https://supportcenter.us.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&so...

[Sanjay_S]

Hi Phoneboy,

I am adding route via GUI. We just have WAN, LAN1 and LAN2 enabled. Adding few additional routes pointing to LAN2's next hop.

We are already running R80.20.20 version but still the same issue. May i know whether this version is out of support already?

Regards,

Sanjay S

[G_W_Albrecht]

CheckPoint always suggests to update SMB units to the latest firmware, i would suggest R20.10.40 for stabiliy and many bug fixes.

[Sanjay_S]

Thank you Albrecht for the input.

But just to re-confirm on the version which i am running is R8.20.20 is already out of support? we have around 90 firewalls so need to plan upgrades of all firewalls asap if it is already out of support.

Regards,

Sanjay S

[Chris_Atkinson]

You can review the support status / milestones for a release here:

https://www.checkpoint.com/support-services/support-life-cycle-policy/

[G_W_Albrecht]

Support only has a value for the main version - so all R80.20.xx will be out of support after some date. R80.20.20 is supported but a bit old. Fact is that higher firmware versions resolve issues, but as long as all works as expected i would not suggest to upgrade.

[_Val_]

R80.20.x is supported till October, 2023. 

[Sanjay_S · Accepted solution]

Thanks All,

I have upgraded to R80.20.50 and the issue seems to be fixed 🙂

Regards,

Sanjay S