05-18-2004
Maybe the checksum field is incorrect and your packet gets discarded...
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hiya folks,
I am a windows xp home user and for awhile I have been thinking about changing my OS, the only problem is that I don't know where to start. Is it called Unix or Linux? Are they the same thing? It's really confusing.
I would really appreaciate some help on this. I have looked all... (1 Reply)
Discussion started by: Mr_Pinky
1 Replies
2. Shell Programming and Scripting
suppose I have data in a log file in the below format
date|time|name|email|address|SSN
date|time|name|email|address|SSN
date|time|name|email|address|SSN
is it possible to create a search engine which takes input as three filters out of which two filters should be optional?
say i give... (4 Replies)
Discussion started by: wannalearn
4 Replies
3. UNIX for Advanced & Expert Users
Please tell me details about terms FIN, ACK, SYN, RST; used in TCP based communication. Also tell me any RFC or other document which tell me details about these terms. (1 Reply)
Discussion started by: mansoorulhaq
1 Replies
4. UNIX for Dummies Questions & Answers
I am using vim version 7.1.314.It don't have syn on.Is there any plug in available for syn on or I have to update the version. (2 Replies)
Discussion started by: karthigayan
2 Replies
5. IP Networking
I was analyzing a TCP snoop. And found following scenario
From Server to Client ---> SEQ 2993 ACK 1744 WIN 8192 LEN 13
From Server to Client ---> SEQ 3006 ACK 1744 WIN 8192 LEN 13
From Client to server --> SEQ 1744 ACK 3019 WIN 3304
I just want to know Why Packet 1 and 2... (3 Replies)
Discussion started by: mr_deb
3 Replies
6. Programming
Hi,
I have the requirement to sniff packets from
the Ethernet card on my Linux machine and
process it and feed it to a RANAP protocol stack.
So far I have written the raw packet sniffer
and successfully sniffing packets and do little
processing. However, for huge number of packets ... (9 Replies)
Discussion started by: rstnsrr
9 Replies
7. AIX
(5 Replies)
Discussion started by: Vishal_dba
5 Replies
LO(4) BSD Kernel Interfaces Manual LO(4)
NAME
lo -- software loopback network interface
SYNOPSIS
device loop
DESCRIPTION
The loop interface is a software loopback mechanism which may be used for performance analysis, software testing, and/or local communication.
As with other network interfaces, the loopback interface must have network addresses assigned for each address family with which it is to be
used. These addresses may be set or changed with the SIOCSIFADDR ioctl(2). The loopback interface should be the last interface configured,
as protocols may use the order of configuration as an indication of priority. The loopback should never be configured first unless no hard-
ware interfaces exist.
If the transmit checksum offload capability flag is enabled on a loopback interface, checksums will not be generated by IP, UDP, or TCP for
packets sent on the interface.
If the receive checksum offload capability flag is enabled on a loopback interface, checksums will not be validated by IP, UDP, or TCP for
packets received on the interface.
By default, both receive and transmit checksum flags will be enabled, in order to avoid the overhead of checksumming for local communication
where data corruption is unlikely. If transmit checksum generation is disabled, then validation should also be disabled in order to avoid
packets being dropped due to invalid checksums.
DIAGNOSTICS
lo%d: can't handle af%d. The interface was handed a message with addresses formatted in an unsuitable address family; the packet was
dropped.
SEE ALSO
inet(4), intro(4)
HISTORY
The lo device appeared in 4.2BSD. The current checksum generation and validation avoidance policy appeared in FreeBSD 8.0.
BSD March 15, 2009 BSD