1.5 KiB
1.5 KiB
NFTables Naming Consolidation Summary
This document summarizes the changes made to consolidate the naming convention for IP allow/block lists in the NFTables integration.
Changes Made
-
Updated NFTablesProxy interface (
ts/proxies/nftables-proxy/models/interfaces.ts
):- Changed
allowedSourceIPs
toipAllowList
- Changed
bannedSourceIPs
toipBlockList
- Changed
-
Updated NFTablesProxy implementation (
ts/proxies/nftables-proxy/nftables-proxy.ts
):- Updated all references from
allowedSourceIPs
toipAllowList
- Updated all references from
bannedSourceIPs
toipBlockList
- Updated all references from
-
Updated NFTablesManager (
ts/proxies/smart-proxy/nftables-manager.ts
):- Changed mapping from
allowedSourceIPs
toipAllowList
- Changed mapping from
bannedSourceIPs
toipBlockList
- Changed mapping from
Files Already Using Consistent Naming
The following files already used the consistent naming convention ipAllowList
and ipBlockList
:
- Route helpers (
ts/proxies/smart-proxy/utils/route-helpers.ts
) - Integration test (
test/test.nftables-integration.ts
) - NFTables example (
examples/nftables-integration.ts
) - Route types (
ts/proxies/smart-proxy/models/route-types.ts
)
Result
The naming is now consistent throughout the codebase:
ipAllowList
is used for lists of allowed IP addressesipBlockList
is used for lists of blocked IP addresses
This matches the naming convention already established in SmartProxy's core routing system.