bugzilla-daemon at netfilter.org
2017-Aug-23 20:14 UTC
[Bug 1177] New: Export 'ct_zone' field.
https://bugzilla.netfilter.org/show_bug.cgi?id=1177 Bug ID: 1177 Summary: Export 'ct_zone' field. Product: ulogd Version: SVN (please provide timestamp) Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: ulogd Assignee: netfilter-buglog at lists.netfilter.org Reporter: chessnut at outlook.com Hi there, how are you guys doing. Not sure if I missed it in the codebase, but it appears that zone field is not exported from ulogd right now. A git grep for 'zone' only turns up timezone. According to the ovs ofctl, there is 'zone' information exported: http://openvswitch.org/support/dist-docs/ovs-ofctl.8.txt My employer, Nutanix, would really like to use this so that we can distinguish between vlans for the same 5-tuple (src IP, src port, dest IP, dest port, protocol). History of the zone concept: - some discussion about using namespaces to solve 5-tuple collisions: http://netdev.vger.kernel.narkive.com/tg0lEdAG/connection-tracking-and-vlan - somewhere along the way, Patrick McHardy mentions the idea of "conntrack zones" - This the RFC (2010): https://lwn.net/Articles/370152/ -- 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/20170823/cfa5c5a0/attachment.html>
Reasonably Related Threads
- [Bug 665] Can't start error opening /var/log/ ...
- ULOG logging may fail on some ulogd/logrotate configurations
- [Bug 1218] New: ULOGD PCAP Plugin Missing Ethernet Headers
- [Bug 977] ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol
- [Bug 741] New: ULOGD segfaults on init