OPNsense Forum

Archive => 19.1 Legacy Series => Topic started by: seized on February 04, 2019, 07:13:13 pm

Title: Port alias tables not saving or persisting (FW rules w/ port aliases dont work)
Post by: seized on February 04, 2019, 07:13:13 pm

I have some port aliases that I use for some firewall rules. They seemed to stop working after the 19.1 upgrade, maybe right after or the next day. From what I can tell its because the port type aliases tables arent being persisted in rules.debug but I am not sure if they are supposed to be persisted.

I created a new alias, new firewall rule referencing it and still see the behavior below where port type aliases are not listed in pfTables under Firewall > Diagnostics, dont show up in pfctl and are listed in rules.debug but not persisted (which I am guessing they should be). I included a hosts type alias that does seem to be working.

The symptoms I end up seeing is that firewall rules referencing the ports alias dont work, that traffic isnt allowed and doesnt match the rule and thus gets dropped.

(https://i.imgur.com/3l7uYJD.png)

(https://i.imgur.com/QqtvEuz.png)

(https://i.imgur.com/xuDL2Vq.png)

(https://i.imgur.com/LRRd8LG.png)

(https://i.imgur.com/DZWobYe.png)

Title: (SOLVED) Port alias tables not saving or persisting
Post by: seized on February 04, 2019, 10:34:13 pm

Sigh. Well this is a non issue, I figured out that the actual ROOT issue is that my install of Home Assistant somehow picked up the Chromecast built into my Vizio TV even though the TV is on a separate subnet and firewall rules shouldnt allow anything. When HomeAssistant cant access a Chromecast device it hangs on startup with a unhelpful error. This whole thread was me erroneously troubleshooting the issues with Home Assistant getting to the Chromecasts that it should be able to, which it could all along I think.

Sorry for the alarmist thread.