Project

General

Profile

Bug #567

Firewall's hostname gets multiple hosts entries

Added by Chris Buechler about 9 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
05/02/2010
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.0
Affected Architecture:

Description

In /etc/hosts, the firewall's hostname is entered once for each interface IP. This leaves you with a round robin DNS on that hostname, such as:
hamakua.buechler.local. 1 IN A 192.168.4.2
hamakua.buechler.local. 1 IN A 10.0.64.120
hamakua.buechler.local. 1 IN A 192.168.22.1
hamakua.buechler.local. 1 IN A 192.168.2.1
hamakua.buechler.local. 1 IN A 192.168.3.1

In 1.2.x and earlier, only the LAN IP is entered in hosts. Many users rely on this behavior, and returning a round robin record is a bit silly.

Associated revisions

Revision e5995f9d (diff)
Added by Ermal Luçi about 9 years ago

Ticket #567. Create an entry on hosts file with the ip address of lan or the first inerface ip without a gateway if lan is not present.

Revision 4994b350 (diff)
Added by Seth Mos about 9 years ago

Re-create the hosts file on bootup after configuring all the interfaces. Ticket #567

History

#1 Updated by Ermal Luçi about 9 years ago

  • Status changed from New to Feedback

#2 Updated by Seth Mos about 9 years ago

On a snapshot from 2010-05-16 it only writes the localhost entry.
Seen on multiple upgraded installs.

# more /etc/hosts
127.0.0.1       localhost localhost.coltex.nl

Edit:
running system_hosts_generate(); manually from the command page works and generates the proper file. After a reboot the file only contains the localhost entry
Edit2:
It appears that get_interface_ip() is failing to return the LAN address during bootup.

#3 Updated by Seth Mos about 9 years ago

  • Status changed from Feedback to Resolved

Recreated the hosts file after configuring interfaces so that it is created properly. Verified this fixes 567

Also available in: Atom PDF