Is it at all related to the fact that they changed from nxdrv.sys to using wireguard-nt and wintun? Also, has anyone got a link to the source code they used for wireguard-nt and wintun? They didn't make it available on their site, so I don't know which version they are using, what the changes were, etc.
this basically makes it useless for us and the few test installs we did reverted to 10.2.315 just fine and we were able to connect. Under DNS servers tab all that shows up are "fec0:0:0:ffff::1" and "fec0:0:0:ffff::2" which is some sort of internal network only default addresses Windows uses for IPv6 (We do not have IPv6 on our network).
When we connect with 319 (We tested on two of the sites, with W11 and W10 21H2), the client connects and gets an IP from our SSL-VPN pool, and we are able to ping all IP's on the subnet, however the clients do NOT get our specific DNS servers. This does something odd, where as the old releases had a virtual adapter that was ALWAYS present on the system, even when not connected, this creates a Virtual SonicWall NIC when the connection is made, so no adapters when you aren't connected.
The changes to me look more like a major version release that should have been like a 10.4.x release or something, like a new branch. If you look at the install folders, the number of files and such it installs are totally different and adds some experimental features if you look in settings). (The fact there's also separate x86 and 圆4 installers now too.). However, despite the release notes for 319 being fairly small like a maintenance release, it appears MUCH has changed on the backend of the program. They'd connect, get an IP from our SSL-VPN pool, get the specified internal DNS servers and routes and be good to go. We have been using v10.2.315 on many of our clients just fine. We're using this with two NSA 4600's with v6.5.4.5 and a 4650 with 6.5.4.7 across three sites. NetExtender v10.2.319 for Windows came out within the last few weeks.
0 kommentar(er)
