Hi @Its-A-Trap  @jake-at-home 

Thanks for posting in our business forum.

Its-A-Trap wrote

  @jake-at-home , Quite possible we are neighbors!

 

Quick update, with a few small caveats...

• My setup is slightly different than yours in that i have Two Internet connections.  I added a XFinity cable modem as a backup when i thought that the issue was on the WaveG Side. I have been experimenting with maintaining both and with having only WaveG connected
• I have not yet set up the testing infrastructure to directly observe the mac address leaking, and am thus relying on observing my port being shut down, so the testing takes quite some time...

 

I need to do further testing, however at this point i am fairly confident that the issue is at least partially associated with the configuration of Hardware Offload.  I am suspicious if there are either potentially multiple initialization code paths that results in different configurations, or if the IPs have some order dependent initialization requirements not being fully respected.

 

• Previously, My port would be shut off for approximately 11 minutes each time this defensive measure was triggered by the upstream switch.  I would encounter this 11 minute gap every 20-30 minutes.
• After Disabling Hardware Offload (With only WaveG Active) my connection was stable for over 2 hours
• After Re-enabling Hardware Offload (with only WaveG Active) my connection continued to remain stable for over 2 hours.
• I then took a risk and re-enabled the second WAN/Lan port for my backup internet connection, after the system was re-provisioned, my system once again exhibited the disconnect behavior.  This behavior did however seem to continue even when i disabled hardware offload (Confused on this one, and need to dig in more...)
• I was able to restore long term stability by unplugging my backup internet connection and disabling Hardware offload 

 

I would like to get to a true root cause as I am sure that it will come back and bite me again soon, as if it is an artifact of the different initialization code paths or some other order of operations. I expect that this is not yet resolved.  Also, I do not currently have a stable configuration that supports my second WAN.

 

In order to really make progress, i likely need to invest the time to setup an upstream switch to enable mirroring and capture so i can have a more reliable signal than waiting for my port to get turned off...  that may be next weekend...

 

For both of you, please prepare a diagram of your current network connection.

I would require a traditional way of configuring your network on the Internet--WAN--LAN. If you have anything in between or double-NAT, please remove them before we move on this case.

As this goes on, I need you to reproduce this issue and Wireshark in a controlled environment instead of an unconventional setup. I will not reply to your message if this is not reproduced in a controlled environment as I cannot help you locate the problem.

Will walk you through this, dig out what's wrong and give this problem a conclusion.

A ticket will be created for each of you.

The port mirroring requires you to perform Wireshark capture. The file should capture and contain the leaked MAC address you mentioned or you see in the log.

Things I need:

1. A conventional diagram ruling out any local devices connected to the WAN.

2. Port mirroring and Wireshark from the WAN.

3. Log of your ISP modem or how you find out this MAC address leaked with evidence.

I need to know what you know about your network. Or it is hard to find out the reason why. And we probably need a real-time remote if this does not go well.

Reply to the ticket I created for you with the information mentioned.

Hi @Its-A-Trap 

Thank you so much for taking the time to post the issue on TP-Link community!

To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID240619566, please check your email box and ensure the support email is well received. Thanks!

Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.

Many thanks for your great cooperation and patience!

Hi @jake-at-home 

Thank you so much for taking the time to post the issue on TP-Link community!

To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID240619582, please check your email box and ensure the support email is well received. Thanks!

Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.

Many thanks for your great cooperation and patience!