I can disable it at my end in the modem’s web config ui. The exchange has to be Broadcom and then I presume, but have no way of testing, that the exchange DSLAM always uses PhyR if you’ve got it and have enabled it. I’ve just had a look at the modem and I see that you can separately enable/disable PhyR in either direction, upstream or downstream. So that must mean that there is such a thing as PhyR upstream. I didn’t know that. I have both upstream and downstream ticked as well as a whole load of other wishes to Santa that are never going to happen, such as SRA, and PTM over ADSL2. I can long for PTM, I know that ADSL2 supports it, wish the DSLAM would, they’ve already written all the PTM code, for VDSL2. Following Burakkucat’s tip, I have selected a restriction to ADSL2 only; ie no ADSL2+.
[Actually, SRA would be a bit dodgy with bonded lines I think, because I have three IP-bonded links and the Firebrick needs to know what the upstream speed of each pipe is, in order to get the correct fraction of the upstream traffic sent to each of the links. Currently it gets told this info at PPP-connect time. If you had SRA, as in G.Fast, there would have to be some other protocol for dynamically updating the Firebrick’s egress speeds per link; maybe some PPP trickery if you’re using PPP, and if not, then who knows.]
No upstream PhyR unfortunately; perhaps that’s to do with Broadcom? Perhaps it’s to do with ADSL2 ? It would be incredibly valuable to me. I think perhaps Broadcom thought about downstream-only, because there was no market for upstream improvement this maybe being because they were thinking about the use case of IP TV which is a downstream-only thing. Broadcom mentions IP TV in the rationale section of a document of theirs about PhyR. They said they would need 9dB downstream SNRM routinely enforced to make IP TV work without L2 ReTX, as the link has to be completely reliable; in any case how would they and ISPs enforce such a margin? And what about SRA? Maybe making it work in two directions would have been a software nightmare? Does the G.INP protocol allow bidirectional ReTX? Thinking about whether ADSL2 might frustrate the possibility of bidirectional implementation, I think PhyR must be independent of ADSL2 because Broadcom surely just implement it over the top, as a higher layer (seeing as it was, I presume, developed independently), without needing to be constrained by anything particular in ADSL2? I certainly could do so, and have done the like, in the distant past.
I wonder why isn’t PhyR happening then on the upstream? Can anyone find out for me?