Depending on the use-case at hand, any DQMH module can facilitate GenNet communication in one of two ways:
This is the default use-case
Modifying a DQMH module to be Generic-Networking-enabled makes the most sense when you want to use a module's API in one application and have its code executed in another application, i.e. use the same module (identical source code) in both applications and configure it as client (forwarding requests via network) on one side and as server (receiving requests via network) on the other side.
Overriding the default DQMH Message Queue class and making a number of modifications to the DQMH module:
Adding the GenNet helper modules (GenNet-Server and GenNet-Client) manually to a common DQMH module provides an alternative way of using the GenNet functions with any given DQMH module. Naturally, this comes with additional work and less automatism.
Technically, this is done by manually adding the code for starting and stopping the helper modules and for calling the network communication functions.