the WF-server had the ability to stop/start a transport via the CLI (ISPN-11240).
The new server should have a similar capability.

Protocol management via CLI

$ cli.sh server connector ls
$ cli.sh server connector ipfilter set <name> --rules=REJECT/192.1.1.1/16
$ cli.sh server connector stop <name>
$ cli.sh server connector start <name>

Aside from start/stop, we should also leverage netty's ipfilter handler which allows filtering based on subnet so that traffic can be blocked selectively.

IP Filtering

<endpoints socket-binding="default" security-realm="default">
         <ip-filter>
            <reject from="172.16.0.0/16"/>
            <accept from="127.0.0.0/8"/>
         </ip-filter>
          <hotrod-connector/>
          <rest-connector/>
</endpoints>