Bug #4805: Using FQDN and IP in alias causes static entries to be lost - pfSense - pfSense bugtracker

Actions

Copy link

Bug #4805

closed

Using FQDN and IP in alias causes static entries to be lost

Added by Tomas Ulicky over 9 years ago. Updated about 7 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Luiz Souza

Category:

Rules / NAT

Target version:

Start date:

06/30/2015

Due date:

% Done:

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

2.2.3

Affected Architecture:

Description

Hi, despite of fact that this issue was resolved (https://redmine.pfsense.org/issues/4296), I have problem, that in Alias1 I have IP 1.1.1.1 and fqdn1.server.com in Alias2 IP 2.2.2.2 and fqdn2.server.com and Alias3 is combining Alias1 and Alias2.
Static ip adresses are missing, sometimes eve whole aliases are missing after reload.
But if use http://files.pfsense.org/jimp/filterdns.fixed from bug 4296, everything is working properly after reload.

Actions

Copy link

Updated by Tomas Ulicky over 9 years ago

For better replication this is what happening:
IP_Alias_10 IP_Alias_6, IP_Alias_2, IP_Alias_1, IP_Alias_3, IP_Alias_4
IP_Alias_1 fqdn1.server.com, 1.1.1.1
IP_Alias_2 fqdn2.server.com, 1.1.1.2
IP_Alias_3 fqdn3.server.com, 1.1.1.3
IP_Alias_4 fqdn4.server.com, 1.1.1.4
IP_Alias_5 1.1.1.5

After pfSense boot this is working properly. After altering any of aliases (changing ip) iP_Alias_5 is missing in pfSense tables completely.

Actions

Copy link

Updated by Tomas Ulicky over 9 years ago

And IP_Alias_10 contains only IP address from IP_Alias_5

Actions

Copy link

Updated by Phillip Davis over 9 years ago

@Tomas - your description of IP_Alias_10 includes IP_Alias_6
But IP_Alias_6 is not mentioned anywhere else.
Is there a typo? Should IP_Alias_10 include IP_Alias_5?

Actions

Copy link

Updated by Tomas Ulicky over 9 years ago

Yeah, sorry this is typo, correct one is:
IP_Alias_10 IP_Alias_5, IP_Alias_2, IP_Alias_1, IP_Alias_3, IP_Alias_4

Actions

Copy link

Updated by Tomas Ulicky over 9 years ago

Update, it is not working even with filterdns.fixed, after some time, if I reload some firewall rules tables are mismatch...

Actions

Copy link

Updated by Tomas Ulicky over 9 years ago

In the log there is correctly: filterdns: adding entry 1.1.1.1 to table IP_Alias_1 on host fqdn1.server.com
But in table this address is not present.

Actions

Copy link

Updated by Tomas Ulicky over 9 years ago

Another observation, after some time (30min-60min) its recover from badly filled tables and are filled with proper IPs.
But in meantime traffic is blocked because ste of tables is not aligned with what was defined in GUI.

Actions

Copy link