Hi all,

I have a problem that when my 4/5G modem sometimes renews IP, it does't give it to my pfsense box (running latest pfSense Plus 24.03.1 release). Yes, I miss the times I had fiber..

So in this situation, I get a lot of dhcp discover messages to 255.255.255.255, but I really never get a real working new IP and working WAN connection.

Quite obvious that my modem is running dnsmasq to provide 'ip-passthrough-mode'. Propably all software in it is partially just (old?) Linux /GNU software, like most todays customer devices do.

If I renew WAN IP from web GUI, I'll start getting a mass of following errors in my system.log, and thus error messages are flooding my system.log.

Arpresolve: can't allocate llinfo for xxx.xxx.xxx.xxx (where xxx.xxx.xxx.xxx is my old ip)

Today I found the below solution to the problem, and made the following shell script /root/bin/renew-wan-ip.sh (and thank a lot for the original author):

#!/bin/sh /usr/local/sbin/dhclient -4 -d -r -lf /var/db/dhclient.leases.ix3 -cf /var/etc/dhclient_wan.conf -sf /usr/local/sbin/pfSense-dhclient-script; php -r "require 'interfaces.inc'; interface_bring_down('wan'); interface_configure("wan");"

So It's almost a one liner. It assumes that yout wan name is 'WAN' and WAN interface is ix3. Please, modify the script to suite your configuration.

I'll try this next time I have this problem, but you may try it now or suggest improvements or better solutions.

And if someone knows a solution for the 'Arpresolve: can't allocate llinfo for xxx.xxx.xxx.xxx' problem in this exact scenario, I would be happy to hear. I'm running latest pfSense Plus 24.03.1 on Netgate 6100 hardware.

Thanks and happy hacking!

@The-Party-of-Hell-No
Yep))) The world is crazy

@johnpozYes you are right and I share it. Unfortunately it's a makeshift cfg... the wireless controller system is there I have it active on Omada with 3 APs. Unfortunately, this connection exists between one house 🏠 towards the other in a distance of 300 mt aircraft .... I should buy at least two outdoor omada antennas, but at the moment I have to postpone ...

@johnpoz thanks, this is very helpful, i will race to enact during the next outing and repost here. thanks for your patience.

@johnpoz thanks, I will review the options you mentions.

@Antibiotic
The start might be the very moment you created the static lease.
The end : the day you deleted it, you will never see that date.

@chudak sounds like https://redmine.pfsense.org/issues/14977

@iptvcld said in Failover DNS when using external DNS server:

Have DNS via VM, would it have any negative impact?

No not really - it doesn't take much resources to serve up 1000 and 1000 of queries even a second..

@Gertjan

Thanks for that wonderful suggestion.
I did not notice that icon.

Actually, the icon was already lit up on device that has active lease, which i all are black until i scroll down to see other status, I just need to get the list of active one's. tried to put "online" query on Search term and voila!

Reason why i need to get numbers of active device daily for a period of time to see how many are connected for a particular project.

Thanks you very much!

Screenshot 2024-05-02 at 7.30.01 AM.png
Screenshot 2024-05-02 at 7.29.40 AM.png

@Gertjan said in Service unbound status:

Windows is not Linux. Linux is not FreeBSD, and surprisingly, pfSense is not FreeBSD

OS is not a human))

@joshgreyz said in Where are log files for Dynamic DNS clients?:

I'm trying to find that information at the CLI -- any ideas?

Like this?

cat /var/log/system.log | grep dyndns

Regards,
fireodo

@mike123 said in Unable to resolve acb.netgate.com:

Login to the shell and type
dig acb.netgate.com

If you get no reponse
i.e. ;; communications error to 127.0.0.1#53: timed out

Iif "Login to the shell and type" is the console or SSH access of pfSense, and you get a "127.0.0.1#53: timed out" after "dig acb.netgate.com" then that means that the dig command couldn't connect to 127.0.0.1, port 53.
That means that unbound isn't running, or listening on 127.0.0.1 port 53 (localhost).
That is not normal at all.
First : : Check if it is running :

[24.03-RELEASE][root@pfSense.bhf.tld]/root: ps ax | grep 'unbound' 41201 - S 0:07.76 /usr/local/sbin/lighttpd_pfb -f /var/unbound/pfb_dnsbl_lighty.conf 86447 - Ss 25:07.40 /usr/local/sbin/unbound -c /var/unbound/unbound.conf 21124 0 S+ 0:00.00 grep unbound

(the second line == ok )

and check on what interface it is listening :

[24.03-RELEASE][root@pfSense.bhf.tld]/root: sockstat | grep 'unbound' unbound unbound 86447 3 udp6 *:53 *:* unbound unbound 86447 4 tcp6 *:53 *:* unbound unbound 86447 5 udp4 *:53 *:* unbound unbound 86447 6 tcp4 *:53 *:* unbound unbound 86447 9 tcp4 127.0.0.1:953 *:* unbound unbound 86447 10 dgram -> /var/run/log unbound unbound 86447 12 stream -> [86447 14] unbound unbound 86447 14 stream -> [86447 12] unbound unbound 86447 15 stream -> [86447 16] unbound unbound 86447 16 stream -> [86447 15]

The first 4 lines means : on port '53' :
For all protocols : TCP and UDP and TCP and UDP
This means all interfaces, which include '127.0.0.1'.
Btw : line 5 is unbound listing on localhost, the control port 953 TCP.

This option :

DNS Server Override -> Allow DNS server list to be overridden by DHCP/PPP on WAN or remote OpenVPN server

exist for very ancient reasons (before 2000 ?), when you had to use the ISP DNS servers, as resolving was 'expensive' and an internet connection was metered, and very slow (POTS modem uplink).
Many ISPs still propose a DNS or two, but I guess no one is using them anymore.
Why getting the info from 'some one' if you can get it from the source ?

@Gertjan that worked. Thank you