Future Fibre fail - can anyone confirm VLAN & protocol

I _knew_ going with TT just because they were the cheaper of the two ISPs currently signed up to CityFibre in my area risked going pear shaped - I was too optimistic I suppose.

Install day was today - all lights on the ONT so optical path presumably OK, installers (Kelly) seemed to have zero detailed technical knowledge of the service - I guess their training is strictly join the dots.

Can't get broadband up & running. OK I'm making it harder for myself in not wanting to use the bundled router/mesh thingy - any router/AP which needs an online account to be "activated" is bad news in my book.

From Googling it seems that DHCP and VLAN 101 or 911 should be the magic sauce but no dice.

Phone tech support (an experience in itself) but chocolate teapot territory - not least because they can't find my account. I don't have the number because TT haven't sent me an account number (so, also, can't register with the TT customer account management either). I suspect it's not working because it hasn't been activated.

Rant over - the actual question:

Has anyone got a 3rd party router running on TT/CityFiber "Fibre 500". If so what are the WAN settings?

To follow up on the above:

1) definitely a mistake speaking to the regular support team, I spoke to the Future Fibre team today and they were much more helpful and clued up.

2) It looks like the WAN parameters might be DHCP and VLAN 981

3) Chances are the service wasn't activated yesterday - disappointing that the dots weren't connected but I think I'll forgive them if the above info is correct and the service actuvates in the next 24-48 hours.

Sorry, mine is on OpenReach, which is a little easier (just DHCP, no VLAN setup).

Hope they sort yours soon

In reply to a post by mr_bean:

To follow up on the above:

1) definitely a mistake speaking to the regular support team, I spoke to the Future Fibre team today and they were much more helpful and clued up.

2) It looks like the WAN parameters might be DHCP and VLAN 981

3) Chances are the service wasn't activated yesterday - disappointing that the dots weren't connected but I think I'll forgive them if the above info is correct and the service actuvates in the next 24-48 hours.

DHCP/IPoE protocol and set VLAN to 911

Thanks for the confirmation

The guy I spoke to was helpful and - the fact that I asked and he responded immediately with "it's VLAN 981" did give me some confidence he was not messing me about but no dice this evening (even with the suggested 30 mins downtime on the ONT).

911 seems to be consistent with other CityFibre deployments, I've tried both though without any luck

Distasteful though it is, I might have to configure the eero - at least if I don't get a connection with that I will know the problem is not the router and I might be able to dump the traffic with Wireshark to see what it is trying to do.

Edited by mr_bean (Sat 15-Jan-22 08:03:10)

Does the bundled router connect and test out OK?

Edit- sorry just read your note about the Eero. That would be the thing to try first.

Edited by Pheasant (Sat 15-Jan-22 00:22:03)

There is certainly no vlan parameters required for the TalkTalk Cityfibre service. It's DHCP from the ONT.

As advised by others try the supplied router first, if there's no service raise a call for it.

I'm currently using a UDMPro connected the ONT and the service works perfectly.

Looking around the 'net TT Future Fibre using Openreach fibre has no VLAN tag but there are claims CF use 911 for TT & several other ISPs

Interestingly the guy I spoke to said you could just plug a laptop in to test things - which would imply/be consistent with DHCP with no VLAN tag (at least without fiddling with the device settings), but then he was quite clear than it was VLAN 981. I checked with untagged frames as well last night BTW, in addition to VLAN 911 & 981.

He also seemed quite unphased when I said I was using a 3rd party router - even asked me what model so he could check if it was compatible - it's a D.link DIR-882 but I did point out that his chart might not be much use as it is running OpenWRT (an adventure in itself involving phone jailbreaking levels of faff - downgrade firmware to one with a known vulnerability, exploit that to get a shell, further exploit the fact that the stock firmware update code does not tidy up after itself in case of an error and finally manually flash the OpenWRT image).

The other claim was that there was a definite problem with service activation - he'd put the request through and that and that it could be another 24 hours before things would work - I'm going to take that as business hours in case there is manual intervention required so that takes us through to Monday afternoon - which, in turn, means it's likely to be Tuesday afternoon before I get the next opportunity to call TT owning to work commitments.

If the service does not magically start working today I will hold my nose and try the eero - though I can say that, unconfigured, it is putting out DHCP discover packets with no VLAN tag AFAICS.

In reply to a post by gordonsuk:

There is certainly no vlan parameters required for the TalkTalk Cityfibre service. It's DHCP from the ONT.

As advised by others try the supplied router first, if there's no service raise a call for it.

I'm currently using a UDMPro connected the ONT and the service works perfectly.

