I am 100% sure I had them assigned correctly (tested and re-tested it 2 dozen times) I think it was a driver issue, I've switched to OPNsense and it worked immediately

Internet went down again. This time, I received the following error in the dhcp logs when trying a wan ip release/renew Apr 16 08:47:23 dhclient Internet Systems Consortium DHCP Client 4.4.1 Apr 16 08:47:23 dhclient Copyright 2004-2018 Internet Systems Consortium. Apr 16 08:47:23 dhclient All rights reserved. Apr 16 08:47:23 dhclient For info, please visit https://www.isc.org/software/dhcp/ Apr 16 08:47:23 dhclient Listening on BPF/em3/00:26:55:ea:82:e6 Apr 16 08:47:23 dhclient Sending on BPF/em3/00:26:55:ea:82:e6 Apr 16 08:47:23 dhclient Can't attach interface {} to bpf device /dev/bpf0: Device not configured Apr 16 08:47:23 dhclient If you think you have received this message due to a bug rather Apr 16 08:47:23 dhclient than a configuration issue please read the section on submitting Apr 16 08:47:23 dhclient bugs on either our web page at www.isc.org or in the README file Apr 16 08:47:23 dhclient before submitting a bug. These pages explain the proper Apr 16 08:47:23 dhclient process and the information we find helpful for debugging. Apr 16 08:47:23 dhclient exiting. Apr 16 08:47:23 dhclient 11334 connection closed Apr 16 08:47:23 dhclient 11334 exiting.

Thank You for this valuable information!

@jimp said in ( 2.4.5) Can't delete an old Static DHCP lease: It must be in the configuration somewhere. Take a backup of config.xml and see if you can find it inside and tell where it is. Worst case scenario you can edit the entry out of the backup and restore it. Just to confirm that editing the config file and restoring the DHCP Server section resolved this. Thanks!

@casperse said in dhcprelay not working after update to 2.4.5: I am having the same problem? But in my case I have only one DHCP on another router in the same subnet.....(Two different ISP's) And I need the Pfsense to use the DHCP on the other router.... So I would think I still need this relay? It worked fine before upgrading Hope you also can help me (See no reason to do another post about the same service) Same Problem for me after upgrading 24.4 to 2.4.5 DHCP relay is not working

How do you have your kill switch set up? Because at the point you're trying to establish the VPN connection, it's obviously not yet established, so is your kill switch blocking the resolver's attempts to resolve us-florida.privateinternetaccess.com? It seems likely, since your test manually resolving with VPN off failed.

@johnpoz Cheers for the reply. You are correct about the approach toward DHCP. It was more of a thought experiment to try and align some new architect with services we already present corporately. It seems now the sensible thing to do is to change the deployment of those services rather than fit an architecture around a legacy pattern. P

@mircolino I doubt there'd be anything on link-local worth listening to. It's not normally used for data, other than with routers.

@johnpoz https://redmine.pfsense.org/issues/10449 someone was more faster then I =D

I don't believe you can.. Run the relay/helper for your vlans on your switch that is doing the vlans. If your switch(es) do not support that - get a better switch. Or just run host all your vlans off your other dhcpd and run relay for all vlans on pfsense. https://docs.netgate.com/pfsense/en/latest/dhcp/dhcp-relay.html To use the DHCP Relay daemon, the DHCP Server must be disabled on all interfaces. The same restriction applies to DHCPv6 relay and the DHCPv6 Server.

BTW: Netgate will add support for this in pfSense 2.5.0 release. Till waiting for 2.5.0 release I enchanted workaround by using of Filer plugin will slightly help to manage BASH scripts. One-line ECHO workaround in ShellCMD is ugly. So: Install Filer plugin Create script in pfSense Diagnostics=>Filer with name: /root/shellcmd_after_filter_changes.sh 2.1. Permissions 700 and Description Create AfterFilterChange Shellcmd script 2.2. File Contents: (all your scripts that must be run by AfterFilterChange Shellcmd script, change it to your need): #!/bin/sh echo "Launching AfterFilterChange Shellcmd script" /bin/sh -c /root/shellcmd_ddns_sub1.example.com.sh /bin/sh -c /root/shellcmd_ddns_sub2.example.com.sh echo "AfterFilterChange Shellcmd script exited with status: OK" 2.3 Execute mode: Do not run this script 3. Create all scripts in Filer with names mentioned in AfterFilterChange Shellcmd script (tune it to your needs): /root/shellcmd_ddns_sub1.example.com 3.1. Permissions 700 and Description Create DDNS sub1.example.com script for Shellcmd 3.2. File Contents: (do not forget adjust your RECORD, ZONE and TOKEN. This sample for ipv4. To change it to ipv6 aaaa record you need change curl -4 to -6 and type a to type aaaa) #!/bin/sh RECORD="sub1.example.com" ZONE="example.com" TOKEN="change-me" TTL="120" PROXIED="false" CHECK_IP_SERVICE="ifconfig.co" ZONES=`curl -X GET "https://api.cloudflare.com/client/v4/zones?name=$ZONE&status=active&match=all" -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json"` ZONES_SUCCESS=`echo $ZONES | /usr/local/bin/jq -r ".success"` if [ "$ZONES_SUCCESS" = "true" ]; then ZONE_ID=`echo $ZONES | /usr/local/bin/jq -r ".result | .[0].id"` DNS_RECORDS=`curl -X GET "https://api.cloudflare.com/client/v4/zones/$ZONE_ID/dns_records?type=A&name=$RECORD&match=all" -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json"` DNS_RECORDS_SUCCESS=`echo $DNS_RECORDS | /usr/local/bin/jq -r ".success"` if [ "$DNS_RECORDS_SUCCESS" = "true" ]; then RECORD_ID=`echo $DNS_RECORDS | /usr/local/bin/jq -r ".result | .[0].id"` IP=`curl -4 $CHECK_IP_SERVICE` UPDDATE_DNS_RECORD=`curl -X PUT "https://api.cloudflare.com/client/v4/zones/$ZONE_ID/dns_records/$RECORD_ID" -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" --data "{\"type\":\"A\",\"name\":\"$RECORD\",\"content\":\"$IP\",\"ttl\":$TTL,\"proxied\":$PROXIED}"` UPDDATE_DNS_RECORD_SUCCESS=`echo $UPDDATE_DNS_RECORD | /usr/local/bin/jq -r ".success"` if [ "$UPDDATE_DNS_RECORD_SUCCESS" = "true" ]; then echo "DynDNS updated: $RECORD to $IP" else echo "DynDNS update failed: $RECORD to $IP" exit 1 fi else echo "Error while tried to get DNS records of Zone: $ZONE_ID" exit 1 fi else echo "Error while tried to get Zones" fi echo "DDNS sub1.example.com exited with status: OK" 3.3 Execute mode: Do not run this script 4. In ShellCmd if you created previously other scripts by my how-to - remove them and leave only: /bin/sh /root/shellcmd_after_filter_changes.sh with type afterfilterchangeshellcmd and Description Run shellcmd_after_filter_changes.sh

Thank you so much! I didnt mind that setting. You made my day :)

Thank you for your reply. Yes, I was hoping to find a scrollbar at the bottom, That was the major issue. There was no way to scroll to the right, nor was there any indicators that you COULD scroll to the right. When you mentioned that the hostname was too long, I saw that the description for my desktop "Michael Kammer Desktop I9" wrapped properly, The item that caused the problem: GS108TMichael, used the same hostname / Description AND client ID Note: I had a SECOND Netgear GS108T switch (all three elements were "GS108TTheatre", previously configured in the list and the Actions column still remained. The problem occurred when I added another identical Router with a sequential IP. Note: the MACS were not even close to each other, so that could not be the issue. so it could not have been the problem as every element in all three fields was 14 characters or less. In any case, when I remove the last item, everything started working normally

Until I can get help resolving this, I flipped back over to the pi-hole and that has fixed what appeared to be a very sluggish DNS. Looking forward to re-enabling pfBlockerNG and use the full functionality of the box.

@chrisgtl Yes, disable private DNS.