I found a bug with the VPN server of the IB 2. Don’t know where to report this, but here is how to reproduce anyway: Initial setup: LAN subnet 192.168.1.0/24 with a locally hosted DNS server (the locally hosted DNS is configured to be the DNS used by the IB). Configuration change: LAN subnet changed to 10.10.10.0/24, and DNS settings updated to reflect the new address. Bug observed: After this change, the VPN server continued to provide the old DNS address (192.168.1.x) to VPN clients instead of the new address (10.10.10.x). Workaround: Restarting the VPN server resolved the issue, after which VPN clients received the correct DNS server address. Firmware version 14.10.30 Bootloader version 3.5.20Nr1582 DECT version 4.12build24 Web portal version 02094

Bug found with VPN server

Viempautteiff16

I found a bug with the VPN server of the IB 2. Don’t know where to report this, but here is how to reproduce anyway:

Initial setup:

LAN subnet 192.168.1.0/24 with a locally hosted DNS server (the locally hosted DNS is configured to be the DNS used by the IB).
Configuration change: LAN subnet changed to 10.10.10.0/24, and DNS settings updated to reflect the new address.
Bug observed: After this change, the VPN server continued to provide the old DNS address (192.168.1.x) to VPN clients instead of the new address (10.10.10.x).
Workaround: Restarting the VPN server resolved the issue, after which VPN clients received the correct DNS server address.

Firmware version 14.10.30
Bootloader version 3.5.20Nr1582
DECT version 4.12build24
Web portal version 02094

bitracer

You just reported it.

MichelB

@Viempautteiff16: Thanks for raising this. It’s somewhat expected that there is this kind of impact when changing the subnet. Since this is not a frequent use case it might not be justified to have an automatic solution. I will check at least to improve the information message that VPN needs to be restarted after changing the subnet.

Cheers

MichelB