[Info-vax] FreeAXP loses network connectivity when laptop is woken up from "sleep"

[David Froble]

presnypreklad at gmail.com wrote:
> I have FreeAXP installed on a laptop. For networking I'm using a virtual NIC (OpenVPN) which is bridged with the laptop's real wired network interface.
> 
> When I boot up the laptop, then start FreeAXP, then boot VMS and start TCP/IP services, I can ping my ADSL router and servers on the Internet (e.g. 8.8.8.8).
> 
> If, however, I put the laptop to "sleep" (without shutting down VMS), after waking it up again VMS is still running (I can get the console back by telnetting to localhost:9000 using Putty) but it no longer has network connectivity. Sleep/wake cycling has no effect on the laptop's networking - just on VMS networking.
> 
> So far, the only way I found to get the network back (in VMS) by shutting down VMS and restarting FreeAXP.
> 
> Back in 2010, Hein reported the same problem (loss of network upon sleep/wake) but he could get it back by running "NET STOP MSICPAP" followed by "NET START MSIPCAP" in a DOS window. This doesn't work in my case. It says the service cannot be stopped. (Yes, I'm running the DOS window with Administrator privileges.) I'm assuming that's because FreeAXP is still running. 
> 
> Once I completely stop FreeAXP and start it back up again, networking is back. But the idea is to get the networking back without having to restart VMS.
> 
> Any ideas greatly appreciated.
> 
> Nathan

I've never used any of the above.

If VMS has never been shut down, then I don't believe that the problem can be in VMS.

Likewise, the FreeAXP is just another program, and it I'd think has never stopped, since 
VMS didn't.

If VMS, and FreeAXP disconnect from the network adapter, for whatever reason, there is a 
good chance that they should be able to re-connect to the adapter.  Note that there could 
be reasons for my logic to be wrong.

Now, if the virtual NIC is dropping connections, then the software (VMS and FreeAXP) that 
have "lost" the device may not know how to recover the device.  Remember, if this was an 
Alpha, the device would be there, or it would not, and if not, the OS has no way of adding 
a device to the hardware.

Can I assume that you have tried the SYSMAN IO CONFIGURE (or something like that, I don't 
remember) to configure the device?  Note that this would be VMS trying to add an existing 
piece of hardware into the configuration.  This would NOT do anything for FreeAXP as far 
as re-finding a device.

If I had to take a "guess", it would be that FreeAXP isn't very robust at re-finding a 
device that has shut itself down.