V3 Problems (Power flashing & solid Amber Service light)

[Hambroski]

Please  note that this is a different problem to the one raised for a different serial number v3 unit.

I am trying to install 40124108412 and 40124107836 at PE31 8AE.

The FAQ does not appear to be relevant due to not covering v3 and also not covering the symptom.

I previously had a v1 box 21196758813 working here fine.

On both V3s I get a flashing red and a solid amber on the service light. No sign of internet and user lights.

I have amended the router to allow port access for:

Port 50 - TCP/IP
Port 4500 - UDP
Port 500 - UDP
Port 123 - UDP

Port 8 - TCP/IP

Port 1723 (BT Customers only) - TCP/UDP

My IP Address is:86.133.19.212

Speednet - 38ms Download 6.8mbps Upload 0.34mbps

Pingtest - 0% lost, Ping 37ms, Jitter 9ms

I have put one in the DMZ but this makes no difference. 

Traceroute via the router shows:

traceroute to 212.183.133.177, 30 hops max

  1  217.47.93.250         40 ms

  2  217.47.93.161         30 ms

  3  213.1.69.86           30 ms

  4  217.41.168.102        40 ms

  5  217.41.168.49         30 ms

  6  217.41.168.107        30 ms

  7  109.159.249.64        30 ms

  8  109.159.249.33        40 ms

  9  213.121.193.97        30 ms

 10  195.66.224.124        40 ms

 11  85.205.116.6          40 ms

 12 Request timed out.     *

 13 Request timed out.     *

Trace complete.

Please can you help

[r5ingh]

Hi,

I'm here to leave this for staff and anyone else who is in the same predicament as me. 

I was looking to configure my new V3 SureSignal to bypass a newly setup VPN client on my rt-n66u running TomatoUSB firmware. I believe the SS works fine with Tomato (using upnp) if there isn't a VPN set-up. Anyhow to let the SS bypass VPN tunelling this is what needs to be done:

This is a permanent solution that survives reboots:

Goto devices and determine your SS DCHP IP, it also helps to add a static reservation for the assigned IP so that your config will work for the forseable future... 

1. Go to TOOLS - SYSTEM - EXECUTE SYTEM COMMANDS and create a nvram variable wich will contain a list of the IP Addresses you want to filter, like this:

nvram set no_vpn_lst="192.168.1.11" (note you can add multiple IPs to this list....)
nvram commit

Copy the contents of the following script and paste to ADMINISTRATION - SCRIPTS - WAN UP, click Save

#!/bin/sh
sleep 30
NO_VPN_LST=`nvram get no_vpn_lst`
[ -z $NO_VPN_LST ] && exit 0
WAN_GWAY="0.0.0.0"
while [ $WAN_GWAY == "0.0.0.0" ]; do
sleep 3
WAN_GWAY=`nvram get wan_gateway`
done
ip route add default via $WAN_GWAY table 10
for ipa in $NO_VPN_LST; do
ip rule add from $ipa table 10
done
ip route flush cache
exit 0

Now save and reboot!

I hope this helps someone, as it did me! Thanks to VF staff for helping everyone out!

[Mark_B]

Thanks for this post, good to see its working.

Are these the Open DNS servers?

Did the Router work with the ISP using PPPoE?  I would be surprised that your service provide goes both ways from PPPoE to PPPoA automatically, i.e. you've changed the Layer 2 from Ethernet to ATM.  Yes, VC Based mux is the most common UK configuration for PPPoA.

Mark.

[Nikon]

I am with BT Connect, ADSL, obviously not Infinity, (just yet, another story).

Yes, the connection was previously established  using PPPoE, and LLC based, it has been like this for over a year, with no obvious issues.

The two DNS servers I used  and stated above are listed under the BT support site, they have multiple pairs and so I picked the lowest of the lot!

Will see if all is OK overnight and undo the changes one at a time to see if I can see what, (if anything) is significant.

[Nikon]

Update!

Well,  I reverted Netgear DGND3700v1 settings back one-by-one, power cycling the VSS after each change;

1)  Multiplexing method from VC based to LLC based. VSS connected OK.

2)  Changed encapsulation back from PPPoA to PPPoE. VSS connected OK.

3)  Went from manually specified DNS servers, to Auto ISP, this assigned  62.6.40.178 and 194.72.9.34. VSS connected OK.

So I am back where I was, but now it works!! Typical! The only thing I changed also in the previous 24 hours was my assigned IP address. Not that it makes any difference, it was 192.168.1.15 and now 192.168.1.12. I edited the firewall settings to reflect this change. "Maybe" there was something in that, but I very much doubt it was the case as I'd been through it a million times, believe me!!

Port Forwarding / Port Triggering

Please select the service type.

Port Forwarding  O

Port Triggering

6	VSS1	8	8	192.168.1.12
7	VSS2	50	50	192.168.1.12
8	VSS3	123	123	192.168.1.12
9	VSS4	500	500	192.168.1.12
10	VSS5	1723	1723	192.168.1.12
11	VSS6	4500	4500	192.168.1.12

So, all things considered I really can't explain why it works today, but simply refused to over previous weeks.

[Mark_B]

A very interesting report, many thanks for posting it.  Having an error that cannot be recreated is very annoying.  Well done for recording the steps you took and rolling back as a check, most people would not bother.

Mark.

[robinv2]

Just a note to say I've taken mine back to Curry's who were completely fine about refunding the wretched Netgear router even though it had been about 7 weeks since purchase - so i big-up for them!

Netgear continue to apologise for the delay in solving my issue and have now "closed" the case - nice.

I'm going to continue with a DLink moden and Dlink router which works flawlessly.

Thanks for all the help - i hope you come up with a solution at some point.

[groovio]

You will find that without doing any change to a router (in my case the draytek 2820) the VSS will work even though it refused to work on it for the past 3 months - simply because I let it do its profile download through another simple router.

So bottom line .. get your VSS profile done on a router on which it works then take it back to your difficult but oh so better router and it will work.

You do not need to open ports or mess with DNS or whatever......

[Hambroski]

Hi Grovio, do mean plug it in to someone else's router?

Thanks,

[groovio]

Yes in my case I bought another router (cost me £20).... which is the preferred option as the profile in terms of WAN settings will be the same (if any)... .

You could try someone elses router as well.. if it works on theirs (after the initial wait) then take it back to yours and try it.

What the VSS makers should do is add a log viewable either via a web interface or a simple text dump.

[Nikon]

Groovio,

Interesting what you say about downloading the profile, however, in my case I downloaded on another network the profile and verified the VSS worked. When I installed on my network, despite having a profile installed it failed to connect. After playing around the VSS downloaded the profile and has worked ever since. It also has re-downloaded the profile on the Netgear DGND3700 several times after a reset. There is something strange I admit....

Also, I just realised that I have actually opened both UDP and TCP for all 6 ports on my firewall, which was another "change" to what I have posted on here previously.