MR70 MS Teams / ZOOM performance issue very choppy

atari8000

Aspirant

Jan 30, 2025

cable modem (147.xxx.xxx.xxx)
PFSENSE on mini PC with 5 ports

port 0 - cable modem

port 1 - 192.168.1.x - serving MR 70 (wireless name AREA1)

port 2 - 192.168.2.x - service MR 70 (wireless name AREA2)

--MR 70 on port 2 has an ethernet cable from it to TP-LINK Deco s4 also in access point mode

----TP-LINK (wireless name AREA-TP and AREA-TP-GUEST) also using 192.168.2.x

DHCP - I assign all IP addresses based on MAC address

Update:
I did get choppy ZOOM on TP-LInk, but not as severe.

I found a zillion articles that teams/zoom totally clobber MESH networks

But I found (but didn't save) a reference that someone using TP-LINK did not have choppyness on TP-LINK guest, which I did not test yet with teams/zoom

I enabled GUEST on Netgear and connected to it

I found I could ping anything on its subnet (research show netgear in AP mode has this issue)

I then connected to AREA-TP-GUEST, and I did get same IP address but I could not ping anything on the subnet

So I am wondering if teams/zoom is, for whatever reason, is doing some full network sweep and saturating the network (which makes some sense that CTS/RTS reduced to a lower number helps...but I don't know for certain).
If the saturation theory is true, then the contained TP link guest, which cannot ping anything on the subnet) wont flood.

This would stink because I would need to either keep TP-LINK for my work connection or watch episodes of McGyver and find the one where he sets up one IP Address to a subnet of /32 and has ability to get to gateway/dns and the internet

michaelkenward
Guru - Experienced User
Jan 30, 2025
atari8000 wrote:

cable modem (147.xxx.xxx.xxx)
PFSENSE on mini PC with 5 ports

port 0 - cable modem

port 1 - 192.168.1.x - serving MR 70 (wireless name AREA1)

port 2 - 192.168.2.x - service MR 70 (wireless name AREA2)

--MR 70 on port 2 has an ethernet cable from it to TP-LINK Deco s4 also in access point mode

----TP-LINK (wireless name AREA-TP and AREA-TP-GUEST) also using 192.168.2.x

Looks like complex mishmash. Two routers on one modem? An invitation to trouble.

Two routers on your network can cause headaches. For example, you can end up with local problems with addresses on your network. Among other things, the other router can misdirect traffic to addresses that the Netgear router usually handles, such as routerlogin.net or the usual default IP address for a router, 192.168.1.1.

This explains some of the other drawbacks.

What is Double NAT? | Answer | NETGEAR Support

It is often easier to use just one router and then to set up the second router as a wifi access point (AP) with a wired connection to the main router. Netgear advises this, as does just about every site you will visit.

How do I change my NETGEAR router to AP mode? | Answer | NETGEAR Support

But that has its own drawbacks:

Disabled Features on the Router when set to AP Mode | Answer | NETGEAR Support

If it is just a separate wifi network that you want, one for IoT and the other for "cell and computers", then you could see if putting the second MR70 into AP mode would work.

There are alternatives, but that is best left until we have a clearer idea of the ultimate goal on this network.

Just another user with time on their hands.
- atari8000
  Aspirant
  Jan 30, 2025
  It may seem like a complex jumble, but it really isn't. This setup has been effective for years. The concept is that since I have many smart devices (IoT) connected to my network, which also includes my PC that contains financial information, passwords, and other sensitive data, it’s only a matter of time before someone hacks the firmware of a smart bulb or a smart switch. This could potentially create a backdoor into my home network. So I decided to make 2 networks in my home. One is for my personal stuff, and the other for everything else. If some uses my kitchen bulb as a backdoor, they would be contained in IoT network.... Well that's the goal
  With me so far?
  So I got this mini PC and installed PF Sense, which allows me to create and control subnet segments. I have AREA1 (192.168.1.x/23) and AREA2 (192.168.2.x/24), meaning my personal stuff can talk to IoT stuff, but IoT cannot talk to personal stuff.
  Goal achieved but with TP-LINK
  TP-LINK doesn't give you the control that Netgear does and requires an app on the phone. So I get NetGear MR70. Everything works perfectly and I can change channels (my primary reason for buying new routers). Torrents, streaming, Wifi Cell calls, IoT control, Alexa , blah blah blah
  It is only Teams and Zoom that it gets choppy on Netgear. As mentioned earlier, I hardwired my old TP router (NG eithernet port to TP ethernet port both in AP mode) and enabled TP GUEST. I connected to it and guess what didn't happen?
  No choppiness I will do more testing, I don't think "double nat" is my issue.
  - michaelkenward
    Guru - Experienced User
    Jan 31, 2025
    While I can understand your paranoia, I am not convinced that your issues with Teams have nothing to do with the design of your network.
    
    If you are serious about security, Netgear provides Armor subscriptions. I currently have a one year trial. I can hardly move without it trying to "protect" me.
    
    I also have two routers running as routers on my network. But the second router operates as the DMZ for the first router. This allows me to operate two separate networks with different core IP addresses.
    
    I would try so simplify the network as much as possible. As it is, I doubt if anyone is going to be able to diagnose what is happening.
    
    That none of the real experts here has stepped in to fill the gaps in my understanding suggests that there isn't a neat answer to your problems.
    
    Just another user with time on their hands.

Forum Discussion

MR70 MS Teams / ZOOM performance issue very choppy