Hi Thien,
PHAM ANH THIEN wrote:
I could not find a well sample dhcp source code on lwip-1.4.0.rc1 and
contribute folder, could you please to point me where it is?
The main problem with your code isn't finding an example but
understanding lwIP threading and how not to break it. Please read the
UDP and TCP are two totally separate protocols built on top of IP, so
there's (from the protocol point of view) no way they can influence each
other. What you're seeing looks like a misconfiguration or a bug in your
port or application. Normally, what you described should work with lwIP.
Felix
Dear all,
I have a little problem to work with a TCP- and UDP connection at the same
time.
There are no problems when I establish the TCP connection or the UDP
connection separately. Only if I would use a UDP connection simultaneously
with one TCP link, I could not receive all UDP frames on
It seems like the makefile is somehow mixing lwIP's definitions with hat of
another network stack. You might be better off posting this question in an ecos
forum, although you might be lucky and find someone with detailed ecos
knowledge on this list... ;-)
Just from reading the log file, and th
On Mon, 2010-10-25 at 21:54 +0700, PHAM ANH THIEN wrote:
> Dear Simon,
>
> Thanks for your quickly reply.
>
> I could not find a well sample dhcp source code on lwip-1.4.0.rc1 and
> contribute folder, could you please to point me where it is?
Searching through the contrib folder for "dhcp_start"
On Mon, 2010-10-25 at 16:26 +0200, michelcky wrote:
> Unfortunately, the application written with this grafcet runner cannot
> be modified.
If the application can't be modified you either need to find someone who
can modify it to use the sockets API properly or wrap it in some code of
your own tha
Dear Simon,
Thanks for your quickly reply.
I could not find a well sample dhcp source code on lwip-1.4.0.rc1 and
contribute folder, could you please to point me where it is?
Thank you very much,
Thien
On Mon, Oct 25, 2010 at 5:19 PM, Simon Goldschmidt wrote:
> You are completely violating lwI
>1) read 2 bytes to find the size of message
>2a) try to read message-size-bytes
>2b) if you get less than message-size-bytes loop to read the rest of the
message until you've got all you want.
OK. I'd try this way this morning. I used the select API to have timeout's
benefit.
You confirm that w
On Mon, 2010-10-25 at 15:30 +0200, m.sim...@xool.fr wrote:
>
> On Mon, 25 Oct 2010 13:59:29 +0100, Kieran Mansley
> wrote:
> > TCP or UDP? The two handle fragmentation rather differently.
> >
>
> Hi,
>
> Using TCP only. We don't try UDP.
OK, that's easy then: it's up to the application to de
Hi
I run into a problem when trying to build a redboot with network support
for my at91sam7x512-based board. In configtool for eCOS, I enabled the
macro CYGPKG_REDBOOT_NETWORKING. For further details of my configuration -
please see the attachment.
When building, the above macro leads to r
Hi All,
I am providing fix that enable running the minimal echo demo
application under Linux.
Without this fix I was not able to run ./echop, because all inbound
ARP packets were silently discarded.
NOTE: The fix also includes my yesterday's fix regarding "possible
access violation in case of err
On Mon, 25 Oct 2010 13:59:29 +0100, Kieran Mansley
wrote:
> TCP or UDP? The two handle fragmentation rather differently.
>
Hi,
Using TCP only. We don't try UDP.
Thanks.
Michel
___
lwip-users mailing list
lwip-users@nongnu.org
http://lists.nongn
TCP or UDP? The two handle fragmentation rather differently.
Kieran
___
lwip-users mailing list
lwip-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/lwip-users
Hi All,
I am providing fix that enable running the minimal echo demo
application under Linux.
Without this fix I was not able to run ./echop, because all inbound
ARP packets were silently discarded.
NOTE: The fix also includes my yesterday's fix regarding "possible
access violation in case of err
Hi,
We have designed an embedded application using LWIP, running on ARM
based board, compiled with Keil uvision and freeRTOS.
The stack used was the 1.3.0 release.
The application is connected to a single PC Windows.
We have detected some problems when a routeur sometimes changes the MTU.
A
You are completely violating lwIP threading: when using tcpip_input and the
tcpip_thread, timers are called for you from that thread already. Also,
dhcp_start() may *not* be called from any other thread than the tcpip_thread
(as any other functions not explicitly allow). Please do read the littl
Dear all,
Has Anyone test get dynamic ip on lwip-1.4.0.rc1? I try to do it with this
code:
{
/* Configure dynamic IP */
vhPrintf("Configure dynamic IP...\n");
netif_add(pEMAC_if, NULL, NULL, NULL, NULL, ethernetif_init,
tcpip_input);
/* make it the default inte
17 matches
Mail list logo
