On Sun, 16 Feb 2014 10:59:10 +0000, tony sayer wrote:

In article om,
dennis@home scribeth thus
On 15/02/2014 11:09, David.WE.Roberts wrote:
I now have my Virgin SuperHub2 set to accept incoming calls to a DMZ
(RPi running a VPN server).

I used 'shields up' to check what the ports were doing.

Now without DMZ turned on everything is stealthed.

With DMZ turned on Port 22 (ssh) and Post 1723 (pptpd for VPN) are
both opened automatically.

The rest go to 'closed' instead of 'stealthed'.

The opening of the two ports seems reasonable for an instant DMZ, but
I am puzzled why the other ports now show as 'closed'.
AFAIK a 'closed' port will show up on a port scan by 'bad people'
whereas a 'stealthed' one will not.

Last time I looked you got a different response from the final router
for a destination that wasn't there and for one that didn't respond.
That is you can stealth your ports but someone can still tell you are
there.



Think I'm missing a post here;(..

Can the OP explain again just what it is he's looking to do, as if its
VPN's over cable systems they can be done without any fuss at all.

Or is he after something else?..

I wish to run a VPN server at home, to allow connection into my home LAN
then out again, so that the call looks to be coming from my home network.

Useful when you are abroad and sites refuse to talk to non-UK IP addresses.

Now implemented using the DMZ feature of the Virgin SH2, which forwards
all incoming calls to a selected IP address, and a Raspberry Pi as the VPN
Server.

My concerns now centre on the way the SH2 implements the DMZ feature.

HTH

Dave R