Project

General

Profile

Actions
Copy link

Bug #284

closed

FQDNs in aliases not added

Added by Chris Buechler over 14 years ago. Updated over 14 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Rules / NAT
Target version:
2.0
Start date:
01/05/2010
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

When an alias contains a FQDN, it is not added to the ruleset at all anymore since the recent filterdns changes. Example alias:

                <alias>
                        <name>test</name>
                        <address>1.0.0.1/32 google.com/32</address>
                        <descr/>
                        <type>network</type>
                        <detail>Entry added Wed, 06 Jan 2010 02:18:54 +0000||Entry added Wed, 06 Jan 2010 02:18:54 +0000||Entry added Wed, 06 Jan 2010 02:26:38 +0000||</detail>
                </alias>

Resulting User Aliases in rules: 

table <test> {   1.0.0.1/32 }
test = "<test>"

Actions
Copy link
 #1

Updated by Seth Mos over 14 years ago

You need to use pfctl -t <alias name> -T show to see what is in it.

table <ext_management> { 127.0.0.1/32 }
ext_management = "<ext_management>"

$ pfctl -t ext_management -T show
127.0.0.1
23.7.39.94

Actions
Copy link
 #2

Updated by Chris Buechler over 14 years ago

  • Status changed from New to Closed

Ah yeah, didn't realize that's how it worked now. This is functioning correctly.

Actions
Copy link

Also available in: Atom PDF