5018

I did a reset today and had the latest config put back on via mySwisscom. I had to reset 2 times (buttonhole under the IB3) and each time I couldn’t access the box again. With the GW IP the browser was constantly spinning and could not see the GUI. I even tried with 2 browsers. Then I installed the latest config 2 more times and only after this 2nd time did it work.

Either the IB3 is broken or the software. It can’t be that I only have problems with it. Yesterday the Bluewin TV wouldn’t even connect after I wanted to watch something on YouTube that was controlled from my mobile phone. Had to completely reboot the TV box without this procedure, no more TV watching was possible.

Called customer support 3 times today and am still waiting for a call back ….. They are probably all busy with IB3 and firmware 15.00.46 problems 🙁.

Dude33 If you do a reset and then wait until the LED on the IB is constantly white again and without restoring the old configuration, then you won’t be able to access the GUI? It may be that the old configuration has a problem. As I said, there are no known problems with the IB3 and 15.00.46. Therefore, the hotline is not burdened by this ;-)

If none of this helps, then the hotline should install 14.xx.xx again. If it then works again, then something in your setup seems to be triggering a bug in 15.00.46.

5018

I did all this yesterday and today there was another outage (can no longer access the GUi) I had to restart the box with a cold start. In the static IP settings suddenly 2 devices appear that do not belong there but are not active and have no assigned IP. I changed the active DHCP range so that hopefully these suspicious devices are no longer on it next time. But I don’t really believe it. It is more likely that there is still corrupt data in the configuration memory that suddenly appears.

I’ll probably have to call …. again tomorrow because nobody is calling back.

Dude33 You can forget about the suspicious devices. It is probably about the device 192.168.1.220. This is an internal process that should not actually appear, but sometimes does. Unmanaged switches are often reported in the device list, but they do not obtain an IP address because they are unmanaged. I also have an Apple TV, which is connected via LAN, but also recognises WLAN access via the Apple ecosystem. The device is also regularly listed in the Wi-Fi list without obtaining an IP address. Now you could argue that the IB should recognise this and not display these devices. Yes, that is the case. But it’s more of a flaw and probably won’t be fixed any time soon (if at all possible with the software module).

On the subject of accessing the GUI. Do you only have the problems from one device (PC?) or also when you want to access the GUI from another device (mobile phone connected via WLAN)? Have you installed ad blocker software (AdGuard or something similar) on the device (PC?)? If so, then define an exception for 192.168.1.1.

Many thanks for all the answers and explanations.

I also had GUI hang-ups with other devices and at least once a day.

In the meantime I was able to replace the IB3, which is now back to version 14.?????. So the box is stable again but without the fixed problems which are in the 15.00.46. e.g. .ch domain resolutions from the LAN do not reach my NAS under 14.????? but with 15.00.46 they do.

Hello
Version of the Internet-Box IB3 firmware applied this evening, we’ll see what it does in practice.

15.00.46/02300

In the meantime, a large number of IB3/4 users have upgraded to version 15.00.46. There are a few findings that will probably lead to a new version being released. As the version contains a new version of the basic operating system, this was to be expected. However, the GUI theme from @Dude33 is not included. This is really an edge case.

Since updating to this firmware, I have the problem that my computer, which is connected to the 2.5Gb port, constantly loses the Ethernet connection completely every few minutes. The 1Gb ports work stable.

I will reset the box and hope for improvement, let’s see.

illetschiller

Yes, does your computer have a 2.5Gbit port?

illetschiller please report the error via the error tool, thank you.

user109 Where can I find this? I have now performed a factory reset and will observe whether the error still occurs.

illetschiller here

https://www.swisscom.ch/de/privatkunden/hilfe/geraet/fehlermelde-formular.html?campID=SC_bugreport

Tom459

Have you already checked the port forwarding and DynDNS?

To be able to run WireGuard on a Raspi within the internal network of a downstream router, the WireGuard server needs a private port, let’s say UDP 61111 as an example:

• on IB3 forwarding of port 61111 from IB3 to the IP of the downstream router within the IB3 network
• On own router Forwarding of port 61111 from own router to the IP of the Raspi within the own network
• The DynDNS used is best tracked directly on the Swisscom Internetbox, or otherwise using an external service that does not derive the public IPv4 of the Internet access directly from the WAN interface of your own internal router.

With this setup, my own WireGuard servers (I have 2 of them) continue to work without any problems, even in parallel with the new WireGuard server of the Internet boxes.

Werner

Hello Werner,

I think I was able to solve it. At least it is currently running. :-)
The ports were/are forwarded correctly, it was apparently the DynDNS.

There it shows me the address of Swisscom e.g. xyz.internet-box.ch and then I had set up one with my personal domain via Infomaniak. When I deactivated this (“Other DynDNS providers”). It worked via the Swisscom address. When I set up the new one from Infomaniak, it also worked and now it works again.

At the moment it works with both.

Apparently the service simply needed a “restart” for the other provider to work properly again.

Before I reactivated the Infomaniak service on the IB 3, I set it up on my Synology for testing purposes and it worked.

Which should I prefer, the DynDNS on the IB or behind it on another device?

Tom459

If possible, update DynDNS directly on the access router (in your case on the Internet box) is the simpler and better solution, because the provider router is the first device to realise if the public IPv4 address actually changes.