Are you on TT Cityfibre based FTTP or Openreach? If Openreach then you do not need to change any VLAN parameters on your router.

You could potentially be wasting your time if TT/Cityfibre haven't correctly provisioned your service, ie the fault is outside your control. First port of call (as others have already suggested) would be to connect the TT router to the Cityfibre ONT to see if the service works as it should. If it doesn't i would leave it connected and then let TT future fibre support know.

Re: VLAN tagging on Cityfibre, I'm pretty sure its 911. Have a look here (ignore PPPoE settings as TT use DHCP/IPoE)

https://support.giga.net.uk/hc/en-gb/articles/360010...

The tricky part is that from what I understand of Vodafone Cityfibre deployments, the VLAN can be different in each area. I second the suggestion to get the Eero box working first before trying anything else.

If you get desperate you can connect the Eero WAN to your PC and sniff the frames, it should be easy to see the VLAN tag that is in use.

CityFibre

Yes, I had come across that support page.

Had TT supplied just about any other router I would have been happy to use it for set-up - but the eero seems to *need* one to download a phone app to configure it and sign up to an online account as part of that process, which seems unnecessarily intrusive to me, it insists on knowing your mobile phone number and ideally it would like your Amazon account details as well (though arguably as eero are Amazon owned if you already have an account it might not worsen your lack of privacy).

Regardless of that the service isn't working today and, as it seems others have no problem with non-TT supplied routers I'm inclined to think that it is a provisioning fault and, yes, I will be better placed to complain if I have at least tried the supplied kit. I would have to (grudgingly) admit that it would not be completely unreasonable of TT to ask me to try the supplied router as part of any fault finding.

So, that is this afternoon's exercise.

Look on the bright side...some folks have been known to voluntarily spend their own money on getting eero's.

You'd might actually like it (at least a bit)

I assume you’ve already tried connected a PC direct to the ONT without any luck?

No, but there's not much I can do with a PC that I can't do with OpenWRT - run Wireshark on the device which is directly connected, perhaps.

> You'd might actually like it (at least a bit)

Apart from the "eero account" thing it's more a question of not needing or desiring any of its features while simultaneously wanting to do stuff that it can't than "liking" it per-se.

The intent is to continue my Andrews and Arnold account and the TT connection will just be used for L2TP access. So once it is tested/running the connection will be shifted to my current firewal/gatewayl box and the current WAN connection out of that will flip to L2TP rather than PPoE - and most of the existing network will continue unchange.

I'd go with CF direct from Andrews and Arnold but that's not available at present.

Anyway the eero doesn't work either.

Edited by mr_bean (Sat 15-Jan-22 15:52:10)

Looks like it’s a Monday call in to support to get the line provisioning sorted.

Yup

Except Monday's are usually too hectic, as is Tuesday morning typically - so Tues PM is likely to be the earliest opportunity that I get

I use a Network Orbi plugged directly to the CityFibre ONT and it connected straight out the box using DHCP no need to set up a VLAN.

The engineers who did the install made sure the service was up and gave evidence of speed test in excess of 500mbps using my old Talktalk router before they left

At the time I ordered FTTP, the Eero was only given to customers on Open Reach network and not CityFibre, not sure why, maybe a compatibility issue at the time.

Service has been rock solid since, fingers crossed you get sorted soon.

In reply to a post by mattlitt:

I use a Network Orbi plugged directly to the CityFibre ONT and it connected straight out the box using DHCP no need to set up a VLAN.

OK

The engineers who did the install made sure the service was up and gave evidence of speed test in excess of 500mbps using my old Talktalk router before they left

The Kelly engineers that turned up seemed to be interested only in setting up the optical path and much less so in checking that the service actually worked. In particular if I didn't want to plug the eero in and install the phone app I was definitely on my own (fair enough, I suppose) - they claimed they'd actually been "told off" by their supervisor for spending too long with clients trying to get the service up and running.

It didn't help that the firmware on the D.Link DIR-882 that I was using was rubbish.

At the time I ordered FTTP, the Eero was only given to customers on Open Reach network and not CityFibre, not sure why, maybe a compatibility issue at the time.

Now *that's* interesting - there are lots of online references to VLAN 911, but I'm not clear that the eero supports VLANs. If you go to "manual setup" it offers just DHCP or static IP and the setup did not ask me who my ISP was so unless it is *very* clever and pulls it from my postcode it doesn't know that I'm on TalkTalk via CityFibre.

Powering it up unconfigured causes it to put out DHCP discover packets, untagged.

So I wonder if early on CF did use VLAN 911 and the eero wasn't compatible, but they've now sorted CF using untagged frames.

