Sure Signal 3 Not connecting

[dmlox]

On 19th. Dec. I had to shut-down my b/band system and S.Sigv3 as well in order to re-locate al the kit and cabling in the same room but in a neat and tidy way.  This took about one-and-a-half hours.  At about 13.30hr. I powered it all up again. B/band worked perfectly immediately, and still does. The S.Sigv3 still will not connect more than 27 hours later and after many 'presses' of the re-set button.

If this rerquires a 're-sync' please do it.

I ran through the routine of 'tracert' and speed check and see no difference, exceeding 5% of indicated value, from that which I recorded and sent to you on 20th October.

The suggestion that a connection will take 10 mins to one hour, as given in the 'Quick Set Up Guide' 65-020-032302B, supplied with the device, seems a little hollow.

DLox

[dmlox]

'Evening Ben,

I receive a b/band connection through a 'private' community wireless scheme which buys capacity from NyNet

I spoke to my provider who confirmed that all the ports required were open for forwarding and all the IP addresses  are allowed through the router. There are about 20 subscribers in 'our' net who use Sure Signal and none seem to have problems.

From 21·30hr on 23 Dec until 03·30 24 Dec we had a electricity outage so all the S.Sigs would experience a 're-set'.

My contract is for a nominal 5Mb but it frequently exceeds 7Mb.upload

Tue. 24 Dec 17·55 to 17·59 I caried out three speed checks using 'Broadband Speedchecker UK'

results:-

Down Mb            UpMb

5·52                    4·98

6·03                    4·73

5·13                    2·59

Which, currently, are within your requirement (even by a scrape)

My IP provider has also told me that at least two of his subscribers report that their S.Sigs have taken up to

48 hrs to connect after a disconection.

Is this unusual?

Have you all a very Merry (hic) Christmas

DLox.:-)

[Retired-Dave]

Hi dmlox,

Has the reset after the power outage made any difference?

I noticed you say this is a wireless scheme. The Sure Signal is designed for a cabled connection due to the quality of service that provides. Is your part of the connection wired or wireless?

It may also be down to the number of Sure Signals being used across the sommunity scheme. The more in use simultaneously, the more overall capacity would be needed. If they're in close proximity, it may also be a case of interference.

48 hours is definitely longer than we'd expect for reconnection, so this could point towards there being an issue hat only you have reported. I'd look at getting the traceroute results to the end provider, pointing out the lags and asking them to check them. Some of the steps could affect all the users on the scheme.

Finally for now, are you able to try a different ethernet cable with your Sure Signal? 

Dave

[dmlox]

Hello Dave,

The power outage has made no differnce at all.

An active 're-set' might last two hours and then fall into a fault mode

Power=flash; I'net=steady orange; Service=OFF; Users=steady orange.

Since the power failure I have lost count of the number of 'resets'.

10.30 this A.M. "fault mode"

Ben H. asked (23/12/13) if I had noticed a drop in I'net speeds - yes

Speaking to my ISP he told me that there had been a problem with a sub-provider to NYNet which had lasted some 5 to 7 days but that it has been 'sorted'.

Since it first connected, 31 Oct. 2013,  it has worked well inwhat can only be described as a badly kept bundle of knitting.

On 19 Dec. I laid all the cabling into small section plastic trunking and lifted the S.Sigv3 and the router off the floor on to beams below the ceiling.

Router and S.Sigv3 are separated by 0·7(+)metre, about the same as originally.

The 'Beeline Broadband' system covers about 200 sq.miles of the southern area of the North Yorks Moors it is sparsely populated and has about 200 subscribers with about 20 known S.Sig. users. The larger company, NYNet, is wholly owned and operated by North Yorkshire County Council and they sell capacity, through fibre optic connection, to a number of Community Providers.  Beeline Broadband have a receiving server, 37.72.114.1, from which the broadband connections are delivered by 8GHz. Tx/Rx mast-head units. Within this scheme my own Rx/Tx has the address 192.168.1.10. All the cabling within our house is "Certified Cat. 5E"  indeed the one piece which I did throw away because it caused problems was that supplied with the S.Sigv3.

Beeline tell me that they are not aware of any other subscriber having this kind of problem.

