Originally posted by fr34kyn01535 January 7, 2025
Similar to how authentik allows trusted networks, it would be cool if we could whitelist networks that are trusted and bypass auth.
While most users don't have a fixed IP to whitelist I came up with a second idea here:
It would actually be quite cool if we can automatically select newt tunnel nodes / sites to whitelist, and their WAN address is added to that whitelist.
Originally created by @miloschwartz on GitHub (Feb 1, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/143
Originally assigned to: @oschwartz10612, @miloschwartz on GitHub.
### Discussed in https://github.com/orgs/fosrl/discussions/11
<div type='discussions-op-text'>
<sup>Originally posted by **fr34kyn01535** January 7, 2025</sup>
Similar to how authentik allows trusted networks, it would be cool if we could whitelist networks that are trusted and bypass auth.
While most users don't have a fixed IP to whitelist I came up with a second idea here:
It would actually be quite cool if we can automatically select newt tunnel nodes / sites to whitelist, and their WAN address is added to that whitelist. </div>
to add to this - within other proxy packages i heavily make use of only allowing internal networks to access certain resources. it's a great additional step along with authentication to minimize the scope of who can access the proxied resource. being able to have something like "allow connections from specified private ip ranges, and deny the rest" would be very useful.
<!-- gh-comment-id:2641270093 -->
@scroguard commented on GitHub (Feb 6, 2025):
to add to this - within other proxy packages i heavily make use of only allowing internal networks to access certain resources. it's a great additional step along with authentication to minimize the scope of who can access the proxied resource. being able to have something like "allow connections from specified private ip ranges, and deny the rest" would be very useful.
The same as an access list as in npm for WireGuard ip connections
<!-- gh-comment-id:2646091510 -->
@synologyy commented on GitHub (Feb 9, 2025):
The same as an access list as in npm for WireGuard ip connections
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @miloschwartz on GitHub (Feb 1, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/143
Originally assigned to: @oschwartz10612, @miloschwartz on GitHub.
Discussed in https://github.com/orgs/fosrl/discussions/11
Originally posted by fr34kyn01535 January 7, 2025
Similar to how authentik allows trusted networks, it would be cool if we could whitelist networks that are trusted and bypass auth.
While most users don't have a fixed IP to whitelist I came up with a second idea here:
It would actually be quite cool if we can automatically select newt tunnel nodes / sites to whitelist, and their WAN address is added to that whitelist.
@scroguard commented on GitHub (Feb 6, 2025):
to add to this - within other proxy packages i heavily make use of only allowing internal networks to access certain resources. it's a great additional step along with authentication to minimize the scope of who can access the proxied resource. being able to have something like "allow connections from specified private ip ranges, and deny the rest" would be very useful.
@synologyy commented on GitHub (Feb 9, 2025):
The same as an access list as in npm for WireGuard ip connections
@miloschwartz commented on GitHub (Feb 13, 2025):
Added in 1.0.0-beta.13