Home
Help
Search
Login
Register
OPNsense Forum
»
English Forums
»
Virtual private networks
»
Wireguard - OPNsense Interface
« previous
next »
Print
Pages: [
1
]
Author
Topic: Wireguard - OPNsense Interface (Read 585 times)
spetrillo
Hero Member
Posts: 720
Karma: 8
Wireguard - OPNsense Interface
«
on:
July 25, 2023, 03:48:28 pm »
Hello all,
I am beginning to use Wireguard for C2S communication and it seems to work well. I have a wg1 device that was created in the Interfaces section of OPNsense, and labeled Wireguard. Now I am about to embark on trying to get a S2S connection going. Do I need a second interface in the OPNsense Interface section, for what will be wg2, or does the S2S connection not need this?
Thanks,
Steve
Logged
Maurice
Hero Member
Posts: 1212
Karma: 158
Re: Wireguard - OPNsense Interface
«
Reply #1 on:
July 25, 2023, 05:11:23 pm »
Depends. An interface (wg1, wg2, ...) gets created by WireGuard for each local instance. Assigning these interfaces (Interfaces: Assignments) is optional. If the routes created by WireGuard are sufficient and you only want to add firewall rules to
WireGuard (Group)
(which apply to all WireGuard instances), then you don't have to assign the wg interfaces at all.
Logged
OPNsense virtual machine images
OPNsense aarch64 firmware repository
Commercial support & engineering available. PM for details (en / de).
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
English Forums
»
Virtual private networks
»
Wireguard - OPNsense Interface