I was wondering if the usual TCP window setting of 840 makes any sense in our current mesh.
This setting was imposed by the assumption that our IP traffic will pass over ax.25 connections, with their MTU and ACK limitations, and does not affect AXIP, AXUDP or other transfer modes.
The question is: Is there anyone forwarding TCP/IP over AX.25 at this moment? Because if not, we could drop that window setting in the routing daemons and get a more streamlined data flow.
Marius, YO2LOJ
Yes, eastnet has several nodes doing this, and more are under construction. --- Pardon my brevity, I'm on a Samsung Galaxy Note 3. Sent via the axMail-FAX suite.
On June 8, 2017 6:59:30 AM marius@yo2loj.ro wrote:
I was wondering if the usual TCP window setting of 840 makes any sense in our current mesh.
This setting was imposed by the assumption that our IP traffic will pass over ax.25 connections, with their MTU and ACK limitations, and does not affect AXIP, AXUDP or other transfer modes.
The question is: Is there anyone forwarding TCP/IP over AX.25 at this moment? Because if not, we could drop that window setting in the routing daemons and get a more streamlined data flow.
Marius, YO2LOJ
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
yes, using tcp/ip over ax25 here on and off to a couple local stations
On 2017-06-08 07:59 AM, marius@yo2loj.ro wrote:
I was wondering if the usual TCP window setting of 840 makes any sense in our current mesh.
This setting was imposed by the assumption that our IP traffic will pass over ax.25 connections, with their MTU and ACK limitations, and does not affect AXIP, AXUDP or other transfer modes.
The question is: Is there anyone forwarding TCP/IP over AX.25 at this moment? Because if not, we could drop that window setting in the routing daemons and get a more streamlined data flow.
Marius, YO2LOJ
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-
Brian -
marius＠yo2loj.ro -
ve1jot