* Bridging and IPT Queueing
@ 2004-07-09 5:05 Jim Mar
2004-07-09 16:48 ` Henrik Nordstrom
0 siblings, 1 reply; 6+ messages in thread
From: Jim Mar @ 2004-07-09 5:05 UTC (permalink / raw)
To: netfilter-devel
I've been looking at IPT Queueing in a bridging environment on
a 2.6 kernel and noticed that the indev associated with the
queued packet is the bridge device, eg. br0, instead of the
physical interface. While this is true, it would be nice to know
the physical indev of the packet. Is there a way of finding it?
I tried looking at the HW address, but that seems broken.
Thanks,
Jim
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Bridging and IPT Queueing
2004-07-09 5:05 Bridging and IPT Queueing Jim Mar
@ 2004-07-09 16:48 ` Henrik Nordstrom
2004-07-12 4:13 ` Jim Mar
0 siblings, 1 reply; 6+ messages in thread
From: Henrik Nordstrom @ 2004-07-09 16:48 UTC (permalink / raw)
To: Jim Mar; +Cc: netfilter-devel
On Thu, 8 Jul 2004, Jim Mar wrote:
> I've been looking at IPT Queueing in a bridging environment on
> a 2.6 kernel and noticed that the indev associated with the
> queued packet is the bridge device, eg. br0, instead of the
> physical interface. While this is true, it would be nice to know
> the physical indev of the packet. Is there a way of finding it?
The physdev match?
> I tried looking at the HW address, but that seems broken.
This should give you the destination HW address of the packet, not the
interface it was received on.
Regards
Henrik
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Bridging and IPT Queueing
2004-07-09 16:48 ` Henrik Nordstrom
@ 2004-07-12 4:13 ` Jim Mar
2004-07-12 10:22 ` Henrik Nordstrom
0 siblings, 1 reply; 6+ messages in thread
From: Jim Mar @ 2004-07-12 4:13 UTC (permalink / raw)
To: Henrik Nordstrom; +Cc: netfilter-devel
Henrik Nordstrom wrote:
>On Thu, 8 Jul 2004, Jim Mar wrote:
>
>
>
>>I've been looking at IPT Queueing in a bridging environment on
>>a 2.6 kernel and noticed that the indev associated with the
>>queued packet is the bridge device, eg. br0, instead of the
>>physical interface. While this is true, it would be nice to know
>>the physical indev of the packet. Is there a way of finding it?
>>
>>
>
>The physdev match?
>
>
Yes, physdev match will work. Thanks. Using physdev match, can I get
the physical indev for a redirected packet?
>
>
>>I tried looking at the HW address, but that seems broken.
>>
>>
>
>This should give you the destination HW address of the packet, not the
>interface it was received on.
>
>Regards
>Henrik
>
>
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Bridging and IPT Queueing
2004-07-12 4:13 ` Jim Mar
@ 2004-07-12 10:22 ` Henrik Nordstrom
2004-07-13 4:29 ` Jim Mar
0 siblings, 1 reply; 6+ messages in thread
From: Henrik Nordstrom @ 2004-07-12 10:22 UTC (permalink / raw)
To: Jim Mar; +Cc: netfilter-devel
On Sun, 11 Jul 2004, Jim Mar wrote:
> Yes, physdev match will work. Thanks. Using physdev match, can I get
> the physical indev for a redirected packet?
You should.
Regards
Henrik
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Bridging and IPT Queueing
2004-07-12 10:22 ` Henrik Nordstrom
@ 2004-07-13 4:29 ` Jim Mar
2004-07-13 7:07 ` Henrik Nordstrom
0 siblings, 1 reply; 6+ messages in thread
From: Jim Mar @ 2004-07-13 4:29 UTC (permalink / raw)
To: Henrik Nordstrom; +Cc: netfilter-devel
Henrik Nordstrom wrote:
>On Sun, 11 Jul 2004, Jim Mar wrote:
>
>
>
>>Yes, physdev match will work. Thanks. Using physdev match, can I get
>>the physical indev for a redirected packet?
>>
>>
>
>You should.
>
>
>
Sorry, I meant from user space, and if so, how?
Jim
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Bridging and IPT Queueing
2004-07-13 4:29 ` Jim Mar
@ 2004-07-13 7:07 ` Henrik Nordstrom
0 siblings, 0 replies; 6+ messages in thread
From: Henrik Nordstrom @ 2004-07-13 7:07 UTC (permalink / raw)
To: Jim Mar; +Cc: netfilter-devel
On Mon, 12 Jul 2004, Jim Mar wrote:
> >>Yes, physdev match will work. Thanks. Using physdev match, can I get
> >>the physical indev for a redirected packet?
>
> Sorry, I meant from user space, and if so, how?
You can Use MARK to set a unique nfmark depending on the physdev and then
make decisions in userspace depending on this.
Regards
Henrik
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2004-07-13 7:07 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-07-09 5:05 Bridging and IPT Queueing Jim Mar
2004-07-09 16:48 ` Henrik Nordstrom
2004-07-12 4:13 ` Jim Mar
2004-07-12 10:22 ` Henrik Nordstrom
2004-07-13 4:29 ` Jim Mar
2004-07-13 7:07 ` Henrik Nordstrom
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.