lwip-users
[Top][All Lists]
Advanced

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

Re: [lwip-users] RFC: ARP Queueing


From: Paul
Subject: Re: [lwip-users] RFC: ARP Queueing
Date: Fri, 16 Apr 2004 21:44:59 +0930
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113

Hi all,

To get around the udp connection this is what I have done
create a master udp_pcbbound to IP_ADDR_ANY port 69. I have moved the source
ip address compare and source port compare into the udp_receive function.
In my receive function I now create a new udp_pcb, bind it to IP _ADDR_ANY
.port 0 and connect it to the incomming ip address and incomming port. I have now
got my tftp service working, although I havent got timeout supported yet.

I'll try and test and report on the cvs code later next week, if I have the time available.

Paul


Leon Woestenberg wrote:

Hello Paul,

Paul wrote:

Hi Leon,

I think that you are overestimating my understanding of ARP_QUEUEING.

>
OK, can you test the latest CVS sources instead? :-)

seems to have arisen in lwip 0.7. Are there any plans to document or rename the

udp_new()
udp_bind()
udp_connect()
udp_disconnect()
udp_recv()

interface (and the tcp equiv) API?

The documentation should be in the code (above the function names). Or did we miss something?

Can you put the UDP_FLAGS_CONNECTED patch
( I cant find a reference to it at the moment but it went along the lines of
(pcb->flags & UDP_FLAGS_CONNECTED ? (remote_port == src):1) )
in udp_input into the stable lwip. This allows a udp port to receive a connection
from any remote port until it has been connected to a fixed port.

From what I know, a PCB with remote address IP_ADDR_ANY (0.0.0.0) and remote port 0 (zero) should do just that.

Regards,

Leon.


_______________________________________________
lwip-users mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/lwip-users






reply via email to

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