Hi @hook.ua. It seems this a bug. radius: gw-ip-address not specified, cann't assign IP address...
This means gw-ip-address not defined in accel-ppp [radius] section. Need to create a bug report on the https://phabricator.vyos.net/.
ps:// can you try manually add gw-ip-address to file daemon config for checking?
sudo nano /var/run/accel-pppd/l2tp.conf
add to section [radius]
Run accel-cmd restart -p 2004 for restarting daemon.
Framed-IP-Address 255.255.255.255 ins not valid. As I remember in RFC used 255.255.255.254 for delegation ip address from server. Can you try to set Assing a static ipv4 address?
Note: try to update you router to the latest version.
I have to check how do that
I switched to chap-secret (local authentication mode) from radius just to check that “plan B” for remote access still works. Unfortunately struck in the same issue. Windows reboot doesn’t help
Each protocol carried over PPP has an associated Network Control Protocol (NCP) that negotiates options for the protocol and brings up the link for that protocol (Table 3-1 on page 3-4)
Upon reception of a Protocol-Reject, the implementation MUST stop
sending packets of the indicated protocol at the earliest
Therefore, stream of accel-l2tp: l2tp0 send [LCP ProtoRej id=160 <00fd>] means that Windows client somehow requests compression but VYOS does not support it.
LCP compression in the L2TP section definitely disabled (check box is off)
You can simple insert this option, by editing template sudo nano /usr/share/vyos/templates/accel-ppp/l2tp.config.tmpl and then reconfigure l2tp service.
But better create bug report on the phabricator. This issue appears with MS-CHAP-v1/v2 and enabled CCP and for others protocols.