42
edits
Docs/OPNsense: Difference between revisions
m
→WAN
No edit summary |
m (→WAN) |
||
| (7 intermediate revisions by 3 users not shown) | |||
|
'''For Layer 1 network details, see [[Docs/Cables]].'''
We have two OPNsense devices, Lasagna and Ravioli.
== Network ==
{| class="wikitable"
!Subnet
|-
|10.10.0.0/24
|}
OOB Management services like [https://www.dell.com/en-us/lp/dt/open-manage-idrac Dell iDRAC] / [https://www.hpe.com/us/en/hpe-integrated-lights-out-ilo.html HP iLO] and internal networking hardware.
{| class="wikitable"
!Subnet
|-
|10.10.1.0/24
|}
Servers and Virtual Machines.
{| class="wikitable"
!Subnet
!Main WAN IP
|-
|141.219.
|141.219.180.69
|}
Our public IP subnet under Tech's <code>141.219.0.0/16</code> block.
{| class="wikitable"
!Subnet
|-
|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 ===
{| class="wikitable"
!Subnet
|-
|10.10.11.0/24
|}
<code>10.10.11.0/25</code> - Wireguard admin range (access to LAN+Management)
<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.
=== pfsync ===
{| class="wikitable"
!Subnet
|-
|10.10.250.0/24
|}
Interface used for High Availability (HA) sync between the 2 firewalls.
Cannot communicate with any other subnet.
▲Neither wireguard config should have access to the internet.
== OPNSense ==
| |||