Tailscale is popular, is a recurring problem to debug for accessing the internal network on- and off-site, and there isn't a fix besides disabling (breaking other connections)-enabling it every time. 100.64.0.0/10 isn't supposed to be used for private networks. https://tailscale.com/kb/1015/100.x-addresses
Docker default IPv4 (172.17.0.0/16)
Relying on 172.xyz, and blocking out sections might be an idea, should be enough addresses (what I've seen most commonly in not-huge corporate networks). 10.x (what I've seen in huge corporate networks) still exists.
This is a relatively painful undertaking, should definitely be coordinated with Erki A and Kristjan (independently).
https://wiki.k-space.ee/en/hosting/network/vpn
- Tailscale is popular, is a recurring problem to debug for accessing the internal network on- and off-site, and there isn't a fix besides disabling (breaking other connections)-enabling it every time. 100.64.0.0/10 isn't supposed to be used for private networks. https://tailscale.com/kb/1015/100.x-addresses
- Docker default IPv4 (172.17.0.0/16)
Relying on 172.xyz, and blocking out sections might be an idea, should be enough addresses (what I've seen most commonly in not-huge corporate networks). 10.x (what I've seen in huge corporate networks) still exists.
This is a relatively painful undertaking, should definitely be coordinated with Erki A and Kristjan (independently).
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.
https://wiki.k-space.ee/en/hosting/network/vpn
Relying on 172.xyz, and blocking out sections might be an idea, should be enough addresses (what I've seen most commonly in not-huge corporate networks). 10.x (what I've seen in huge corporate networks) still exists.
This is a relatively painful undertaking, should definitely be coordinated with Erki A and Kristjan (independently).