aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: TCP overhead  (Read 3185 times)

emnops

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 2
TCP overhead
« on: October 26, 2004, 07:14:22 PM »
According to this http://www.amule.org/amule/thread.php?threadid=3789 thread, it looks like the "overhead" statistics in amule is not enough for those using internet providers that count all the traffic, including technical TCP packets. So it would be nice to have an additional overhead stat, call it for example "TCP overhead". It should account for the size of implied ack packets received or sent as a response to the peer... This may require acquiring some technical details about the interface of course, but I can't figure all the details now... So, is this possible?
« Last Edit: October 26, 2004, 07:16:00 PM by emnops »
Logged

Jacobo221

  • Hero Member
  • *****
  • Karma: 3
  • Offline Offline
  • Posts: 2712
Re: TCP overhead
« Reply #1 on: October 26, 2004, 11:23:52 PM »
Maybe Preferences -> Connection -> Show overhead bandwidth does that already? no idea really :-/
Greetings!
Logged

lfroen

  • Guest
Re: TCP overhead
« Reply #2 on: October 27, 2004, 02:05:46 PM »
It's not that simple. aMule doesn't know what "lies beneth" - meaning, that there's no way for application to know what is it under tcp. This is what OSI model is about.

From application point of view there's only "socket" thingie - over tcp it doesn't know evet how many packets were sent. Same thing is number of ACK, SYN, FIN, RST packets - application layer doesn't see it, but provider does.
One more variable to calculation - network layer. Over ADSL you have PPTP and/or PPPoE headers.

Remark about "K" and "M" letters - amule using "K" for 1024 and "M" for 1024*1024. While it's true in computers, it's wrong in communications. 100Mbps ethernet meaning that speed is 100*10^6 bits per second. So, provider equipment counts in "K" and "M" - which means 10^3 and 10^6 respectivly.
Logged

phoenix

  • Evil respawning bird from aMule Dev Team
  • Developer
  • Hero Member
  • *****
  • Karma: 44
  • Offline Offline
  • Posts: 2503
  • The last shadow you'll ever see
Re: TCP overhead
« Reply #3 on: October 27, 2004, 07:58:23 PM »
Another very important issue is that when refering to 10^3, a small caps letter "k" should be used.
Like 25 kHz. 25 kbps.

Ok, bad joke, but it is true. :D The kilo prefix is small caps.

Cheers!
Logged

lfroen

  • Guest
Re: TCP overhead
« Reply #4 on: October 27, 2004, 08:23:38 PM »
Go tell it to all comm equipment manufacturers, IEEE, IETF and so on. I just want you to know how many bits your 100_M_ network card can transmit. I don't know if it's M or m written on it's box. It doesn't matter. It transmit and receives 100*10^6 bits. Write it any way you want :)
Logged