NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
IP Passthrough with AT&&& Gigapower Pace 5268 to Netgear AC1900 r7000
AT&T UVERSE gigapower has a recommended way to "pass through" IP using what they describe as "dmz plus". There is frighteningly little one can manipulate on the AT&T Pace device. "The device that you...
This answer applies to any router.
AT&T tech support gives out faulty/incomplete information about IP Passthrough using the PACE 5268.
To use "IP Passthrough" :
If you leave the Pace 5268 with its default setting using 192.168.0.x. with a subnet mask of 255.x.x.x. you must switch your own router to 10.x.x.x or 172.x.x.x for "IP Passthrough" to work with your router. Keep the subnet mask the same.
I do not know know technically why the IP address conflict occurs because AT&T does not publish a single technical document on "IP Passthrough" as of this posting. But AT&T numerous times told me it was okay to use 192.168.10.X for my router. I even paid them "extra" for this faulty, wrong, incorrect technical support. They are just reading from scripts. And their go to answer is to blame "the router."
I just switched my router to the other Private IP adress ranges out of desperation at having tried everything else. We should all refuse to hand our personal data transfer over to an AT&T device about which there is little or no information -- and through which new Trump adminstration FCC will make it legal for AT&T to sell any information passing through that PACE 5268.
I would love it if an engineer would weigh in on how/why this conflict is created. The drop in bandwidth is extemely odd.
Just got gigapower installed, with a Pace 5268, and i have it DMZ+ to my pfsense box, and get sevre bottlenecking
If I go straight off the Pace, it's unthrottled. Very odd.
This answer applies to any router.
AT&T tech support gives out faulty/incomplete information about IP Passthrough using the PACE 5268.
To use "IP Passthrough" :
If you leave the Pace 5268 with its default setting using 192.168.0.x. with a subnet mask of 255.x.x.x. you must switch your own router to 10.x.x.x or 172.x.x.x for "IP Passthrough" to work with your router. Keep the subnet mask the same.
I do not know know technically why the IP address conflict occurs because AT&T does not publish a single technical document on "IP Passthrough" as of this posting. But AT&T numerous times told me it was okay to use 192.168.10.X for my router. I even paid them "extra" for this faulty, wrong, incorrect technical support. They are just reading from scripts. And their go to answer is to blame "the router."
I just switched my router to the other Private IP adress ranges out of desperation at having tried everything else. We should all refuse to hand our personal data transfer over to an AT&T device about which there is little or no information -- and through which new Trump adminstration FCC will make it legal for AT&T to sell any information passing through that PACE 5268.
I would love it if an engineer would weigh in on how/why this conflict is created. The drop in bandwidth is extemely odd.
i had the same issues with mine a while back, after tinkering with it, i have been able to get 900+ up and download.
Couple questions about your 5268 and netgear:
What version/software is 5268 on? should appear on the broadband page.
do you show ipv6 on or off? if its on does it show 6rd, or duel stack?
have you adjusted any of the firewall advanced configuration?
What firmware is on your netgear?
Is qos enabled or disabled?
for reference this is what i 'm getting using gigapower and the r7000.