Project

General

Profile

Actions

Bug #3746

closed

Firewall hostname being reset by DHCP WAN client

Added by Jim Pingle almost 10 years ago. Updated almost 10 years ago.

Status:
Resolved
Priority:
Normal
Category:
Operating System
Target version:
Start date:
07/07/2014
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2
Affected Architecture:
All

Description

If the firewall has a DHCP WAN, and the DHCP server on WAN supplies a hostname to the client, the firewall will take the hostname given and clobber the hostname configured from System > General.

Removing or commenting out the call to check_hostname in /sbin/dhclient-script allows the firewall to retain its chosen hostname. It isn't clear if this behavior is actually desirable or if that code is safe to remove, hence the ticket.

The logic change from e912bfae186b6b657daf52607f9d027f46be0478 (2.1.x) and ff3da5dba67c64514808e86165e92362f3ff8b33 (2.2) seems to have triggered this new behavior. This affects 2.1.4 and 2.2.

Actions #1

Updated by Renato Botelho almost 10 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #3

Updated by Jim Pingle almost 10 years ago

  • Status changed from Feedback to Resolved

This appears to have fixed it. The latest snap contains the proper hostname on my system that easily replicated the problem before.

Actions

Also available in: Atom PDF