Hi all,
Warm Greetings!! I am new in LWIP usage. I like to know which header
lwip will start considering whether in MAC layer headers or IP headers??
Kindly give some explanation about the process of LWIP.
Many Thanks,
--
View this message in context:
http://lwip.100.n7.nabble.com/lwip
Hello All
Did anyone have a look at the lldp code base?
Regards
Amit Ashara
On Sat, Nov 5, 2016 at 12:57 AM, Amit Ashara wrote:
> Hello All,
>
> The Manifest has been updated now and the new package is available for
> download.
>
> http://www.ti.com/lit/zip/spmc023
>
> Regards
> Amit Ashara
>
> package loss is < 1%.
anything above absolute zero is no good, indicating a problem in your
system.
I would accept that some frames might get corrupted in the wire... of
course...
> I thought someone had experienced same issues.
lwIP problems, when properly reported, are found and fixed.
Y
Hi,
the return err value is always OK! No error. I am actually receiving packets
and I can messure the losses because I label the packages with numbers and I
see what package arrive. When I send less data, package loss is < 1%. So I
think there is some buffer or memory problem. The loss is random
I already did.. just need to test it now 😊
From: Sergio R. Caprile
Sent: Friday, November 11, 2016 6:05 PM
To: lwip-users@nongnu.org
Subject: Re: [lwip-users] lwIP 2.0.0 released
> Great work. Need to find the time to move from 1.41 to 2.0 J
Same here.
Congrats to all the team, you guys rule!
> Great work. Need to find the time to move from 1.41 to 2.0 J
Same here.
Congrats to all the team, you guys rule!
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
* @return ERR_OK if data was sent, any other err_t on error
*/
err_t
netconn_sendto(struct netconn *conn, struct netbuf *buf, ip_addr_t
*addr, u16_t port)
Instead of tuning UDP, I think you should first try checking return
codes to see if datagrams are being sent or what.
Maybe (just maybe)