Tracing route to cluster4.vap.vodafone.co.uk [212.183.133.177] over a maximum of 30 hops:

 Monday 23rd. December 2013

  1    <1 ms    <1 ms    <1 ms  192.168.1.10

  2   107 ms    65 ms    67 ms  37.72.114.1

  3    63 ms    82 ms    18 ms  31.25.4.209

  4    21 ms    53 ms    72 ms  100.80.194.193

  5   223 ms    76 ms   107 ms  nodns.phoenix.co.uk [195.200.132.187]

  6    83 ms    96 ms   318 ms  nodns.phoenix.co.uk [195.200.132.189]

  7    80 ms    52 ms    70 ms  v862.wf-ih-cs-01.phoenix.co.uk [212.102.206.45]

  8   264 ms    45 ms    55 ms  ge00.wf-sd-tr-01.phoenix.co.uk [195.200.158.222]

  9   102 ms    68 ms    90 ms  ge02.e-10-tr-01.phoenix.co.uk [212.102.192.226]

 10    93 ms    63 ms    57 ms  212.113.9.137

 11   111 ms    45 ms    67 ms  ae-51-51.csw1.London1.Level3.net [4.69.139.88]

 12   293 ms    47 ms    61 ms  ae-119-3505.edge4.London1.Level3.net [4.69.166.1]

 13    57 ms    77 ms    54 ms  195.50.122.66

 14   101 ms   106 ms    39 ms  85.205.116.2

 15     *        *        *     Request timed out.

(16 to 29 inclusive)

30     *        *        *     Request timed out.

 Trace complete.

Tracing route to cluster4.vap.vodafone.co.uk [212.183.133.177] over a maximum of 30 hops:

Thursday 26 Dec. 2013

Speed check  Up = 14·70 Mbps;  Down = 4·74 Mbps.

  1    <1 ms    <1 ms    <1 ms  192.168.1.10
  2    21 ms    47 ms    39 ms  37.72.114.1
  3    21 ms    25 ms   102 ms  31.25.4.209
  4    20 ms    13 ms    40 ms  100.80.194.193
  5    37 ms    23 ms    16 ms  nodns.phoenix.co.uk [195.200.132.187]
  6    46 ms    37 ms    67 ms  nodns.phoenix.co.uk [195.200.132.189]
  7    62 ms    75 ms    51 ms  v862.wf-ih-cs-01.phoenix.co.uk [212.102.206.45]

  8    52 ms    54 ms    26 ms  ge00.wf-sd-tr-01.phoenix.co.uk [195.200.158.222]

  9    65 ms    51 ms    55 ms  ge02.e-10-tr-01.phoenix.co.uk [212.102.192.226]

 10    29 ms    54 ms    33 ms  xe-8-1-0-1100.edge6.London1.Level3.net [212.113.9.137]
 11    55 ms    74 ms    87 ms  ae-51-51.csw1.London1.Level3.net [4.69.139.88]
 12    56 ms    38 ms    51 ms  ae-119-3505.edge4.London1.Level3.net [4.69.166.1]
 13    58 ms    89 ms    64 ms  195.50.122.66
 14    64 ms    77 ms    51 ms  85.205.116.2
 15     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Regards

DLox

[Retired-Dave]

Hi dmlox,

Although Beeline say that they're unaware of other users with issues, it doesn't mean they aren't there.

The traceroutes regularly show peaks which are causing the Sure Signal to time out. Some of these look like they're within the scheme, and some outside. This is something we can't help with, as they need to be addressed by the service provider - the Sure Signal itself is not part of the traceroute.

This is not uncommon on wireless connections. Unlike fixed line ones, they can suffer from interference and be affected by things like the weather or line of sight issues. 

The only other possibility is a faulty Sure Signal box.  Try testing the box on a different internet connection, such as a friend's or relative's. A solid, stable connection will rule this out.

Dave

[dmlox]

Hello Dave,

I follow your comments and will address them.

Today, Friday 27th, is very windy with rain and I notive that my aerial mast is waving in the wind.

I did the Vodafone .Net tests.

Ookla Speed test at 11·02hr

Server:  Leeds; Webfusion

Ping  62mSec

Down:  6·59Mbps

Up:  3·14 Mbps

PingTest at 11·12hr

Server:  Milton Keynes

Quality:  B*  MOS 4.30

Ping:  56mSec;   Jitter: 15mSec.

Friday 27 Dec 2013;  10·47hr.

Tracing route to cluster4.vap.vodafone.co.uk [212.183.133.177]