Service has been rock solid since, fingers crossed you get sorted soon.

Fingers crossed

No luck over the weekend, including trying the eero. Looks like I might be able to get home in time to call CS today, unless it has magically sprung into life while I have been at work.

Edited by mr_bean (Mon 17-Jan-22 13:57:12)

In reply to a post by jpm:

The tricky part is that from what I understand of Vodafone Cityfibre deployments, the VLAN can be different in each area. I second the suggestion to get the Eero box working first before trying anything else.

Multiple possible VLANs would be somewhat annoying.

The eero doesn't work either.

If you get desperate you can connect the Eero WAN to your PC and sniff the frames, it should be easy to see the VLAN tag that is in use.

It puts out untagged DHCP discover frames and IPV6 neighbour solicitations.

Just got off the phone to TT - they say that they have identified a problem with the provisioning which CF need to fix - apparently the request has been generated today (?duplicating work on Friday, assuming that was done).

While I think that the eero supports VLAN tagging the WAN interface - there's a support page on the eero site that discusses it, for instance - the only manual setting offered on the app is either DHCP (with no option to set a VLAN tag) or static IP (again, no VLAN in the settings).

The guy today would not confirm the WAN settings - positively impolite considering that TT officially support 3rd party modems and there are details on the website (that are probably wrong, but they are there).

One annoying thing is that they won't tell me my account number and have not sent me my account number on any documentation - so I can't register on the website or use the support forums.

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.

Edited by mr_bean (Mon 17-Jan-22 17:11:22)

They are really slow at sorting accounts. Mine took 16 days from the date of activation before it was created.

Not directly related to OP, just want to have a rant.
Am with TalkTalk Business on openreach FTTP + copper line for phone.
Install was done by 'Kowboy Communications', they are a disgrace, enough said.
After several months the phone was 'cut off', at first TTB denied I ever had a contract for it! Took some time to get it back.
Every few weeks (once a month?) I get an email inviting me to 'upgrade' my service to 'superfast', as I'm already on 'ultrafast' I ignore them, last friday I got a sms from courier to say my new router was being delivered! On checking the last email I got I saw lower down that I was getting a 'free' upgrade to 'superfast'! All the online help was offline, I don't know why, eventually found a phone number, it took some time before the operative could understand that I had both copper and fibre, it was a quite surreal conversation with him telling me that as I was phoning on my copper line I didn't have FTTP, I think we got there in the end and my fingers are crossed that my 'upgrade from 'ultrafast ' to superfast' has been stopped.

OK, at least I know it's not just mine

Rant away

I was not impressed with the general support line which, judging from the over-compressed audio, latency and accent on the other end of the line was in India. Another annoyance was the use of Anglicised names - I don't know what the guy I spoke to was called but "Jason" seems so unlikely as to actually be irritating.

Most of the call was wasted just trying to get the basics across - such as multiple attempts to get him to understand how my surname was spelled despite the use of the phonetic alphabet.

Then it was clear he did not understand the product and kept asking for my TT phone number. At the very least the operators should know that the product exists, they can't deal with it and how to re-direct a customer. It wasn't his fault I didn't have my account number but operators should be trained to recognise that new customers might not have one and to explain this when people call in.

At least the Future Fibre team have been able to use the order number and have been polite, albeit not terribly forthcoming with what is actually going on or how to set up a 3rd party router.

I thought TTB only offered a data only service on Openreach FTTP? At least that was the case when I took out their Fibre 900 service in Oct 2020. No real issues with TTB, though for some strange reason my upload on TTB never goes above 100 Mbps whilst the equivalent service on BT Business gives me 119-120 Mbps upload. Nothing to get my knickers in a twist over though

(Sorry for going off topic OP)

In reply to a post by Skardu:

I thought TTB only offered a data only service on Openreach FTTP? At least that was the case when I took out their Fibre 900 service in Oct 2020. No real issues with TTB, though for some strange reason my upload on TTB never goes above 100 Mbps whilst the equivalent service on BT Business gives me 119-120 Mbps upload. Nothing to get my knickers in a twist over though

(Sorry for going off topic OP)

I have a hybrid cable coming from the pole, it has fibre and copper, it splits at the eaves, copper going to a 5C mk4 'Master Socket', and fibre to a Huawei ONT.

On Openreach, TTB supply you with their router, which you can use or keep in the box. Mine never made it out of the box. Straightforward PPPoE connection on Openreach for TTB. Resi TT on Openreach uses IPoE.

I don’t have a voice service with them, none was ever offered or indeed needed as we’ve run SIP connections for the office and for domestic for ages - makes it dead easy to change ISP and keep voice services running without interruption.

