Topics

Team,

Unfortunately my ISP DHCP is not working like expected. It does have long delays while answering DHCP request. This might be on intention from my ISP to present DDOS, so it may only allow refresh or renews based on lease time.  So If I need to reboot my OpnSense Box, the Boot Process often sticks quite long waiting for an IP-Address for the WAN Interface. The GUI and SSH does not respond during this time, so I can not do any remote troubleshooting. And this takes too much time for the impatient.

Often I need wait for the Gui to come up and then refresh the WAN interface.

Is there a workaround this ? I thought about giving an Alias IP-to the wan interface to come up faster. But I also had the impression that dhclient then silently dies.


Also dhclient fails quite often

Code Select Expand

/var/log/system/system_20251110.log:<13>1 2025-11-10T09:42:00+01:00 fw02. dhclient 59547 - [meta sequenceId="1"] dhclient-script: Reason FAIL on igc0 executing
/var/log/system/system_20251110.log:<13>1 2025-11-10T09:43:16+01:00 fw02. dhclient 92764 - [meta sequenceId="1"] dhclient-script: Reason FAIL on igc0 executing
/var/log/system/system_20251110.log:<13>1 2025-11-10T09:44:32+01:00 fw02. dhclient 9958 - [meta sequenceId="1"] dhclient-script: Reason FAIL on igc0 executing
/var/log/system/system_20251110.log:<13>1 2025-11-10T09:45:48+01:00 fw02. dhclient 23794 - [meta sequenceId="1"] dhclient-script: Reason FAIL on igc0 executing
/var/log/system/system_20251110.log:<13>1 2025-11-10T09:47:04+01:00 fw02. dhclient 49297 - [meta sequenceId="1"] dhclient-script: Reason FAIL on igc0 executing
/var/log/system/system_20251110.log:<13>1 2025-11-10T09:48:20+01:00 fw02. dhclient 64839 - [meta sequenceId="1"] dhclient-script: Reason FAIL on igc0 executing
/var/log/system/system_20251110.log:<13>1 2025-11-10T09:49:36+01:00 fw02. dhclient 79970 - [meta sequenceId="1"] dhclient-script: Reason FAIL on igc0 executing
/var/log/system/system_20251110.log:<13>1 2025-11-10T09:50:52+01:00 fw02. dhclient 95641 - [meta sequenceId="1"] dhclient-script: Reason FAIL on igc0 executing
/var/log/system/system_20251110.log:<13>1 2025-11-10T09:52:08+01:00 fw02. dhclient 55318 - [meta sequenceId="3"] dhclient-script: Reason FAIL on igc0 executing
/var/log/system/system_20251110.log:<13>1 2025-11-10T09:52:46+01:00 fw02. dhclient 58830 - [meta sequenceId="4"] New IP Address (igc0): 100.90.13.75
/var/log/system/system_20251110.log:<13>1 2025-11-10T09:52:46+01:00 fw02. dhclient 59179 - [meta sequenceId="5"] New Subnet Mask (igc0): 255.255.0.0
/var/log/system/system_20251110.log:<13>1 2025-11-10T09:52:46+01:00 fw02. dhclient 59614 - [meta sequenceId="6"] New Broadcast Address (igc0): 100.90.255.255
/var/log/system/system_20251110.log:<13>1 2025-11-10T09:52:46+01:00 fw02. dhclient 59884 - [meta sequenceId="7"] New Routers (igc0): 100.90.0.1
/var/log/system/system_20251110.log:<13>1 2025-11-10T09:53:24+01:00 fw02. dhclient 74079 - [meta sequenceId="8"] dhclient-script: Reason FAIL on igc0 executing
/var/log/system/system_20251110.log:<13>1 2025-11-10T09:54:40+01:00 fw02. dhclient 88471 - [meta sequenceId="1"] dhclient-script: Reason FAIL on igc0 executing


Could someone give me some hints to debug this further ?

Thanks

Versions
OPNsense 25.7.7_4-amd64
FreeBSD 14.3-RELEASE-p4

Hello Team, I noticed that if you use DNSMasq and add static Hosts the FQDN alias will also be a host entry for the IPv4 address in the Host file.

Could that be changed into the DNSMAQ CNAME Syntax? That would also allow all IP-Addresses for the host to have the alias.

from DNSMASQ

Code Select Expand

> --cname=<cname>,[<cname>,]<target>[,<TTL>]
    Return a CNAME record which indicates that <cname> is really <target>. There is a significant limitation on the target; > it must be a DNS record which is known to dnsmasq and NOT a DNS record which comes from an upstream server. The cname must > be unique, but it is permissible to have more than one cname pointing to the same target. Indeed it's possible to declare > > multiple cnames to a target in a single line, like so: --cname=cname1,cname2,target

    If the time-to-live is given, it overrides the default, which is zero or the value of --local-ttl. The value is a positive integer and gives the time-to-live in seconds.