Re: [lwip-users] Behavior of netif_set_link_down

[Nikolas Karakotas]

I believe it has to do with your ethernet driver and how it is implemented.
Even if you send data to your hardware you should control this with a 
incrementer for example just like a round robin.

Regards,
Nick

-----Original Message----- 
From: Richner Simon
Sent: Wednesday, May 01, 2013 6:18 PM
To: Mailing list for lwIP users
Subject: [lwip-users] Behavior of netif_set_link_down

Hi,

In my driver I call <netif_set_link_up> and <netif_set_link_down> when I
detect that a cable was connected to / removed from my device. However,
I noticed, that only setting the link up triggers <dhcp_network_changed>
and not setting link down. So when a cable gets removed, the
NETIF_FLAG_UP stays true.

In my application, I send some data periodically to a predefined IP.
When now the cable gets disconnected, the application doesn't get
informed about this, neighter gets the netif set down. So my application
continues to spam my hardware and sooner or later I get a buffer
overflow on my hardware!

=> What is calling <netif_set_link_down> good for, when it doesn't bring
the interface down?

=> What would be the best way to tell my application to stop streaming?



Best Regards
Simon

_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users