Thanks Trampas! You went down the same road I started on with the ability to
detect the disconnection. I was told we cannot change the hardware, so I am
trying to find the correct location in Lwip to “clean up” when there is no
route. Just haven’t found it yet.
The correct solution in using
Dan,
I had been using a RMII phy and noticed similar issues. Specifically I
could not detect cable connected or disconnected using the RMII, the link
activity bit does not work for cable connected/disconnected. I was shocked
to find that RMII did not provide this functionality. Sure the LED
I have am working on an issue with our device. First here are the particulars
Micro: STM32F427
LwIP: 2.0.3
WolfSSL: 3.15.3
Microchip managed switch KSZ8863RLLI.
If one removes the Ethernet cable from our device (typically during heavy
traffic) the network is not usable for many minutes upon
Has anyone used LWIP to create a mass storage device that can mapped as a
drive on a PC? That is a samba or other type of server?
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
On Tue, Mar 31, 2020 at 10:11 PM Simon Goldschmidt wrote:
> You're mixing link state with admin state here. That might work, but
> might not work in some situations.
It's not so clear to me.
Which pattern should I adopt to keep the link status under control?
What do you mean by 'admin state'?
How
On 31.03.2020 21:34, Massimiliano Cialdi wrote:
I have a process that polls the PHY to find out if the link is up or
down. It calls netif_set_link_up()/netif_set_link_down(). I also have
the link callback calling netif_set_up()/netif_set_down().
You're mixing link state with admin state
I have a process that polls the PHY to find out if the link is up or
down. It calls netif_set_link_up()/netif_set_link_down(). I also have
the link callback calling netif_set_up()/netif_set_down().
I wonder what happens if the functions:
conn = netconn_new(NETCONN_UDP);
netconn_bind(conn,
