Distributed Checksum Clearinghouse 1.3.101 (Default branch)

Tags

Special Forums News, Links, Events and Announcements Software Releases - RSS News Distributed Checksum Clearinghouse 1.3.101 (Default branch)

01-11-2009

Registered User

26,240, 27

Join Date: Sep 2000

Last Activity: 1 August 2008, 3:09 PM EDT

Posts: 26,240

Thanks Given: 0

Thanked 27 Times in 26 Posts

Distributed Checksum Clearinghouse 1.3.101 (Default branch)

Distributed Checksum Clearinghouse (DCC) is a system of clients and servers that collect and count checksums related to mail messages. The counts can be used by SMTP servers and mail user agents to detect and reject bulk mail. DCC servers can exchange common checksums. The checksums include values that are "fuzzy", or constant across common variations in bulk messages. License: Free for non-commercial use Changes:
Groups of DNS blacklists that can be independently enabled in per-user whiteclnt files are supported.

More...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Virtualization and Cloud Computing

Dapper Distributed Dataflow Engine 0.91 (Default branch)

Dapper, or "Distributed and Parallel Program Execution Runtime", is a tool for taming the complexities of developing for large-scale cloud and grid computing, enabling the user to create distributed computations from the essentials: the code that will execute, along with a dataflow graph...

LEARN ABOUT OSX

tc-csum

Checksum action in tc(8)					       Linux						  Checksum action in tc(8)

NAME

       csum - checksum update action

SYNOPSIS

       tc ... action csum UPDATE

       UPDATE := TARGET [ UPDATE ]

       TARGET := { ip4h | icmp | igmp | tcp | udp | udplite | sctp | SWEETS }

       SWEETS := { and | or | + }

DESCRIPTION

       The csum action triggers checksum recalculation of specified packet headers. It is commonly used to fix incorrect checksums after the pedit
       action has modified the packet content.

OPTIONS

       TARGET Specify which headers to update: IPv4 header (ip4h), ICMP header (icmp), IGMP header (igmp), TCP header  (tcp),  UDP  header  (udp),
	      UDPLite header (udplite) or SCTP header (sctp).

       SWEETS These are merely syntactic sugar and ignored internally.

EXAMPLES

       The following performs stateless NAT for incoming packets from 192.0.2.100 to new destination 198.51.100.1. Assuming these are UDP packets,
       both IP and UDP checksums have to be recalculated:

	      # tc qdisc add dev eth0 ingress handle ffff:
	      # tc filter add dev eth0 prio 1 protocol ip parent ffff: 
		   u32 match ip src 192.0.2.100/32 flowid :1 
		   action pedit munge ip dst set 198.51.100.1 pipe 
		   csum ip and udp

SEE ALSO

       tc(8), tc-pedit(8)

iproute2							    11 Jan 2015 					  Checksum action in tc(8)

Software Releases - RSS News