pgloor

  • Joined
  • Level1
  • Points108
  • Posts26
  • Solutions2
  • I just found an answer about the Cockpit App in another thread. It says that it should also work in the browser, but that wasn’t the case for me.

    By the way, I deleted the browser cache. I’ll be in Germany in 2 weeks and will test it again and contact support if necessary.

    Show original language (German)
  • @fmueller: No, I don’t mean the roaming app. It may have been little more than a link, but it was embedded in its own window. By that I mean I didn’t have a browser menu. However, what I saw in the app was 1:1 what I also see in the browser. This “Cockpit App” was installed for me by an employee in the Swisscom Shop.

    Show original language (German)
  • Querying the cockpit with prepaid is only possible via WLAN

  • I use a PREPAID subscription with a data package for data roaming abroad. As far as I remember, in the past I was able to view and top up the credit at any time using the Cockpit app. Unfortunately, I deleted the Cockpit app and couldn’t find it anywhere, so I have to do it via a browser.

    If I wanted to establish a connection to cockpit.swisscom.ch in France without WiFi, it took forever (it felt like at least a minute) until the browser gave me an error message, which usually said that this address could not be found can be.

    IMG-20210815-WA0000.jpg

    IMG-20210815-WA0001.jpg

    I tried it with different browsers (Google, Chrome, Samsung Internet). The problem was always the same, only the text of the error message was different. It worked over a WiFi connection.

    Show original language (German)
    • @pgloor Über den Webbrowser geht das nur, wenn du im Netz bist, z.B. WLAN, sonst geht das nicht. Auf der Natelapp ist das was anderes, weil die Verbindung eine andere ist.

  • This is not about the fundamental discussion of whether IPv6 is generally an advantage or disadvantage for customers, but rather about “native IPv6” and some of us have reasons for this.

    I am also aware of problems from end customers who have problems with IPv6, but that has absolutely nothing to do with the introduction of “native IPv6”. Rather the opposite is the case.

    It would be a total shame if Swisscom fell to the level of its competitors, but at least that doesn’t seem to be the case.

    Show original language (German)
  • Today at 10:49 a.m. I received another call like this from the number 0044 833 212 991. A nice lady tried to explain to me in broken German that she was calling from Microsoft Support because I had caught a virus via a phishing email and that she wanted to help me remove it.

    I put her off for a while and always said a friendly yes to her explanations. When she became more specific and wanted information from me, I asked her for my Microsoft Partner ID. She ignored the question and replied that she had my software number.

    I doubled down: “So you can certainly tell me my Microsoft Partner ID”?

    You: “Oh, you are a partner”?

    Me: “Yes”

    You: “Bloody bullshit… Fuck off…”

    The conversation was over.

    Show original language (German)
  • After I performed the hardware reset, set STP and removed the strange entry of an iPhone from the device list, everything is stable again.![:smile:](https://community.swisscom.ch/html/@56675CEE52B2535AADE735290D6EE556/images /smilies/smiling.png “:smile:”)

    I also removed the repeater or no longer connected it, but I had already switched it off. This dates back to an earlier installation, but is probably no longer needed because in connection with the switch from ISDN/Centro Grande to the Internet box, the location of the WLAN router was also changed and could be placed more centrally.

    Show original language (German)
  • I wanted to, but couldn’t:roll_eyes: I don’t even know how this setting was set .

    As already mentioned, since the HW reset tonight the utilization has returned to normal.

    Show original language (German)
  • Internet box standard with firmware 08.08.28. Tonight I couldn’t even log into the box.

    The quick tests only said that something was wrong with the router. At the end of the questionable three tests, I was supposed to hire a technician for a fee! What a disgrace.

    I then performed a hardware reset (with the paper clip) and lo and behold, it seems to have achieved something.

    Somehow I still don’t trust it. My son’s iPhone showed up in the overview as a wired device this morning. That’s not possible at all.

    I then removed it from the device list and now it appears again under WLAN but with -2 at the end of the name.

    My trust in this box is decreasing, as is my trust in Swisscom in general.

    Show original language (German)
  • Unfortunately it didn’t help. Same thing again this evening and as I’m writing this I’m not even able to log into the Internet Box after I restarted the box.

    Show original language (German)
  • Maybe this has been resolved. I also deleted the port forwardings and not just deactivated them. Then I restarted the Internet Box. Afterwards the CPU utilization briefly went to 89% and then fell back to < 20%.

    I hope it stays that way.

    Show original language (German)
  • CPU utilization > 90%

  • Since yesterday our internet feels extremely slow. My son feels the same way too. It doesn’t matter whether the computer is connected to the Internet box via WLAN or with a cable via the LAN.

    Internet speed tests for http://hsi.bluewin.ch/speedtestJs are usually only slightly below the expected 40 Mbit/s. On the other hand, connections, such as to the SBB timetable, break down unexpectedly during the search. It sucks!

    When I looked at the diagnosis a little more closely today, I noticed that the CPU utilization of the Internet Box was almost always over 90% high for hours over the last 24 hours, with a few exceptions. Even at night when the computers were switched off.

    The > 90% CPU is also present when there is really no or hardly any traffic.

    After a restart, the utilization was immediately around 80% from the start and after an hour it was back to 90%, and the trend was rising.

    What could be going on and what should I do? It’s still working so far, but I think the problems with the “slow” connection and the > 90% CPU usage are related.

    Otherwise, I had the impression that the problems arose after I deactivated a port forwarding that I no longer needed. Port forwardings are no longer active.

    Show original language (German)
    • After I performed the hardware reset, set STP and removed the strange entry of an iPhone from the device list, everything is stable again.![:smile:](https://community.swisscom.ch/html/@56675CEE52B2535AADE735290D6EE556/images /smilies/smiling.png “:smile:”)

      I also removed the repeater or no longer connected it, but I had already switched it off. This dates back to an earlier installation, but is probably no longer needed because in connection with the switch from ISDN/Centro Grande to the Internet box, the location of the WLAN router was also changed and could be placed more centrally.

  • The idea of ​​@PowerMac corresponds roughly to what I thought of myself.

    A DDNS Portmapper Box is available at http://www.feste-ip.net. I’ll try to do something similar with a Raspberry Pi in the next few days to delve deeper into the subject.

    I will briefly report on my experiences and results later in this thread.

    Show original language (German)

  • @PowerMac wrote:

    Swisscom is currently using an interim solution called “6rd”, in which the IPv6 prefix is ​​calculated from the dynamically allocated IPv4. When the IPv4 changes, the IPv6 prefix inevitably does too. Details can be found in the document linked by @user109.


    The document that @user109 refers to is great for my current work, but it doesn’t answer the DynDNS question either. My work specifically relates to a personal project that is about clarifying how to enable IPv6 for home-based servers such as Opensimulator in the future. The document therefore provides the best overview of the entire problem that I have ever seen.


    @PowerMac wrote:
    If noip.com does not support dynamic updates of IPv6 (AAAA records), switch to another provider. It certainly works with afraid.org and Synology’s DDNS service; other providers can be found using a search engine.


    On the one hand, I paid for the service in advance for three years at noip.com. Well, it’s your own fault.

    As for Synology’s solution, it is only a solution for Synology products. I admit, that’s one approach, but here the buck is simply passed from one person to another.

    I haven’t found any other solutions that are supported by the Pirelli Centro Grande.

    If, for technical reasons, because you missed it or for whatever reason, it is not possible to offer fixed IPv6 addresses, it would not be easy for a company like Swisscom to offer a solution in the spirit of Synology, where you can simply use the routable one, for example IP of the devices could register?

    I expect a professional solution from Swisscom that is officially supported by Swisscom, whether with DynDNS service or a fixed IpV6 Global prefix doesn’t matter to me. Is that asking too much?

    Show original language (German)

  • @Tux0ne wrote:
    Just additional. For SME products on ALL IP, native IPv6 is/is offered, provided you have fixed IPv4.
    It’s my turn. I just received another sign of life from Swisscom on Friday…


    I don’t want to change subscriptions and, as a private user, I certainly don’t want an SME solution. All I expect is the same performance as before even when switching to IPv6.

    However, I would be willing to pay a little more for a fixed prefix (e.g. CHF 2 / month or something similar to the DynDNS service costs).

    Show original language (German)
  • Dynamic IPv6 prefixes, how is that supposed to work?

  • I have a Pirelli Centro Grande ISDN router with IPv6 turned on. For years I have been using DynDNS from the provider No-IP for a specific application. This always worked well and without any problems.

    Today I looked into IPv6 in more detail and discovered that every time the IPv4 address changes (e.g. after restarting the router) the IPv6 prefix also changes. This means that my computers always get a new IPv6 address. How does Swisscom imagine this will work?

    With IPv4 I have port forwarding, which means I only have to change the IPv4 address at noip.com and the Centro Grande with DynDNS does this well and completely automatically. I can use port forwarding to send the protocols to their destinations.

    With IPv6, however, each target host has an IPv6 address and I see no way to automatically and dynamically allocate these addresses when the IPv6 address changes.

    Have I missed something or have I made a fundamental error in thinking? Or what was Swisscom thinking? I assume there is a solution. It has to, right?

    P.S. But please don’t come and say the solution is IPv4… we’re in 2016!

    Show original language (German)

    • @pgloor schrieb:

      […]

      Heute habe ich mich mal eingehender mit IPv6 befasst und dabei festgestellt, dass sich mit jedem Wechsel der IPv4 Adresse (z.B. nach Neustart des Routers) auch der IPv6 Präfix ändert. Das heisst, meine Rechner bekommen auch immer eine neue IPv6 Adresse. Wie stellt sich Swisscom vor, dass das funktionieren soll?


      Swisscom verwendet aktuell eine Übergangslösung namens “6rd”, bei der das IPv6-Präfix aus der dynamisch zugeteilten IPv4 errechnet wird. Wenn sich die IPv4 ändert, tut dies zwangsläufig auch das IPv6-Präfix. Details sind im von @user109 verlinkten Dokument zu finden.


      @pgloor schrieb:

      […]

      Bei IPv4 habe ich Portforwarding, d.h. ich muss also nur die IPv4 Adresse bei noip.com ändern und das macht der Centro Grande mit DynDNS gut und völlig automatisch. Über das Port-Forwarding kann ich die Protokolle ihren Zielen zuführen.

      Bei IPv6 hat aber jeder Zielhost eine IPv6 Adresse und ich sehe keine Möglichkeit, wie ich diese Adressen bei einem Wechsel der IPv6-Adresse automatisch und dynamisch zuteilen soll.

      […]

      P.S. Aber bitte kommt jetzt nicht und sagt die Lösung ist IPv4… wir sind im Jahr 2016!


      Falls noip.com keine dynamischen Updates der IPv6 (AAAA-Records) unterstützt, wechsle zu einem anderen Provider. Sicher funktionieren tuts mit afraid.org und dem DDNS-Service von Synology, andere Anbieter sind per Suchmaschine zu finden. Da nun jedes Zielgerät in deinem Netz eine andere Adresse hat, musst du auch auf jedem dieser Geräte einen DDNS-Client konfigurieren.

      Eine anderer Lösungsansatz ist natives IPv6 ohne wechselnde Präfixe, was faktisch in etwa einer statischen IPv4 entspricht. Das hat Vor- und Nachteile und ist sowieso bei Swisscom momentan nicht~ mit einem KMU-Abo möglich.

      Auf dem Router brauchtst du bei IPv6 kein Portforwarding mehr, ggf. musst du noch eine Firewallrule einrichten um den Zugriff zu erlauben.

      Edit: gem. Kommentar von Tux0ne.

  • I solved it: In Swisscom Kundencenter, delete the SSID under the WLAN 2 settings, enter the key and click on continue or save changes. Then WLAN 2 disappears in the router. There’s just one small problem: In Kundencenter, WLAN 1 is also gone!

    But that can also be remedied: re-enter the information from WLAN 1 with the original data, then you have control over WLAN 1 again.

    Post edited (January 23, 2016 12:08): Added the final solution to the post and removed the sentence in which I let out my frustration.

    Show original language (German)