Author Topic: inetcfg.ini - window size, but why this result?  (Read 1518 times)

Dariusz Piatkowski

  • Hero Member
  • *****
  • Posts: 1417
  • Karma: +27/-0
    • View Profile
inetcfg.ini - window size, but why this result?
« on: March 03, 2025, 05:13:19 am »
So a couple of days ago the AOS testers list was asked with giving some new SEND & RECEIVE window sizes a try.

Ever since I went to a 1Gig fibre line I had tweaked my inetcfg.ini to use the max allowable value for both TCP & UDP windows.

However this request prompted me to test and surprisingly enough I found that the smaller window size actually caused a repeatable 20-25% improvement when doing a speedtest run.

OK, nice...so I permanently updated my inetcfg.ini with these values, and carried along.

Today I needed to reboot my machine, all was good. The box re-started fine, I brought up my regular apps: PMMail, Thunderbird, RDP, Firefox...but whoa...hang on...why isn't Firefox taking me anywhere????

Yeah, it just sat there, spinning, "connecting..." but it would never go anywhere.

So I check the other apps: PMMail is good, but TB...nope, same story as FF.

I whip up the speedtest CLI...nope, not going anywhere either.

After numerous trials I determined that the window sizing was impacting certain apps. Further on, I found that on my machine anything smaller than 131,072 (so 128K) would cause the above described "stall", while anything bigger consistenty 'just works'!!! ugh???

Can anyone explain this please?

Here are the contents of my inetcfg.ini:

Code: [Select]
#Inetcfg:       CURRENT DEFAULT MINIMUM MAXIMUM

keepalive       60      7800    0       7800    KeepAlive (sec)
tcpswinsize     131072  32768   1024    246723  TCP SendWindow Size
tcprwinsize     131072  32768   1024    246723  TCP RecvWindow Size
udpswinsize     131072  9216    1024    246723  UDP SendWindow Size
udprwinsize     131072  41600   1024    246723  UDP RecvWindow Size
lingertime      120     120     0       65535   Linger Time (sec)
probecnt        8       8       1       8       Number Of KeepAlive Probes
ipforward       0       0       0       1       IP Forwarding flag ON/OFF
mtudiscover     1       1       0       1       TCP Path MTU Discovery ON/OFF
arpkillc        1200    1200    180     15300   ARP Complete TimeOut (sec)
arpkilli        180     180     60      1200    ARP InComplete TimeOut (sec)
lipcstswinsize  10240   10240   1024    246723  LIPC Stream SendWindow Size
lipcstrwinsize  10240   10240   1024    246723  LIPC Stream RecvWindow Size
lipcdgswinsize  2048    2048    1024    246723  LIPC Dgram SendWindow Size
lipcdgrwinsize  4096    4096    1024    246723  LIPC Dgram RecvWindow Size
synattack       0       0       0       1       SYN Attack Flag ON/OFF
syncookie       0       0       0       1       SYN Cookie Flag ON/OFF
firewall        0       0       0       1       FIREWALL ON/OFF
multidefrt      1       1       0       1       Multiple Default Routes ON/OFF
winscale        1       1       0       1       TCP Window Scale ON/OFF
timestmp        1       0       0       1       TCP TimeStamps ON/OFF
realslow        20      20      1       100     TCP TW Q Slow Timeout ticks
perfhttp        1       1       0       1       Fast Path HTTP ON/OFF
tcpttl          64      64      1       255     TCP  TTL (hops)
udpttl          64      64      1       255     UDP  TTL (hops)
icmpttl         64      64      1       255     ICMP TTL (hops)
fragttl         60      60      1       255     Fragment TTL (sec)
reusetw         1       1       0       1       Reuse Time Wait ON/OFF
msl             30      30      1       16384   TCP MaxSegLifeTime (sec)
cc              0       0       0       1       TTCP function ON/OFF
sack            1       0       0       1       Selective ACK ON/OFF

