-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEE7sBxPmxNSLEwQp4k5k1h0mWW9oAFAmHOCH0ACgkQ5k1h0mWW
9oDRPwf9HWsRP3ZwpaoCXLUCiEprzqwI9jPihjgentX/HHoLAhnLo5aBHZ3RLv5z
EKQDP1uyC5qhAxdQDQSRXRyZrjdkCo1efPQcChkKpc555nhHej0fHVrclv/rnOuS
ItF1friJyrnyEpeRKU+vgULMc7fETiwIT14IcEsOpa0HNV0EJGSBbIsn//k3XLH8
R72L87ZJp+ZW231KXVjmKelYYOxwRYmnLBNBaQz6TGX4wpR2nZvXOkXtHtQfWifi
7GFur6uKRT5cspPOLx4ViRoxQNKUEgwagvGViWmp2k+YMHTzJmMMbTvCPNnhOyXE
Aq07Ly46sORKrg5RvtCYHxexx1yGZg==
=XrgM
-----END PGP SIGNATURE-----
> 30. des. 2021 kl. 18:20 skrev Marin BERNARD <lists@olivarim.com>:
>>
>
> Thank you for your answer. I understand. I was reluctant to create tables for lists as small as 2-10 items, but it seems to be the way to go indeed.
> <publickey - lists@olivarim.com - 0xFD5D9CF2.asc>
For use cases like the ones in the referenced articles, where the data consists of IP addresses, potentially with masks, tables are definitely the way to go.
Tables have other advantages too, in that they offer flexibility not found elsewhere.
For example, they offer the ability to add to and remove addresses on the fly without reloading the configuration, you can save their content to files and initialize their content from external files.
For good measure, it might be useful to look into state tracking options and overflow tables for actually adaptive ('learning') configurations. Several of my more recent articles at the first URL in my signature have hopefully useful examples and references.
All he best,
Peter
—
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
No comments:
Post a Comment