how to delete an entry from: Firewall => Diagnostics => pfTables

Started by gonzo, March 01, 2018, 09:56:37 AM

Previous topic - Next topic
Hi :)

How to delete an entry from:  Firewall => Diagnostics => pfTables ?

gonzo


seriously, no one knows the answer to this simple question ?

I would think that if you remove the Alias it should remove the pfTable entry.
If it doesn't, then report the issue on github https://github.com/opnsense/core/issues


Yes, I have removed all aliases, but pFTables entries are still visible

https://github.com/opnsense/core/issues/2240

@gonzo
Try this: start by giving feedback to your older posts. You know, just to let people know that they are not talking to empty walls. Maybe then they will be willing to help you. This is not a charity event nor a paid support to just demand and receive help right when you clap your hands. Seriously.
OPNsense v18 | HW: Gigabyte Z370N-WIFI, i3-8100, 8GB RAM, 60GB SSD, | Controllers: 82575GB-quad, 82574, I221, I219-V | PPPoE: RDS Romania | Down: 980Mbit/s | Up: 500Mbit/s

Team Rebellion Member


Quote from: gonzo on March 05, 2018, 07:00:46 AM
hi :)

Do you know any older post with this problem ?

That's not the point. The point is, all your older posts are left hanging in the air. When people actually invest their time in helping you (or at least trying), it would be nice to provide feedback, for at least two reasons:

1. Others with the same problem might find a solution there. If you stay silent, it helps absolutely nobody
2. If an issue is fixed by the devs (or anybody else) and a patch is provided, or at least attempted, or a helpful hint was given to you, they need confirmation that it actually worked so that they can improve OPNsense not just for you, but for everybody else
3. Bonus: to thank them for their efforts
OPNsense v18 | HW: Gigabyte Z370N-WIFI, i3-8100, 8GB RAM, 60GB SSD, | Controllers: 82575GB-quad, 82574, I221, I219-V | PPPoE: RDS Romania | Down: 980Mbit/s | Up: 500Mbit/s

Team Rebellion Member


Yes, I agree with you, and that's why I reported this problem yesterday as a mistake. A moment ago Franco wrote that it is enough to do a reboot. I can check it out tomorrow around 7 am. As soon as I know something, I will let you know if it works

Thanks. :)

The table exists as a separate entity and it's not necessarily tied to the current rules / does not have to be used in them.

It makes at least some sense to not purge tables, because:

1. If we only disable the alias usage in the rules we still want to update the table for when it's being used again.
2. If we delete the alias it cannot be used anyway.
3. Cleaning up the table for (1) or (2) adds more code.


Cheers,
Franco


Franco, so I can delete tables that are now empty without performing a reboot ?

No, that's not what I said. In (3) I stated that explicitly deleting tables would require more code (and research as to how it works). In (1) and (2) it was said that it's allegedly better to keep the tables instead of deleting them.


OK, but in my opinion it is good to remove unnecessary tables due to aesthetic and maintaining order reasons  :)

But you do also realise that this adds no operational value for the cost of coding and testing time that could be spent elsewhere?


Of course, you are right.
Due to the fact that my firewall is already operating in a production environment, I have to patch up the restart, I have to inform users about the interruption in the operation of services, etc. From my point of view this is a big inconvenience.