> socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 10
> bind(10, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("MailScanner warning: numerical links are often malicious: 0.0.0.0")}, 16) = 0
> connect(10, {sa_family=AF_INET, sin_port=htons(111), sin_addr=inet_addr("
MailScanner warning: numerical links are often malicious: 127.0.0.1")}, 16
As far as I know, with a TCP socket, before a connect..there has to be on the server part an accept..
It is strange..it creates a socket..and after..it wants itself to connect to the same socket?? In fact, they have the same socket id (the socket created..and the one we connect to..), it seems the connect show correct address (
MailScanner warning: numerical links are often malicious: 127.0.0.1)..but what is the MailScanner warning: numerical links are often malicious: 0.0.0.0 on the bind operation?
Could the problem come from a bad network configuration? (I didn't configured anything..)
What I know is that sometimes..I have direct access to the net..some other times..I have to perform a netcardconfigurations (wich performs a dhcp broadcast..)
See u.
Julien.