The information below is for those who need more technical information about our bonding services.
Protocol Support/Port influence:
Bonding is 100% transparent to ALL protocols VPNs are fully supported IPsec, PPTP, etc.
Port forwarding is performed by the customer router; Bonding forwards ALL ports and does not block any ports.
Bonding efficiency is nearly always greater than 85%.
The level of bonding efficiency is related to the speed stability of the lines supporting the bond. In most cases Uplink bonding is 95% and Downlink is 90%
Typical compression ratios of Compression running on Bonders are about 1.5-1.7x for plain text, about 2-4x for HTML, and of course 1.0x for JPEGs, PNGs and other pre-compressed data. Definitive benchmarking of compression effect is difficult as internet / broadband data is made up of an ever changing mix of types of data and levels it can be compressed.
QoS is bi-directional on both data and control packets and 100% fully customisable. Default parameters (all customisable) are: 4 Classes of traffic (Real Time, Interactive, Routine, Bulk).
Reserved percentages for each are: 40%, 20%, 20%, 20% respectively.
Packet Filters and Classes:
Real-time – 40% of bandwidth is reserved for real-time traffic.
- ICMP packets up to 500 bytes
- Inter-Asterisk eXchange version 2 (IAX2) traffic
- SIP and H.323 control traffic
- Packets with DSCP expedited forwarding requested
- This profile will classify VoIP traffic correctly on networks using IAX2 or phones that send traffic with the DSCP expedited forwarding class. On other networks, it may be necessary to identify VoIP traffic using source or destination network matching.
Interactive – 20% of bandwidth is reserved for interactive traffic, classified as follows:
- DNS traffic
- Microsoft RDP traffic
- TCP acknowledgements
- SSH traffic. (To avoid classifying SCP traffic as interactive, SSH is limited to 20 packets per second per connection)
- This is the default class. Packets not matching any filter are classified as routine. 20% of bandwidth is reserved for this traffic.
Bulk – 20% of bandwidth is reserved for bulk traffic, classified as follows.
- FTP traffic On ports 20, 21 only; data traffic on other ports will not be matched.
- HTTP/S traffic part of flows greater than 2 MB
Bond Security (two variants):
HMAC: Hash-based message authentication codes. Data is signed and verified using an HMAC code. The algorithm uses MD5 hashing and a 30-byte secret key. HMAC-MD5 is defined in RFC 2104; or
Encryption: Data is encrypted between bonders and our aggregation network using the DTLS 1.2 protocol. DTLS is based on SSL/TLS, and is defined in RFC 4347 and RFC 6347.
Three ciphers are available: AES 128, AES 256 or Salsa20 256
TCP Accelerating process for dealing with unstable Bonded connections or connections with high jitter. By default TCP Acceleration is enabled on Ports 80, 443 and 8080 (http and https traffic). Additional ports available by request.