All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oscar Mechanic <oscar@ufomechanic.net>
To: netfilter-devel@lists.netfilter.org
Subject: bandwidth saving idea
Date: Mon, 11 Jul 2005 14:16:42 +0100	[thread overview]
Message-ID: <1121087802.4967.35.camel@OSCARLAPLIN> (raw)
In-Reply-To: <42C853F4.6010702@outerspace.dyndns.org>

Hi

   You could suggest the mail should go to LARTC but as I intend to use
netfilter codebase. You may consider this to be daft

Simple scenario

I have machines one is alabama and the other in berkley called machine A
and machine B they are both routers.

machine A has a serial number A000 and machine B has a serial number
B000.

machine A and machine B send packets to each other all the time as they
belong to the same business. These may be citrix packets POP packets
etc...

Machine A sends a packet to machine B. As the packet passes through
machine A it records the MD5 checksum on the packet and holds it in
memory. Machine B is doing the same (All packets sent from A the
checksums are recorded) and it is holding the payload aswell. The key
for finding the payload is the checksum. 

For simplicity lets say the max size of the (FIFO)list in memory is
1000. 

If the same packet is sent again through A it does not send the payload
to Machine B but sends the checksum. B sees the checksum finds the
payload and replaces the checksum with the payload.

(This should work! but it only becomes useful if you can do it with a
list of checksums in the one packet)

If I am not mistaken I can do this with QUEUE target and then turn it
into a module.


Opinions anyone ? 
  

  reply	other threads:[~2005-07-11 13:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-01  0:41 Iptables and kernel modules LAAROUCHI Youssef
2005-07-03 21:09 ` Jonas Berlin
2005-07-11 13:16   ` Oscar Mechanic [this message]
2005-07-11 13:26     ` bandwidth saving idea Eric Leblond
2005-07-11 14:38       ` Oscar Mechanic
2005-07-11 14:49         ` Eric Leblond
2005-07-11 15:02           ` Amin Azez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1121087802.4967.35.camel@OSCARLAPLIN \
    --to=oscar@ufomechanic.net \
    --cc=netfilter-devel@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.