lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] tcp_connect doesn't start the callback function


From: Marianovich, Andre
Subject: Re: [lwip-users] tcp_connect doesn't start the callback function
Date: Fri, 19 Mar 2010 10:54:19 +0100
User-agent: Thunderbird 2.0.0.23 (Windows/20090812)

Thanks for your realy fast reply. Unfortunately I'm totaly new to lwIP but I try to do my best. Well, should I use some kind of network analyzing tool like wireshark to scan if there is packet transfer at all?

I use the lwip130 and this is out of the xilinx documentation:

"lwip130_v1_00_a in EDK provides adapters for the xps_ethernetlite and xps_ll_temac Xilinx® Ethernet MAC cores, and is based on the lwIP stack version 1.3.0."

The Xilinx tools also provide a version 3.00.a of the lwip stack.

When I debug the code everything seems to work fine excepting the callback function of tcp_connect. The whole network hardware work too because a linux that could run too can ping the host and connect to it.


Kieran Mansley schrieb:
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
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-users




reply via email to

[Prev in Thread] Current Thread [Next in Thread]