netfilter buglog - Oct 2018 - [Bug 1284] New: nft doesn't accept interface names starting with a number

https://bugzilla.netfilter.org/show_bug.cgi?id=1284

            Bug ID: 1284
           Summary: nft doesn't accept interface names starting with a
                    number
           Product: nftables
           Version: unspecified
          Hardware: x86_64
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: nft
          Assignee: pablo at netfilter.org
          Reporter: ville.skytta at iki.fi

...at least in iifname, oifname. Not a problem otherwise for the system to have
interface names starting with a number that I can see. For example:

# ip link show dev 5af3c3f0
14: 5af3c3f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc [...]

# nft add rule inet filter forward iifname 5af3c3f0 jump meh
Error: syntax error, unexpected jump
add rule inet filter forward iifname 5af3c3f0 jump meh
                                              ^^^^

This is with nft from Debian Stretch backports' 0.9.0-1~bpo9+1.

-- 
You are receiving this mail because:
You are watching all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.netfilter.org/pipermail/netfilter-buglog/attachments/20181024/547e04ac/attachment.html>

https://bugzilla.netfilter.org/show_bug.cgi?id=1284

Pablo Neira Ayuso <pablo at netfilter.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WONTFIX
             Status|NEW                         |RESOLVED

--- Comment #1 from Pablo Neira Ayuso <pablo at netfilter.org> ---
You have to quote your interface name:

nft add rule inet filter forward iifname \"5af3c3f0\" jump meh

-- 
You are receiving this mail because:
You are watching all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.netfilter.org/pipermail/netfilter-buglog/attachments/20190712/65cf3c04/attachment.html>