Ethernet cable of CCTV DVR to LAN port on router -now causing pkt collisions post full fibre upgrade

[Mytv123]

Upgrade from (copper fm cabinet) 'superfast 35' to 'Superfast150' last April. Whilst appreciating the improved speeds, the stability has got steadily worse - ignoring the initial 2 week settling in period. 150MB one minute - nothing the next - then recovers for Sky to say 'all fine'. Their own published record details the average speed just 6mb yesterday and 23mb 2 weeks earlier.

Numerous hours to SKY helpdesk and reaching out to OpenReach have me no further forward - save for latter instructing me to remove the ethernet cables re hard wiring of computer and my CCTV (for worldwide monitoring). Obviously hard wired is the industry standard preference, but causing LAN 'Collision Pkts' - anything from 11 to 47 to 100+ when both connected and in use.  It's as if the LAN sockets in router aren't really available for use anymore. I must stress that other than the change fm 35 to 150 (ie full fibre) the configuration has not altered (nor the hard wiring of computer and cctv for 12 years or so). Black router replaced by SKY following problems (same model as when working with copper 35) - same problems.

I see there is refererence to programming the router? Does this need to be done following the SKY engineer instructed hard reset? Appears higher number when using socket 1 vs socket 3 for the CCTV.

Not having access to the CCTV remotely is not really viable - nor expected from the 'upgrade'/degredation in offering.

Any help appreciated. My CCTV DVR does not have a wifi option - understand once can use a 'bridge' to create a wifi compatible signal. But at end of the day, will never be as stable - or secure - as direct ethernet wired. Moreover it will be a lower received speed.

[jamesn123]

@Mytv123 

Have you tried the simple fixes like replacing the ethernet cable for your CCTV system?

Can you post a screenshot of your router stats?

[Mytv123]

