Sali

I also looked at the messages, there is nothing special. The interesting thing is, Let’s Encrypt works via IB3 / Syno, everything is entered correctly, but every 1 to 2 days it doesn’t connect. Everything is entered correctly, but since the last FW it just happens and I have no idea why. Either it’s because of me, because of Synology’s FW or the IB3 or the firmware. That was the only question 😉

I think the error is probably the IP3’s DDNS service, which stutters every now and then. I no longer used it via xxxxxxx.internet-box.ch, but rather via another service (xxxxxxx.ddns.net/noip.com), and it works perfectly again….

Yes, I think it has nothing to do with let’s encrypt.

Then, in the event of a problem, you would have to check whether the IP is still resolved correctly.

If this is the case, you would have to check the service on the server or the router that has a bug.

@Dani CH It’s always the old story that SC’s DDNS service stutters or doesn’t work at all. That’s why I avoid it and use DynDns.Org, it costs a bit, but it works very reliably.

@user109

Sali and thanks for the info. I tried something again in the afternoon, and maybe the reason was found with the bonding of the IB3 & 5G Booster…

@user109 I also often use ddns from Swisscom, but I don’t really know how it stutters once it’s set up. What stuttered for me from time to time was the repeated setup after changing the box or after a firmware update. But that’s another story.

@Dani CH ok, of course bonding can also have an influence. I’m glad I don’t have to rely on it. The increase in speed may be great once it’s running, but it also makes the whole thing much more complex. And I now think that something has been loaded onto something that is probably raising more questions and problems than Swisscom would actually like. I very much hope that this bon(un)ding remains an emergency solution and that the accelerated FTTH expansion will resume soon.

@kaetho OT: Sunrise has sided with Swisscom in the fiber optic dispute.

[https://www.nau.ch/news/wirtschaft/sunrise-upc-fur-glasfibro-ausbauplane-der-swisscom-kritik-an-weko-66064265](https://www.nau.ch/news/ economy/sunrise-upc-for-fiber-optic-expansion-plane-of-swisscom-criticism-of-weko-66064265)

@user109 exciting. The process is getting rolling. Some people are slowly beginning to notice that the statement “The losers are everyone who doesn’t yet have an FTTH Anschluss” * but there is more truth in it than first assumed. I can well imagine that the move to attack Swisscom where it hurts (with customers) will ultimately do more harm than good. Because this blockage not only affects Swisscom customers, but everyone. Time will tell…

*By the way, the saying wasn’t mine… 😉

oh, cool, 00/13/05! Then things will continue soon 😉

Hello everyone

I wanted to revisit this topic and ask if anyone else has the same problem with the IB4? My firmware is currently version 13.20.26/13.20.18/01923 (I have never updated anything manually).

My VPN connection (L2TP, from the Windows laptop via a mobile hotspot) works and I see my laptop in the device list on the IB4 as a VPN device. As discussed above, the laptop is then assigned an internal 192.xxxx address. However, a 194.xxxx IP address is also displayed. Assume that this is not a static assignment.

If I then want to access Synology via the browser, the connection is blocked due to my firewall settings there (no entry of IP addresses outside my network) and the website is not loaded. When I relax the firewall rules, I see that the laptop has logged into Synology with the IP 194.xxxx.

Does anyone of you have a solution so that the assigned internal 192.xxxx address is used?

Thank you!

Actually, as you can see in post #48, this error was already corrected almost 2 years ago.

Of course, it could be that this error was accidentally reactivated in a newer firmware.

It’s best to report your problem via the hotline or chat so that a ticket is recorded.

The immediate solution is also clear:

- just do without the IP restriction on the Syno, because if, as is sensible anyway, you have not activated any direct port forwardings on the Syno, omitting the IP restriction is actually no real loss of security, since you will then only via the VPN connection that Syno can access.

or:

- do without the IB VPN server and replace it with another VPN server within your network, in your situation probably directly with the Syno VPN server.