[vhochstein]

>At the time of connection establishment the IP address was not specified >explicitely. Just treat 0.0.0.0 as anyt local IP.

Let me try to explain it again.

I ve got a tcp connection between two processes. In some packets both src and dest IP are correct and in other packets one is set to 0.0.0.0

Unfortunetly, I cannot understand, why sometimes you have the correct IP and sometimes not. Your explanation refering to connection establishment does not seam to fit from my point of view.

—
Volker

[vhochstein]

Localhost Monitor works at TDI level, so there are no actual packets there, but blocks of data instead. Some blocks can be splitted or merged, probably this is what you’ve expirienced…

Does that splitting or merging mix up also incomming and outgoing streams?

If your answer is now, than I m definetly missing some data, cause the stream is sendout to another process and received by that process. Unfortunetly, 1606 Bytes are send by Source Process and 3760 Bytes are received by Destination Process. All other “stream packets” in that time slot are OK, so send and received bytes are matching.

—
Volker

[vhochstein]

@SerpentFly wrote:

“IP Address 0.0.0.0” is just any local IP address (it’s not always known from which concrete IP the connection will work from at the time of connection establishment).

Could you please be a little bit more specific? What do you mean by stating “not always known”?
In addition I see these 0.0.0.0 also in already established TCP Pipes.

—
Volker

[Author]

Posts