Now that I have WireGuard up and running and can connect from work to home I was wondering what else WireGuard could be used for and I thought about the LAN parties I used to attend/host in the late 90's.
So my question (hypothetical, no intention to actually do this, it's purely because I am interested in how this works) is:
Given my home LAN at 192.168.2.x and my WireGuard internal server IP at 10.64.0.1, how would I set up a home gaming LAN at say 10.50.0.x that others could join and the only thing they could see is that very network and the server on it that would be running there. Others should not be able to see (not even when guessing) my 192.168.2.x network, really only 10.50.0.x.
I assume I would have to somehow create this 10.50.0.x network, but how? What firewall rules (if any) would I need to add to router to prevent others from accessing the 192.168.2.x network? Would I need to create a dedicated WireGuard client file (.conf) that I would give to those wanting to join the LAN party? What settings would it need?
Again, this is just a hypothetical use case which allows me to better understand how this all works. Thanks in advance for any replies.
WireGuard + LAN party
Moderator: Moderators
Re: WireGuard + LAN party
Gaming usually requires the lowest ping possiable
Adding a VPN will most likly increase the ping rate
I suspect if you have really good hardware i won't make any difference
Adding a VPN will most likly increase the ping rate
I suspect if you have really good hardware i won't make any difference
Re: WireGuard + LAN party
This is a little out of the scope of Gargoyle unfortunately as you're now adding additional networks which aren't UI supported.
It can be done but it might be very quickly undone the next time you press Save Changes anywhere.
What you're wanting to do is a bit like what we used to use Hamachi for back in the day.
I would set up WireGuard and issue client keys to all of my participants and let us all run on the 10.64.0.1/24 subnet (including yourself). This prevents you needing to allow routing into your LAN subnet for protection.
Firewall rules for extra protection.
You could set up a second WireGuard interface as well, I think Gargoyle is keyed off "wg0" and would not touch anything if you established it as "wg1" or "wglanparty" (keeping in mind maximum interface name lengths).
Again not in the GUI.
It can be done but it might be very quickly undone the next time you press Save Changes anywhere.
What you're wanting to do is a bit like what we used to use Hamachi for back in the day.
I would set up WireGuard and issue client keys to all of my participants and let us all run on the 10.64.0.1/24 subnet (including yourself). This prevents you needing to allow routing into your LAN subnet for protection.
Firewall rules for extra protection.
You could set up a second WireGuard interface as well, I think Gargoyle is keyed off "wg0" and would not touch anything if you established it as "wg1" or "wglanparty" (keeping in mind maximum interface name lengths).
Again not in the GUI.
https://lantisproject.com/downloads/gargoylebuilds for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
https://lantisproject.com/blog
Please be respectful when posting. I do this in my free time on a volunteer basis.
https://lantisproject.com/blog
Re: WireGuard + LAN party
not yetAgain not in the GUI.