SSH overhead.

From: Shashank Khanvilkar (shashank_at_evl.uic.edu)
Date: 06/27/03 

Date: Thu, 26 Jun 2003 17:33:35 -0500

Hi,
When I send a packet of 100 bytes (say) using ssh, how much overhead bytes
can I expect for ssh to add to my packet.
I am assuming that I use public key encryption with following options:
cipher: aes128-cbc
mesage-digest: hmac-md5
compression: none
I know the crude technique of finding out how much overhead will each
cipher+message digest algorithm will add. But I would like to know a more
elegant technique (if any such exists).

Is the following correct:
Application (100 bytes) --> ssh(??) --> TCP ((20 bytes basic + 12 bytes
options = 32 bytes) --> IP (20 bytes) --> ethernet (14 bytes) --> packet
sent over the wire. 

-- 
Regards
Shashank
http://mia.ece.uic.edu/~papers

Relevant Pages

  • Re: bites, bytes, packets, TCP, and DSL speed
    ... there will be 18 bytes of overhead per frame (source and destination MAC ... of overhead (version, header length, type of service, packet length, ... assuming the network can carry full-size Ethernet frames end-to-end, ... Packets larger than your line's MTU size will be fragmented at the IP ...
    (comp.sys.mac.comm)
  • Re: sendfile(2) SF_NOPUSH flag proposal
    ... >>at the start of a transaction and turned off at the end of a transaction. ... it's unintentionally fragging up to one packet ... The overhead of toggling it would be costly. ... > change is cheap" to justify adding this feature. ...
    (freebsd-arch)
  • Re: Cross Realm MIT <-> Windows Close But No Cigar
    ... Info about the two domains and ssh / smbclient test results follows. ... I created some principals and it confirmed the enctype was archfour-hmac: ... debug2: we sent a gssapi-with-mic packet, ...
    (comp.protocols.kerberos)
  • Re: FreeBSD handles leapsecond correctly
    ... :never ever passes a packet again until a down/up on the receiving interface. ... considering that we haven't removed the MP lock from the network ... The single biggest overhead we have right now is that we have not ...
    (freebsd-current)
  • Re: FreeBSD handles leapsecond correctly
    ... >:I've been testing network and routing performance over the past two weeks ... >:never ever passes a packet again until a down/up on the receiving interface. ... > between 3 uS and 1.2 uS per packet of overhead. ... > serialized down to effectively 1 cpu due to the MP lock. ...
    (freebsd-current)