02-05-2013
Directory csum / cksum
I've created a directory in /tmp/csum-test on AIX 6.1. Then another under AIX 7.1 host called /tmp/csum-test. There is no files in the directories.
When I run csum -h SHA1 /tmp/csum-test on AIX 6.1 host it gives me a different value then if I run csum -h SHA1 /tmp/csum-test under the AIX 7.1 host. Granted the csum binaries are different however should csum have reported a different value and what is it including in it's comparisons for directories and files?
In simpler terms, what is this command comparing? I've searched around but couldn't find an answer that explicitly outlines the logic.
Cheers,
Tom
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
hello all.
I'm not asking about the algorithm - or how it goes about computing the checksum - I'm asking how it views/looks at the files it does the cksum on.
For instance:
Say you had a directory named "dir_A"
And within this directory you had some files.
So:
dir_A
- file1
-... (5 Replies)
Discussion started by: kapolani
5 Replies
2. Shell Programming and Scripting
Hi there,
I have a query about cksum. I'm running a script on the Unix box and in a script the cksum result differs from when I run it manually. As far as I can see the file is not being changed, is there any other times that the cksum would be different. (4 Replies)
Discussion started by: rjsha1
4 Replies
3. Shell Programming and Scripting
Hi,
I have a working script, well it works on my machine but when I try it on others the cksum section does not work properly (I know the scripting is not of a high quality but I'm just trying to get it working)
Heres the script:
#!/bin/sh
case $# in
0) echo "usage: enshar filename... (7 Replies)
Discussion started by: Dim-Wit
7 Replies
4. Shell Programming and Scripting
hi,
I am trying to use the cksum feature in unix. when i make a call to it i get returned something along the lines of:
4603435 14 file3
how do i get the first part of this response only; i.e:
4603435
I'm trying to use at a way without the use of sed and creating temp... (4 Replies)
Discussion started by: leeRoberts2007
4 Replies
5. UNIX for Advanced & Expert Users
Hi,
On what factors does the cksum depend.
If i build 2 machines exactly the same, then can i get the checksum of 2 compiled files same.
Thanks (3 Replies)
Discussion started by: vibhor_agarwali
3 Replies
6. Shell Programming and Scripting
Hi all,
So I have a binary file and I need to generate an expected EEPROM checksum for it. Ideally, I would like to input the file (with the path) and output a computed checksum. Ive been using (cksum file1) with no avail and I was just curious as to whether there is such thing as EEPROM cksum,... (1 Reply)
Discussion started by: TeamUSA
1 Replies
7. UNIX for Advanced & Expert Users
I know i can run cksum <filename> . However, how i can run cksum on all the files and directories in the $HOME ?? (SUNOS) (4 Replies)
Discussion started by: moe458
4 Replies
8. UNIX for Dummies Questions & Answers
I did this:
ls -lrRt | grep ^* | cksum *
but it is showing cksum of sub-directories.
Thanks You
Please use code tags when posting data and code samples, thank you. (3 Replies)
Discussion started by: ezee
3 Replies
9. Solaris
Hi,
I am getting read error when i run cksum </dir> but this command runs successfully for the files and in different server it runs for both files and directories. I am using in both the servers solaris 10 with patch 148888-03. Please suggest...
# cksum ravi(directory)
3454912345 0... (3 Replies)
Discussion started by: Navkreddy
3 Replies
LEARN ABOUT OSX
tc-tunnel_key
Tunnel metadata manipulation action in tc(8) Linux Tunnel metadata manipulation action in tc(8)
NAME
tunnel_key - Tunnel metadata manipulation
SYNOPSIS
tc ... action tunnel_key { unset | SET }
SET := set src_ip ADDRESS dst_ip ADDRESS id KEY_ID dst_port UDP_PORT [ csum | nocsum ]
DESCRIPTION
The tunnel_key action combined with a shared IP tunnel device, allows to perform IP tunnel en- or decapsulation on a packet, reflected by
the operation modes UNSET and SET. The UNSET mode is optional - even without using it, the metadata information will be released automati-
cally when packet processing will be finished. UNSET function could be used in cases when traffic is forwarded between two tunnels, where
the metadata from the first tunnel will be used for encapsulation done by the second tunnel. SET mode requires the source and destination
ip ADDRESS and the tunnel key id KEY_ID which will be used by the ip tunnel shared device to create the tunnel header. The tunnel_key
action is useful only in combination with a mirred redirect action to a shared IP tunnel device which will use the metadata (for SET ) and
unset the metadata created by it (for UNSET ).
OPTIONS
unset Unset the tunnel metadata created by the IP tunnel device. This function is not mandatory and might be used only in some specific
use cases (as explained above).
set Set tunnel metadata to be used by the IP tunnel device. Requires id , src_ip and dst_ip options. dst_port is optional.
id Tunnel ID (for example VNI in VXLAN tunnel)
src_ip Outer header source IP address (IPv4 or IPv6)
dst_ip Outer header destination IP address (IPv4 or IPv6)
dst_port
Outer header destination UDP port
[no]csum
Controlls outer UDP checksum. When set to csum (which is default), the outer UDP checksum is calculated and included in the
packets. When set to nocsum, outer UDP checksum is zero. Note that when using zero UDP checksums with IPv6, the other tunnel
endpoint must be configured to accept such packets. In Linux, this would be the udp6zerocsumrx option for the VXLAN tunnel
interface.
If using nocsum with IPv6, be sure you know what you are doing. Zero UDP checksums provide weaker protection against cor-
rupted packets. See RFC6935 for details.
EXAMPLES
The following example encapsulates incoming ICMP packets on eth0 into a vxlan tunnel, by setting metadata to VNI 11, source IP 11.11.0.1
and destination IP 11.11.0.2, and by redirecting the packet with the metadata to device vxlan0, which will do the actual encapsulation
using the metadata:
#tc qdisc add dev eth0 handle ffff: ingress
#tc filter add dev eth0 protocol ip parent ffff:
flower
ip_proto icmp
action tunnel_key set
src_ip 11.11.0.1
dst_ip 11.11.0.2
id 11
action mirred egress redirect dev vxlan0
Here is an example of the unset function: Incoming VXLAN traffic with outer IP's and VNI 11 is decapsulated by vxlan0 and metadata is unset
before redirecting to tunl1 device:
#tc qdisc add dev eth0 handle ffff: ingress
#tc filter add dev vxlan0 protocol ip parent ffff: flower
enc_src_ip 11.11.0.2 enc_dst_ip 11.11.0.1 enc_key_id 11 action tunnel_key unset action mirred egress redirect dev tunl1
SEE ALSO
tc(8)
iproute2 10 Nov 2016 Tunnel metadata manipulation action in tc(8)