You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Typically meadtap would be run in an externally-facing network context, and leverage some kind of a tap device that resides in an inward-facing network namespace to serve as the gateway. It would be nice if it were possible to open ports in the externally-facing network context, and proxy them to locations in the inward-facing network context. Building an api that would cause meadtap to listen on external ports and forward them. Main implements a PoC of this in serve_local here, but that is static and nonsensical for anything outside of the test environment:
Typically meadtap would be run in an externally-facing network context, and leverage some kind of a tap device that resides in an inward-facing network namespace to serve as the gateway. It would be nice if it were possible to open ports in the externally-facing network context, and proxy them to locations in the inward-facing network context. Building an api that would cause meadtap to listen on external ports and forward them. Main implements a PoC of this in serve_local here, but that is static and nonsensical for anything outside of the test environment:
meadinthemiddle/meadtap/main.go
Line 218 in c4a6b83
The text was updated successfully, but these errors were encountered: