On Fri, 2010-03-19 at 10:19 +0100, Marianovich, Andre wrote: > Hi > > At some point there was a mail in which someone had a problem with the > tcp_connect function but there was no answer. This did not seem to call > the callback function. I now have the same problem. I would like to > write a client (lwIP RAW API) to connect to a host running iperf. But > apparently the tcp_connect function does nothing, does not call the > callback function I suppose and it will not connect. All should run on > the PPC 405 of a Xilinx Virtex 4 board. Below I've added the whole code > which is quite similar to the code of the previously mentioned message.
To solve this we need to establish a cause for why the connected callback is not happening. Could you for example see if the tcp_connect() results in SYN packets being sent on the wire, and the other end responding (easiest to do this with a packet capture)? If that works it would be worth turning on some of the debugging in lwIP to establish what happens when the other end responds. If you don't seen any packets on the wire, then there is likely some problem between lwIP and the driver you're using. Are you able to test this and establish that it is all working correctly? E.g. sending and receiving UDP packets. Do you know which version of lwIP you are using, and which port to your hardware? Kieran _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
