@Burakkucat - I did indeed do just that, I firstly uploaded your config file. But I think I may have made a mess of something somehow, maybe I had to do some other kind of 'commit' operation afterwards, because the ATM-related settings didn't look correct to me and did not look like your screenshots. VPI / VCI was expected to be 0 / 38 and if memory serves the web UI showed 35 and was not showing up as pure bridge, so I must have screwed something up. I discovered belatedly that I had to keep hitting “save all” or similar after making changes as well as some hitting some other UI control ('submit' or 'enter' or some such) in settings pages, so had to hit two different kinds of 'commit'. Maybe that is where I went wrong.
But anyway, I went through the entire web UI from end to end and compared what I actually had with the complete selection of screenshots that Burakkucat had provided.
Kitizens, Burakkucat's generous help with this project has been above and beyond the call. His claws were worn down taking dozens of screenshots and saving a config file for me.
I need to try again and recheck that the settings are exactly as Burakkucat provided, with the possible exception of the RFC2684/LLC thing if it turns out that I really have to do this and I am not just being pessimistic. Can anyone confirm that PPPoEoA VC-MUX doesn't work with 21CN by consulting the great times if standard lore? (21CN as in my case. Would be interesting to know about 20CN too.)
Perhaps someone else who is on PPPoEoA (i.e. not on VDSL2) could check the VC-MUX vs LLC thing quickly for me? There are at least three tests - BT 20CN, BT 21CN and various LLU ADSL options. I'm assuming that this only depends on the DSLAM? Is that correct? - and not on anything further upstream as well? But I don't know why I am thinking that, who knows.
I will try it myself when I can recruit my cheerful volunteer hopefully tomorrow. I need a means of paying my test assistant suitably for her modem-swapping efforts.
I can set the DLinks to VC-MUX if I end up going back to them. I didn't realise that it would be such a big deal in terms of efficiency, I had never done the arithmetic before. (See the Wikipedia article on PPPoE, the section on PPPoEoA overheads over DSL, will need to adjust the figure given for RFC2684 LLC overhead and change it from 10 bytes to 2 bytes [I think] for VC-MUX-bridged-PDUs.)
I also ought to retest with just the one new modem going in case of some screw-up of some kind and anyway it will be a lot easier to see what is going on.
And I ought to see what is going on with MTU. I am using approximately the same huge ~9000 byte MTU that Burakkucat recommended, but not exactly the same value because according to the modem UI the specified value of 9216 was reduced to a lower 'current value'. AA and the Firebrick will limit it to 1500 I suspect, and in any case I can't really play with this until I get rid of the mixture of modems with different MTUs which of course would be a nightmare. I ought to check that some mixed MTU thing is not the source of the performance hell, that would be fixed by testing the Huawei on its own. And of course I could clamp the Huawei at 1500 while it has to play nicely alongside its DLink brethren if this does turn out to be an issue.
So possible causes of performance hell:
- 3dB SNRM - just way too aggressive, huge number of initial HECs
- MTU mixture
- My mistake in my config
- If I get the config exactly the same as Burakkucat had it, is that guaranteed to be a good thing (DSLAMs)? On the legs of my grandmother.
Have I forgotten anything?