Hello @Anonymous and @MarcoG1983

I also installed the beta this morning. But I didn’t have any problems with IP assignments because I run the DHCP service on my Synology. If you have a Syno NAS, I can only advise you to run the DHCP service through it. The management and reliability are worlds better.

For some time now I have been running DHCP, DNS and VPN via the Syno. WLAN transmits via the Apple Airports and I have “outsourced” the switch functionality of the IB to a Cisco SG300.

The Internet box was downgraded to a pure modem.

Greetings & happy Easter

Rene

Edit: Swisscom’s dynamic DNS service now appears to be able to be activated in the network settings and in the application section. Actually nice, since I’ve wanted to turn off the application part for some time. Unfortunately, the DNS service is then also deactivated in the network settings. In my opinion it’s pointless. Either via the application part or the network settings…

---

@rene.borer wrote:

Hello @Anonymous and @MarcoG1983

I also installed the beta this morning. But I didn’t have any problems with IP assignments because I run the DHCP service on my Synology. If you have a Syno NAS, I can only advise you to run the DHCP service through it. The management and reliability are worlds better.

I’ve been running DHCP, DNS and VPN via the Syno for some time now. WLAN transmits via the Apple Airports and I have “outsourced” the switch functionality of the IB to a Cisco SG300.

The Internet box has been downgraded to a pure modem.

Greetings and happy Easter

Rene

---

A pure modem would be bridge mode and that is not available with the Internet Box, so it still has router functions.

:smileywink:

Thanks for your answers.

Yes, basically I mean it that way.

It’s clear to me about the “beta” because I work in software development myself. That’s okay too. BETA is BETA.

All I really cared about was, regardless of the BETA, how good the restoration of the existing configuration is after a factory reset with local backup (I’ve tested the Kundencenter backup, but it’s not satisfactory).

Reason of the question:
Since I always connect, record, etc. x different devices to my router for software development, I reset the box every now and then to keep it “clean” and reconfigure everything (I know that 99% will say this is not necessary).

If this works properly for my standard configuration (fixed installed devices) with the local backup, it would of course be an enormous time saving than having to reconfigure everything after a reset.

And sorry that I’m in the wrong topic, I just picked up on the backup here.

Greeting

Marco

---

@MarcoG1983 wrote:

Thanks for your answers.

Yes, basically I mean it that way.

It’s clear to me about the “beta” because I work in software development myself. That’s okay too. BETA is BETA.

I was really just concerned about, regardless of the BETA, how good the restoration of the existing configuration is after a factory reset with local backup (I’ve tested the backup, but it’s not satisfactory).

Reason for the question:
Since I always connect, record, etc. different devices to my router for software development, I reset the box every now and then to keep it “clean” and reconfigure everything (I know that 99% will say that this is not necessary).

If this works properly for my standard configuration (fixed installed devices) with the local backup, it would of course be an enormous time saving than having to reconfigure everything after a reset.

And sorry that I’m in the wrong topic, I just picked up on the backup here.

Greetings

Marco

---

I always create a backup of the Internet box on an internal computer and didn’t have any major problems restoring it, especially if there was still a large telephone list.

In any case, the latest (beta) firmware makes a very good impression so far and if you make the effort to enter the set data by hand and then save it again, you have a very stable Internet box. As always, don’t forget to set the two frequencies 2.4GHZ and 5.0GHz individually to make the WLAN more stable.

---

@Anonymous wrote:

restoring the config didn’t help either.

My devices already have a fixed IP but with the SONOS it’s not about the IB having to do that there.

Why do you need a fixed IP? Because my home automation addresses the SONOS via IP.

By the way, because of the large network. There are currently 44 devices on the LAN and that’s not quite all of them:smileyvery-happy:

---

Yes, it is clear that every user uses a different configuration and there are correspondingly different requirements. I don’t have a Sonos system myself, but I do have a NAS and alarm systems. With the Sonos, it is also known that conflicts arise again and again for some users. I have a Sonos installed with friends and we use the Airport Extreme as a WLAN access point, with the Internet box it wouldn’t be possible either way this is connected in the basement below.

N.B. I enter fixed IP addresses for the device where it is easy to enter them, the rest can also be done via the Internet box.

