Guide for configuring vpn2 using pfsense. Host already connected using linux
-
I've read that three times now and I still have no idea what you really want to do. Maybe a network diagram would help. I will say that such connections usually use IPSEC to do site-to-site VPN. Your VPN provider likely has a guide on how to configure your router for IPSEC to connect with them.
-
I am not sure how I could draw a diagram to better explain my desires. If I setup a pfsense VM using a second VPN provider then the sites I visit would see THAT IP instead of vpn1's. I am trying to add hops to better conceal my original location and be more difficult to trace. Ultimately I want to use at least 3 vpns for this purpose. I don't want to get political here but I have a need for such a configuration. I know this can be done quite easily in a fully bridged setup because I have friends that do it.
For now lets stay with one additional vpn and then I'll build from there if I can get at least two working. Hope this clears things up some. I don't know all the fancy jargon so bear with me please!
-
OK I think I understand what you are trying to do. Too bad for you that I have no idea how to do it :-[
-
OK, thanks for taking the time to read through it.
So, anyone else that can jump in? Is the confusion because I want to create virtual routers in VM's? If I had the physical nic's I would bridge but I don't.
-
When setting up a vm guest, if you dont want vpn2 to go through vpn1 which is on your host/baremetal, bridge the vm guest, that basically shares the physical network card although the host OS will still see network traffic passing over it from another OS.
If you want to send vpn2 through vpn1, then use nat and the virtual software should route you through vpn1, giving you what I suspect you want if you mean nested as in sending vpn2 through vpn1.
Depending on what you use to run your vm guests in this may be easy or hard, it depends on your virtualisation software used.
-
If you're really that paranoid, ditch the VMs and rent several VPSes from different providers around the world and then chain your connections through them via IPSEC.
-
"I am trying to add hops to better conceal my original location and be more difficult to trace"
How would nested vms do that?? Dude really seems like your tinfoil hat shrunk in the wash or something JFC…
"I don't want to get political here but I have a need for such a configuration."
BS BS BS.... Who exactly are you wanting to hide from?? Create you vpn to your trusted enpoint.. Done!
-
Harsh comments would be an understatement! I just wanted to learn something useful.
I am sorry to have bothered you guys.
Admins, please feel free to close or delete this thread. VERY disappointed!!
-
You're not a bother but we don't think you can do what you want to do. Plus we don't really care what your purposes are. If you need to hide behind 12 proxies so you won't get sued by the MPAA for running a zillion torrents, whatever. But it's hard to give best advice when you're being cagey about your end goals and what you're doing.
-
Nested VMs on your side would do NOTHING to hide your connection point.. Hiding your traffic from your connection provider requires just one layer of encryption. putting a tunnel inside a tunnel inside a tunnel is pretty pointless..
Create a tunnel to a trusted endpoint on the outside of your connections providers network. If you then want to bounce a connection off of that through multiple proxies, turn tor through that connection even to hide your actual connection point from the tor network or proxies you use.
But running nested vms to accomplish this goal is just wasted resources time and performance.