over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.10  (Home Tx/Rx)

  2    10 ms     9 ms    10 ms  37.72.114.1  (NYNet server)

  3    34 ms    21 ms    10 ms  31.25.4.209

  4    17 ms    13 ms    17 ms  100.80.194.193

  5    31 ms    52 ms    41 ms  nodns.phoenix.co.uk [195.200.132.187]

  6    20 ms    22 ms    20 ms  nodns.phoenix.co.uk [195.200.132.189]

  7    32 ms    15 ms    29 ms  v862.wf-ih-cs-01.phoenix.co.uk [212.102.206.45]

  8    23 ms    19 ms    26 ms  ge00.wf-sd-tr-01.phoenix.co.uk [195.200.158.222]

  9    29 ms    20 ms    31 ms  ge02.e-10-tr-01.phoenix.co.uk [212.102.192.226]

 10    24 ms    24 ms    21 ms  xe-8-1-0-1100.edge6.London1.Level3.net [212.113.9.137]

 11    25 ms    23 ms    24 ms  ae-51-51.csw1.London1.Level3.net [4.69.139.88]

 12    23 ms    26 ms    27 ms  ae-121-3507.edge4.London1.Level3.net [4.69.166.9]

 13    41 ms    47 ms    39 ms  195.50.122.66

 14    40 ms    36 ms    39 ms  85.205.116.2

 15     *        *        *     Request timed out.

30     *        *        *     Request timed out.

Trace complete.

If what I read in the e-forum is a good guide these results see quite acceptable.

I will converse a little morw with my ISP.

[Retired-Dave]

Hi dmlox,

Let us know how you get on.

The traceroutes have been very variable - whilst it may work well on some occasions, on others it's been quicte poor. Make sure you show them all of them you've posted here to show how changeable it's been.

Dave

[dmlox]

Good-day Dave,

In conjunction with my internet provider we have tested and confirmed the Ports and IP addresses are all open and allowed, this is confirmed on Vodafone whitelist.

My near neighbour, 750meter distant, has four S.Sigv3 working in his property and we share the same Tx/Rx relay station which is 1km away. They all auto-reconnected after the recent power failure which affected our area.

It has been confirmed that there are no other S.Sig user problems within the BeeLine Broadband system.

The DHCP range has been widened.

The DMZ has been relaxed

The bandwidth in my Tx/Rx has been widened

There are now no more moves which my provider can make.

This S.Sigv3 has been trying to connect since the 19th of December 2013, 13 days!

It is currently in its common mode

Power = flashing

I'net = steady orange

Service = OFF

Users = steady orange

Vodafone administrators know of 'problems' in 'My Account' and in 'Services' > Sure Signal.

These are indicated by highlighted messages in gray boxes.

I have written a formal letter to Newbury requiring these problem to be resolved along with eight questions.

Regards

DMLox

[Gemma]

Hi dmlox,

The Sure Signal isn’t designed for wireless community broadband services. It’s designed to run on a standard fixed line broadband connection.

The light sequence you’re seeing indicates an issue with the quality of your broadband connection.

Would you be able to ask your neighbour to test your Sure Signal on their internet connection to rule out a faulty box?

Thanks,

Gemma

[dmlox]

Hi Gemma,

There is nothing at all problematical with this broadband connection.

Read my previous post regarding our near neighbour with four S,Sig working perfectly through the same local (1km) distant relay station.

I bought the S.Sig on 23 Oct. '13 it started to function on the 1st Nov. '13 and worked until 19 Dec. '13 including one power glitch from which it recovered itsel correctly.

It is astonishing that the instrument was designed to operate on a cable only system when its application and concept are ideal for our kind of situation. This indicates an incompetent engineering design.

If Vodafone cannot provide a working resolution to this S.Sig before 08.00hr. 8 Jan '14. I will return it to the shoip whence it was purchased as 'Not fit for purpose' under several clauses of the Sale of Goods Act 1979 and the Supply of Goods and Services Act 1982

Regards

DLox

[Retired-Dave]

Hi dmlox,

The Sure Signal requires a minimum specification, which a non-hardwired connection can’t always provide.

There will be instances where the Sure Signal will work on these connections, however we can’t guarantee that the setup will work at your specific location.

All indicators from our end show that the issue is down to the connection quality, which is backed up by the light sequence and the traceroutes.

As Gemma suggested, the next test would be to try an alternate connection to rule out a fault with the box itself. As your neighbour has working Sure Signals, there's would be a good one to test on.

Dave