Core: new Alias no working anymore

Created on 16 May 2019  路  11Comments  路  Source: opnsense/core

Describe the bug
Not able to create a new working alias - old ones are working good
19.1.6

NOT UPDATED/NOT REBOOTED because feeling curious if currently working alias also begin to fail. - Possible to debug a little more first?

First thought it is related to alias on floating rules. But is not limited to that. Don't think so but mention the old issue where I also had problems: #3321

To Reproduce
Steps to reproduce the behavior:

  1. Go to Firewall/Alias
  2. Create a new alias, type host(s) with name h_t_itops_repo (had a longer before), IP xx.xx.xx.12
    (tried that to with an Alias type network and xx.xx.xx.12/32)
  3. (A) Used the alias on Floating Rule (incoming to ip)
  4. PASS
  5. IPv4
  6. TCP
  7. Source Any
  8. Destination: ALIAS h_t_itops_repo
  9. Destination Port: HTTP HTTPS
  1. (B) Used the alias on Interface (outgoing from ip)
  2. PASS
  3. IPv4
  4. TCP/IP
  5. Source: ALIAS h_t_itops_repo
  6. Destination: any
  7. Destination Port: HTTP HTTPS

Expected behavior
Traffic should be passed in both rules, but isn't. As soon as i change the rules to use the ip instead of the alias, traffic is passed through.

Screenshots
Floating rule
not working
image
Working
image

Interface rule
not Working
image

Working
image

Relevant log files
not working

pass inet proto tcp from {any} to $h_t_itops_repo port $pg_HTTP_HTTPS keep state label "USER_RULE: 1122REPORULE" # f53a6faaf0b327cddd53ad2d684ef22a
pass in quick on vmx2_vlan602 inet proto {tcp udp} from $h_t_itops_repo to {any} port $pg_HTTP_HTTPS keep state label "USER_RULE: 1122REPORULE" # 7b7e21c152105d90c470d54457d64c9c

working

 grep 1122 /tmp/rules.debug
pass inet proto tcp from {any} to {10.40.2.58} port $pg_HTTP_HTTPS keep state label "USER_RULE: 1122REPORULE" # c9eb0325669251250be0c4031f1ae357
pass in quick on vmx2_vlan602 inet proto {tcp udp} from {10.40.2.58} to {any} port $pg_HTTP_HTTPS keep state label "USER_RULE: 1122REPORULE" # cff36fecc774b83a007504ee24fb9707

Additional context
Add any other context about the problem here.

Environment
(2x) VMWARE Virtual Guest in HA
OPNsense 19.1.6-amd64
FreeBSD 11.2-RELEASE-p9-HBSD
OpenSSL 1.0.2r 26 Feb 2019

support

All 11 comments

just found something - Firewall Diagnostics pfTables
the entry for h_t_itops_repo is empty
image

did you hit apply (in the alias form)? if not, please inspect the logs for anything out of the ordinary.

yes

just created an additional one and hit apply - but no usage in a rule, only to test adding an Alias - same problem: emtpy in pfTables

(same on primary and secondary)

There was a relevant alias fix in 19.1.7.

sure? - thought I looked over the release notes? - let me try

ok.. updated slave to 19.1.7 and pftable shows now the entry correctly. And sure the rules are working.
I'm sorry that I overlooked that fix. Is there any way to donate you both a 馃嵑 ?

No worries, all good. Thanks for the quick feedback :)

would love to

Was this page helpful?
0 / 5 - 0 ratings