Re: [nftables 0.9.2] does jump require a kconf to be set to get it working?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 12/02/2020 18:52, ѽ҉ᶬḳ℠ wrote:

On 12/02/2020 18:40, kfm@xxxxxxxxxxxxx wrote:
On 12/02/2020 16:41, ѽ҉ᶬḳ℠ wrote:
Have tried to some online guidance which NFT features require which kernel config to be set to get them working and whether jump is among such feature set.

Because hitting:

Error: Could not process rule: Not supported

with:

table inet filter  {
  chain input  { type filter hook input priority 0; iifname pppoe-wan jump wan_i }
}

As shown, this isn't quite valid nft syntax. Please post a minimal - but complete - ruleset that reproduces your issue in a form that is verbatim. Include the wan_i definition, even if it merely an empty chain.

table inet filter {
    chain input { type filter hook input priority 0; iifname pppoe-wan jump wan_i; }
     chain wan_i  { type filter hook input priority 0; }
}


You may not jump to the wan_i chain because it is hooked. It makes as little sense as trying to run iptables -I INPUT -j INPUT.

--
Kerin Millar



[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux