Leaderboard

(Edited on April 23) Just as a note, since the first days of April the situation with VPNs in Russia is going into the real Cheburnet phase: Spyware VPN detectors will be inserted into all the major commercial mobile apps (Max, VK, Yandex, banks, phone carriers, etc.), every detected endpoint IP will most likely go into the country-wide blacklist The increase of the cross-border backbone bandwidth has already been vetoed because it has grown over the top in the last year due to the VPNs Because of that there are rumors that more than 15 GB/month of cross-border traffic will have added cost for every end user (proven but action currently delayed due to the technical difficulties in detecting the cross-border traffic at the ISP level) VPN software will be detected on every in-country VPS hosting provider to prevent using them as bridges (it is already a common practice to circumvent white list blocks) Recently there were wired Internet shutdowns looking very much like tests of white list blocks (before that only mobile Internet had white lists) By the way, it's very hard to find any AirVPN server which is not yet blocked. But I can still find some (mostly in Netherlands) by automated scanning. AmneziaWG is necessary, of course

Wonder why this is still not being considered

The gender is a more or less unnecessary piece of information around here. Even if you wanted to provide your pronouns, no one would be able to see this preference when replying in a thread. It's not in the quick info dialog when hovering over the poster's name, and by default profiles are inaccessable to all, so no one would be able to see that info in the first place. You could use the Location field to enter those, it's visible directly under your name, but that'd be displayed with a Location label, see the example on the left under my name (and compare it with how I formatted it in the profile). You must also be advised that this version on IP.Board comes from a different internet era altogether (~10 years ago, I believe), one that didn't have the custom of providing pronouns, or having a variety of genders to identify as. So, you may treat Not telling simply as virtually equivalent to non-binary.

Hi everyone, I'm using AirVPN through WireGuard on my OpenWrt router (latest stable version), but I'm having trouble getting IPv6 to work properly. IPv4 traffic goes through the VPN just fine, but IPv6 traffic does not. Here are my relevant settings and config: // network: config interface 'loopback' option device 'lo' option proto 'static' option ipaddr '127.0.0.1' option netmask '255.0.0.0' config globals 'globals' option ula_prefix 'fdef:xxxx:xxxx::/48' option packet_steering '1' config device option name 'br-lan' option type 'bridge' list ports 'lan1' list ports 'lan2' list ports 'lan3' list ports 'lan4' config interface 'lan' option device 'br-lan' option proto 'static' option ipaddr '192.168.1.1' option netmask '255.255.255.0' option ip6assign '60' config interface 'wan' option device 'wan.10' option proto 'dhcp' option peerdns '0' list dns '1.1.1.2' config interface 'wan6' option device 'wan.10' option proto 'dhcpv6' option reqaddress 'try' option reqprefix 'auto' option peerdns '0' list dns '2606:4700:4700::1112' config device option type '8021q' option ifname 'wan' option vid '10' option name 'wan.10' config interface 'vpn' option proto 'wireguard' option private_key '***REDACTED***' list addresses '10.x.x.x/32' list addresses 'fdxx:xxxx:xxxx:xxxx::xxxx/128' config wireguard_vpn 'wgserver' option public_key '***REDACTED***' option preshared_key '***REDACTED***' option endpoint_host 'xxx.xxx.xxx.xxx' option endpoint_port '1637' option persistent_keepalive '15' option route_allowed_ips '1' list allowed_ips '0.0.0.0/0' list allowed_ips '::/0' // firewall config defaults option syn_flood '1' option input 'REJECT' option output 'ACCEPT' option forward 'REJECT' config zone 'lan' option name 'lan' list network 'lan' option input 'ACCEPT' option output 'ACCEPT' option forward 'ACCEPT' config zone 'wan' option name 'wan' list network 'wan' list network 'wan6' list network 'vpn' option input 'REJECT' option output 'ACCEPT' option forward 'REJECT' option masq '1' option mtu_fix '1' config forwarding option src 'lan' option dest 'wan' # IPv6-related firewall rules omitted for brevity but mostly default ICMPv6 & DHCPv6 Despite ::/0 being in the allowed_ips for the WireGuard interface, my IPv6 traffic still seems to go out through the regular WAN or not at all. Does anyone know what I'm missing or how to properly force all IPv6 traffic through the VPN tunnel like IPv4? Thanks in advance!