> This thing you describe is still not possible to understand. DHCP or not DHCP, when the RRC is behind > a NAT router it should not cease functioning after in your case a disrupt in the external network
> (ADSL).
I would tend to agree on the theory but it will be dependant upon what the IP stack puts into cache and how it manages its (internal network) DHCP handshake. It seems as though every other device on my network, PCs(Win + LINUX), IPhones, Internet Radio, 2 x STB etc, fixed or DHCP has no problems with the router (Cisco- Linksys) of the loss of ADSL + change of supplier IP. Even changing the router from Linksys to 2Wire does not resolve it.
Using DHCP for the RRC controller is not really acceptable as if there is any issue, and there are several every day) I first have to hunt in the router's DHCP table and guess what IP it has.
The problem is probably triggered more often as in the UK the ISPs circulate their IP addresses, from a large pool of quite different /24s on the DHCP servers. That means that if your router drops its PPP session for whatever reason it will almost always gain a new external address often from a very different netblock. This means that the router NAT table has to be refreshed with each new request from a downstream device. It seems that the RRC IP stack does not behave in the same way as all of the other devices on my network. It does, like all other devices retain the same (internal) IP address after such a change. Perhaps it is a quirk of the embedded stack and the caching of the DHCP credentials, in particular when an 'external' DNS server has been selected. However a 10 (not 5!) minute power-down will reset things.
If I have time I will capture 'normal' and 'lock-up' traffic with Wireshark.
73
John G4SWX