<html>
<head>
<base href="https://bugzilla.netfilter.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - No support for PHYSDEV within NFLOG stack"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1505">1505</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>No support for PHYSDEV within NFLOG stack
</td>
</tr>
<tr>
<th>Product</th>
<td>ulogd
</td>
</tr>
<tr>
<th>Version</th>
<td>2.0.0beta1
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86_64
</td>
</tr>
<tr>
<th>OS</th>
<td>Ubuntu
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>P5
</td>
</tr>
<tr>
<th>Component</th>
<td>ulogd
</td>
</tr>
<tr>
<th>Assignee</th>
<td>netfilter-buglog@lists.netfilter.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>aidan.walton@gmail.com
</td>
</tr></table>
<p>
<div>
<pre>Hi,
I have tried to inspect the various elements involved in the NFLOG target when
defined inside iptables. Specifically I am trying to understand what happens to
information about the physdev selected during the route process. When the older
nflog_ipv4 module is used and messages from iptables TRACE target are viewed
via dmesg. The input and output types PHYSIN and PHYSOUT can be seen:
as exmaple:
IN=int_br0 OUT= PHYSIN=int_eth0.
However when using the nfnetfilter_log module and ulogd this information is not
parsed. I can only see IN/OUT and not PHYSIN/PHYSOUT
Looking at the libnetfilter_log code, I see functions such as:
uint32_t nflog_get_physindev(struct nflog_data *nfad)
This would appear to suggest that this data is handled by the kernel module.
However in the ulogd plugin ulogd_inppkt_NFLOG, I can not find any reference to
this object or any object of a similar name.
The outputs from ulogd never contain any references to physdev.
Either I misunderstand the usage or the data is not actually coming from the
kernel module, or the plugins do not support it.
Either way, if I want to trace traffic with iptables and see the data about
physdev-in or physdev-out I am forced to swap back to the nflog_ipv4 module,
inspect dmesg and then drop back into nfnetfilter_log for ongoing logging.
Hmmmm, any suggestions?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>