From: "Javier Prieto Martínez" <javier.prieto.ext@juntadeandalucia.es>
To: Marc Cozzi <cozzi@hertz.rad.nd.edu>
Cc: netfilter@vger.kernel.org
Subject: Re: Redirecting ports in a bridge
Date: Fri, 18 Apr 2008 14:34:42 +0200 [thread overview]
Message-ID: <48089562.6010908@juntadeandalucia.es> (raw)
In-Reply-To: <9376B7D1C2D4834285B48542AECC46F113FADC@faraday.rad.nd.edu>
I'm using tcpdump for testing, but my appliance has it's own Java client
for that purpose.
Marc Cozzi escribió:
> Jan,
>
> Can I ask what you are using for traffic logging
> on your bridge? I am in need of fairly decent accounting
> software for all traffic passing through the bridge.
> HTTP, P2P, SSH etc. Bytes, time, IP# and so forth.
>
> Regards,
>
> --marc
>
>
>
>> -----Original Message-----
>> From: netfilter-owner@vger.kernel.org
>> [mailto:netfilter-owner@vger.kernel.org] On Behalf Of Javier
>> Prieto Martínez
>> Sent: Friday, April 18, 2008 7:41 AM
>> To: Jan Engelhardt; netfilter@vger.kernel.org
>> Subject: Re: Redirecting ports in a bridge
>>
>> I need the bridge because the appliance is supposed to be
>> totally trasparent to the network, as its main use is logging traffic.
>>
>> It just has an IP address for administration purposes, but it
>> doesn't really need it. Anyway, I can disable bridging as
>> it's an appliance with a closed configuration.
>>
>>
>>
>> Jan Engelhardt escribió:
>>
>>> On Friday 2008-04-18 12:55, Javier Prieto Martínez wrote:
>>>
>>>
>>>>>
>>>>>
>>>>>
>>>> You're right. I'll try again:
>>>>
>>>> * LAN1 (192.168.1.0/22)
>>>>
>>>> [CLIENTS]--- [ROUTER (.7)]
>>>>
>>>>
>>>> * LAN2 (192.168.2.0/22)
>>>>
>>>> [ROUTER (.7)] -- [APPLIANCE (.40)] -- SERVERS (.1&.2)
>>>>
>>>>
>>>>
>>>>> IF you do bridge, then despite cabling being correct, you
>>>>>
>> get a NAT
>>
>>>>> shortcircuit: jengelh.medozas.de/images/dnat-mistake.png
>>>>>
>>>>>
>>>>>
>>>> That's probably the problem, as far as I've seen with TCPDump. The
>>>> point is, how can I fix that shortcut?
>>>>
>>>>
>>> You do not seem to need a bridge.
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe
>>>
>> netfilter"
>>
>>> in the body of a message to majordomo@vger.kernel.org More
>>>
>> majordomo
>>
>>> info at http://vger.kernel.org/majordomo-info.html
>>>
>>>
>>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> netfilter" in the body of a message to
>> majordomo@vger.kernel.org More majordomo info at
>> http://vger.kernel.org/majordomo-info.html
>>
>>
>
>
next prev parent reply other threads:[~2008-04-18 12:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 9:27 Redirecting ports in a bridge Javier Prieto Martínez
2008-04-18 10:35 ` Jan Engelhardt
2008-04-18 10:55 ` Javier Prieto Martínez
2008-04-18 11:29 ` Jan Engelhardt
2008-04-18 11:41 ` Javier Prieto Martínez
2008-04-18 12:26 ` Marc Cozzi
2008-04-18 12:34 ` Javier Prieto Martínez [this message]
2008-04-23 15:25 ` Jan Engelhardt
2008-04-18 14:38 ` Grant Taylor
2008-04-21 6:55 ` Javier Prieto Martínez
2008-04-22 1:30 ` Grant Taylor
2008-04-22 6:15 ` Javier Prieto Martínez
2008-04-22 14:29 ` Grant Taylor
2008-04-22 15:10 ` Javier Prieto Martínez
2008-04-22 19:24 ` Grant Taylor
2008-04-23 15:24 ` Jan Engelhardt
2008-04-23 17:16 ` Grant Taylor
2008-04-23 18:48 ` Jan Engelhardt
2008-04-23 18:57 ` Grant Taylor
2008-04-24 6:15 ` Javier Prieto Martínez
2008-04-18 14:34 ` Grant Taylor
2008-04-18 14:44 ` Grant Taylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48089562.6010908@juntadeandalucia.es \
--to=javier.prieto.ext@juntadeandalucia.es \
--cc=cozzi@hertz.rad.nd.edu \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox