IPFire Network Interface Not Found

Today I'd like to talk about IPFire and a problem I had recently with the network cards.

IPFire is my favourite lightweight firewall distribution. It's easy to setup and configure which, in my opinion, makes it perfect for labs and POCs.

I have a lab environment set up on my Windows 10 computer with multiple virtual networks and virtual machines. I have setup a virtual network with Active Directory domain controllers acting as DCHP and DNS servers, several test servers and workstations. I have even joined an Ubuntu Server to this Active Directory Domain.

All these in a private virtual network... So I had to make internet connection available to those machines. I created a new virtual machine and installed IPFire. I added three virtual network adapters to the virtual machine - one connected to my LAN and the other two connected to two private virtual networks.

After a little bit of configuration, my virtual machines could access the internet through the IPFire virtual machine.

The only problem I had was when I moved the virtual machine to another host for another lab. The virtual network adapters were not configured with static MAC addresses so when IPFire started, it could not find the NICs.

This is very easy to fix, just take a note of the MAC addresses of the adapters in Hyper-V and the network they're connected to and then update the /var/ipfire/ethernet/settings file with the new MAC addresses. Be very careful here and set the right MAC address for the right adapter. Reboot the VM and you should be all set.

Popular posts from this blog

Domain Controller Machine Password Reset

Image
On my lab environment, I've configured two Active Directory sites since most enterprises have offices in more that one places. My lab however is not running 24/7 and the domain controllers in the second site are rarely turned on in order to save resources. This leads to issues with the Active Directory replication such as the "The target principal name is incorrect" error when I execute:  repadmin /syncall /AdeP. To remedy the issue, we have to reset the machine password of the domain controller that has been offline. First off, we are going to stop and disable the Kerberos Key Distribution Center (kdc) service on the problematic domain controller, in our case DC4. There may be some tickets in the cache so we should also clear them using klist purge Now it's time to change the machine password of the domain controller using the command netdom resetpwd /s:dc3 /ud:lab\administrator /pd:* Replace the "lab\administrator" with an account on your
Keep reading

Configuring a Certificate on Exchange Receive Connector

Today's article is about configuring Exchange receive connectors with specific certificates. Out of the box, Exchange uses self signed certificates to provide TLS secured mail flow. This will definitely be an issue if you expose the SMTP protocol to client computers since they won't trust the certificate. In this article we are going to configure a certificate that was issued by a third part authority to the Client Frontend receive connector. We'll start with getting the thumbprint of the certificate using the Get-ExchangeCertificate cmdlet: [PS] C:\> Get-ExchangeCertificate Thumbprint                               Subject ----------                               ------- 241B864DC82C664FECBA18B8D54987AAFB65B4C2 CN=*.lab.com, ... D4D210886B34E690191A1F008C78FDD0E7325DD4 CN=Exchange2013A 960171662EB261162F9C8CBE12E0B75D6F06ABB0 CN=Microsoft Exchange Server Auth Certificate 2690324B827A9F2B75D59104F81CAAA57CDD627B CN=WMSvc-Exchange2013A [PS]
Keep reading

Running Multiple NGINX Ingress Controllers in AKS

Image
In some of the previous articles of this blog, we went through the process of installing NGINX as the Ingress Controller in AKS clusters. Either for applications that should be available directly from the public internet, or for applications that should only be accessed from networks considered internal. In the majority of the cases, however, and given that an AKS cluster is an environment that is designed to host multiple applications and provide economy at scale, additional ingress controllers may be required. In this post, we're going to go through the process of deploying an additional NGINX ingress controller that is going to be used for internal applications. The below diagram depicts the desired outcome: The Angular application is published via the public NGINX through the Azure Load Balancer that has been assigned a public IP. The .NET app is published by a different set of NGINX pods that are deployed in a different namespace and their ingress controller service is connect
Keep reading