05-28-2008
Quote:
Originally Posted by
aamirglb
Hello Friends,
I'm constructing the IP Packets by using the RAW Sockets. If I give any value for VER/TTL/Protocol the packet is being transmitted with that particular values.
But in case of IP Checksum, I'm always getting the correct checksum value irrespective of the value I give.
Can anyone please let me know, who is filling the correct checksum and how to disable it??
Thanks in Advance.
Regards,
Aamir
LOL, its the kernel obviously
, what option did ya use after opening the socket ???
AFAIK, if you include the ip header (which you did) then the kernel will compute that checksum for you if checksum field is 0 otherwise your packet will be sent using that value... So your problem seems a bit weird to me too
10 More Discussions You Might Find Interesting
1. SCO
Does anyone know the answer to this?
When I run "sum -r" on a file that I've down loaded from the sco website, the 1st set of numbers differs from the checksum on the download page but the
2nd set matches.
If I try to install the patch, I get errors.
Anyone has an answer? (3 Replies)
Discussion started by: jn5519
3 Replies
2. Solaris
Hi Community,
Does anyone know how Disabling checksum offload on Solaris10?
Please help me, this issue is very urgent
Thank you
Have a nice day (3 Replies)
Discussion started by: Sunb3
3 Replies
3. Solaris
Anyone can tell me the different between "cksum" and "sum" command on Solaris? I read the man pages but still not get it.
And how to display the md5 checksum for a file.
Thanks, (1 Reply)
Discussion started by: redstone
1 Replies
4. Shell Programming and Scripting
I wanted a script that can give the checksum of a particular zipped file.
Can somebody help me in writing a shell script in getting the checksum of a particular tar file. (1 Reply)
Discussion started by: vkca
1 Replies
5. Shell Programming and Scripting
Hi ALL,
I use solaris OS and SFTP to get/put files from remote server.I use the below command ,
sftp user@host<<EOF
cd "dir"
get --checksum "filename"
EOF
I am getting a strange error as " get --checksum INVALID paramter". It has been working succesfully since last 3 years but all of a... (1 Reply)
Discussion started by: mohanpadamata
1 Replies
6. Shell Programming and Scripting
Hi Guys,
Sometimes, I have a problem with transferred files in ftp session. Thats why I want to produce checksum value in my local server and remote server. But I could not find anyway to produce checksum value of transferred files in remote server.
Do you have any idea?
Thanks,
Emre (3 Replies)
Discussion started by: ce_emre21
3 Replies
7. UNIX for Dummies Questions & Answers
Hi All,
In file transfer with sftp protocol, what is the purpose "checksum" solves? Is this something not getting the file which has already been bought?
Waiting for your response !!! (1 Reply)
Discussion started by: sk84993
1 Replies
8. IP Networking
Hello
I am communicating with two devices using my computer over UDP protocol. The application is running fine. When I monitored the UDP traffic using Wireshark software, I found that there were too many Checksum errors.
Please find attached the png file showing this error. I am about to... (0 Replies)
Discussion started by: AustinCann
0 Replies
9. Solaris
Hi Guys,
I have about MD5 checksum so many times but I can't figure out how to use it. Can someone please show me how to perform an MD5 checksum?
Thanks a lot guys. (1 Reply)
Discussion started by: cjashu
1 Replies
10. Shell Programming and Scripting
is there a way to get a script to do a checksum on itself?
something like this:
#!/bin/sh
myexpectedsig=$(cksum $0 | awk '{print $1}')
if ; then
exit
else
who
uptime
date
fi
im looking for something that would always represent the running script, which is why im... (6 Replies)
Discussion started by: SkySmart
6 Replies
XNB(4) BSD Kernel Interfaces Manual XNB(4)
NAME
xnb -- Xen Paravirtualized Backend Ethernet Driver
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
options XENHVM
device xenpci
DESCRIPTION
The xnb driver provides the back half of a paravirtualized xen(4) network connection. The netback and netfront drivers appear to their
respective operating systems as Ethernet devices linked by a crossover cable. Typically, xnb will run on Domain 0 and the netfront driver
will run on a guest domain. However, it is also possible to run xnb on a guest domain. It may be bridged or routed to provide the net-
front's domain access to other guest domains or to a physical network.
In most respects, the xnb device appears to the OS as an other Ethernet device. It can be configured at runtime entirely with ifconfig(8).
In particular, it supports MAC changing, arbitrary MTU sizes, checksum offload for IP, UDP, and TCP for both receive and transmit, and TSO.
However, see CAVEATS before enabling txcsum, rxcsum, or tso.
SYSCTL VARIABLES
The following read-only variables are available via sysctl(8):
dev.xnb.%d.dump_rings
Displays information about the ring buffers used to pass requests between the netfront and netback. Mostly useful for debugging, but
can also be used to get traffic statistics.
dev.xnb.%d.unit_test_results
Runs a builtin suite of unit tests and displays the results. Does not affect the operation of the driver in any way. Note that the
test suite simulates error conditions; this will result in error messages being printed to the system log.
SEE ALSO
arp(4), netintro(4), ng_ether(4), xen(4), ifconfig(8)
HISTORY
The xnb device driver first appeared in FreeBSD 10.0.
AUTHORS
The xnb driver was written by Alan Somers <alans@spectralogic.com> and John Suykerbuyk <johns@spectralogic.com>.
CAVEATS
Packets sent through Xennet pass over shared memory, so the protocol includes no form of link-layer checksum or CRC. Furthermore, Xennet
drivers always report to their hosts that they support receive and transmit checksum offloading. They "offload" the checksum calculation by
simply skipping it. That works fine for packets that are exchanged between two domains on the same machine. However, when a Xennet inter-
face is bridged to a physical interface, a correct checksum must be attached to any packets bound for that physical interface. Currently,
FreeBSD lacks any mechanism for an Ethernet device to inform the OS that newly received packets are valid even though their checksums are
not. So if the netfront driver is configured to offload checksum calculations, it will pass non-checksumed packets to xnb, which must then
calculate the checksum in software before passing the packet to the OS.
For this reason, it is recommended that if xnb is bridged to a physical interface, then transmit checksum offloading should be disabled on
the netfront. The Xennet protocol does not have any mechanism for the netback to request the netfront to do this; the operator must do it
manually.
BUGS
The xnb driver does not properly checksum UDP datagrams that span more than one Ethernet frame. Nor does it correctly checksum IPv6 packets.
To workaround that bug, disable transmit checksum offloading on the netfront driver.
BSD
June 6, 2014 BSD