In reply to a post by ferretuk:

My very first contribution to this thread suggested that you assign a static address to your router. Subsequent posts have tried to explain why and to correct some if your apparent misunderstandings.

If this has appeared to be a rigmarole then I've failed and, frankly, I won't bother again!

My router gets a 2001:8B0:1111... address on it's WAN port and I've manually configured the LAN port to advertise my /64 prefix. I've statically configured the router LAN to be <My Prefix>::1

I think you can do the same in Network Setting>Home Netwok>LAN Setup (if I read the manual correctly?) Set LAN IPv6 Address to Static and enter an address within your allocation i.e Prefix::1 and then put your prefix address and length in the ULA IPv6 Address Setup boxes.

As I hinted, I'm no expert, and this may be nonsense!

It is.

Better than watching the fools lantern this !

Oh I'm still messing with the BQM . Having got it completely independent of the LAN I want it cleaner still. Which is wjy the New BQM in my sig is temporarily also disabled.

Latest BQM now in sig, previous one disabled, previously disabled one deleted from sig but still available from earlier links. For now. In case I go back to it.

I really have no idea why you've taken offence at my attempts to help. Eventually you've entered a static address for your router LAN port as suggested. In my case I used <My Prefix>::1, you've chosen a much more complicated address.*

The section about then entering the prefix and subnet size was taken directly from the manual for your router. If this stage wasn't necessary then take it up with Zyxel!

At the end of the day I tried to help but your reaction really makes me wonder why I bothered. For the record I never questioned the working of your BQM - I merely pointed out that you set it up to ping your PC but then configured the router to be on the same address (creating a duplicate IP). Hopefully your PC moved to a different address so this configuration error didn't cause a problem...

*Actually, after re-reading the thread I'm not actually sure which address you have used as you still seem to be confused between the AAISP 2001:8b0:1111... address for the WAN side of your router and your LAN side /64 which will be 2001.8b0:???:????... but hey ho!

Edited by ferretuk (Sun 04-Dec-16 23:27:53)

Meanwhile my flake AA supplied router refuses to work behind the OR router. Set to Ethernet Wan but refuses to access the internet. So angrily pulled the modem to router Ethernet and stuffed the DSL line back into the zyXel and instant internet with the router still set to Ethernet Wan! Left it that way and behaving since. This router really is a bag of snakes. Even if it wasn't' the IPv6 won't work with any router. Tomorrow will be interesting as I see my fault likely to be closed at lunchtime.

Because, perhaps unintentionally, you have seemed to preach, and your solution though a decent workaround is not the correct one.

1) Your first post in this thread (Sat 26-Nov-16 19:51:38) was extremely out of kilter with the Subject and everything I had posted in the OP and replies to others.

2) Your explanations are so convoluted they are impossible to follow unless the person reading already knows the answer.

3) You describe having done various things in your LAN setup in order to ping a LAN address.You insist I should be doing things in the LAN setup of my router "Network Setting>Home Netwok>LAN Setup (if I read the manual correctly?)". (Fri 02-Dec-16 10:42:41)

At no point have I done anything at all in the "Home Network" page. I want my router pinged on a WAN address - but using the ZyXel in the desired single-box setup it is not visible.

5) Your post in MCM/s thread again goes on and on about the LAN. In reply to that, yes - I expect the WAN side to be static. Which you yourself have discovered it is.

6) Again in this thread

Hope you get it sorted and that I haven't confused things.

I don't think you need to (or should) be making changes on the WAN side. It's the LAN that's yours, hence suggesting you statically configure the router LAN interface. Remember that all IPv6 addresses are public so pinging the LAN side (or even a statically configured device on your network) with the BQM gives the same information as pinging the WAN interface.

I completely disagree.

Yes, one can mess around as you have done, and I genuinely admire your arriving at the solution you have, but it is not the best solution. It is a router WAN address issue. With your setup you could see what it is. With the one-box setup I couldn't (so far as I know).

****************
It is clear once you get to the right place in the AA help pages that there is a static WAN address. Assuming I have converted my static IPv4 correctly to give the final /32 then the final BQM in my sig is now using that. It is even possible that because of that I can reset the static setting in my WAN setup to obtain an IP address automatically. Because it should be the fixed one that I have worked out.

Note I did thank you some time ago for giving me an idea how to achieve what I wanted - I just couldn't accept your solution and still don't. Even though it works for you and would work for me. So yes, you helped and I thank you for that.

When I try going back to automatic IPv6 acquisition, if the BQM continues to work then the only changes made on my router since delivery from AA will be setting it to dual-stack modem/router mode rather than WAN-fed IPv4 router. All I needed was the static IPv6 address.

Edited by RobertoS (Mon 05-Dec-16 00:03:00)

Ah, finally the penny drops! Your posts about entering the IP address obtained by your PC into the router config led me to think that you were setting it in the network setting I pointed you at, not in the WAN section of the router Further references to calculating addresses within your /64 just compounded the issue!

You are absolutely correct that pinging the WAN address is more elegant and I could change my BQM to do this instead. At the point I set mine up I did not know that the WAN address was static. The only caveat to this is that should AAISP change the address scheme for some reason (and I can't see why they would!) it will break of course.

There *should* be no need for you to change the router from automatic address setting on the WAN as the IP address allocated is per the description on the support site. In fact, if it does stop working you must have calculated the address incorrectly but I suspect that this won't be the case as I think you'd lose IPv6 connectivity as your /64 wouldn't be routed to you if it were wrong? In any event, as with IPv4, statically assigning the WAN address is a 'bad thing'

[Edit] I see from info in another thread more info regarding the bug with the Zyxel router you mentioned in your first post affecting possible intermittent loss of IPv6 with this router. In this case, AAISP do suggest making the WAN address statis as a workaround.

Edited by ferretuk (Mon 05-Dec-16 10:05:55)

Just to wind this up really, and thanks to all for their advice. It all added up to my finding the solution.

The WAN IPv6 address is dynamic one from the router point of view, but fixed by the ISP DHCP. (As per Plusnet and AAISP "static" IPv4 addresses). Basically it is nothing at all to do with the customer's allocated /48 and /64 IPv6 addresses.

It is a fixed, the same for all customers, /32 prefix followed by the last 32 bits being their "static" IPv4 address for that line converted to hex. There is no need to set this in the router. Just obtain from the ISP as normal.

Regarding my main question - a combined mode/router to suit, in the end I plumped for a Billion 8800NL R2, following some disastrous experiments with various combinations including a new Draytek Vigor 130 feeding (at different times) the ZyXel set in router mode and my Asus RT-N66U.

That experimenting knocked me down, in three steps, to a 45Mbps banding from my original 60Mbps banding.

The final drop in fact occurred about 10am the morning after I installed the Billion. That held that night, and the following night rose straight back up to 55Mbps banding. Where it has now been ever since. And no doubt will be for some time. I did one power cycle a few days ago, just to see what happened. Nothing changed.

> xdslctl info --show
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 14451 Kbps, Downstream rate = 64496 Kbps
Bearer: 0, Upstream rate = 14466 Kbps, Downstream rate = 54999 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 9.3 5.9
Attn(dB): 18.9 0.0
Pwr(dBm): 13.6 7.4

VDSL2 framing
Bearer 0
MSGc: -6 26
B: 227 237
M: 1 1
T: 0 64
R: 12 16
S: 0.1319 0.5233
L: 14562 3883
D: 4 1
I: 240 127
N: 240 254
Q: 4 0
V: 0 0
RxQueue: 132 0
TxQueue: 33 0
G.INP Framing: 18 0
G.INP lookback: 31 0
RRC bits: 0 24
Bearer 1
MSGc: 122 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 8.0000 0.0000
L: 32 0
D: 1 0
I: 32 0
N: 32 0
Q: 0 0
V: 0 0
RxQueue: 0 0
TxQueue: 0 0
G.INP Framing: 0 0
G.INP lookback: 0 0
RRC bits: 0 0

Counters
Bearer 0
OHF: 0 190450
OHFErr: 0 20
RS: 850535572 4014547
RSCorr: 238903 283
RSUnCorr: 0 0
Bearer 1
OHF: 28297213 0
OHFErr: 0 0
RS: 226377214 0
RSCorr: 0 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 131849514 0
rtx_c: 12090 0
rtx_uc: 0 0

G.INP Counters
LEFTRS: 5 0
minEFTR: 54996 0
errFreeBits: 381343978 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 829311163 0
Data Cells: 63174695 0
Drop Cells: 0
Bit Errors: 0 0

Bearer 1
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 0 0
Data Cells: 0 0
Drop Cells: 0
Bit Errors: 0 0

ES: 0 19
SES: 0 0
UAS: 28 28
AS: 454581

Bearer 0
INP: 51.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 8.40
OR: 0.01 30.45
AgR: 55120.28 14496.97

Bearer 1
INP: 2.00 0.00
INPRein: 2.00 0.00
delay: 0 0
PER: 16.06 0.01
OR: 63.75 0.01
AgR: 63.75 0.01

Bitswap: 210766/218860 970/973

Edited by RobertoS (Tue 10-Jan-17 17:49:31)

On my Asus RT-AC68U running Merlin, ( not an option on all in one units) I never even noticed IPV6 kick in with BT infinity it was seamless.

I agree PFsense is a great way to go for the ultimate in responsiveness and for a fully fire walled connection going forward especially when 100mbps+ is the norm. but it's ether impractical or too expensive to have a mini pc in a nice router sized box. and your always likely to be running a modem, and maybe a 3rd box for the best wireless performance with this. it's just too impractical for most. Hopefully good 1 box solutions will come when 300mbps + connections become the norm.

For others that haven't found their solution yet, the main this is when your experimenting keep using the same modem plugged in and and keeping the DSL sync, and only play with the router. only switch to a combined modem router when you happy after testing it using Ethernet wan to that modem that never needed to resync. That way you can avoid DLM screwing with your connection. 1 or 2 retrains a day shouldn't have too much impact but if you have alot of noise in your area it may just trigger DLM intervention, it's safer to avoid it if you can.

On an ECI cab, i never used to have issue with broadcom modems, I'm now getting enough errors that a broadcom modem will result in interleaving and much slower speeds within a 2 weeks. I need a lantiq based modem like the ECI-r openreach modem and the lower error counts to keep the max speeds and stay interleave free.