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?Synology NAS crashes my Helix gateway
I'm hoping that someone can help me find a solution to my problem. A little context: I've been with Vidéotron for over 20 years, prior to moving to their Helix service I had their legacy Hybrid Fibre Internet and never had a problem. I was using my own routers and everything was working well. When the technician installed my Helix gateway I asked him to set it up in bridge mode since I wanted to keep using my routers. After the installation everything seemed to be fine for a couple of days; then the problems started. The internet would go down so I'd check the gateway to find that the light was red. I would unplug it, plug it back in and the internet connection would come back. This lasted another few days and it would go down again. Some days I would have to reset it 4-5 times. I called customer support and they told me the problem was on my end since the gateway was in bridge mode. I explained that my setup had not changed, save for the new gateway, and I had no issues with the previous modem. They explained that it was different since Helix combines the modem and the router and offered no real help. After several months of dealing with this very annoying inconvenience I decided to reset the Helix gateway to it's factory settings and only use that for my home network. After setting up everything the issue started happening again. This time I knew that it wasn't because of my routers so I started eliminating other devices. I determined that the problem was caused by my Synology NAS. This is actually a "faux" Synology NAS, meaning that I'm using open source software called Xpenology to run the Synology DSM software on a regular computer. So, whenever I plug my NAS into the network it crashes the Helix gateway. Sometimes it's almost immediate whereas some other times it can stay up for an hour or so. I've played around with different settings on the NAS and turned off most of the services but that didn't resolve the issue. What I tried today and what seems to be working so far, is leaving the gateway field blank in the NAS network settings so that I can still access it locally but it can't reach out to the internet. I apologize for the very long post and if you've made it this far I want to thank you for reading this. Does anyone have any suggestions? PS. I hooked up my NAS to my dad's Helix gateway and it ran fine for about 10-15 minutes. I realize now that I should have left it connected for at least a few hours.
Is bridge mode really passthru?
I just switched from regular modem from videotron to Helix. I have put helix in bridge mode. Since then, I am not able to connect to my FTP server at home. When connecting the helix portal via the web interface, nothing is related to firewall. And since I am in bridge mode, I cannot use the Helix app. So Is there anything I am missing?Improving VoIP Stability While Traveling – Stag VPN Experience
<p>Hey everyone,</p> <p> I wanted to share a quick tip for those who rely on VoIP or internet calling services while traveling or working remotely. I've been using <strong>Stag VPN</strong> recently to stabilize my internet connection during calls, especially over public or shared networks. </p> <p> Before using it, I often had call drops or jitter issues with my internet telephony setup. But with Stag VPN, the connection feels more stable and secure. It routes traffic efficiently and helps avoid ISP throttling or region-based disruptions. </p> <p> Anyone else here tried using a VPN for internet calling? Would love to hear your experience or other recommendations! </p> <p><strong>Tags:</strong> <em>#VoIP</em>, <em>#VPN</em>, <em>#StagVPN</em>, <em>#InternetCalling</em>, <em>#RemoteWork</em></p>