<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: IPv6 in Internet</title>
    <link>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/87651#M21706</link>
    <description>&lt;P&gt;Matter-certified devices. Thread, the underlying networking protocol often used with Matter, is explicitly built on IPv6. As found on various sites in a Google search. It can run on v4, but it limits it's full ability for expandability as IoTdevices are in greater use as v4 is being pushed to its limits of devices and will result in conflicts. This has been known as mentioned since 2000s theoretically and in testing and formalized in 2017 as mentioned.&amp;nbsp;&lt;/P&gt;&lt;P&gt;8 years later, all cable services are using ipv6 and bell is not. I too suspect this has something to do with ppoe and the need to stay backwards comparable to ppoe ovecdsl, ADSL and VDSL.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was just reading that ipv6 is not established with the initial ppoe connection it appears to be established locally, which may account for why we see it at the fibe stream level and not elsewhere. Whatever the reason, bell is limiting our movement to thread protocol based matter devices. D-Link is transitions to their TAPO brand which is matter and replacing the kasa brand which is traditional 2.4 and non matter based. I can't use the QR code to connect TAPO devices to their management tools, I have to establish them manually. Not sure why, but I will soon see with a change to an ipv6 based company whether I can use the QR code.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;a href="https://forum.bell.ca/t5/user/viewprofilepage/user-id/910463609"&gt;@SteveD&lt;/a&gt;&amp;nbsp;I have often heard lower level staff say oh it's coming this year. I figure they just tell us what they think or what they think we want to hear.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Bell has been critized on many forums over the years for absence of ipv6.&amp;nbsp;&lt;/P&gt;&lt;P&gt;It reminds me of how we know poor can be bridged with many challenges and now I find that theoretically ipv6 can be supported on ppoe with challenges. Appears like the tunnel solution described early, totally beyond my skill set, creating ipv6vallocation locally my flow over ipv4 and communication may occur that way, but seems bottom line that ppoe which permitted for single non share connections for DSL from the central station, then substations to the device over copper may never have been intended to be able to support ipv6 well. .&lt;/P&gt;&lt;P&gt;Theoretical only, but in general poor is a pain for home networking where a higher degree of isolation of your network form isp is desired, as well as enterprise firewall and VPN solutions are desirable for connection for at home or iff site work. If your employer pays for a business ISO connection wonderful, but not always available.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just saying and agreed time for bell to move into the 21st century, or at least stay up with industry standards. Last on the block I guess.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 01 Jun 2025 05:58:40 GMT</pubDate>
    <dc:creator>Retiredandbored</dc:creator>
    <dc:date>2025-06-01T05:58:40Z</dc:date>
    <item>
      <title>Gigahub and IPv6</title>
      <link>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/10489#M3064</link>
      <description>&lt;P&gt;In early October I switched from a third party internet provider that was using Bell’s copper lines to Fibe 3.0. When I made that switch I had issues with a lot of devices on my network, I used my own router using PPPoE pass through, so other than a change in external IP, things remained the same internally. I realized that I wasn’t getting an IPv6 address as part of the connection.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;i bypassed my equipment and connected directly to the Gigahub and couldn’t find any hint of configuration for IPv6 and my laptop wasn’t getting an IPv6 address.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;I called support ad the tech that I spoke to indicated that the next version of the firmware for the Gigahub would support IPv6 and I wanted to get an update. Do we have an ETA for IPv6 on the Gigahub?&lt;/P&gt;</description>
      <pubDate>Mon, 21 Nov 2022 01:11:30 GMT</pubDate>
      <guid>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/10489#M3064</guid>
      <dc:creator>SteveD</dc:creator>
      <dc:date>2022-11-21T01:11:30Z</dc:date>
    </item>
    <item>
      <title>Re: Gigahub and IPv6</title>
      <link>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/10577#M3073</link>
      <description>&lt;P&gt;Hi there &lt;a href="https://forum.bell.ca/t5/user/viewprofilepage/user-id/910463609"&gt;@SteveD&lt;/a&gt;,&amp;nbsp;&lt;BR /&gt;Thanks for your post and welcome to the Bell Community.&lt;/P&gt;
