[GH-ISSUE #681] Block direct port access using rules #1564

Closed
opened 2026-04-16 08:14:12 -05:00 by GiteaMirror · 2 comments
Owner

Originally created by @imakecodes on GitHub (May 5, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/681

Is there any possibility to block access to the ports based on the IP address attempting the connection? Or to follow a similar logic to what is already in place for domains and subdomains?

Originally created by @imakecodes on GitHub (May 5, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/681 Is there any possibility to block access to the ports based on the IP address attempting the connection? Or to follow a similar logic to what is already in place for domains and subdomains?
Author
Owner

@oschwartz10612 commented on GitHub (May 5, 2025):

Are you talking about blocking to raw tcp or udp resources? Unfortunately that is not built in right now into the application and might be tough because we dont have the use of badger yet like we do for http.

<!-- gh-comment-id:2852433786 --> @oschwartz10612 commented on GitHub (May 5, 2025): Are you talking about blocking to raw tcp or udp resources? Unfortunately that is not built in right now into the application and might be tough because we dont have the use of badger yet like we do for http.
Author
Owner

@oschwartz10612 commented on GitHub (May 5, 2025):

I think we can keep this as a feature request. I will move to discussions so people can upvote.

<!-- gh-comment-id:2852434909 --> @oschwartz10612 commented on GitHub (May 5, 2025): I think we can keep this as a feature request. I will move to discussions so people can upvote.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#1564