search

newsnowlabs / docker-ingress-routing-daemon

Docker swarm daemon that modifies ingress mesh routing to expose true client IPs to service containers
MIT License
190 stars 37 forks source link

Feature Request: Whitelist Services/Ports #33

Closed ztimson closed 1 year ago

ztimson commented 1 year ago

Hey I have been using dird for awhile and it works great for websites; however it can cause issues for game servers & other complex services.

I can currently blacklist these services/ports but it's quite a hassel when you have multiple servers and services that are being updated.

I really only need IP's corrected for my reverse proxy that all my web services run through. Can whitelisting be added as arguments? Using a whitelist would save me form having to check & reconfigure dird when I run into a routing issue with a new service.

Thanks!

struanb commented 1 year ago

Hi @ztimson Thanks for using DIRD. For some reason we didn't receive notification, so apologies for the delayed response.

Have you tried using any of these options?

--services <services>  - service names to disable masquerading for
             --tcp-ports <ports>  - TCP ports to disable masquerading for
             --udp-ports <ports>  - UDP ports to disable masquerading for

"Disable masquerading for" means "enable routing for", so these should be the whitelist options that you want.

ztimson commented 1 year ago

@struanb No problem at all, using the flags provided did indeed work, thank you! The language defintely confused me.

struanb commented 1 year ago

I've updated the language in the README, which I hope you agree is clearer about the whitelisting options, and will now close this issue.