Rogers IPv6 Status

Need Help?

That's what we're here for! The goal of the Rogers Community is to help you find answers on everything Rogers. Can't find what you're looking for? Just ask!
cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
I Plan to Stick Around
Posts: 271

Re: Rogers IPv6 Status


@sergeturgeon wrote:

> For your router's IPv6 IP, yes.

 

And, do you know the format?

 

I understand IPv6 addresses from the local LAN won't have a Rogers domain name but the router should  have a hostname.

 

My use-case is to establish a VPN connection to my home router using an IPv6 hostname instead of its IPv6 address. 

 

 

 

 


You should now have a host name based on the firewall/router and cable modem MAC addresses in the form:

CPE<router MAC address>-CM<modem MAC address>.cpe.net6.cable.rogers.com

 

I don't recall seeing this when I checked a few months ago.

 

I Plan to Stick Around
Posts: 271

Re: Rogers IPv6 Status


@RogersDave wrote:

Rogers IPv6 Settings for pFSense firewall

In WAN Interface menu:

  • Use IPv4 connectivity as parent interface: yes
  • Request only a IPv6 prefix: no
  • DHCPv6 Prefix Delegation Size: 64
  • Send IPv6 prefix hint: yes

In LAN Interface menu:

  • IPv6 Configuration Type: track interface
  • IPv6 Interface: WAN
  • IPv6 Prefix ID: 0

In Advanced Settings / Network menu:

  • Allow IPv6: enabled

pFSense may need to be rebooted for the configuration changes to take effect.


Earlier in the thread I mentioned how my prefix would change after something as simple as disconnecting/jreconnecting the WAN Ethernet cable.  I discovered the problem was caused by pfSense sending a DHCPv6 release.  This has since been corrected in pfSense v 2.3.3.  In Interfaces > WAN, under DHCP6 Client Configuration, enable: "Do not allow PD/Address release".  This will cause pfSense to stop sending the release.

I Plan to Stick Around
Posts: 271

Re: Rogers IPv6 Status


@JKnott wrote:

@sergeturgeon wrote:

> For your router's IPv6 IP, yes.

 

And, do you know the format?

 

I understand IPv6 addresses from the local LAN won't have a Rogers domain name but the router should  have a hostname.

 

My use-case is to establish a VPN connection to my home router using an IPv6 hostname instead of its IPv6 address. 

 

 

 

 


You should now have a host name based on the firewall/router and cable modem MAC addresses in the form:

CPE<router MAC address>-CM<modem MAC address>.cpe.net6.cable.rogers.com

 

I don't recall seeing this when I checked a few months ago.

 


 

I just checked and see the CPE MAC is different for IPv4 & IPv6.  The IPv4 CPE MAC reflects the WAN NIC MAC, but the  IPv6 CPE MAC is from the LAN NIC.

Resident Expert
Resident Expert
Posts: 1,083

Re: Rogers IPv6 Status

IPV6 has been enabled for the CODA 4582!

just reboot the modem to get IPV6.

 



I Plan to Stick Around
Posts: 108

Re: Rogers IPv6 Status

IPv6 Dual homing with Rogers and another ISP?

 

Now that Rogers has enabled IPv6 for the CODA, I'll have Rogers and TS handing out IPv6 to me.

Anyone one here have it successfuly running and routing properly in an active/active setup?

Resident Expert
Resident Expert
Posts: 6,229

Re: Rogers IPv6 Status

@yyzsam you must be running something like a PfSense type of router or an Asus router with dual wan enabled?  If its a PfSense type of router, you might be better off asking that question in the forum for that router.  



I'm a Reliable Contributor
Posts: 146

Re: Rogers IPv6 Status


@JKnott wrote:

@RogersDave wrote:

Rogers IPv6 Settings for pFSense firewall

In WAN Interface menu:

  • Use IPv4 connectivity as parent interface: yes
  • Request only a IPv6 prefix: no
  • DHCPv6 Prefix Delegation Size: 64
  • Send IPv6 prefix hint: yes

In LAN Interface menu:

  • IPv6 Configuration Type: track interface
  • IPv6 Interface: WAN
  • IPv6 Prefix ID: 0

In Advanced Settings / Network menu:

  • Allow IPv6: enabled

pFSense may need to be rebooted for the configuration changes to take effect.


Earlier in the thread I mentioned how my prefix would change after something as simple as disconnecting/jreconnecting the WAN Ethernet cable.  I discovered the problem was caused by pfSense sending a DHCPv6 release.  This has since been corrected in pfSense v 2.3.3.  In Interfaces > WAN, under DHCP6 Client Configuration, enable: "Do not allow PD/Address release".  This will cause pfSense to stop sending the release.


@JKnott I've tested "Use IPv4 connectivity as parent interface: no" and it works.  Any thoughts on why this would need to be set to yes?

I Plan to Stick Around
Posts: 271

Re: Rogers IPv6 Status


@Double_K wrote:

@JKnott I've tested "Use IPv4 connectivity as parent interface: no" and it works.  Any thoughts on why this would need to be set to yes?


 

Did you try rebooting after you did that?  pfSense has to get it's prefix from somewhere.  With Rogers, it uses DHCPv6 prefix delegation.  If you don't get it from the IPv4 interface, where will you get it?

 

I Plan to Stick Around
Posts: 108

Re: Rogers IPv6 Status

My research told it wouldn't work but last night I quickly set it up and it appears to be working OK but there are some oddities or maybe because I'm new to IPv6 and don't fully understand.

It isn't assigning 2 IPv6 addresses from each provider to all clients, it's just using Rogers at the moment but I am able to route traffic across each ISP. My research said this most likely wouldn't be possible because the ISP wouldn't allow it.

Lot's of testing to do today.

BTW I am using Sophos UTM 9.x
I Plan to Stick Around
Posts: 271

Re: Rogers IPv6 Status


@yyzsam wrote:
My research told it wouldn't work but last night I quickly set it up and it appears to be working OK but there are some oddities or maybe because I'm new to IPv6 and don't fully understand.

It isn't assigning 2 IPv6 addresses from each provider to all clients, it's just using Rogers at the moment but I am able to route traffic across each ISP. My research said this most likely wouldn't be possible because the ISP wouldn't allow it.

Lot's of testing to do today.

BTW I am using Sophos UTM 9.x

 

 

I'm not sure what your question is.  It's certainly possible to assign multiple IPv6 addresses to an interface.  In fact, that makes it easy to move from one ISP to another without disruption.

Order Now!
Wilder vs. Ortiz II Live
LIVE: Saturday, November 23, 2019 8PM ET
Channels: 348 (HD) | 350 (SD) | Ignite TV 499
Price: $74.99 (HD) | $69.99 (SD) | Ignite TV $74.99
DTV can order on Nov. 21st & Ignite TV customers can order now!

Reigning heavyweight world champion Deontay "The Bronze Bomber'' Wilder takes on his most dangerous challenger as he defends his WBC title in a rematch against once-beaten Cuban slugger Luis "King Kong'' Ortiz.