In reply to a post by Pheasant:

On Openreach, TTB supply you with their router, which you can use or keep in the box. Mine never made it out of the box. Straightforward PPPoE connection on Openreach for TTB. Resi TT on Openreach uses IPoE.

I don’t have a voice service with them, none was ever offered or indeed needed as we’ve run SIP connections for the office and for domestic for ages - makes it dead easy to change ISP and keep voice services running without interruption.

We where looking at change to FTTP at start of last years lockdown, there was no certainty of a timely switch over after porting number to SIP, which may have left us with no service for a unknown time. When present contract ends will most likely port number to a SIP service, as fibre is now in place and any loss of service will be minimal, if any at all. With at best a patchy mobile signal some form of landline is a lifeline.

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)

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

Pretty standard for any mass-market ISP. While a new Vodafone (OR FTTP) connection I've just taken is on a technical level working perfectly fine, I've had two interactions with technical support in two days.

The first, to get PPPoE login details: I instead get issued SIP credentials for the associated VoIP account that I have no need of. Naturally, they are of no use for the PPPoE session I try to bring up at ten past midnight. For anyone having this problem in the future, the SIP login is of the form voi..... rather than dsl.....

The second, to try and correct the error: I'm issued PPPoE details with a capital i in place of a lowercase L, and instructions to add a VLAN tag which isn't required.

However, they have issued a static IP at no charge, and the service works well and is very keenly priced.

All of this sort of thing is why I prefer AAISP.

I'd hope that technical support might be a bit better on the business side, but I'm not convinced.

As is always the case on Forum posts, the author of a post knows exactly what they mean but the reader can interpret the words in many different ways.

Not much point ruminating over Vlan ID's if none is required and TalkTalk are unable to give any useful information. I tried to point out that there is almost certainly a Vlan tag on your service but you never see it at the customer interface, but as you claim to "know all that " I will leave you to it.

In reply to a post by Realalemadrid:

As is always the case on Forum posts, the author of a post knows exactly what they mean but the reader can interpret the words in many different ways.

A weakness of using natural language for communication, I'm afraid.

Not much point ruminating over Vlan ID's if none is required and TalkTalk are unable to give any useful information.

Except that others will come after, trying to figure out how to set up their non-TT router (remembering that this is something officially sanctioned by TT) - it might help if there is some reliable information on the 'net as to what works and why there might be conflicting information flying around. Particularly as TT themselves seem "unable to give any useful information" - one agent gave me what was apparently wrong info, one refused to tell me anything saying "we don't give that info" even though TT allow 3rd party routers.

