Actions
Forum Thread Details
  • Replies 9 replies
  • Subscribers 501 subscribers
  • Views 1118 views
  • Users 0 members are here
Related

VPN will it solve my problem?

colporteur

I have an Archer AX11000 router that can support a VPN. I need to provide credentials to a VPN server to complete the configuration. I recall using VPN's at work. The VPN enabled me to remote into the company network from the Internet. I would like to VPN into my home network.

I've long since retired and don't have access to the network brains that made it work at the company. I would buy them a coffee and float the questions. To access the company network we had a dongle that generated a code along with a username and password to use on the VPN concentrator. If all the magic worked my laptop at home was sitting on the company network.

I'm with hand-in-hand asking the brains in the E14 Community this network question. Does the Archer router VPN provide this same access? I would need to connect the router to a service like NordVPN. Once that is done can I use the VPN to get into my home network or would that require some other networking device?

Parents

  •   first I need some answers if it windows no luck (dont use it) But if you use a Linux distro, btw all I use here is Debian its a very easy thing what you want to do is install on host or sever put ssh server on it on your client put ssh client on it. Now the thing you will need is you fixed address of the host (server) and generate a key. put the info on the client. thats it.  check the web for more details ~~~ Cris.  

  • in reply to phoenixcomm

    I'd argue that an exposed Wireguard server for example, would be more secure than an SSH server. There are a huge number of "bots" scanning for exposed SSH servers and trying to brute force logins, causing significant load on the server. In comparison, a Wireguard server's exposed UDP port will never reply to requests unless properly authenticated, making it very very difficult(if not impossible) to even find the port of the server.

    If exposing an SSH server, it's a good idea to have port knocking and/or fail2ban set up at the very least.

Reply
  • in reply to phoenixcomm

    I'd argue that an exposed Wireguard server for example, would be more secure than an SSH server. There are a huge number of "bots" scanning for exposed SSH servers and trying to brute force logins, causing significant load on the server. In comparison, a Wireguard server's exposed UDP port will never reply to requests unless properly authenticated, making it very very difficult(if not impossible) to even find the port of the server.

    If exposing an SSH server, it's a good idea to have port knocking and/or fail2ban set up at the very least.

Children
No Data