Remy

  • Hero Member
  • *****
  • Posts: 823
  • Karma: +14/-1
    • View Profile
Re: inetcfg.ini - window size, but why this result?
« Reply #1 on: March 03, 2025, 11:42:33 am »
Which OS/2 driver do you use and what's your network chipset ?

I always have this king of issue (I found one setting which "seems" having reduced stallen state)

I have a chipset which is support by MMRE driver,  I have a correct speed on some link but awfull on  other like when I download updates from Smedley site. (speed never goes above 138KB !  - under windows, up to 2MB or trying using Aos from under a virtual box using a different driver than MMRE, speed goes up to 1.8MB and never got a stall status !)

I reported this problem several times to ArcaOS since Arcos 2.0 and each time, it ended with no problem found, for them MMRE is well operationnal....
The MMRE driver is unable to correctly work with in my case RealtekĀ® 8111G Gigabit LAN

my config:
PC/Arca OS (enabled as 100Mb ]-----[ Powerline technology Gb ]---- Eth Gb ----( internet box)
when under Windows (enabled as Gb and throuput up to 250Mb)

Checkjng the parm I changed and will update this post...     
       

Remy

  • Hero Member
  • *****
  • Posts: 823
  • Karma: +14/-1
    • View Profile
Re: inetcfg.ini - window size, but why this result?
« Reply #2 on: March 03, 2025, 09:41:35 pm »
Only entries left into inetcfg.ini since upgrading to AOs 5.1.1
Other optimized entries removed (when was under 5.0.x)

keepalive 800
realslow 30
lingertime 240

arpkillc 3600
arpkilli 300
timestmp 1
synattack 1
sack 1

Dave Yeo

  • Hero Member
  • *****
  • Posts: 5270
  • Karma: +122/-1
    • View Profile
Re: inetcfg.ini - window size, but why this result?
« Reply #3 on: March 04, 2025, 12:53:04 am »
Only entries left into inetcfg.ini since upgrading to AOs 5.1.1
Other optimized entries removed (when was under 5.0.x)

keepalive 800
realslow 30
lingertime 240

arpkillc 3600
arpkilli 300
timestmp 1
synattack 1
sack 1

After backing up your inetcfg.ini, run "inetcfg -g all" to bring them back. After optimizing, run "inetcfg -s all"
Seems you only need  to have your optimized settings in inetcfg.ini.

Dariusz Piatkowski

  • Hero Member
  • *****
  • Posts: 1417
  • Karma: +27/-0
    • View Profile
Re: inetcfg.ini - window size, but why this result?
« Reply #4 on: March 04, 2025, 05:41:28 am »
Hello Remy!

Which OS/2 driver do you use and what's your network chipset ?

I also use the MMRE driver here:

Code: [Select]
Signature:       @#Arca Noae LLC:1.1.9#@##1## 18 Sep 2023 13:35:25     DAZAR1
 ::::9::SVN105@@RealTek 8139C+/8169/8169S/8110S/8168/8111/8101E PCI NIC driver
Vendor:          Arca Noae LLC
Revision:        1.01.9
Date/Time:       18 Sep 2023 13:35:25
Build Machine:   DAZAR1
FixPak Version:  SVN105
File Version:    1.1.9
Description:     RealTek 8139C+/8169/8169S/8110S/8168/8111/8101E PCI NIC driver

I always have this king of issue (I found one setting which "seems" having reduced stallen state)

I have a chipset which is support by MMRE driver,  I have a correct speed on some link but awfull on  other like when I download updates from Smedley site. (speed never goes above 138KB !  - under windows, up to 2MB or trying using Aos from under a virtual box using a different driver than MMRE, speed goes up to 1.8MB and never got a stall status !)

Hmm, so this is slightly different symptom than what I'm seeing, but that is not to say that the root cause may be different.

