Wifi connection stops after period or reboot

[BryanH 0]

Updated to 8.2.800 and couldn't connect to wifi networks, no IP Address collected from DHCP. 

Can confirm issue is resolved when removing Eset Network Protection from system preferences>Network. or Disabling Firewall.

 

I have forgotten networks and rejoined typing in the password; no prompts for saving network connection as Private or Public. Image attached.

 

Image attached of errors listed in firewall logs; Can you please confirm which option to select when right clicking a firewall log entry to Allow it permanently and whether this will hold without the network profile being saved as private?

 

Have two Macs, this issue is only happening on the laptop running Monterey 12.7.6, the imac running Sequoia 15.1.1 is connecting fine with Ethernet(Wifi Untested).

~Bryan

 

Edited November 27 by BryanH

[BryanH 0]

Urgency Bump

[itman 1,807]

On 11/27/2024 at 3:17 AM, BryanH said:

Image attached of errors listed in firewall logs;

Really looks like DHCP processing is borked.

[BryanH 0]

yeah just need an explanation and fix for why ESET is causing it

[itman 1,807]

3 hours ago, BryanH said:

yeah just need an explanation and fix for why ESET is causing it

Eset should be using the local device assigned IPv4 address; 192.168.0.153 or 192.168.0.163 depending on network connection used, in the DHCP handshaking connections which clearly isn't being done.

-EDIT- There is also any issue with Eset finding a DNS server since the logs show the target address being one in the APIPA address range. This range is only used when there is an issue with assignment of a valid local subnet IP address. This might be related to DHCP not being properly setup.

Edited November 30 by itman

[BryanH 0]

its firewall related, firewall is blocking network access/dhcp.

[Robertos 68]

Hello,

Here is the answer to your original question: Creating a rule for an application does not affect the network profile assignment.

 

Please note that firewall rules can only be created for applications. If you don't see the application name listed in the "Application" column of the firewall log, it means that application-specific rule could not be created from selected log row.

 

Let me know if you have any further questions or need clarification!

[Robertos 68]

About blocking DHCP:
 

It appears that the firewall rules may have been affected by an previous version of the configuration module. In this case, the best solution is to perform a clean installation of the product. Please follow these steps:

1. Uninstall the product.
2. Restart your macOS.
3. Perform a fresh installation of the product.
4. Reconfigure the firewall if you had previously set up any custom rules.

We sincerely apologize for the inconvenience this may cause and appreciate your understanding. If you have any further questions or need assistance, please don't hesitate to reach out.