Stale socket message port?
In my channel, I have the ability to listen for UDP messages for a certain LAN message.
I create the UDP socket at startup, and it lives through the entire lifetime of the channel.
I can receive these UDP messages as long as the channel hasn't been inactive for a few hours. (I don't typically close my channel on my TVs).
After a few hours of the channel being open (not necessarily active, say overnight) I can no longer receive the UDP responses from my LAN. I can see the query message being sent, so I know the send part of it is still working, it just seems like the receive part becomes broken after a period of inactivity.
With that said, is there something about the message port for sockets that makes them become unresponsive after the socket has been inactive for a period of time?
I create the UDP socket at startup, and it lives through the entire lifetime of the channel.
I can receive these UDP messages as long as the channel hasn't been inactive for a few hours. (I don't typically close my channel on my TVs).
After a few hours of the channel being open (not necessarily active, say overnight) I can no longer receive the UDP responses from my LAN. I can see the query message being sent, so I know the send part of it is still working, it just seems like the receive part becomes broken after a period of inactivity.
With that said, is there something about the message port for sockets that makes them become unresponsive after the socket has been inactive for a period of time?
