Plusnet: Stop blocking my incoming VPN connection.

[#1]

---

@7up wrote:

It has bugs! Factory reset doesn't wipe 200 odd pages of logging either. It should! That's what a factory reset is supposed to do right? - Put it back to factory new condition..

---

You did unplug it  - didn't you ?

[#2]

For what it's worth I found the factory reset found in the gui doesn't work where as the pin hole reset does

[#3]

---

@Dan_the_Van wrote:
For what it's worth I found the factory reset found in the gui doesn't work where as the pin hole reset does

---

That may be why it still has logs then - but even so, factory reset should mean factory reset. If it doesn't do a factory reset then it's a bug.

[#4]

The naritive in GUI does suggest a full factory reset.
When I was in support we'd call something like this a feature, that way no fix would provided.

[#5]

@bobpullen Well scratch that, your router is blocking traffic A_G_A_I_N.

Direct from the event viewer:

The other night once I established that your device had decided to go by device name rather than the static-set IP address and reset it back to IP for port forwarding, I was able to connect my phone via vpn around 8 times. Obviously though, this was not away from home (which as previously noted, seems to be where the trouble starts).

Now today, I turn on the computer, go out with the missus, while we're out try to connect to the PC from my phone.. nothing. Repeated attempts.. nothing.

Get home, here we go, Windows itself is saying that the router is probably the fault. Yes, I've tried port clamping on the VPN page of the hub - no difference.

Kindly explain to me how the router decided to redirect ports to 'Atlanta' in the first place instead of 192.168.1.2 and how once discovered and updated, HOW IS IT BLOCKING ME YET AGAIN. Has someone at Plusnet HQ been remotely tinkering?

I want some answers, I've had enough of this [-Censored-] now.

[#6]

@bobpullen still can't connect again.

Whats changed since the other night when i got it working? - I've not tinkered, that only leaves your organisation with the ability to do so.

What has happened to block my access again?

[#7]

@bobpullen this was NOT me - just seconds ago..

I'm in the router right now and see no unknown devices connected. That means it's got to be coming from somewhere.

If it's not me and it's not anyboy else local.. 

Care to explain?

EDIT: I've removed it.. but note the spelling mistake in the log (seriously this log file really needs to be more user friendly)

[#8]

and here we have conclusive proof... my phone is blocked by IP address:

Plusnet if you want to block me again, the IP ending .233 is the one i'm currently on.

[#9]

while we're out try to connect to the PC from my phone.

Is this your recent Android 14 purchase? I thought L2TP was dropped in that version.?

[#10]

No, that doesn't have support for older VPN protocols.

I'm using my trusty old Android 5 device which has never had issues connecting in the past. Yes it's old but it never messes about.

[#11]

Not sure if it helps, I created a port forward rule 42150 TCP/UDP here are the log entries of the rule being created, also with me testing the the rule using https://www.yougetsignal.com/tools/open-ports/ 

What is significant of the above test I do not have any device which uses that port, the port checker fails but the Hub reports an accepted inbound connection.

A working port forward rule message would look identical but the port checker would show a successful connection.

I would really be helpful if the message included a NAK for when the destination IP Address is down or the connection failed.

Have you considered dumping L2TP for something else? I have two Wireguard VPN servers, one is a Oracle Virtual Box guest system and the second is an old Raspberry Pi model 2. All is required for each is a single UDP port forward rule, the config scripts allows for the setting of a unique port for each server, importantly NOT the application default port. I have a static IP Address but it does support DDNS 

See https://www.pivpn.io/ 

HTH

[#12]

Well until the recent woes I've never needed to think of another VPN.

I've never had issues until recently when the Plusnet router seems to be determined to block me from having access to my own computer. I'm fed up with it.

[#13]

I was suggesting a pragmatic approach to your issue, I personally would not be comfortable with so many 'common  ports' open to the public internet.

Might I suggest a less angry tone when you are looking for help?

[#14]

See this from my POV, for years I've had this working flawlessly and suddenly it stops. I've literally had to chase my tail round repeatedly trying to find the fault, then find the router is playing games with me for no reason.
I shouldn't have to put up with that, I changed nothing!

[#15]

With regard to the common ports, I've had Apache web server running on my pc for years and none of those sites have been breached.

I run an FTP server on it too.

Who said I've got common ports open? - you can redirect external ports to different ports inside the network as I have for incoming rdp connections.