Brain's Workbench
Software Versions
The following software versions were used in this post.
Install the qemu-guest-agent package.
pkg install -y qemu-guest-agent
Once installed, there is a note on how to setup the agent.
Modify your `/etc/rc.conf` by adding these settings
qemu_guest_agent_enable="YES" qemu_guest_agent_flags="-d -v -l /var/log/qemu-ga.log"
and run
For a qemu proxmox guest PFSense acts weriedly with the network speed- it gets extremely slow. So her goes the little tweaks that worked for me-
First, I chose Intel E1000 Interfaces instead VirtIO.
Second, in the PFSense webconsole-
In pfSense GUI, System > Advanced > Networking > Tick on-
For simplicity, you can also follow the step by step instructions from your pfSense WebGUI below:
1. Create a PORT alias:
Firewall -> Aliases -> Ports -> + AddName: WhatsAppPortsTCP
Port: 443
-> + Add PortPort: 5222
Save (bottom) -> Apply Changes (top right)
2. Create a URL alias:
Firewall -> Aliases – URLs -> + AddName: WhatsAppIPv4_URL
Type: URL Table (IPs)
URL Table (IPs): https://adamnetworks.dev/pub/fwaliases/raw/master/ips/whatsapp.txt /(update frequency): 1
Save (bottom) -> Apply Changes (top right)
* Note: If your cdrom device is not acd0, check the bootup messages for the proper device.
If you deploy pfSense on a XenServer, you may be shocked at the performance loss-specially on interface speed! But wait, there are some tweaks to make this usable.
Installing pfSense
Go ahead and setup pfSense like normal, and when you are done, perform the following tweaks. (the day till it’s tested on pfsense version 2.5.2 and xen on scp-ng 8.1)
XenServer tweaks
Find UUID for the pfSense VM you just installed.
xe vm-list
You should get something like the following
uuid ( RO) : b435d920-eb22-b45d-5058-091619ed427f name-label ( RW): pfSense power-state ( RO): running uuid ( RO) : 42626f69-6185-4aa6-a125-839700f96828 name-label ( RW): Control domain on host: xenserver-000 power-state ( RO): running
We want the UUID of the instance running pfSense, b435d920-eb22-b45d-5058-091619ed427f in this case.
Installing the Package
The pfSense 2.X package manager includes both FreeRadius and FreeRadius2 as installation options. For this example, I’m going to be using FreeRadius2 since it has some additional features not found in the previous version.
Only one version of radius can be installed on pfSense at a time. If you previously installed any radius packages, go ahead and remove them first.
The package installation will briefly interrupt traffic passing through the router as the service starts, so be careful when running the installation on a production system.
You cannot run both FreeRadius and FreeRadius2 on the same pfSense system. Make sure to remove one before installing the other. The setup process will automatically download and install the radius package along with all of its dependencies. The installation normally takes a couple of minutes to complete.
After it’s finished, there will be a new menu item for the package in the services menu. The FreeRadius installation normally takes a couple minutes to complete.
Open a browser software, enter the IP address of your Pfsense firewall and access web interface. In our example, the following URL was entered in the Browser:
https://192.168.15.11
The Pfsense web interface should be presented. After a successful login, you will be sent to the Pfsense Dashboard.
Access the Pfsense Services menu and select the SNMP option.
This article shows you how to allow ##ping## on the WAN side of your pfSense firewall. By default, ping to WAN address is disabled on pfSense for security reason. However, you may want to allow ping for different reasons, here is how:
# Login to pfSense
# Open Firewall > Rules.
# Change Interface to wAN.
# Change Protocol to ICMP.
Before building a PPoE system, it is estimated to assume that we’re building it on the following principal and prerequisite conditions-
For easy understanding here goes my mockup instace WAN and LAN IP-
So here goes the steps-
Step 1: Create and Configure PPPoE Server:
FreeRADIUS offers an easy to use command line tool to check if the server is running and listening to incoming requests. Aninterface, a NAS/Client and a user must all be configured:
The following output should appear if everything was setup correctly: