42
edits
Docs/OPNsense: Difference between revisions
m
→WAN
(add section and subnet for pfsync) |
m (→WAN) |
||
| (2 intermediate revisions by the same user not shown) | |||
|
{| class="wikitable"
!Subnet
!Main WAN IP
|-
|141.219.180.64/27
|141.219.180.69
|}
Our public IP subnet under Tech's <code>141.219.0.0/16</code> block.
|10.10.10.0/24
|}
OpenVPN can be used as a secondary admin/user option compared to wireguard or can be used for homelab routing. This allows devices on a members network to communicate directly with lug devices, depending on what is configured on the user side and the server's side.
=== Wireguard ===
<code>10.10.11.128/25</code> - Wireguard user range (access to only LAN)
All members can
Neither wireguard config should have access to the internet and are not intended for standard VPN traffic through LUG as an exit.▼
Endpoint networks can be configured as needed but OpenVPN may be preferred for this usecase as LUG/users can dynamically change routes/receive DHCP updates.
▲Neither wireguard config should have access to the internet.
=== pfsync ===
| |||