08-23-2012
What do you mean by packets expecting the same ack ?
ack's are not something you expect but something you acknowledge having received. There is nothing wrong for two packets to show the same ack value, especially here when the party hasn't sent anything in the meantime.
9 More Discussions You Might Find Interesting
1. Programming
Hi,
I'm trying to create a RAW TCP SYN packet and send it from one Linux machine to another. I know the packet I have created is well formed and is received by the peer.
Now what I want is to get an ACK for my SYN. I want the peer's Network protocol stack to send me an ACK for that. I know... (17 Replies)
Discussion started by: zampya
17 Replies
2. Linux
Hi all,
A security scanner has been done on a linux server and have found that
The remote host does not discard RCP SYN packets which have the FIN flag set.
It tells that I need to request a patch which I haven't found yet.
I have Red Hat Linux release 7.0 (Guinness)
Kernel 2.2.16-22... (2 Replies)
Discussion started by: bert.n
2 Replies
3. 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
4. Programming
Hello All
Hope someone can help me with an idea or two on how to approach the following situation;
I currently have a process that generates sequenced files. The sequencing is very important and skipping sequences are not allowed. The applicaton has a single thread that consume data produced... (9 Replies)
Discussion started by: bcpkvh
9 Replies
5. 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
6. Shell Programming and Scripting
Hi!
I have some sequencing data that I have aligned using maq software
Now, I have data that looks like this each line is a 'tag'
chr1 10001
chr1 10002
chr1 10005
chr1 10007
chr1 10008
chr1 10008
chr1 10008
chr1 10019
chr1 10019
chr1 10020
What I really want to find out is how... (1 Reply)
Discussion started by: biobio
1 Replies
7. Shell Programming and Scripting
I am not sure if this is entirely possible, but I want to compare data in a particular column in several .txt files and have a new file generated. I am a biologist with limited unix knowledge. There are currently no programs written for this type of analysis.
First I would like to define the... (1 Reply)
Discussion started by: kellywilliams
1 Replies
8. IP Networking
Hello,
Our software is using a TCP socket (AF_INET, SOCK_STREAM) to communicate with an Ethernet device. When we send a message, the message object writes itself in full onto the socket's stream buffer before the software invokes send() from socket.h.
I'm still researching, but have 2... (1 Reply)
Discussion started by: bix_20002000
1 Replies
9. Solaris
I have problem with oracle solaris 10 running on oracle sparc T4-2 server.
Os information: 5.10 Generic_150400-03 sun4v sparc sun4v
Output from tcpstat.d script
TCP bytes: out outRetrans in inDup inUnorder
6833763 7300 98884 0... (2 Replies)
Discussion started by: insatiable1610
2 Replies
CTL(5) CTL file format of ASIM/LIP6/CAO-VLSI lab. CTL(5)
NAME
ctl - Control Temporal Logic file format.
ORIGIN
This software belongs to the ALLIANCE CAD SYSTEM developed by the ASIM team at LIP6 laboratory of Universite Pierre et Marie CURIE, in
Paris, France.
Web : http://asim.lip6.fr/recherche/alliance/
E-mail : alliance-users@asim.lip6.fr
DESCRIPTION
This document describes the CTL file format used by moka(1) for model checking of finite states machine description.
This CTL file format subset is defined to enable classical CTL formulae description.
A CTL file is made of two parts: a declaration part and a formulae statement part.
The declaration part described types, constants, macros and all variables used in CTL formulae. It also describes assumption conditions
and initial conditions that have to be applied by moka(1) during the model checking.
The formulae statement part described all the CTL formulae that have to be verified.
All boolean and relational VHDL operators are supported (see vbe(5)) and also the 8 CTL operators AF, AG, AX, AU, EF, EG, EX and EU. The
CTL file format support also the imply boolean operator '->' and the equivalence operator '<=>'.
EXAMPLE
-- user type definition
TYPE A_ETAT_TYPE IS (A_E0, A_E1);
TYPE B_ETAT_TYPE IS (B_E0, B_E1);
-- variables definition
VARIABLE A_NS, A_CS : A_ETAT_TYPE;
VARIABLE B_NS, B_CS : B_ETAT_TYPE;
VARIABLE ck : BIT;
VARIABLE data_in : BIT;
VARIABLE data_out : BIT;
VARIABLE reset : BIT;
VARIABLE ack : BIT;
VARIABLE req : BIT;
-- example of a macros definition
DEFINE def1 : BOOLEAN := ack='1';
-- the assigned value can be a constant
DEFINE c1 : BIT := '1';
-- the assumption condition
ASSUME ass1 := (reset='0');
-- the initial reset condition
-- be careful, the assumption condition is not applied
-- to the initial conditions.
RESET_COND init1 := (reset='1');
-- It is also possible to describe the first state
-- with the INITIAL keywork, as follows:
--
-- INITIAL init1 := ((A_CS=A_E0) AND (B_CS=B_E0));
--
-- formulae description statement part
begin
prop1 : EX( ack='1' );
prop2 : AG( req -> AF( ack ) );
prop4 : AU( req='1', ack='1');
end;
SEE ALSO
moka(1)
BUG REPORT
This tool is under development at the ASIM department of the LIP6 laboratory.
We need your feedback to improve documentation and tools.
ASIM
/LIP6 August 5, 2002 CTL(5)