Apple Airport Extreme/Time Capsule port forwarding settings for VSS

[foucault5]

I've been through a lot of threads on this and the party line seems to be different each time (range from "buy new hardware" to "set up port forwarding" to "just kill yourself now and save time later") - is there an agreed fix?

Like many others experiencing the problem I've just upgraded to BT Infinity (via Plusnet in this case) using the standard BT Fibre modem and connecting to an Apple Time Capsule using ethernet. Both ethernet and wifi devices on my home network work fine. Except our friendly VSS version 1, naturally which has now hit the solid/flashing power light only stage, following plenty of soft/hard resets and waiting.

What I can work out so far is as follows:

VSS may need private IP address reserving despite/because of running DHCP. I've reserved it 10.0.1.66 which is within my DHCP range and put in the right MAC key. From everything I can find, that seems right.

VSS needs various ports forwarding. This is where it all goes a bit wrong, because the guidance on this forum and on portforward.com where a number of posts link provides guidance for setting the ports on v5.x of Airport Utility (I think). v6.x allows IPv4 Port Mapping and gives the following fields:

Description [I assume I can pick what I like, and have used VSS here]

Public UDP Ports

Public TCP Ports

Private IP address [I've put the static assigned address 10.0.1.66 here - is this right?]

Private UDP Ports

Private TCP Ports

It seems that the ports I need to forward are 8 50 123 500 4500 1723 (again, from other posts here). Can anyone translate this into AirPort Utility fields as per above? I don't know what the distinction between public and private or UDP and TCP is in this context. Also don't know what the separator is for multiple ports: space, comma, something else?

I don't really understand anything much about network configuration and have got this far with help files and exploring AirPort Utility. Would really appreciate it if anyone can just give a simple box-by-box fix to get this going.

thanks

[Retired-Andy]

Hi foucault5,

Was this thread one of the ones you looked at? If not, can you give the suggestions a go. If it doesn't work for you can you take a look at our Sure Signal Troubleshooting thread.

If this doesn’t resolve your query, please post your reply either below, or in the relevant thread, together with the details requested, including the following information.

Your speed test results from here.
Your ping test results from here.
Your external IP address from here.
The results of a traceroute.
Your Sure Signal serial number:

VSS Traceroute command

On a PC:

Click on Start and select Run
Type CMD into the Run box and press enter/click ok
A black box will appear.
In this box type tracert 212.183.133.177 press Enter
Paste the output of this command into your reply.

This will help us get the quickest possible resolution for you.

Thanks

Andrew

[foucault5]

Hi Andrew

Thanks for the reply. I've looked through that thread but I would rather solve this with existing hardware if possible rather than introducing an extra router into the chain or buying a new modem. I couldn't find any suggestions going beyond hardware changes so have run the tests you requested.

Ping is 28ms, download 20.05Mbps and upload 15.02Mbps (we like BT Infinity...)

IP address 87.115.75.19

SS serial number 21225084611

Traceroute:

traceroute to 212.183.133.177 (212.183.133.177), 64 hops max, 52 byte packets
 1  10.0.1.1 (10.0.1.1)  0.517 ms  0.322 ms  0.246 ms
 2  lo0-central10.ptw-ag04.plus.net (195.166.128.194)  12.512 ms  7.267 ms  9.939 ms
 3  link13-central10.ptw-gw01.plus.net (84.93.248.120)  7.240 ms  6.784 ms  7.501 ms
 4  xe-10-0-0.ptw-cr01.plus.net (212.159.1.40)  6.932 ms  6.885 ms  6.696 ms
 5  ae2.ptw-cr02.plus.net (195.166.129.5)  6.699 ms  6.685 ms  6.462 ms
 6  ae2.ptw-cr01.plus.net (195.166.129.4)  43.254 ms  8.034 ms  6.480 ms
 7  lndgw2.arcor-ip.net (195.66.224.124)  10.990 ms  9.290 ms  12.189 ms
 8  85.205.116.14 (85.205.116.14)  8.985 ms  7.836 ms  7.720 ms
 9  * * *
10  * * *

[everything from 9 onwards times out]

Let me know if you need anything further - otherwise, suggestions welcome.

thanks

[Jenny]

Hi foucault5,

Thanks for getting back to us.

Everything looks fine as far as I can tell.

Could you have a look at this thread and let me know if it resolves the query?

Thanks,

Jenny

[foucault5]

Jenny

Sorry about the long absence... I tried a lot of things, none of which worked, so gave up for a while.

The thread you've linked simply suggests buying new hardware, which I don't really want to do. Is there a Vodafone line on the settings a router needs when talking to BT Infinity via PPPoE or is the party line simply that it doesn't work without a specific (non-standard) cable modem? I've had a look through the threads but can't see any new solutions since February.

thanks

[Retired-Kay]

Hi foucault5, 

We are aware of an issue with BT Infinity broadband routers and are investigating this. I'd recommend subscribing to this thread for updates. 

If possible please test the Sure signal on a different Internet connection (at a friend/family members) so that we can rule out a hardware fault. 

Thanks, 

Kay