Ten years ago I would have recommended Ubiquiti as router and firewall, but they have gone to the cloud now.
How so?
All my Ubiquiti stuff runs entirely locally. There is one exception, which is their doorbell, that requires a (free) UI cloud login to enable push notifications to my phone. It is one of the reasons I like them.
You can enable a cloud login to act as an administrator, I do that for some charities I help out with. They have UniFi kit and I can get alerts to issues and make changes as needed for them via the cloud login. The cloud service acts as a proxy to their local on premise controller, confusingly called a cloud key or cloud gateway, despite not using the cloud for any of the configuration data. I could also VPN onto their LAN and do it "locally", either is fine.
I've recently moved back to using a UnFi router from a MikroTik, hard to ignore the performance of some of the new routers.
I want to set up a hardware (router) based VPN at the lab and at home (plus my Android phone).
What do I need?
I know I could just get any of the dozen software based VPN's that are advertised constantly, but I think that having hardware just do it at the router level is way cooler.
I presume my phone will need one of those software options though.
My home router supports OpenVPN and PPTP
My lab router is an old TP-Link C1200 and Google Gemini seems to think it's capable using OpenVPN via tplinkwifi.net ?
I also have my dedicated server in the US, so can potentially set up a VPN via that server box I presume?
Dave, I would stay away from any of SOHO routers as front end to the Internet.
The AX6000 from TP-LINK may be a good AP choice at home, but I wouldn’t trust it as a router,
the AX6000 can be configured as AP only and link with decent router.
Dave, I would stay away from any of SOHO routers as front end to the Internet.
The AX6000 from TP-LINK may be a good AP choice at home, but I wouldn’t trust it as a router,
the AX6000 can be configured as AP only and link with decent router.
Why?
My only goal is to have an IP address on all machines at home and the lab (plus phone) that is not Australia.
Ten years ago I would have recommended Ubiquiti as router and firewall, but they have gone to the cloud now.How so?
All my Ubiquiti stuff runs entirely locally. There is one exception, which is their doorbell, that requires a (free) UI cloud login to enable push notifications to my phone. It is one of the reasons I like them.
You can enable a cloud login to act as an administrator, I do that for some charities I help out with. They have UniFi kit and I can get alerts to issues and make changes as needed for them via the cloud login. The cloud service acts as a proxy to their local on premise controller, confusingly called a cloud key or cloud gateway, despite not using the cloud for any of the configuration data. I could also VPN onto their LAN and do it "locally", either is fine.
I've recently moved back to using a UnFi router from a MikroTik, hard to ignore the performance of some of the new routers.
If you're looking to build a new router, pfSense is my recommendation. Runs on normal Intel-based hardware. Supports Wireguard as well.
Dave, I would stay away from any of SOHO routers as front end to the Internet.
The AX6000 from TP-LINK may be a good AP choice at home, but I wouldn’t trust it as a router,
the AX6000 can be configured as AP only and link with decent router.
Why?
Dave, I would stay away from any of SOHO routers as front end to the Internet.
The AX6000 from TP-LINK may be a good AP choice at home, but I wouldn’t trust it as a router,
the AX6000 can be configured as AP only and link with decent router.Why?They're a perpetual vulnerability engine. Google $router-brand + "vulnerability" to see all the horror stories. And they're typically never patched or fixed via press release, "oh, that's gone out of support in the two weeks since it was released, you'll have to buy a new model and see if that fixes it".
Dave, I would stay away from any of SOHO routers as front end to the Internet.
The AX6000 from TP-LINK may be a good AP choice at home, but I wouldn’t trust it as a router,
the AX6000 can be configured as AP only and link with decent router.Why?They're a perpetual vulnerability engine. Google $router-brand + "vulnerability" to see all the horror stories. And they're typically never patched or fixed via press release, "oh, that's gone out of support in the two weeks since it was released, you'll have to buy a new model and see if that fixes it".
Wouldn't that be the same for every router, ever? At some point it's going to get discontinued for support.
Finally got some time to respond here properly
@EEVBlog, there is no such thing as a "hardware VPN" device, in years gone by there was when it was important to offload the VPN workload to a hardware device to accelerate the encryption, but these days there is no advantage to using a "hardware" device. They are all embedded Linux devices running VPN client software.
If anything there is a very very good reason to avoid them, which is outdated software and vulnerabilities. Unless your spending big for a enterprise grade device with a support contract, they are not worth touching. You're better served recycling an old PC and installing pfSense or similar which will not only be practically free, but cutting edge and maintainable. Your recycled PC becomes your "hardware VPN" device with more power then any cheapo TP-Link like device.
In the past I have used Wyse Thin Clients for this purpose (They are just embedded PCs in a small form factor), pfSense sings along on them very well and can easily cope with the traffic for most small to medium sized businesses (think, 25+ users). The only downside here is they usually only have one Ethernet port, which can be limiting and confuse new users on how it could still be viable (ie, VLANs).
If you're willing to spend a bit of cash on something decent, there are fully integrated industrial PCs on AliExpress that are absolutely perfect for this, for example:
https://www.aliexpress.com/item/1005008165245304.html
(Attachment Link)
Finally got some time to respond here properly
@EEVBlog, there is no such thing as a "hardware VPN" device, in years gone by there was when it was important to offload the VPN workload to a hardware device to accelerate the encryption, but these days there is no advantage to using a "hardware" device. They are all embedded Linux devices running VPN client software.
If anything there is a very very good reason to avoid them, which is outdated software and vulnerabilities. Unless your spending big for a enterprise grade device with a support contract, they are not worth touching. You're better served recycling an old PC and installing pfSense or similar which will not only be practically free, but cutting edge and maintainable. Your recycled PC becomes your "hardware VPN" device with more power then any cheapo TP-Link like device.
In the past I have used Wyse Thin Clients for this purpose (They are just embedded PCs in a small form factor), pfSense sings along on them very well and can easily cope with the traffic for most small to medium sized businesses (think, 25+ users). The only downside here is they usually only have one Ethernet port, which can be limiting and confuse new users on how it could still be viable (ie, VLANs).
If you're willing to spend a bit of cash on something decent, there are fully integrated industrial PCs on AliExpress that are absolutely perfect for this, for example:
https://www.aliexpress.com/item/1005008165245304.html
(Attachment Link)
Thanks. I've got several of those new Beelink mini PC's sitting doing nothing, and they have dual ethernet ports.
So I just install pfSense and insert inline between my NBN modem and my router and that's it?
So I have to subscribe to pfSense and pay per US$0.08/hr? That's almost US$60/month, or US$120/month for home and work. Seems pricey?
Finally got some time to respond here properly
@EEVBlog, there is no such thing as a "hardware VPN" device, in years gone by there was when it was important to offload the VPN workload to a hardware device to accelerate the encryption, but these days there is no advantage to using a "hardware" device. They are all embedded Linux devices running VPN client software.
If anything there is a very very good reason to avoid them, which is outdated software and vulnerabilities. Unless your spending big for a enterprise grade device with a support contract, they are not worth touching. You're better served recycling an old PC and installing pfSense or similar which will not only be practically free, but cutting edge and maintainable. Your recycled PC becomes your "hardware VPN" device with more power then any cheapo TP-Link like device.
In the past I have used Wyse Thin Clients for this purpose (They are just embedded PCs in a small form factor), pfSense sings along on them very well and can easily cope with the traffic for most small to medium sized businesses (think, 25+ users). The only downside here is they usually only have one Ethernet port, which can be limiting and confuse new users on how it could still be viable (ie, VLANs).
If you're willing to spend a bit of cash on something decent, there are fully integrated industrial PCs on AliExpress that are absolutely perfect for this, for example:
https://www.aliexpress.com/item/1005008165245304.html
(Attachment Link)
Thanks. I've got several of those new Beelink mini PC's sitting doing nothing, and they have dual ethernet ports.
So I just install pfSense and insert inline between my NBN modem and my router and that's it?
So I have to subscribe to pfSense and pay per US$0.08/hr? That's almost US$60/month, or US$120/month for home and work. Seems pricey?
You don't have to pay a dime for pfSense, only if you want support.
And yes, just put in in-between, there will be some configuration required. Ideally you would put the router into "Bridge Mode" too if you can, this way the pfSense box becomes the router, and the NBN modem/router just becomes a dumb modem. You will need the authentication details from your ISP for this though as you will need to put them into pfSense.
I recommend you don't change your network at all initially, put pfSense on it, treat your LAN as if it's the WAN, and put a PC/Laptop on the new "LAN" interface for testing/configuring/verification, etc.
If I were closer i'd come and give you a hand, doing this for the first time can be quite a chore as it's a pretty steep learning curve. If I were you, i'd take up @Halcyon on his offer for help.
Grok said if I want VPN capability I need to use one of the third part services like Nord, ExpressVPN etc?
pfSense has multiple VPN clients available to it and can connect to most of the offerings out there. It really depends on your usage requirements.
1) If you want to link your home to your lab, you need a corporate VPN service, or run your own, which is what I would do. In your office you'd setup pfSense to be a VPN server, not client.
2) If you are intending to route your traffic through another country for your entire network to bypass network/geo restrictions, you would need to use one of these services, or rent a VPS in one of these countries and setup a VPN server for your own usage.
If you setup your gateway to route your traffic via a VPN, this will affect every device on your LAN, not just your PC. Generally when you want to bypass a network/geo restriction you'd just use a VPN client on your own PC for that temporary session. Routing your entire network through a VPN service will slow things down considerably, no matter how fast they claim to be (remember, 200+ms from AU to US minimum).

Is that router ISP supplied, or one you threw in there?