First IPv6 Home Project failed

By

For the past few days, I've been trying to implement a dual-stack network for my home VLAN (non-IoT), but today it fails due to no supported feature set on some devices in my network.

I want to describe the details so that you too can learn from my mistakes or guide me to do better.

My home network is designed like this:



If you remember, I have written an article "Does NAT66 or NPTv6 need it?" These are similar requirements. My ISP modem and Dream Machines, both are designed to obtain IPv6 using the Prefix Delegation or static assignments. The ISP modem is getting PD subnet, but it is failing to supply to the Dream machine. Now, I have a single option for assigning IPv6 as Static on the Dream Machine.

And I have assigned the Site Local Subnet in the LAN and configured NAT with ipv6table. Used nonstandard option as ip6tables -t nat -A POSTROUTING -o eth4 -j MASQUERADE. There is no direct option to configure NATv6.NAT66, NAT64 etc.

What was the failure with this scenario: Some of the Devices were losing DNS resolution intermittently. Even ICMPv6 was also not stable. Currently, I am not sure about the root cause, but it was happening on the Dream machine.

In this condition, Dream machine only has the option to configure the DHCPv6 option. I can't find an option to implement SLAAC. And we are all aware of an issue with Android devices for DHCPv6. Google is not interested in implementing this feature in android. It works in Apple & Windows.

The second issue is related to Public Static IPv6 on the Dream machine. This IPv6 can change on every internet disconnection or ONT reboot. I might need to update it on every reboot. My Home Modem or ONT is rebooting once a day because my wife shut down the main Power supply, once he is getting out for a long time as going to the park or market.

How to resolve this issue:
Option 1: Remove the ISP modem and the Internet connection must be directly terminated on the Dream machine.
Option 2: Use another router that can support NAT66 or other options such as SLAAC configuration.
Option 3: Work harder to make NAT66 stable on Dream machine and replace Android devices, which seems not possible right now.




Comments

Post a Comment

Popular posts from this blog

Dark side of Extreme ELRP Protocols and some best practices

By
Image
This is my first blog here. I hope to continue this blog eventually. I decided to write blogs here only. Previously, I tried several places, like on my website, WordPress, etc. I came back to Blogspot after a long time. Without further delay, let me jump to the subject. Recently, I received an interesting topic from my colleagues. He explained to me that he can't find the loop on the extreme switches. All switches show loop disturbances. Even two or three switches are not accessible. After solving this problem, I have decided to carry out a LAB on this topic. My main focus will be some questions 1. Why are all the switches showing loops, but the loop was only available on one switch? 2. What action should be taken to avoid such complete downtime if the loop is detected again? Designed a LAB with the following information: Let's change some configurations on the switches. I am using the default VLAN for this lab purpose. As MST is enabled by default on the default VLAN. I will d...
Read more

Does NAT66 or NPTv6 need it?

By
Image
Does NAT66 or NPTv6 need it? Let's understand the NAT requirements with an Ipv6 address. Have you ever heard that we don't require NATing with IPv6? Is it true?  My answer will be yes if you are a CCNA student, otherwise, it is only a half-truth. How? Let's try to understand with a few examples: 1. In Theoretical or book statements, IPv6 does not require any NATing because we have enough IPv6 Addresses. Your ISP might supply a/48 prefixes, so you have more than the required networks or prefixes for your office/home. So mostly you will not have to translate from private to public or vice versa. But is it a 100% true statement? I think no and practical is also approved no. Let's check other points.  2. What if your ISP modem does not respond to the Client's RA messages? If you still need Ipv6 Enabled network, then you mostly prefer to use NPTv6.  3. In the future you might change your ISP and you don't want to be stuck in a face to reconfigure the complete network...
Read more

BGP Slow Peer Detection

By
Image
 What is Slow peer detection? We have a group of routers with the same outgoing route-map (outbound policy), which means the router will place all neighbors in the same group because the router wants to save resources to perform the same task multiple times for example: sending route updates.  The router will select a "Leader Router or Neighbor" and perform update or other algorithm tasks and will also replicate to all other routers in the same group.  What if any of one router is too slow due to hardware or software issues? This slow router is called Slow Peer. Slow peers affect the BGP convergence of the entire update group. If one BGP peer is slow, it causes the entire update group to slow down. The result is that the other update group members will have slower convergence as well. For this reason, the issue should be resolved. You can identify the slow peer and move it out of the update group. In order to complete this task, you can change the outbound policy for...
Read more