New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#2731 - Wireguard interface mask settings #8516
Comments
yalexey: You can see dialogue here |
jow-: So what is wrong with |
yalexey: This is standard configuration of WG interface: WG0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:192.168.160.2 P-t-P:192.168.160.2 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MTU:1420 Metric:1 RX packets:620 errors:0 dropped:0 overruns:0 frame:0 TX packets:683 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:350740 (342.5 KiB) TX bytes:77324 (75.5 KiB) It's working, but not for all cases. Maybe it is problem of bird4, but until I don't change interface mask to 255.255.255.0 manually, a new dynamic routes through 192.168.160.1 on other side of tunnel can't be created over this interface. Any static routes don't change the problem. Not to mention that static routes for VPN connections are not a good idea. |
yalexey: OK. I will describe it again in sequence.
|
yalexey:
Wireguard interface by default start with equal IP addresses on both ends of PvP connection and mask 255.255.255.255
That's prevent from routing and some package working. Even static routes don't resolve this issue totally.
I have to manually set network mask option in /etc/config/network to make bird4 work with this.
Mainteiners of luci said, protocols need to accept configuration in address/cidr or address/mask format from web configuration utility. So netmask field in luci is unavailable.
But wireguard oblivious don't.
The text was updated successfully, but these errors were encountered: