In reply to a post by mr_bean:

Anyway the current claim is that it could take 48 hours to activate so I have to wait it out and see if it springs into life at some point - then bend thir ear again late Weds or Thurs if it does not go live by then.

24 hours have passed - no change including the fact that the eero will not connect either.

Will see what tomorrow brings.

Maybe try calling Cityfibre directly to get some clarity? They should at least be able to tell you if the issue is at their end or at Talktalks. Yeah I know they're the network wholesaler but on the few times i've called them directly they've been very helpful so pretty sure they won't fob you off.

You can also ask them whether the VLAN 911 tagging applies to all ISPs using their network or only to some or whether some ISPs like Talktalk don't even use VLAN tagging.

Edited by Skardu (Tue 18-Jan-22 21:27:43)

In reply to a post by Skardu:

Maybe try calling Cityfibre directly to get some clarity? They should at least be able to tell you if the issue is at their end or at Talktalks. Yeah I know they're the network wholesaler but on the few times i've called them directly they've been very helpful so pretty sure they won't fob you off.

Anything's an option at this point.

TT keep saying that they can see a problem, for now I'll badger them as I'm not CF's customer - but I might try it if TT can't resolve the issue.

You can also ask them whether the VLAN 911 tagging applies to all ISPs using their network or only to some or whether some ISPs like Talktalk don't even use VLAN tagging.

I would hope that *someone* in their tech support knew - the installation guy did not have a clue.

His ability to configure a router seemed to boil down to "usually there's a QR code or something".

In developments which will surprise no one, still no internet connection.

Will try the Future Fibre team one more time tomorrow - after that I think it will need to be the complaints team.

Finally, yes!!!

Apparently CF asked for extra information on Monday at 5:30PM but the guy I spoke to was no longer there to respond - nor was he in Tues, Weds or yesterday so it just sat there until I phoned today.

But it does seem to be up and running. Speeds are meh, but I'm probably bottlenecked by the ancient Buffalo AP and even more ancient laptop that I've been using for testing. I'll configure something faster/more modern later on.

For confirmation - DHCP, no VLAN tag. Might try 911 later just to see if the tag actually makes a difference.

Nice one. Pleased to hear it's working.

If you put a Vlan tag on the router it will not get any better in fact it will just stop working, there is no Vlan ID on the customer side of the ONT.

In reply to a post by Realalemadrid:

If you put a Vlan tag on the router it will not get any better in fact it will just stop working, there is no Vlan ID on the customer side of the ONT.

I think you mis-parsed my sentence - although I agree it was ambiguous.

There are several places on-line which claim that TT over CityFibre needs VLAN tagging - typically VLAN 911, TT themselves told me that VLAN 981 was the right one.

I simply wondered whether the VLAN tag is ignored.

You previously stated "For confirmation - DHCP, no VLAN tag."

So if that works I would conclude that it is the correct configuration, so I fail to understand why you would want to try a Vlan ID on the router WAN connection. If it is not required why add it.

Many GEA and Leased Line services use Vlan Tagging, in some cases the VLAN id is passed through to the end users equipment so the router has to be configured to use it. Openreach FTTC and FTTP use a Vlan ID but it is stripped out by the modem or ONT and does not get to the user's router.

It would seem that your connection falls into this latter category.

Feel free to try adding a Vlan ID but I don't believe it will help you in any way,

As for TT giving out technical information that is either incorrect or irrelevant, I'm not surprised.

In reply to a post by Realalemadrid:

You previously stated "For confirmation - DHCP, no VLAN tag."

So if that works I would conclude that it is the correct configuration, so I fail to understand why you would want to try a Vlan ID on the router WAN connection. If it is not required why add it.

Many GEA and Leased Line services use Vlan Tagging, in some cases the VLAN id is passed through to the end users equipment so the router has to be configured to use it. Openreach FTTC and FTTP use a Vlan ID but it is stripped out by the modem or ONT and does not get to the user's router.

It would seem that your connection falls into this latter category.

Yes, I know all that.

Feel free to try adding a Vlan ID but I don't believe it will help you in any way,

I'm not expecting it to "help" my connection. It will either stop it working or have no effect, as you say.

As I said - you seem to have taken "make any difference" to mean "make my slow connection better"; I did not mean that.

It was a question of reconciling DHCP/Untagged frames with reports saying "use VLAN 911" and, indeed, advice to use VLAN 981 - were these wrong, perhaps assuming that since other ISPs need tagged frames then TT's service would also. Were they correct in that tagged frames work, but are unneeded or is it possible that TT have switched to untagged frames for newer installs?

As for TT giving out technical information that is either incorrect or irrelevant, I'm not surprised.

Me neither, to be honest.

As for not hitting the advertised speed - as I said, that was down to using an AP which has a single core 680MHz CPU - I was only using that because it is fairly small and convenient for testing; I've swapped it for something a bit more suited to a 500Mbps link and speed test last night showed 270/330Mbps. Even then I suspect the AP is the bottleneck but can't terminate the connection in faster kit without a bit of domestic network rejiggery, which will have to wait.

Edited by mr_bean (Fri 21-Jan-22 13:00:55)