Strangely enough in my case I can actually change these window sizes AFTER the application has been started, and that seems to be alright, it does not cause any problems. However trying to change first and then start the app will cause a guaranteed failure to connect.

I reported this problem several times to ArcaOS since Arcos 2.0 and each time, it ended with no problem found, for them MMRE is well operationnal....
The MMRE driver is unable to correctly work with in my case RealtekĀ® 8111G Gigabit LAN

My MSI motherboard specs the Realtek RTL8111E NIC hardware and is reported as follows:

Code: [Select]
Bus 2 (PCI Express), Device Number 0, Device Function 0
 Vendor 10ECh Realtek Semiconductor Co., Ltd.
 Device 8168h RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 Command 0007h (I/O Access, Memory Access, BusMaster)
 Status 0010h (Has Capabilities List, Fast Timing)
 Revision 06h, Header Type 00h, Bus Latency Timer 00h
 Self test 00h (Self test not supported)
 Cache line size 64 Bytes (16 DWords)
 PCI Class Network, type Ethernet
 Subsystem ID 76401462h Unknown
 Subsystem Vendor 1462h Micro-Star International Co., Ltd. [MSI]
 Address 0 is an I/O Port : D000h..D0FFh
 Address 1 is not present or not configured!
 Address 2 is a Memory Address (64-bit, Prefetchable) : FE904000h..FE904FFFh
 Address 4 is a Memory Address (64-bit, Prefetchable) : FE900000h..FE903FFFh
 System IRQ 46, INT# A
...

Remy

  • Hero Member
  • *****
  • Posts: 823
  • Karma: +14/-1
    • View Profile
Re: inetcfg.ini - window size, but why this result?
« Reply #5 on: March 04, 2025, 10:07:35 am »
Here (I'm at latest build level but this changed nothing)

Code: [Select]
Signature:       @#Arca Noae LLC:1.1.10#@##1## 5 Dec 2024 17:57:29      DAZAR1
  ::::10::SVN110@@RealTek 8139C+/8169/8169S/8110S/8168/8111/8101E PCI NIC driver

Vendor:          Arca Noae LLC
Revision:        1.01.10
Date/Time:       5 Dec 2024 17:57:29
Build Machine:   DAZAR1
FixPak Version:  SVN110
File Version:    1.1.10
Description:     RealTek 8139C+/8169/8169S/8110S/8168/8111/8101E PCI NIC driver

and HW:

Code: [Select]
Bus 5 (PCI Express), Device Number 0, Device Function 0
 Vendor 10ECh Realtek Semiconductor Co., Ltd.
 Device 8168h RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 Command 0007h (I/O Access, Memory Access, BusMaster)
 Status 0010h (Has Capabilities List, Fast Timing)
 Revision 0Ch, Header Type 00h, Bus Latency Timer 00h
 Self test 00h (Self test not supported)
 Cache line size 64 Bytes (16 DWords)
 PCI Class Network, type Ethernet
 Subsystem ID 79221462h Unknown
 Subsystem Vendor 1462h Micro-Star International Co., Ltd. [MSI]
 Address 0 is an I/O Port : E000h..E0FFh
 Address 1 is not present or not configured!
 Address 2 is a Memory Address (64-bit) : F7100000h..F7100FFFh
 Address 4 is a Memory Address (64-bit, Prefetchable) : F0000000h..F0003FFFh
 System IRQ (disabled), INT# A
 
 I have System IRQ (disabled) !?

under  HW Manager:  IRQ 53 EXC
« Last Edit: March 04, 2025, 12:40:14 pm by Remy »

Lars

  • Hero Member
  • *****
  • Posts: 1399
  • Karma: +70/-0
    • View Profile
Re: inetcfg.ini - window size, but why this result?
« Reply #6 on: March 05, 2025, 08:29:13 am »
I suspect that "System IRQ (disabled)" indicates that it is using MSI instead of the conventional PCI IRQ Line.
I have the same PCI output but it also says "MSI is enabled".