Networking


How to configure PFsense to PXE boot using FOGProject

For testing purposes I’m using PFsense to allow my clients to PXE boot using the FOG TFTP server.

This are the settings which are working :

PropertyValue
Next serverIP Address of FOG Server
Default BIOS file nameundionly.kpxe
UEFI 32 bit file nameipxe32.efi
UEFI 64 bit file nameipxe.efi

 

You can find these settings in the PFsense DHCP service menu.


How to configure PXE booting using PfSense

For some testing in my lab environment I needed PXE boot to work. This is how I configured PfSense to support PXE boot. In this scenario I wanted some Windows and Linux devices to boot to an imaging environment. For the Windows devices I needed option 66 en 67 but somehow when I specified those settings in PfSense I didn’t got it to work. The solution was very simple :

Log on to the Webinterface of PfSense, go to services/dhcp server.

Specify the following options :

  • IP Address of TFTP server
  • Enable network booting yes
  • Next Server (= IP Address of TFTP server)
  • Default Bios file name (= filename of legacy of UEFI bootfile name, in my case undionly.kpxe)

pfsense_pxeboot

Save these settings and you’re all set! You don’t have to specify the 66 and 67 settings!


How to configure pfSense to allow outgoing SMTP traffic

In this scenario I would like to allow SMTP traffic to my internet provider so that an application in my test environment is able to send notification messages. In this environment I use pfSense.

For this to work, you have to create a port forwarding rule on the LAN interface forwarding traffic to any IP with port 587.

Open the pfSense interace and go to Firewall rules:

pfsense_smtp_001

Then create a new rule as follows:

pfsense_smtp_002

Make sure you use the right (internal) IP address of the server which is sending the emails.


Setting up Aerohive WiFi test environment Part 1 2

In this blogpost I describe I’ve taken to setyp my Aerohive WiFi whitebox environment. In my case I used the following products :

  • HP 1910 POE Switch (ofcourse you can choose another POE Switch)
  • 2x AP130 Aerohive Accesspoints incl. licenses
  • and 2 cigars while building. 🙂

IMG_20161215_090129435

First I powerd up the HP 1910 POE (power over ethernet) switch. When the fans are making less noise the Switch is bootend. First plugin an ethernetkabel to your core switch or ISP modem. I used Angry IP Scanner to locate the switch on my subnet.

Angry IP Scanner

In my case I found 192.168.0.20 the DHCP IP address taken by the switch. Now let’s login to the webinterface. Use your favourite browser and go to the IP address you found.

HP Switch menu

By Default use Admin as username with no password and the specified Captcha. When logged on change the password ofcourse and go through the wizard to change your IP Address and device name etc. Download the latest firmware for the HP1910 switch here.

Ok. now we have our Switch in working order. Check! Now we are going to configure the WiFi devices. First we must create a working Hive Manager account (Cloud). Go here to create your account. Log in when you are able to.

HiveManager1

Congrats! We are going places!

HiveManager2

Now we are going to create a location. A location is the specification where your Office and devices are present. There are 2 options. When you have floorplan of your building/office then you can easily import that file. But it’s also possible to draw your own plan. It’s based on google maps. So you can specify the address and then draw on top of the building.

HiveManager3

I choose the Create a New Network Plan option. It’s pretty straightforward.

After creating your location (and floorplan, just specify the locations of your floor) you see something like this:

HiveManager4

Now it’s time to add our devices. In my case I choose for 2 AP 130 devices. I want to test roaming for example. Go to the monitor/devices/add device option, see below.

HiveManager5

Specify your serial number and go to the next-next-next steps while creating a network policy.

HiveManager6

Voila! You added your device and created your first Network Policy.

Now connect your AP130 device. Watch the red light turn white. When you see that your AP is registred correctly! Now let’s check in the Hive Manager.

HiveManager7

You can see that the AP is green and that means everything is correct!

Wrap up

What we have just did is to quickly configure the POE Switch (in my case HP1910), created an Hive Manager Cloud account and configured our first Network Policy with one device.

Let’s connect to the Accesspoint using the credentials you’ve just specified. And check if the connection is working.

HiveManager8

In my case everything is working. My mobile phone has a working connection!