Nebulo stops transiting DNS requests upon change of AFWall+ profile.

I've got 4 profiles set up in AFWall+... Default (which I normally use, it blocks all of Google's CIDR ranges), Google (which allows Google CIDR ranges), Testing (which allows everything) and Lockdown (self-explanatory).

Nebulo is enabled in all but the Lockdown profile, since that profile just DROPs all packets, IPv4 and IPv6. It's good for catching which apps are attempting to communicate, without allowing that communication.

When I switch from one profile to another, Nebulo stops working, even if Nebulo is whitelisted in the profile being switched from and in the profile being switched to.

I have to go into Nebulo, to the main screen, press the "Stop" button, wait a few seconds, then press the "Start" button, then it'll start working again.

This isn't exactly a change of connection state (the WiFi connection remains connected throughout), so I'm not sure how one could figure out how to programmatically bring Nebulo back to life.

I suspect Nebulo glitches upon any network congestion (my wife uses the internet in the evenings and consumes most of the bandwidth at times, and it's then that I also notice Nebulo exhibiting similar behavior to above).