Certainly the TT "community" pages are actually not much use especially their official "how to set up a 3rd party router" as it talks about "fibre broadband" (here I think they actually mean FTTC/VDSL, but it's ambiguous) and VLAN 101.

Even the various support forum topics where people as do not seem to carry an unambiguous "this is what you need".

My curiosity is of the form "my install is not using end-user-visible VLAN tags - why are there reports that they are needed".

I tried to point out that there is almost certainly a Vlan tag on your service but you never see it at the customer interface, but as you claim to "know all that " I will leave you to it.

Well, yes but utterly irrelevant so end user router settings, is it not?

In reply to a post by mr_bean:

Except that others will come after, trying to figure out how to set up their non-TT router (remembering that this is something officially sanctioned by TT) - it might help if there is some reliable information on the 'net as to what works

If you post your findings on the TalkTalk Future Fibre forum, then there's a good chance one of the OCEs there will turn it into a 'sticky' post to let others know how to use a third party router on Cityfibre based TT services. They may even make you a guru on the TT forum

https://community.talktalk.co.uk/t5/Future-Fibre/bd-...

Edited by Skardu (Fri 21-Jan-22 16:15:43)

In reply to a post by Skardu:

If you post your findings on the TalkTalk Future Fibre forum, then there's a good chance one of the OCEs there will turn it into a 'sticky' post to let others know how to use a third party router on Cityfibre based TT services. They may even make you a guru on the TT forum

https://community.talktalk.co.uk/t5/Future-Fibre/bd-...

Possibly but as TT haven't sent me an account number I can't register on the forums.

There was even a hint that I might not see the account number until they start billing me ... in 6 months!

You should still get a bill after the first month, but it will show a negative figure, if I recall correctly.

In reply to a post by Skardu:

In reply to a post by mr_bean:

Except that others will come after, trying to figure out how to set up their non-TT router (remembering that this is something officially sanctioned by TT) - it might help if there is some reliable information on the 'net as to what works

If you post your findings on the TalkTalk Future Fibre forum, then there's a good chance one of the OCEs there will turn it into a 'sticky' post to let others know how to use a third party router on Cityfibre based TT services. They may even make you a guru on the TT forum

https://community.talktalk.co.uk/t5/Future-Fibre/bd-...

Unlikely as many Talktalk connections over CityFibre do indeed use a VLAN as was initially advised.

No idea if it is different in different areas or if Talktalk have changed the setup for new customers in all areas now but if it's the former then a single sticky post with instructions would be useless.

In reply to a post by burble:

I think we got there in the end and my fingers are crossed that my 'upgrade from 'ultrafast ' to superfast' has been stopped.

I think I may have uncrossed my fingers as got this message today.

Following our recent communication regarding your free Superfast Fibre upgrade, we are reaching out about the router which we sent to you via YODEL.

Unfortunately, we are experiencing a technical issue and are not quite ready for you to install the router yet.

If you have already installed the router and it is working correctly, then no action is required. If you are still using your old router, please continue to do so and do not install the new router for the time being.

We’ll be back in touch in the next few days to let you know what to do next.

Already had a bad day reloading windows on gf's laptop as she somehow managed to completely mess it up, how I don't know, then having a wrestle with the HP printer which decided it needed setting up again to enable printing off her laptop.

In reply to a post by burble:

Already had a bad day reloading windows on gf's laptop as she somehow managed to completely mess it up, how I don't know, then having a wrestle with the HP printer which decided it needed setting up again to enable printing off her laptop.

Sounds like my average day, there's always something that's broken on a Windows based device.

I know one of my devices blue screens if its woken up from sleep mode, no idea why but it does.
Other times sleep mode works and hibernation mode causes a blue screen.
It all depends on if I ran windows update

If it makes it better Microsoft Issued out a Surface Pro 6 firmware update recently that causes my surface pro to blue screen since it "wasn't compatible"

The team that send out finalised updates should probably get someone to test them instead of a mass market test to find out printing is broken/

In reply to a post by j0hn83:

In reply to a post by Skardu:

In reply to a post by mr_bean:

Except that others will come after, trying to figure out how to set up their non-TT router (remembering that this is something officially sanctioned by TT) - it might help if there is some reliable information on the 'net as to what works

If you post your findings on the TalkTalk Future Fibre forum, then there's a good chance one of the OCEs there will turn it into a 'sticky' post to let others know how to use a third party router on Cityfibre based TT services. They may even make you a guru on the TT forum

https://community.talktalk.co.uk/t5/Future-Fibre/bd-...

Unlikely as many Talktalk connections over CityFibre do indeed use a VLAN as was initially advised.

No idea if it is different in different areas or if Talktalk have changed the setup for new customers in all areas now but if it's the former then a single sticky post with instructions would be useless.

I wonder if these changes are indeed being driven by the National Access Network that CityFibre are/have deployed?

Are you spannering on your own or have you gone to work for a larger company now?

I'm part time on the IT service desk at MASS Consultants
Although for various legal and security reasons and due to the work undertaken, I must clarify that all opinions are not related in any way to the company.
I'm sure if you take a look at the site, it's self explanatory.
(EDIT) (I am still on my last few months at Sixth form, and will be looking down the degree apprenticeship route) (BT recruitment have invited me to an assessment centre although no news on when. (Applied for a network engineer role)) (I will add that if my current employer does intend on having degree apprenticeships in one of the fields i would be interested in they will take priority for various reasons. One of those being existing apprentices at the company considerably higher salary if we include commuting costs to London based sites, (or any site really) I'm less than 5 minutes drive or 10 bike away from the office at the moment.
To add to all that the company is very supportive of their staff and has a good environment with comprehensive benefits.

Edited by RR_The_IT_Guy (Thu 27-Jan-22 17:53:52)

Continuing my slightly off topic posts.
Have had a flurry of emails from TTB about my "upgrade to superfast" and the new router, so thought I'd plug the new router into my copper line, well it synced in, but the WWW isn't available. Unfortunately this router seems a bit sparse on connection info, all I could find was it had connected at 0.5 which would be much lower than FTTC, even a little bit low for my old ADSL,

0.5/0.5 is the data package Openreach sell for VOIP calling.

In reply to a post by j0hn83:

0.5/0.5 is the data package Openreach sell for VOIP calling.

Yes i did wonder about that but forgot to ask in my previous post if this would show if you was to plug a router into a standard master socket with no internet contract. We have another property on the same exchange which has also got a copper line, no mention from BT (the phone provider) about any changes, so I'm guessing this is not anything to do with analogue phone withdrawal, maybe I'll have to plug the router in to see if same thing happens there.