El Viernes, 30 de Junio de 2006 20:30, julien bodd escribió:
socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 10 bind(10, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("
0.0.0.0")}, 16) = 0
connect(10, {sa_family=AF_INET, sin_port=htons(111), sin_addr=inet_addr("
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 (127.0.0.1)..but what is the 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.
I fowarded thi info to higher hackers :D, they will tell us what to do, but, I think you are right: it must be a socket problem and a network config problem. There is some relationship between KDE and GTK failures and networks failures? I mean: when kate and firefox fails, the netowork is ok? or, the network was configured in another way? -- Marcos Guglielmetti * Director del desarrollo de Musix GNU+Linux, 100% Software Libre * Descarga el CD de Musix: (www.musix.org.ar) (www.pc-musica.com.ar/musix) * Videos, programas y otras cosas en: ftp://musix.ourproject.org/pub/musix/ * Reporte de errores a: https://www.musix.org.ar/wiki/index.php?title=Problemas-Bugs *IRC: #musix channel on freenode