Sure Signal V3 solid red light, slow flashing internet light

[allsys]

Hi There,

Have a new sure signal box with serial number 40124141306 (new one with a plug in it). Was ok for a week or so then for no reason will not work. The light sequence is solid red light, then slow flashing white internet light with nothing else displayed. Please can you help me to resolve asap. Test results from troubleshoot guide below:

Ping - 29ms (Jitter 2ms)

Download - 4.2mbps

Upload - 0.67mbps

IP - 2.218.99.152

Tracert results:

[mrsfiregazer]

Well ive just had a conversation with a lady from technical support. She is saying that an upload speed of 0.9Mbps is too low and I should speak to my ISP and when asked about a whitelist knew nothing of it. Gettting nowhere here.

[grolschuk]

I'd say 0.9meg is fine as an upload speed... for people on normal ADSL 0.6 - 1.0 is a usual range.

Checking the whitelist for the Demon IP range is a good idea, being a major ISP, I'd hope they were already included.

The ISP themselves won't block any ports, but the router would do... Placing in a DMZ isn't always going to fix it.

Did the link to the other post make any sense? They were having exactly the same problem as you until they changed the router settings as described.

[mrsfiregazer]

Hi grolshuk,

thanks for the reply.

As it stands at the moment i have NAT filtering open and the SIP ALG disabled All the ports are still fowarded and the firewall settings set as in your link. The device is still the DMZ server.

Until I get a response from Vodaphone not really sure how to progress this TBH. It does seem that every man and his dog can get through to the device since putting it on the DMZ because of messages like the following in the log.

[LAN access from remote] from 219.235.0.185:6000 to 192.168.0.7:3306 Wednesday, August 13,2014 14:58:32 [LAN access from remote] from 23.95.27.231:6000 to 192.168.0.7:1433 Wednesday, August 13,2014 14:58:17

[LAN access from remote] from 178.20.39.119:53 to 192.168.0.7:6953 Wednesday, August 13,2014 14:55:16

[LAN access from remote] from 221.10.201.16:4830 to 192.168.0.7:23 Wednesday, August 13,2014 14:52:06

[LAN access from remote] from 221.10.201.16:4830 to 192.168.0.7:23 Wednesday, August 13,2014 14:52:00

[LAN access from remote] from 221.10.201.16:4830 to 192.168.0.7:23 Wednesday, August 13,2014 14:51:57

[LAN access from remote] from 125.68.45.32:49912 to 192.168.0.7:23 Wednesday, August 13,2014 14:51:27

but im also getting this message a lot

[SS3 port 4500 rule match] from 192.168.0.7:4500 to 212.183.133.179:4500 Wednesday, August 13,2014 15:06:53

[SS3 port 4500 rule match] from 192.168.0.7:4500 to 212.183.133.179:4500 Wednesday, August 13,2014 15:06:38

[SS3 port 4500 rule match] from 192.168.0.7:4500 to 212.183.133.179:4500 Wednesday, August 13,2014 15:05:59

[SS3 port 4500 rule match] from 192.168.0.7:4500 to 212.183.133.179:4500 Wednesday, August 13,2014 15:05:56

[SS3 port 4500 rule match] from 192.168.0.7:4500 to 212.183.133.179:4500 Wednesday, August 13,2014 15:05:36

As if the VSS3 is trying to talk to the server at Vodaphone and getting no response. I have no idea what port 4500 is used for. Steep learning curve for someone used to plug and play

Guess I'll just have to wait for a reply from one of the Tech Team and see if its a white list issue.

[mrsfiregazer]

Done a bit more digging while I wait and it appears that port 4500 is for IPsec NAT-Traversal. Found the following regarding this;

"During phase 1, if NAT Traversal is used, one or both peer's identify to each other that they are using NAT Traversal, then the IKE negotiations switch to using UDP port 4500. After this the data is sent and handled using IPSec over UDP, which is effectively NAT Traversal. The receiving peer first unwraps the IPSec packet from its UDP wrapper (the NAT Traversal part that occurred at the sending peer end) and then processes the traffic as a standard IPSec packet."

From the logs it appears my VSS3 is identifying itself to the Vodaphone server but getting nowt back. Will do a bit more reading whilst I wait ...... 

[DaveCD]

Hi mrsfiregazer.

The IP address is included on the whitelist.

I noticed that there had been a location change, I've reset this and resynchronised the device.

Please confirm the light sequence you are now seeing on the Sure Signal.

I would also recommend a reset as below:

• Press and hold the reset button for 10 seconds will factory reset the device. This will trigger the software reload and profile sync to the Sure Signal.

DaveCD

[mrsfiregazer]

So over the weekend I dug out my old netgear router DGN2000 and followed the same procedure of port forwarding and the device has connected and appears to be working ok. Following up with netgear to try and find out why the 3700v2 isn't working.

Like to thank everyone who helped out here.

[Retired-Laura]

Hi mrsfiregazer,

This is great news.

Thanks for the update.

Cheers,

Laura

[ezfones]

Hello,

I have the same issue but wonder if it could be a firewall issue? Could someone please have a look into it?

PING: 7MS

Download: 11.66

Upload 10.35

IP: 81.109.162.94

Serial Number: 42142818147

 

[mrsfiregazer]

hi,
are you using a netgear dgnd3700v2 as we'll?

if so then you may be suffering the same problem with port500 being used somehow by the router itself and not allowing it to be forwarded. I have logged this with netgear but am not really getting anywhere, think I may have to buy another router and use the netgear as a wifi repeater or door stop.

If when you forward your ports you add logging you should be able to see the device communicating via ports 4500 and 500 to the vodaphone servers.

[grolschuk]

If you are not on the router suggested above, and are using VM's Super Hub... Log into the router's advanced config pages, go to Security -> Firewall -> VPN, and enable vpn passthrough on IPSec (remove the tick if it is already there, add it if it is clear). Apply/Save the settings, reboot the super hub, then reset the suresignal, see if it gives any better results.