Page 1 of 1


Posted: Fri Jul 03, 2020 5:52 pm
by gramler
The virtual hub extended option help for "DisableIPParsing" says:

"If you set this option to non-zero value, then the Virtual Hub will disable the internal parsing function of IP headers in all Ethernet packets. This option can eliminate the amount of CPU and RAM usages, however the Vitual Hub will not perform building and maintenance of the IP address table internally, and some IP-related security policies will not work effectively."

What exactly does "will not work effectively." mean?
What will not work, what will be less effective and how will it impact performance.

Disabling this option on a vHub with complicated rules and +- 100 sessions drop CPU usage (over 8 nodes) from 40% above "baseline" to 2%

But which filter can/can't be used with this?

Re: DisableIPParsing

Posted: Thu Jul 23, 2020 10:20 am
by gramler
Will any rules run at all?
ie is the the simple fact that NO rules will execute?

Re: DisableIPParsing

Posted: Fri Nov 20, 2020 5:35 am
by gramler
It seems that layer 3 routing will not work at all with this option disabled?
Is that really so?

If so the only way to use this option is when making use of layer 2 / bridge functionality only.

ps. and thanks for all the help. NOT :-((