My network setup is:
Router (DHCP, for the 6500 static IP) - Ethernet switch - notebook and 6500.
I can easily setup a connection between 6500 and notebook only, but if I start my router as a DHCP server later, the 6500 crashes and has to be restarted.
Because of this behavior, which can easily be avoided, I think it is an IP problem and the 6500 loses connection.
I have had fewer of these crashes since I told my router to reserve a static IP to the 6500.
I have a very old (10 years...) Siemens router which works quite well with a rewritten Linux firmware.
Interestingly I also had to reserve static IP's for my Android smartphones and tablets, connected by WLAN of course. My notebooks and my main server all use DHCP and have no connecting problems at all, whether by cable or by WLAN. Weird...
73, Alex DH2ID
Don - I had some similar disconnect issues. Turned out my ethernet switch (16 port) was the issue. I ended up moving the radio and main computer connection to the primary routers 4 ports. The router then is also connected to the ethernet switch for all the other stuff. That way if the 16 port switch "blinked", it didn't affect the radio/computer. It would obviously loose connection to printers and other computers, which I don't much care about.
Network drives, printers and other computers re-connect if the switch blinks, but the radio/computer does not. So, I believe the switch was ocassionally "blinking", and I just isolated it out. I don't know if in a future release SDR can be written to try and re-connect before it gives up the "lost connection" message.
With the "reliable" switch, I haven't had a random disconnect in weeks. Before it was pretty much daily!
Brent - W8XG (formerly NB4AP)