&lt;P&gt;Currently at this time we do not support IPv6 through residential service.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 22 Nov 2022 19:42:09 GMT</pubDate>
      <guid>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/10577#M3073</guid>
      <dc:creator>BellNick</dc:creator>
      <dc:date>2022-11-22T19:42:09Z</dc:date>
    </item>
    <item>
      <title>Re: Gigahub and IPv6</title>
      <link>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/10578#M3074</link>
      <description>&lt;P&gt;Sorry, just had to check my calendar, the initial RFCs for IPv6 came out in the 1990s, it is currently 2022.&lt;/P&gt;&lt;P&gt;Was the tech that I was speaking to mis-informed or did he straight up lie to me to get me off the phone?&lt;/P&gt;&lt;P&gt;Is there a timeline for when Bell will support IPv6 on their residential services?&lt;/P&gt;</description>
      <pubDate>Tue, 22 Nov 2022 19:47:41 GMT</pubDate>
      <guid>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/10578#M3074</guid>
      <dc:creator>SteveD</dc:creator>
      <dc:date>2022-11-22T19:47:41Z</dc:date>
    </item>
    <item>
      <title>Re: Gigahub and IPv6</title>
      <link>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/16124#M4859</link>
      <description>&lt;P&gt;You can create a tunnel from a device behind the gigahub to He.net via their service tunnelbroker.net&lt;/P&gt;</description>
      <pubDate>Tue, 07 Mar 2023 07:00:38 GMT</pubDate>
      <guid>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/16124#M4859</guid>
      <dc:creator>hackman</dc:creator>
      <dc:date>2023-03-07T07:00:38Z</dc:date>
    </item>
    <item>
      <title>Re: Gigahub and IPv6</title>
      <link>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/19396#M5587</link>
      <description>&lt;P&gt;Have you tried a Huuricane Electric ipv6 tunnel?&amp;nbsp; I'm trying, and on two systems both transmit but get no reply.&amp;nbsp; I'm not sure what the problem is yet, but it's startign to look like Bell is blocking protocol 41 IP messages.&lt;/P&gt;</description>
      <pubDate>Fri, 05 May 2023 16:49:57 GMT</pubDate>
      <guid>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/19396#M5587</guid>
      <dc:creator>snowblower</dc:creator>
      <dc:date>2023-05-05T16:49:57Z</dc:date>
    </item>
    <item>
      <title>Re: Gigahub and IPv6</title>
      <link>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/19438#M5599</link>
      <description>&lt;P&gt;I tried and had some success, but in retrospect it was slow and laggy. However I tried to run the HE IPv6 tunnel on a box that has a VPN so it is total possible that running over the VPN allowed it to work, but at the same time caused the delay. I’ll have to retest on a different box.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 06 May 2023 15:38:05 GMT</pubDate>
      <guid>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/19438#M5599</guid>
      <dc:creator>SteveD</dc:creator>
      <dc:date>2023-05-06T15:38:05Z</dc:date>
    </item>
    <item>
      <title>Re: Gigahub and IPv6</title>
      <link>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/19439#M5600</link>
      <description>&lt;P&gt;I finally got it working. The key was to use a separate router and connect to the GigaHub using a ppoe connection. That provided me with a separate IP address that was pingable. I could never get a ping through the GigaHub before, and it might have been blocking other stuff (despite all my experiementing with DMS and Advanced DMZ.&lt;/P&gt;</description>
      <pubDate>Sat, 06 May 2023 16:53:26 GMT</pubDate>
      <guid>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/19439#M5600</guid>
      <dc:creator>snowblower</dc:creator>
      <dc:date>2023-05-06T16:53:26Z</dc:date>
    </item>
    <item>
      <title>Re: Gigahub and IPv6</title>
      <link>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/20237#M5810</link>
      <description>&lt;P&gt;I wrote up a how-to for setting up a ipv6 tunnel router that will work on Bell's fiber network with a GigaHub:&lt;/P&gt;&lt;P&gt;&lt;A href="https://jptrainor.github.io/ipv6/2023/05/16/ipv6-tunnel-on-bell-fibre.html" target="_blank" rel="noopener"&gt;https://jptrainor.github.io/ipv6/2023/05/16/ipv6-tunnel-on-bell-fibre.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;... it's the best solution I could come up with as a hold-over until Bell joins the rest of us in the 21st century and supports IPv6.&lt;/P&gt;</description>
      <pubDate>Wed, 24 May 2023 19:32:40 GMT</pubDate>
      <guid>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/20237#M5810</guid>
      <dc:creator>snowblower</dc:creator>
      <dc:date>2023-05-24T19:32:40Z</dc:date>
    </item>
    <item>
      <title>Re: Gigahub and IPv6</title>
      <link>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/20739#M5934</link>
      <description>&lt;P&gt;I tried this, got the basics working, but too much random stuff is happening to make it worth it.&lt;/P&gt;&lt;P&gt;streaming services are misbehaving, Google searches are constantly asking me to prove that I’m not a bot, etc&lt;/P&gt;&lt;P&gt;I had a rep from Rogers come to my door the other day, seriously considering switching once my introductory price with Bell is gone.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jun 2023 23:04:04 GMT</pubDate>
      <guid>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/20739#M5934</guid>
      <dc:creator>SteveD</dc:creator>
      <dc:date>2023-06-04T23:04:04Z</dc:date>
    </item>
    <item>
      <title>Re: Gigahub and IPv6</title>
      <link>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/20862#M5966</link>
      <description>&lt;P&gt;Yes, I experienced google asking me if I'm a bot when I use the HE tunnel. I only use it occasionally to test some software where IPV6 is a must have, so it's not a problem. I have a dedicated sub-network that I connect to when I need IPV6.&amp;nbsp; The rest of the time I use Bell's vanilla IPV4. If I needed IPV6 day to day then Bell would not be an option as an ISP.&amp;nbsp; Hopefully Bell join the 21st century soon. I imagine that every peice of equipment that runs their network already supports it and all they need to do is configure it and turn it on.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jun 2023 13:05:29 GMT</pubDate>
      <guid>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/20862#M5966</guid>
      <dc:creator>snowblower</dc:creator>
      <dc:date>2023-06-06T13:05:29Z</dc:date>
    </item>
    <item>
      <title>Re: Gigahub and IPv6</title>
      <link>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/20873#M5973</link>
      <description>&lt;P&gt;I quickly looked into VPNs with IPv6 support and found one that seems to offer 10GB of traffic a month for free, so I might try to add this to my network using a separate VLAN/SSID.&lt;/P&gt;&lt;P&gt;Also you comment about Bell joining the 21st century is a bit strange, the first RFCs for IPv6 came out in the 20th century, so I would consider this them joining the 20th century.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jun 2023 13:49:27 GMT</pubDate>
      <guid>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/20873#M5973</guid>
      <dc:creator>SteveD</dc:creator>
      <dc:date>2023-06-06T13:49:27Z</dc:date>
    </item>
    <item>
      <title>Re: Gigahub and IPv6</title>
      <link>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/20892#M5978</link>
      <description>&lt;P&gt;I give them a break until 2017 when the draft standard was finally ratified.&amp;nbsp; After that, they are being complacent and living in the past. IMO&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jun 2023 16:27:31 GMT</pubDate>
      <guid>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/20892#M5978</guid>
      <dc:creator>snowblower</dc:creator>
      <dc:date>2023-06-06T16:27:31Z</dc:date>
    </item>
    <item>
      <title>Re: Gigahub and IPv6</title>
      <link>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/23172#M6465</link>
      <description>&lt;P&gt;I seriously do not understand why IPv6 is not already available.&lt;/P&gt;&lt;P&gt;I currently have Five 3.0... and considering switching to a "slower" cable provider to get IPv6. I need IPv6 to access and test some part of our network when I work from home. Using a tunnel may work... but it's definitely not optimal.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 00:14:51 GMT</pubDate>
      <guid>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/23172#M6465</guid>
      <dc:creator>Zadigre</dc:creator>
      <dc:date>2023-07-11T00:14:51Z</dc:date>
    </item>
    <item>
      <title>Re: Gigahub and IPv6</title>
      <link>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/23836#M6582</link>
      <description>&lt;P&gt;I have a number of Bell Fibe TV boxes and was very surprised to learn that each of these TV Android boxes had for its ID what looks like a ipv6 address … can anyone from Bell confirm this?&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jul 2023 15:26:19 GMT</pubDate>
      <guid>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/23836#M6582</guid>
      <dc:creator>iteoc</dc:creator>
      <dc:date>2023-07-18T15:26:19Z</dc:date>
    </item>
    <item>
      <title>Re: Gigahub and IPv6</title>
      <link>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/23839#M6583</link>
      <description>&lt;P&gt;can you give an example of what you are seeing?&lt;BR /&gt;TVs are on their own vlan/network... so I'm not really surprised to see they may be using IPv6 internally.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jul 2023 16:18:59 GMT</pubDate>
      <guid>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/23839#M6583</guid>
      <dc:creator>Zadigre</dc:creator>
      <dc:date>2023-07-18T16:18:59Z</dc:date>
    </item>
    <item>
      <title>Re: Gigahub and IPv6</title>
      <link>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/23849#M6585</link>
      <description>&lt;P&gt;If you are a Fibe TV Box subscriber go to Settings scroll down to &lt;STRONG&gt;System Info&lt;/STRONG&gt; and that's where you will see the ID that I believe looks very much like a ipv6 address.&lt;/P&gt;&lt;P&gt;I would post a Screen shot except that would violate the TOS on this fourm due to the sensitive info that is presented....&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jul 2023 17:21:07 GMT</pubDate>
      <guid>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/23849#M6585</guid>
      <dc:creator>iteoc</dc:creator>
      <dc:date>2023-07-18T17:21:07Z</dc:date>
    </item>
    <item>
      <title>Re: Gigahub and IPv6</title>
      <link>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/23855#M6586</link>
      <description>&lt;P&gt;IPv6 should be something like&amp;nbsp;&lt;SPAN&gt;2001:1234:4567:7890:abcd:1234:4567:7890. Is this what you are seeing?&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jul 2023 18:00:59 GMT</pubDate>
      <guid>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/23855#M6586</guid>
      <dc:creator>Zadigre</dc:creator>
      <dc:date>2023-07-18T18:00:59Z</dc:date>
    </item>
    <item>
      <title>Re: Gigahub and IPv6</title>
      <link>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/23873#M6589</link>
      <description>&lt;P&gt;Yes it Looks similar …&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jul 2023 21:00:29 GMT</pubDate>
      <guid>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/23873#M6589</guid>
      <dc:creator>iteoc</dc:creator>
      <dc:date>2023-07-18T21:00:29Z</dc:date>
    </item>
    <item>
      <title>Re: Gigahub and IPv6</title>
      <link>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/23885#M6591</link>
      <description>&lt;P&gt;that's one more proof bell is ready for IPv6. I don't know what they are waiting for exactly&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jul 2023 23:00:12 GMT</pubDate>
      <guid>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/23885#M6591</guid>
      <dc:creator>Zadigre</dc:creator>
      <dc:date>2023-07-18T23:00:12Z</dc:date>
    </item>
    <item>
      <title>Ipv-6</title>
      <link>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/30808#M8223</link>
      <description>&lt;P&gt;Just wondering if ipv-6 is still not a possibility in the setting of the modem ?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 01 Oct 2023 19:34:19 GMT</pubDate>
      <guid>https://forum.bell.ca/t5/internet/gigahub-and-ipv6/m-p/30808#M8223</guid>
      <dc:creator>Paps</dc:creator>
      <dc:date>2023-10-01T19:34:19Z</dc:date>
    </item>
  </channel>
</rss>

