<!--- Provide a general summary of the issue in the Title above --> Enable inlets-pro and TCP with inletsctl kfwd ## Expected Behaviour <!--- If you're describing a bug, tell us what should happen --> <!--- If you're suggesting a change/improvement, tell us how it should work --> inlets-pro users should be able to do raw TCP forwarding with `inletsctl kfwd` ## Current Behaviour <!--- If describing a bug, tell us what happens instead of the expected behavior --> <!--- If suggesting a change/improvement, explain the difference from current behavior --> OSS inlets users can forward HTTP/s ports ## Possible Solution <!--- Not obligatory, but suggest a fix/reason for the bug, --> <!--- or ideas how to implement the addition or change --> * Forward an API like Redis, Mongo or Postgresql * Using inlets-pro YAML files instead of inlets OSS - see docs for examples - https://github.com/inlets/inlets-pro-pkg/tree/master/docs * Listen locally using `inlets-pro server` instead of `inlets server`
Enable inlets-pro and TCP with inletsctl kfwd
Expected Behaviour
inlets-pro users should be able to do raw TCP forwarding with
inletsctl kfwdCurrent Behaviour
OSS inlets users can forward HTTP/s ports
Possible Solution
inlets-pro serverinstead ofinlets server