Comment 8 for bug 69892

A "default route" being gone is different than not associating after resume. Perhaps you need to be clearer about your issue.

As a result of a suspend, the network interface is brought down and, when appropriate, the DHCP lease is released. This is normal and correct behavior.

After resuming from a suspend, NM will search the local APs and attempt to (re-)associate and retrieve a DHCP lease from the highest priority friendly.

No matter how you cut it, there is a timeframe where no '"default route" will exist. Does this clarify things for you? Can you clarify for us?