Streaming Helix sous Linux
Bonjour, Je vous gratifie d'un énième message demandant la compatibilité de la plateforme de diffusion Web d'Helix avec Linux. Je consomme pas mal de streaming et Vidéotron est la seule entreprise que je connaisse qui ait réussi à pondre une plateforme Web qui bloque certains de leurs clients sur la base de leur système d'exploitation. J'ai même un abonnement avec un autre diffuseur Canadien que je ne nommerai pas, et où c'est bel et bien simple TM . Tourlou !
Une commande vocal anglophone
J'étais un peu frustré lorsque ma commander vocale configuré en français ne comprenait pas toujours ce que je lui disais. Pourtant le français est ma langue maternelle. J'ai décidé de configurer celle-ci en anglais. Et quel différence! 98% de taux de réussite dans la compréhension de mes demandes. Si vous avez de la difficulté à vous faire comprendre en français et que votre anglais est assez bon, je vous suggère de faire comme moi.
Changing DNS servers in Helix Fi
This question has been asked in 2 other threads on this forum in 2023 and 2025 with the only solutions being to either change the DNS setting on each device connected to the Helix gateway or to buy a router and connect to the gateway in bridged mode. I have a better suggestion: Videotron developers *finally* update the Helix Fi app by adding an "Edit" button on the DNS server page to allow paying customers to change it there. How hard can that be? We can edit other features on the gateway like the DMZ, so why not the DNS settings?? I get that the hardware runs on Comcast's Xfinity xFi platform which locks down advanced networking configurations to prioritize ecosystem integration, support simplicity, and security over user customization. In light of that, just add a check box next to a statement that says something like: "I understand that changing the default DNS settings may cause Vidéotron Helix services (including Helix TV, parental controls, and advanced security features) to malfunction or stop working entirely. I agree that Vidéotron is not responsible for any service disruptions caused by custom DNS configurations, and that Vidéotron technical support cannot assist in troubleshooting network issues arising from these changes. I assume full responsibility for managing my custom network settings." I would be willing to check that box!
Recurring incorrect geolocation issue affecting multiple Videotron public IP ranges
Hello, I am experiencing a recurring geolocation issue affecting my Videotron Internet connection and multiple public IP addresses assigned to my account. All devices connected through my home Internet connection (computers, phones, tablets) are incorrectly geolocated by Google services to Qiddiya City / Saudi Arabia instead of Montreal, Canada. Symptoms include: Google Maps immediately placing my location in Saudi Arabia “Near me” searches returning Middle East results Incorrect regional results and geolocation across Google services time and date Important troubleshooting already completed: The issue affects ALL devices connected to my home Internet LTE/5G on the same phones works perfectly and immediately returns the correct location. IPv6 is disabled I use my own router (UDM-Pro) with the Videotron modem in bridge mode Most importantly: Changing the WAN/public IP temporarily resolves the issue, but after approximately 3-4 days the problem returns again. Example affected IPs: 135.19.220.105 184.162.107.94 This strongly suggests that there is an issue with the geolocation/routing information associated with certain Videotron IP ranges or upstream routing pools. This is clearly not: a browser issue a device issue a WiFi issue or a Google account issue Please escalate this issue to the appropriate network/networking-geolocation team and investigate: incorrect IP geolocation registration upstream routing/geolocation databases DHCP pool assignments possible incorrect registration of Videotron IP blocks with Google geolocation services At this point, the issue is recurring across multiple IP assignments and requires investigation from the network side. Thank you.Block incoming connections and ports - ZyXEL EMG2926-Q10A
Greetings, On the Videotron modem ZyXEL EMG2926-Q10A, does anyone know how to block all incoming traffic (from the internet to the modem) and how to lock all ports from incoming connections? When login into the modem via a web browser and the clicking on: Expert Mode > Configuration (left side of the screen) > Security > Firewall > Services > Add firewall rule , I cannot find the option for “incomming” traffic or “outgoing” traffic. There is only the “Source_IP_Address” which I suspect is the way to block the incomming connections to the modem. From my point of view, one would have to list all IP addresses as “source” by stating an IP address range such as 0.0.0.0 to 255.255.255.255. 1) Is that the way to block incoming connections to the router? 2) What is the correct way to type/state an IP address range in the EMG2926-Q10A? Regarding blocking the ports on the modem from incoming connections: 3) is that within: Expert Mode > Configuration > Security > Firewall > Services > Add firewall rule > SourcePortRange that ports 0 to 65535 have to be typed in to prevent people outside the network from scanning/using ports on the modem? Lastly, its not clear if creating a firewall rule (as stated above; “Add a firewall rule”) will create a rule that “allows” or “block” the traffic. 4) Does firewall rules block or allow traffic? Thanks in advance, Regards, BIPv6 et Helix en mode pont / IPv6 & Helix Bridge Mode
Ce sujet est revenu à plusieurs reprises au fil des années, avec des niveaux de résolution variables. Je pense que plusieurs clients — particulièrement ceux d’entre nous qui travaillent dans le domaine des technologies — attendent toujours une réponse claire et officielle de Vidéotron concernant la prise en charge d’IPv6 sur des routeurs et pare-feu gérés par le client. Pour quiconque dépasse une configuration résidentielle de base, la passerelle Helix n’est généralement pas utilisée comme routeur principal ou pare-feu en périphérie du réseau. Plusieurs clients utilisent plutôt des solutions plus avancées comme Unifi Gateway, pfSense, OPNsense, IPFire ou VyOS. Avec IPv4, tout fonctionne très bien lorsque le modem Helix est configuré en mode pont (bridge mode). Par contre, du côté d’IPv6, la situation demeure non résolue. Pendant un certain temps, Vidéotron offrait le 6rd comme solution de contournement, mais plusieurs utilisateurs ont rapporté des résultats inconsistants, ce qui explique peut-être pourquoi cette option a finalement été abandonnée. Nous voilà rendus en 2026, et il ne semble toujours pas y avoir de solution documentée ou officiellement supportée. Pourtant, une solution existe clairement sous une forme ou une autre, puisque la passerelle Helix est capable d’attribuer des adresses IPv6 lorsqu’elle fonctionne en mode routeur. La question est donc simple : pourquoi la configuration requise pour le mode pont n’est-elle pas documentée publiquement? TL;DR En 2026, comment un client utilisant une passerelle Helix en mode pont peut-il configurer IPv6 sur son propre routeur ou pare-feu? ---- This topic has come up several times over the years, with varying degrees of resolution. I think many customers—especially those of us in the tech industry—have been waiting for a clear and official response from Videotron regarding IPv6 support on client-managed border routers and firewalls. For anyone beyond the most basic home setup, the Helix gateway is often not used as the primary border router or firewall. Many customers rely on more advanced solutions such as Unifi Gateway, pfSense, OPNsense, IPFire, or VyOS. With IPv4, this works perfectly fine when the Helix modem is placed in bridge mode. IPv6, however, is still unresolved. There was a period when Videotron offered 6rd as a workaround, but many users reported inconsistent results, which may explain why it was eventually discontinued. Fast-forward to 2026, and there still does not appear to be a documented or supported solution. Yet one clearly exists in some form, since the Helix gateway is capable of provisioning IPv6 when operating in router mode. This raises a simple question: why is the required configuration for bridge mode not publicly documented? TL;DR In 2026, how can a customer using a Helix gateway in bridge mode configure IPv6 on their own firewall/router hardware?
Configuration de la messagerie Thunderbird
J'ai passé plus d'une heure ce matin avec le service technique pour essayer de configurer Thunderbird, sans succès. Le programme fonctionnait parfaitement hier. J'ai réinstallé Thunderbird et tenté de le réinstaller, sans plus de succès. Quelqu'un a-t-il déjà rencontré ce problème et réussi à le résoudre ?
