Superhub Keep losing wired connection

RobTi · 22-12-2011, 09:23

Keep getting the following faults and i loose connection to the hub, any one tell me what it means.

I have had a few engineers out fitting filters ( downstream to high, downstream to low) next one removes it then next one refits it and tells me that its all down to my cabling ( home done with cat 5e cable and because i havent fitted the faceplates onto the back boxes i am getting interference), so was told nothing more could be done so i connected 1 pc direct to the hub with a virgin media self install cable and still the same on that pc.

Getting these nearly every day

IP packet w/MC or BC SRC addr
SYN Flood
Illegal TCP header

Thanks

Robert

kwikbreaks · 22-12-2011, 09:54

What exactly do you mean by "loose connection to the hub"?

If it screws up and you then plug the PC into a different port using a proper ethernet patch lead does it work without rebooting the hub?

Have you checked the lights on your hub ethernet ports? If the wiring is defective they'll be out. You can buy a tester on eBay for a couple of quid to check your wiring. If you've got faceplates just hanging on the end of cables then they won't last long.

I've seen the second two on my Superhub log when I had one and I think the first is a misdiagnosis (possibly caused by using pingtest.net) and the second is just a duff packet which will probably be resent.

General Maximus · 22-12-2011, 09:59

the best thing to do is get a proper cable and and directly connect one device to the shub and look at what the power levels are yourself. If they are poo it hasn't got anything to do with your cabling around the house, it is the connection between your modem and the cmts

RobTi · 22-12-2011, 10:13

Thanks for the replies when it looses connection it is only for a few seconds till it reconnects unfortunatly its in the attic and i can't get to it in time when it does this, its as if it reboots and then reconnects, i have had 1 pc connected by a 10m terminated cable and left it with only that one connected and still got a fault with that one signal levels look fine.

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 299000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK
Security Enabled BPI+
Downstream Channels
Lock Status Modulation Channel ID Max Raw Bit Rate Frequency Power SNR Docsis/EuroDocsis locked
Locked QAM256 104 55616000 Kbits/sec 299000000 Hz -0.1 dBmV 40.9 dB Hybrid
Locked QAM256 103 55616000 Kbits/sec 291000000 Hz 0.1 dBmV 40.4 dB Hybrid
Locked QAM256 105 55616000 Kbits/sec 307000000 Hz 0.0 dBmV 40.8 dB Hybrid
Locked QAM256 106 55616000 Kbits/sec 315000000 Hz -0.2 dBmV 40.7 dB Hybrid
Unlocked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 0.0 dB Unknown
Unlocked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 0.0 dB Unknown
Unlocked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 0.0 dB Unknown
Unlocked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 0.0 dB Unknown
Upstream Channels
Lock Status Modulation Channel ID Max Raw Bit Rate Frequency Power
Locked TDMA 4 10240 Kbits/sec 25800000 Hz 44.5 dBmV
Unlocked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
Unlocked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
Unlocked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
Primary Downstream Service Flow
Downstream(0)
SFID 94
Max Traffic Rate 32220000 bps
Max Traffic Burst 3044 bytes
Mix Traffic Rate 0 bps
Primary Upstream Service Flow
Upstream(0)
SFID 93
Max Traffic Rate 1111000 bps
Max Traffic Burst 8160 bytes
Mix Traffic Rate 0 bps
Max Concatenated Burst 8160 bytes
Scheduling Type Best Effort

Thu Dec 15 22:06:22 2011 Critical (3) DHCP FAILED - Requested Info not supported.;CM-MAC=CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
Thu Dec 15 22:06:18 2011 Critical (3) No Ranging Response received - T3 time-out;CM-M;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) DHCP FAILED - Requested Info not supported.;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) DHCP FAILED - Requested Info not supported.;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Robert

kwikbreaks · 22-12-2011, 10:57

From the sound of it they were feeding you BS as your cabling is very unlikely to be the problem given lots of people report that their superhubs do that sort of thing. Do you use wireless at all? JB66 reckons any wifi interference gives them grief. At the end of the day splash a few quid on a router that works and put the thing in modem mode. There's nothing I can see in your stats to suggest problems but I'm noexpert on them.

General Maximus · 22-12-2011, 15:32

I agree with kwikbreaks, it isnt your physical connection to the hub that is causing the problem, it is the hub being less than super as a router/switch and loads of peeps have got the same problem as you

RobTi · 22-12-2011, 16:07

Thanks for the replies i have a 5 port gigabyte switch downstairs i will give the modem mode a try with that and see if it helps.

If i change to modem mode will i lose wi-fi

Thanks

Robert

kwikbreaks · 22-12-2011, 16:16

Modem mode = modem only - no routing no wifi - just a plain modem.

I don't think a modem + switch is going to work - you'll need a dhcp server running somewhere as the modem just passes the public IP to whatever is on its LAN port.

You could try just using the Superhub as a gateway and dhcp server if you connect everything to the switch and just run the one cable from hub to switch - that way the Superhub doesn't have to deal with your home network traffic.

shiner · 22-12-2011, 21:11

Your problems sound pretty similar to mine :

http://www.cableforum.co.uk/board/12...es-it-fix.html

I'm about to try modem mode to see if it helps