Yep - new SKY-supplied ethernet et al. Followed all their instructions to no avail - their 'solution' is I pay even more for a higher speed service (that I don't need - not a gamer!) to enlist the Sky Max hub and wifi engineer support. With current upgrade/degredation in service (mindful identical setup with copper bar land line) - this is not something I'm keen to take forward!

Following my last discussion with Sky on Sunday, we managed 2hours of everything plugged in and working fine with zero pkts colliding. Then went to 16 where it remained until this luncthime (particularly poor stability) - and now  showing 28.

NB Hub was replaced 12/7/25 and has dropped below guaranteed average 3 times in this period. It's not so much these figures as the instability that is my concern - 1 minute 150Mb speed, then next nil and then back up to 130/150Mb with no changes instigated by me.

I have also been monitoring the SysLog and wonder if the 'your cctv' is a  bum steer (they don't support any '3rd party applicance' using the LAN!, since I also had pkt collisions with just my PC hardwired on ethernet.

From my layman reading, this is regularly seeing the VOiP lost, licence applied for - not always sent - and back up again - IPV6 up/down. We obviously only took up the VOiP with full fibre when our problems started - giving up the fibre to cabinet landline.  NB this is despite a full hard reset of Hub/Router and the inevitable 'settling in' in last 3 days.

Any help/suggestions gratefully received.

The syslog of last 24 hours or so is currently:

apologies for small size - I did simply insert all the data but the repeated use of 0805  10 (the date and partial time!) apparently identifies me!

[jamesn123]

@Mytv123 

Just to clarify, if you pull the cable out of your CCTV system the broadband performs fine?

[Mytv123]

No alas not.

The act of removing the ethernet cable from LAN1 (cctv - flashing green and static orange at back/100mb limitation) and LAN2 (pc - both flashing green/1Gb functionality), simply allows the collision pkts to revert to 0 - though sometimes a router reset is required all the same.  System seems more stable over time without them connected (we did a 4 day test with Sky and both LAN cables out) - indeed whilst collision pkts remain 0.

It seems to be anything using the LAN on a hard-wired basis that is the 'Sky' issue (mindful they won't support anything not made by Sky). NB this configuration is exactly how I had it in the same model sky hub with copper to cabinet 35MB - only change is I have a 'landline' now plugged into router too receiving full fibre 150MB  NB all lights on front of openreach box socket and sky hub all green (regardless of whether internet/wifi working or not)!

I have reset the router and currently having everything how I need it, ie all working as expected and no collision pkts on LAN despite cctv and pc ethernet connected to hub.  It seems to be as time goes by post the reset that the issues of phone disconnecting/reconnecting (even though not really used by us - just available for others to ring in), and 'WAN IPV6 up/down' seems to kick in. Also regular searches for licence which are sometimes met & sometimes not. I assume the licences sought will be on the sky/openreach platform rather than my devices themselves (mindful pc invariably not even in use) - only the cctv on 24/7.

By way of another test, I have replaced the landline phone from a cordless one (base unit receiver/recorder plugged into router) with a traditional landline phone into router. I'll monitor the system logs and stability going forward again - it'll be interesting if the phone keeps disconnecting/reconnecting, and to establish why that should be. Both pensioners so not ideal if can't rely on phone to actually work if ever need it!

[Mytv123]

apologies for delay - I know I answered but now seems lost from the thread!

Alas not. But once both PC and CCTV ethernet cable removed from Hub it is easier to get the collision pkts back to 0.  (reset still sometimes needed). Indeed system is stable when that remains the case - did a 4 day trial with them out with Sky. The stability was fine. Reality is, however, a hard wired PC is faster and a cctv without worldwide access is useless. Sky don't support any '3rd party devices' - ie anything not made by Sky!

CCTV is in LAN1 socket (flashing green and static orange at back - ie 100MB limitation) with PC in LAN2 socket (both green/1GB) - all four lights on front remain green - as do the 3 on the OpenReach box - regardless of whether internet/wifi up/working.

I must stress the configuration and devices are no different than when 35MB copper to cabinet, save now full fibre 150MB and of course a phone plugged into hub post losing landline. I have taken the opportunity to replace the cordless phone and base unit (plugged into hub) with a standard landline plugged into hub and will monitor if that makes any difference on the 'connected/unconnected' status of phone - even though not used by us, just to receive calls.

I have undertaken a reset and currently got everything working will all devices I want plugged in, in. I have 0 collision pkts currently and my status log post the reset is okay.  Continuing need to connect the phone, apply for licence (presumably from Sky/Openreach vs my devices) and have IVP06 up/down.  It is the longer time goes by from the reset that the issues - collision pkts/stability of service - exacerbates exponentially.

Current stats and syslog:

[jamesn123]

@Mytv123 

Okay so what if you connect just one of them? i.e just the CCTV then just the PC? Is the issue arrising when you have both connected at the same time? 

[Mytv123]

No difference. It can be either one or both.  It seems to be the act of inserting any none-sky product into the lan sockets - whether my PC or CCTV - I even tried a different cctv NVR recorder (brand new) with same issue.

Currently, I have maintained both cables in, 0 collision pkts and full suite of green lights 1hour 45 mins since reset:

That said, the instability comes from the continual searching/applying for and finding licences. 1 minute 150MB speed, then next nothing/hanging endlessly. (In conjunction with times on syslog - mindful GMT vs BST clock).

In particular, note 15:48:08 syslog: DHCPC_STATE_REQUESTING no valid response received. Falling back to DHCPC_STATE_START_DISCOVERY

It is presumably this continual resetting 'behind the scences' that holds up the signal - even though green throughout (and still 0 pkts).  I think the LAN pkts may be something SKY's latched onto to absolve responsbility, when in reality it is the system searching and not being satisfied/continually re-trying so making the situation worse as length of time post reset goes on.

[Not-So-VIP · Accepted solution]

"ANSWERED"

Hobson's choice but to pay even more and upgrade to Max router (not actually a sky product but badged as such). By tech desk own admission, the 203 router supplied is not fit for purpose when more than a few devices/'complex' set up involved. IE the Router is not sufficiently programmable to cope with different demands, vs Max which is programmable with recourse to inhouse wifi expert on home visit too.

What a pity the salesmen doing the upgrades aren't aware/share this info. Buyer beware - if you upgrade to full fibre they want you on Sky Max hub really (just like the push from Sky Q to Glass), but let you migrate with the inferior hub to then incur more cost soon after.

[JimM1]

@Mytv123 Question for you, is the wanoe connected onto port 4 that is marked wan in red letters and going to the ONT,  Just dont see why you always display a wan time error everytime you post up! Are you disturbing all the cables or a bad cable connection on the back off the hub!

[Not-So-VIP]

Yep - and replaced with new Sky Ethernet cable too. Openreach adamant inside vs outside the house - I remain to be convinced given phone forever connected unconnected.

It just seems to want to continually reset.

Invested so much time I've just had to bite the bullet and pay for Max hub. Ok so far - with recourse to a WiFi home expert visit if necessary. At least it was cheaper then replacing cctv with a new system that may/may not have same issues and still not be supported by sky as a 3rd party appliance.