Bonjour, Je me confronte à un souci depuis un certain temps et j'aurais besoin d'une confirmation de gens qui s'y connaissent. Est-ce que l'Internet Box 3 de Swisscom a une isolation hardcodée entre ses réseaux filaires et sans-fil? J'arrive à accéder a mon Nas sans problème via l'ip locale depuis ma tour qui est connectée en ethernet mais impossible de faire pareil avec mon laptop en wifi. Je sais que cette limitation existe pour le wifi guest mais qu'en est-il pour pour le wifi principal? Merci d'avance. Hello, I encounter an issue for a while and I would like a confirmation from people who know. Is wifi isolation hard-coded in the Internet Box 3 firmware? I can access my NAS from my fixed computer which is connected through ethernet but I can't from my laptop which uses wifi. I know that this limitation does exist on guest wifi, but what about the main wifi network? Thanks.

> @"J.Porta"#p925238 > Verfügt die Internet-Box 3 von Swisscom über eine fest programmierte Trennung zwischen ihren kabelgebundenen und kabellosen Netzwerken? Nein, so eine Isolierung gibt es definitiv nicht.

@"POGO 1104"#p925240 J'avoue que je ne comprends pas bien alors. Hier je ne pouvais pas du tout accéder a mon nas via son ip locale et maintenant ca refonctionne. Par contre impossible d'accéder a un docker Adguard déployé sur le Nas via une ip fixe. Je lui ai défini une MAC adresse fixe, mais elle commence par 02:42, est-ce que ca peut être un problème? [upl-image-preview uuid=fab7b07f-2a82-4904-bcd2-fa2c45698ef9 url=https://static.community.swisscom.ch/2026-06-26/1782459095-813825-image.png alt={TEXT?}]

Hallo @"J.Porta"#p925238 Es kann auf das Netzwerk bzw. deren Komponenten ankommen, aber grundsätzlich werden innerhalb des privaten Netzwerks keine IPs blockiert. LG Dana

@"J.Porta"#p925243 The static IP you assign to the container must be in the same network subnet range. Otherwise you won’t be able to access it. The MAC address is irrelevant. You probably messed up something with the docker networking. Which NAS do you have?

@"J.Porta"#p925243 Also bear in mind that you need to select the correct network type/driver. It needs to be macvlan for something like AdGuard. Some NASes only allow bridge and host to be selected from the WebUI.

@"bitracer"#p925581 Thank you for your answer. The IP was indeed in the same range. I decided to pause the Adguard project as the virtual switch of my Qnap TS-462 seems to mess with the box. But I suppose that the problem is elsewhere. To summarize I can't access my NAS QTS interface (administration) using a PC connected to my wifi. It is intermittent, sometimes it works, sometimes it times out. Isolation was the primary hypothesis but it won't be intermittent. I have a Internet Box 3 with 2 Wlan Box 3 repeaters. My wifi computer is connected on a Wlan box. My NAS is connected with a cable directly to the IB3 The IB3 is configured to distribute the static IP to the NAS and to the PC. My NAS has only one container (Vaultwarden) configured in NAT mode, which use the same IP as the NAS itself. Honestly, I don't know where to look anymore. I won't resume the deployment of Adguard until I've fixed this issue. Having a custom DNS server but not available by wifi would be useless :-D

@"J.Porta"#p925887 You need to narrow down what the issue is. How are WLAN-Boxes connected to the IB3? Cable or wireless? Are there any network switches in between? You can try to turn of the WLAN-Boxes, and test everything with only IB3. Get closer to the IB with the computer if you have WiFi signal issues. Also disable UPnP on the NAS. This could also be a virtual network issue on the QNAP. If all above doesn’t help, reset the network a create it again from scratch. Simplify it as much as you can, and turn of the firewall temporarily.

@"bitracer"#p925907 I have already removed all the firewalls to check (quFirewall on NAS, and Windows firewall on PC). I have also turned the both repeaters (which are connected by wifi to the IB3) and I got the same results. UPnP and Bonjour are already disabled on the NAS. I have no other switches anywhere in my network. It is crazy, sometimes I launch a ping and the first two requests return data while the two last ones time out! This is my virtual network configuration. I did not touch anything, it was created by Container Station: [upl-image-preview uuid=8e956d6e-29a6-4d58-9b41-eb80453ac1e2 url=https://static.community.swisscom.ch/2026-07-02/1783006918-411432-image.png alt={TEXT?}] [upl-image-preview uuid=3c0092ee-0c75-4254-82e0-54e085301277 url=https://static.community.swisscom.ch/2026-07-02/1783006974-908230-image.png alt={TEXT?}] Does it look normal?

I cannot believe it, I ran a ping just before writing my answer to check it was still broken… And I just ran one now after posting my answer… [upl-image-preview uuid=c7677c68-9de7-4e88-a05a-ba72a002a258 url=https://static.community.swisscom.ch/2026-07-02/1783007136-684452-image.png alt={TEXT?}] How can that be so intermittent?

@"J.Porta"#p925942 Are you sure there is no IP conflict somewhere? Switch the NAS to DHCP end test with the newly assigned IP address.

Isolation forcée sur le wifi standard (IB3)?

bitracer

J.Porta Beyond that, only replacing the IB remains. Maybe there’s really a hardware issue with the ports. Do you have another device you can hook up via ethernet to test? If that passes then it’s a QNAP issue.

J.Porta

bitracer

I’ve made some new tests from another wifi laptop, which is used by a member of my family. It is interesting because I can’t still join the WTS admin interface with the IP, but the Qnap sync app has absolutely no problem to join the NAS to run the sync. This is really strange, but maybe it is going through the MyQnap network to join it, I’m not sure.

This is really depressing.

WalterB

J.Porta

Hast Du mit dem QNAP Finder auf dem Notebook probiert ?

Qfinder Pro | Einfaches Auffinden, Zugreifen und Verwalten Ihrer QNAP NAS | QNAP

Selber kann ich mit allen WLAN Geräte intern auf das QNAP NAS zugreifen und extern über die VPN Verbindung auch keine Probleme.

J.Porta

WalterB I’ve indeed tried. QFinder see the NAS when it is reachable by browser, but it is not visible when it is not accessible by browser. Globally it is consistent.

I think that the issue lies in the ARP table which is corrupted by something during the day. Rebooting the box solves the issue, but I don’t want to have to reboot it once a day just to ensure that a router can use properly an ARP table…

WalterB

J.Porta

Du kannst vielleicht noch über das QNAP Forum probieren dort gibt es manchmal noch gute Hnweise.

https://forum.qnapclub.de/

PowerMac

J.Porta Beim Durchlesen des Threads, insbesondere aufgrund deiner Bemerkung weiter oben dass du dem AdGuard-Docker eine feste MAC-Adresse (??) zugewiesen hast, ist mir der Verdacht auf einen MAC-Konflikt aufgekommen. Führe wiederholt den Befehl “arp -a” aus und schau:

Ob sich die Zuordnung bestimmter MAC- zu IP-Adressen ändert
Ob sich mehrere IP-Adressen dieselbe MAC-Adresse teilen

Letzteres wäre grundsätzlich erlaubt, aber es sollte dafür einen nachvollziehbaren Grund geben (z.B. VMs oder Container).

Ausserdem kannst du via Webinterface der Internetbox schauen, an welchem Port welches Gerät mit welcher MAC-Adresse angeschlossen ist. Ändert sich der angezeigte Port für die problematische MAC-Adresse sporadisch? Wenn ja, dann an den betroffenen Ports weitersuchen.

« Vorherige Seite