interfaces->assignments missing add button
-
@passerby Those are not dedicated interfaces but a 4-port switch.
https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/switch-overview.html -
Hello. Have you resolved your issue? if yes, how? Thank
-
The Plus button only appears if there are unassigned interfaces available to add. In the 2100 all interfaces are assigned by default.
What are you trying to do?
Steve
-
@stephenw10 said in interfaces->assignments missing add button:
The Plus button only appears if there are unassigned interfaces available to add. In the 2100 all interfaces are assigned by default.
What are you trying to do?
Steve
I want to use protected router/firewall VMs as VPN clients to route one VPN tunnel through another. This is necessary to isolate fields of activity from each other, complicate profiling and surveillance, and also to reduce harm from malware and hacks.
-
Ok. At a more basic level though you are trying to add new interfaces and there is no add button?
What interface are you trying to add?
What do you expect to see?
-
like this picture. But I don't have "add" -
So you're trying to assign a bridge as an interface? Did you create the bridge already?
-
@wall need to add the OPT1 interface
-
@stephenw10 yes, created
-
Did you create an interface to add? The plus button won't appear until there are unassigned interfaces to add. That means creating on, like a bridge, first.
-
@wall This is an image from Google, for example. Sorry
-
Ok, so what do you actually see? What are you trying to do?
-
@stephenw10 I created a pfSense virtual machine, installed the OS, configured a working VM on the internal pfSense network. Next, I installed the WireGuard plugin. To configure, I used the VPN provider’s ready-made configuration file...
-
@wall At the stage of assigning a network interface, I encountered the absence of an “add” button. I don't know what could be the reason
-
The tun_wg0 interface either doesn't exist or is already assigned.
Do you see it in the dropdown selection for WAN/LAN?
-
@stephenw10 said in interfaces->assignments missing add button:
The tun_wg0 interface
That's right. The tun_wg0 interface has not been assigned. Thank you! But now the problem is the “handshake” - it’s red, not green... don’t know
-
Something is misconfigured in the WireGuard setup then. Unfortunately there is almost no debug logging in wireguard.
-
@stephenw10 I'm sorry. But I still don’t understand the reason for the red and not green handshakes.
My situation: my host PC is connected to the "IVPN" client, OpenVPN protocol. Installed the pfSense virtual machine and Linux VM. By default, the VM's network adapters are connected to NAT. That is, they use the active network gateway of the host machine.. Next, I created an internal network in the VM pfSense settings in “Adapter 2”. Next, I changed the Linux VM network from NAT to the internal pfSense network. Launched VM's.
From the start, pfSsense has 2 interfaces with a DHCP server on the WAN. From the Linux VM I went to http://192.168.1.1, installed wireguard, created a tun_wg0 tunnel using this guide from IVPN: https://www.ivpn.net/setup/router/pfsense-wireguard/
Having reached the firewall settings (I didn’t start), I decided to check the handshakes. But unfortunately it is red. Don't know -
So traffic from pfSense is being routed over OpenVPN on the host machine? I'm not sure WireGuard would be able to connect over OpenVPN to the same provider. I could imagine routing issues.
