Messaggio archiviato #340

Da: "Roderick Klein" <> Intestazioni complete
Messaggio non codificato
Oggetto: Re: [eCS-ISP] Injoy FW 4.2.2 and download datarates (connection speed) the eternal mistery :)
Data: Wed, 16 Jun 2021 21:25:20 +0100
A: eCS ISP Mailing List <>

On 16-06-21 09:11, Massimo S. wrote:

Il 16/06/2021 02:40, Roderick Klein ha scritto:
On 14-06-21 08:59, Massimo S. wrote:
Hi all,

in the eternal mistery of this topic with no help or support from the
the firewall (as default internet gateway) with Intermediary section
values of default

Assemble packets: ON
MTU: 1500
MSS Auto Adjust: disabled

if you do a speed test it say you have a 20Megabit connection while you
have a 100Mb FTTC

playing with these parameters the situation improve
(e.g. giving 1492 as MTU and playing with MSS)

on an FTTC (100Mbit/sec full granted) i'm able even to raise downloads
from 2 MegaBytes/sec to 9MegaBytes/sec, anyway the upstreaming bandwidth
it's not
so much good and i'd like to improve it

even using tcp analyzer

i'm not able to improve further the performances (download/upload
and i get no support at all from the sw house, ticket not answered

Has this simply not been a long standing issue that the performance of
the Injoy firewall, where the systems is connected to a fast internet
connections lags behind ?

playin with RWIN size in inetcfg.ini it seems not to improve too much

while i can survive with this in my office, i still have aound some
Injoy FW
at customers's places and internet speed improvement is giving me some

anyone has experience with IJ FW and a 100Megabit/sec FTTC connection
using INJOY FW as default lan gateway?

I am starting to get the impression this is a a current, please note
thst word *current*, limitation in fxwrap.sys.


do you mean that there could be udpates that fix the issue?
or V5 will fix the issue?

I do not know when and how it can fixed. What does seem to be the case is that the Injoy Firewall can not provide high threwput, we need on modern fiber optic lines.

I get the impression the filtering logic runs at user level in OS/2 (RING 3 cpu level) and the fxwrap driver runs at kernel 0 (ring 0).
I get the impression every TCP/IP packets has to send from rin0 to ring 3 and back to ring 0. This consumes a lot of CPU time if this is correct.

The IBM OS/2 firewall, like on Linux is ring 0 driver. Where the packet filtering is done at kernel level directly. This provides a great perfomance gain. But that IBM filter driver can of course not used by the Injoy Firewall.

Note that make such changes, if that would help is a lot lot of work!
Right now I get the impression the guys at BWW are extremely busy surviving and working on getting the new Otter Browser beta out the door.



Isriviti: Feed, Riassunto, Indice.
Scrivi a ListMaster