Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.01.org/mailman/listinfo/connman
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. autoload of nft modules (Daniel Wagner)
----------------------------------------------------------------------
Message: 1
Date: Wed, 27 Apr 2016 10:52:13 +0200
From: Daniel Wagner <[email protected]>
To: [email protected]
Cc: [email protected], Dragos Tatulea <[email protected]>
Subject: autoload of nft modules
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Hi,
Dragos and I are working on getting nft support into ConnMan [1]. Now we
face a small problem with the rule we load, which are essentially:
nft add table connman
nft add chain connman nat-prerouting \
{ type nat hook prerouting priortiy 0 ; }
nft add chain connman nat-postrouting \
{ type nat hook postrouting priortiy 0 ; }
nft add chain connman filter-output \
{ type filter hook output priority 0 ; }
These work nicely using the nft CLI but when we run those commands
via libnftnl after a fresh reboot of the system, there is a ENOENT at
the third rule.
If though all related modules are loaded (e.g. via running the nft cli
first) there is no problem.
So my question is, do we need to load the modules our self first or
should the kernel load the modules by itself?
That is observed with libnftnl 1.0.5 and kernel 4.4.6.
cheers,
daniel
[1] https://lists.01.org/pipermail/connman/2016-April/000643.html
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 6, Issue 21
**************************************
