#uverse — Public Fediverse posts

Just spent almost an hour on the phone with an #ATT #Uverse Broadband Engineering Lead.

Takeaways:

1) There's an ARP SPAM issue (that my L3 switch is suppressing) that the BGW320 has for all folks with static IPs where every millisecond it's asking for MACs of IPs without a current assignment, nonstop. It affects those with larger IP subnets more. I have a /25, so I get slammed. It's been there for...pretty much forever.

2) FW 6.30.5 fixes an issue where UDP sessions remained open longer than necessary, which would fill up the internal NAT Table (even with statics), @ 8192 states, and cause high CPU load, 4-digit latency, and eventually full on packet drops (as Tiggi.es was experiencing) until a RG reboot.

3) FW 6.30.5 did NOT up the state count to an intended 32767, but their tech lead changed it for my own RG

4) ATT is going to be rolling out 10GBit service in my area next year, which we'll be moving to. I'll be getting their new BGW620 in a month or so with a 10GBe port on it in preparation. It also has Wifi7, but I'm disabling that since I've got a Wifi7 mesh already.

5) ATT has an almost impenetrable firewall between their customer disservice dept and engineering that I was only able to get around using my Worksona and LinkedIn and customers should never have to go through what I went through. This is actually getting escalated.

6) My Central Office is having issues that limit my up speed to 2.5-3GBit. They should have this resolved by early next week.

I'm a plucky l'il burr.

Just spent almost an hour on the phone with an #ATT #Uverse Broadband Engineering Lead.

Takeaways:

1) There's an ARP SPAM issue (that my L3 switch is suppressing) that the BGW320 has for all folks with static IPs where every millisecond it's asking for MACs of IPs without a current assignment, nonstop. It affects those with larger IP subnets more. I have a /25, so I get slammed. It's been there for...pretty much forever.

2) FW 6.30.5 fixes an issue where UDP sessions remained open longer than necessary, which would fill up the internal NAT Table (even with statics), @ 8192 states, and cause high CPU load, 4-digit latency, and eventually full on packet drops (as Tiggi.es was experiencing) until a RG reboot.

3) FW 6.30.5 did NOT up the state count to an intended 32767, but their tech lead changed it for my own RG

4) ATT is going to be rolling out 10GBit service in my area next year, which we'll be moving to. I'll be getting their new BGW620 in a month or so with a 10GBe port on it in preparation. It also has Wifi7, but I'm disabling that since I've got a Wifi7 mesh already.

5) ATT has an almost impenetrable firewall between their customer disservice dept and engineering that I was only able to get around using my Worksona and LinkedIn and customers should never have to go through what I went through. This is actually getting escalated.

6) My Central Office is having issues that limit my up speed to 2.5-3GBit. They should have this resolved by early next week.

I'm a plucky l'il burr.

Just spent almost an hour on the phone with an #ATT #Uverse Broadband Engineering Lead.

Takeaways:

1) There's an ARP SPAM issue (that my L3 switch is suppressing) that the BGW320 has for all folks with static IPs where every millisecond it's asking for MACs of IPs without a current assignment, nonstop. It affects those with larger IP subnets more. I have a /25, so I get slammed. It's been there for...pretty much forever.

2) FW 6.30.5 fixes an issue where UDP sessions remained open longer than necessary, which would fill up the internal NAT Table (even with statics), @ 8192 states, and cause high CPU load, 4-digit latency, and eventually full on packet drops (as Tiggi.es was experiencing) until a RG reboot.

3) FW 6.30.5 did NOT up the state count to an intended 32767, but their tech lead changed it for my own RG

4) ATT is going to be rolling out 10GBit service in my area next year, which we'll be moving to. I'll be getting their new BGW620 in a month or so with a 10GBe port on it in preparation. It also has Wifi7, but I'm disabling that since I've got a Wifi7 mesh already.

5) ATT has an almost impenetrable firewall between their customer disservice dept and engineering that I was only able to get around using my Worksona and LinkedIn and customers should never have to go through what I went through. This is actually getting escalated.

6) My Central Office is having issues that limit my up speed to 2.5-3GBit. They should have this resolved by early next week.

I'm a plucky l'il burr.

Just spent almost an hour on the phone with an #ATT #Uverse Broadband Engineering Lead.

Takeaways:

1) There's an ARP SPAM issue (that my L3 switch is suppressing) that the BGW320 has for all folks with static IPs where every millisecond it's asking for MACs of IPs without a current assignment, nonstop. It affects those with larger IP subnets more. I have a /25, so I get slammed. It's been there for...pretty much forever.

2) FW 6.30.5 fixes an issue where UDP sessions remained open longer than necessary, which would fill up the internal NAT Table (even with statics), @ 8192 states, and cause high CPU load, 4-digit latency, and eventually full on packet drops (as Tiggi.es was experiencing) until a RG reboot.

3) FW 6.30.5 did NOT up the state count to an intended 32767, but their tech lead changed it for my own RG

4) ATT is going to be rolling out 10GBit service in my area next year, which we'll be moving to. I'll be getting their new BGW620 in a month or so with a 10GBe port on it in preparation. It also has Wifi7, but I'm disabling that since I've got a Wifi7 mesh already.

5) ATT has an almost impenetrable firewall between their customer disservice dept and engineering that I was only able to get around using my Worksona and LinkedIn and customers should never have to go through what I went through. This is actually getting escalated.

6) My Central Office is having issues that limit my up speed to 2.5-3GBit. They should have this resolved by early next week.

I'm a plucky l'il burr.

Just spent almost an hour on the phone with an #ATT #Uverse Broadband Engineering Lead.

Takeaways:

1) There's an ARP SPAM issue (that my L3 switch is suppressing) that the BGW320 has for all folks with static IPs where every millisecond it's asking for MACs of IPs without a current assignment, nonstop. It affects those with larger IP subnets more. I have a /25, so I get slammed. It's been there for...pretty much forever.

2) FW 6.30.5 fixes an issue where UDP sessions remained open longer than necessary, which would fill up the internal NAT Table (even with statics), @ 8192 states, and cause high CPU load, 4-digit latency, and eventually full on packet drops (as Tiggi.es was experiencing) until a RG reboot.

3) FW 6.30.5 did NOT up the state count to an intended 32767, but their tech lead changed it for my own RG

4) ATT is going to be rolling out 10GBit service in my area next year, which we'll be moving to. I'll be getting their new BGW620 in a month or so with a 10GBe port on it in preparation. It also has Wifi7, but I'm disabling that since I've got a Wifi7 mesh already.

5) ATT has an almost impenetrable firewall between their customer disservice dept and engineering that I was only able to get around using my Worksona and LinkedIn and customers should never have to go through what I went through. This is actually getting escalated.

6) My Central Office is having issues that limit my up speed to 2.5-3GBit. They should have this resolved by early next week.

I'm a plucky l'il burr.