Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[GreenBay42]

On that page under Advanced Settings, what do you have enabled?  I have all 4 enabled.

I will mirror your settings to see if I can connect

[me_iauras]

All 4 options under the Advanced firewall tab are enabled (disabling them however does not make any difference as they are mostly for specific traffic from inside the network like a VPN to a server from outside or VOIP)

[GreenBay42]

Ok we verified with SPI enabled does not allow you to connect as you stated.

There was a ticket from another country in our DTrack system with this exact issue. They gave a beta firmware 1.10B02BETA that fixed the issue. We are testing that firmware now to see if it does work. Not sure why 1.11 didnt have this fix (if it works). If the beta works, I will post here for you to try, then we will reopen the ticket for firmware 1.11.

[me_iauras]

great , 10x for you swift work/help .

[GreenBay42]

Well i did drop the ball since you reported this a month ago.....

The beta failed. I will reopen the ticket and hope to hear from them early next week. Thanks for being patient.

[me_iauras]

OK thank you  for it .
I actually think that the SPI firewall issues are a little more generall in blocking public/private key transfers .
I'm saying this because in absence of a working VPN I tried to post my NAS portal on the web (to be able to access my data somehow ) via the Port Forward/Virtual Server options . I was succesfull in doing it for the unsecured http portal but the https just doesn't work (I've tried both a Port Fw seting on port 443 towards my NAS and also a Virtual Server with another port , ex. 8443 , pointing to port 443 on my NAS's IP  ); the TLS/SSL handshake just doesn't work . If I disable the SPI firewall then it functions as it should .
I'm hoping that the VPN/Firewall fix will fix this issue too as this one might have a bigger impact on more users than a non functioning VPN which less users would use in my opinion.

[GreenBay42]

Sorry for the delay. I received BETA firmware to fix the vpn issue. Please let me know if this works for you.

ftp://FTP2.DLINK.COM/PRODUCTS/DIR-882/REVA/DIR-882_A1_v1.11B01_for_open_SPI_vpn_noworking_issue_2018_10_12%281012162256%29.bin.zip

[me_iauras]

The issue indeed seems to be resolved ; here's hoping that the SPI firewall is active and protecting us and not just "on" .
I'll see in the coming days the stability of the build to conclude if it can be used as a daily driver or not .
Anyway thanks for the work you're doing bridging the gap between the clients and the engineers .

Now I know that I might be reaching for the sky but could we know if the present performance on  the VPN connection is all/roughly all the router can give (in my testing I'm geting ~ 9-10mb/s down and 13-14 mb/s up ) or can there be some further refining of the code to improve the speed .
Anyhoo for now I'm glad it works as is .

[GreenBay42]

It is normal for speeds to slow down due to the overhead of the router encrypting/decryption the VPN traffic.  I sent dtrack your speeds you posted earlier in this thread. Will hear back next week.

[wonders81]

Hi!
I have a DIR-882 (HW:A1 FW:1.11) and I have the same issue: if I turn on the SPI firewall I can't connect to the VPN and the ports defined in virtual server section aren't working. Is it safe to install this linked beta version?

[me_iauras]

@wonders81
Since I've installed the beta I've had no issues with any bug/instability so from my experience I say give it a try .

[FurryNutz]

Please give it a try and let us know how it works for you. If somethings happens, you can revert back to prior FW.

Hi!
I have a DIR-882 (HW:A1 FW:1.11) and I have the same issue: if I turn on the SPI firewall I can't connect to the VPN and the ports defined in virtual server section aren't working. Is it safe to install this linked beta version?

[wonders81]

OK, I uploaded the beta version, the router rebooted, but the version number is still FW: 1.11 on the web interface, and the problem still persist. I cannot connect through VPN if the SPI IPv4 is enabled. Is there a way to check the fw version number somewhere else?

[FurryNutz]

Did you factory reset the router after uploading the FW file then set up from scratch?
This beta version is v1.11 B01 I presume the date would be how you determine from the last version you had loaded.

OK, I uploaded the beta version, the router rebooted, but the version number is still FW: 1.11 on the web interface, and the problem still persist. I cannot connect through VPN if the SPI IPv4 is enabled. Is there a way to check the fw version number somewhere else?

[me_iauras]

OK, I uploaded the beta version, the router rebooted, but the version number is still FW: 1.11 on the web interface, and the problem still persist. I cannot connect through VPN if the SPI IPv4 is enabled. Is there a way to check the fw version number somewhere else?

For me it works ; as you can see from the screenshots >> https://imgur.com/a/OqHaFv6
As you can see I was connected to the VPN ( Samsung S9 , wifi and 4G ) as I was navigating the router's interface ; indeed the sw version is not changed (probably different build number though).
Hope it helps you