Hello Walter

Thank you very much for your answer (even on public holidays!)

I hope it’s the last time I bother you here today!

My approach for today would have been:

1. Backup data LOCALLY

2. Firmware update BETA

3. Factory reset

4. Restore the data that was created BEFORE the firmware update.

As I understand your answer, do you recommend recreating the configuration AFTER the update (BETA)? So don’t play the backup that I made before the firmware update?

Last:
I hope I haven’t overlooked anything, but from what I know, after a reset for the fixed IP assignment, I always have to first connect the device to the DHCP area and can only assign the IP fix after connecting for the first time. This means that I cannot assign the IP before connecting the device for the first time.

I see it that way, right?

Thanks again for the great support!

Greeting

Marco

---

@MarcoG1983 wrote:

Hello Walter

Thank you very much for your answer (even on public holidays!)

I hope it’s the last time I bother you here today!

My approach for today would have been:

1. Backup data LOCALLY

2. Firmware update BETA

3. Factory reset

4. Restore the data that was created BEFORE the firmware update.

As I understand your answer, do you recommend recreating the configuration AFTER the update (BETA)? So don’t play the backup that I made before the firmware update?

Last:
I hope I haven’t overlooked anything, but as far as I know, after a reset for the fixed IP assignment, I always have to first connect the device to the DHCP area and can only assign the IP fix after connecting for the first time. This means that I cannot assign the IP before connecting the device for the first time.

I see it that way, right?

Thanks again for the great support!

Greetings

Marco

---

You have to do the reset before the latest firmware update, if you do it the other way around the old firmware will be reinstalled.

The advantage of re-entering everything by hand after installing the firmware is that you don’t have to reinstall old errors when restoring them if they were present.

If I give a device a fixed IP address, the device is normally connected to the Internet box and then I give this device the fixed IP address, of course it cannot be an IP address that has already been used somewhere.

At the end you can completely shut down the Internet box and restart it.

Thank you very much. So everything is clear except for one thing.

Your quote *You can’t know everything* would probably have caught my attention, but it can’t fully explain it to me.

Why the reset before the update? Does this have to do with the BETA status?

Maybe I’m seeing this wrong, but if I update to the beta first, the old firmware should be gone and the router should reset itself with the BETA and therefore the BETA should still be there after the reset.

Or is the old firmware included in the data backup?

Warm wishes

Marco

@MarcoG1983 just iron the beta over it and it’s good!!! Worked for me without reset and restore.

but would still recommend a DASI.

YOU’RE RIGHT!

Now something becomes clear to me.

With my procedure (firmware, reset, configuration) I had the problem twice that the IB still got a different firmware after the reset.

I think this could be exactly what you described.

I’m going to do the update today without a reset.

Thank you for your help and detailed explanations.

I wish you all a happy Easter!

Greetings

Marco

Hello everyone,

I also installed the new beta and since then the WebGUI has no longer been available. The new version (07.50.29, Internet Box Standard) is displayed in Kundencenter, but no further settings can be modified. Is there a different access path specifically for the beta?

Internet is online and SWTV 2.0 works perfectly.

Greetings Martin

---

@Anonymous wrote:

my HD Phone Aascona always has the internal number 203. can no longer be changed. Even after gasping it is still at 203.

Already reported it.

---

You can change the number according to the picture below if you click internally!

---

@mabu1 wrote:

Hello everyone,

I also installed the new beta and since then the WebGUI has no longer been available. The new version (07.50.29, Internet Box Standard) is displayed in Kundencenter, but no further settings can be modified. Is there a different access path specifically for the beta? Internet is online and SWTV 2.0 works perfectly.

Greetings Martin

---

I always go via the internet browser and enter 192.168.1.1

Name: admin

Password: (can be found in Kundencenter).

@Anonymous, @WalterB,

I have already reset the box, restarted it and tried to reach the WebGUI from different platforms via IP (192.168.1.1) or “domain” (internetbox.home). Unfortunately, all variants have failed so far.

The box may automatically install new “stable” firmware as soon as it is available.

I reported the problem once using the form.

Greetings & have a nice evening,

Martin