R80.20 Jumbo Hotfix Accumulator - New Ongoing Take #74

[Yifat_Chen]

Hi,

A new Ongoing Jumbo Hotfix Accumulator take for R80.20 (take 74) is available. Please refer to sk137592.

R80.20 JHF T74 is the same as T73 (including only alignment to Mail Transfer Agent engine).

• The new releases will not be published via CPUSE as a recommended version.
• Availability:
  • Will be provided by customer support
  • Available for download via CPUSE by using package identifier

R80.20 JHF Take #74 content:

PRJ-503 - Alignment to Mail Transfer Agent Engine Update. Refer to sk123174.

[NickGriffiths]

fw monitor filters still appear to be broken in this release (as reported on previous release thread). Tested on R80.20 VM management and 3100 single gateway,

Shame really, as there are a few stability fixes that really should be rolled out; but will be sticking with T47 (on customer environments) until these issues are resolved.

[Coby_Schmidt]

@NickGriffiths.

There was indeed a behavioral change of FW monitor in this take.

Up until R80.20 FW monitor was not monitoring accelerated traffic by PPAK. In R80.20 we introduced the ability to monitor this traffic, however it was not enabled by default (Due to high performance impact). One of the reasons for this high performance impact is the inability to use the "-e" filter which is not supported on PPAK.

Now, starting from take 73, we have made substantial changes to FW monitor. Together with performance optimizations we have also embedded new filtering abilities in FW monitor.

By using "-F" flag you can filter certain connection. For example, to filter a host with the IP “8.8.8.8” you should use: fw monitor -F "8.8.8.8,0,0,0,0" -F "0,0,8.8.8.8,0,0".

The syntax is simple. -F "{src IP}, {src port}, {dst IP},{dst port}, {protocol num}". “0” can be used as a wild card.

For more information about this check  sk30583 ("what is FW monitor") or ask me.

[ClaudiaPeter]

Is it intended that "-e" doesn't filter any more, so "-F" is not an additional option but replaces "-e"?