>I was very happy to see that NetBSD supports powermanagment. But I
>noticed the following problem (maybe I just did something wrong or 
>misunderstood something):
>
>If I put the system into suspend (deep sleep) mode with `apm -z` and
>wake it up later (power on), I get the system back just like I left it -
>except that the network is no longer responding. I can't ping any host
>and no host can ping me - I have to reboot to get networking back.
>
>Is this a bug or is it just not possible to reanimate networking? Or did
>I miss something in configuration?

>Thanx for any help in advance!

Diagnosing this problem really depends on the driver and hardware
you're using, which isn't given in your message above.
If you  specify

	* The version of NetBSD you're using (and date, for -current)

	* exactly what network interface you're using
	  (name, model, bus, firmware/asic level, etc.),

	* the kind of machine you're using (e.g., laptop?)

	* ideally, the network-interface attach messages the
	  kernel gives at boot time, and any mesages for the
	  bus your network is attatched to;

then you're likely to get better-directed advice. As it is:

It sounds like the suspend is putting your network interface
to sleep (low-power mode), but the resume is  not waking it up.

If you have console access, does 
	 ifconfig <ifname> down; ifconfig <ifname> up
help at all after an APM resume?

hope that helps some,
--Jonathan