From: Rasca <rasca-ml@triad.de>
To: Jeffrey Laramie <JALaramie@Loudoun-Fairfax.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: port forwarding with one interface to trace traffic?
Date: Thu, 22 Jan 2004 14:36:34 +0100 [thread overview]
Message-ID: <400FD1E2.8090604@triad.de> (raw)
In-Reply-To: <400FCD45.3050604@Loudoun-Fairfax.com>
Hi,
Jeffrey Laramie schrieb:
>
>>
>> 3. Connect a hub (not a switch) to the printer's ethernet cable (or to
>> the Mac's ethernet cable), and plug the Linux machine running ethereal
>> into the hub, so you can sniff the packets off the wire without any NAT.
>>
>>
>
> This is dangerously OT, but what's the difference? I always thought that
> the difference between a switch and a hub was simply a matter of
> internal plumbing that affected how the pipes were connected and had no
> effect on the actual tcp/ip connections. I've used them interchangeably
> and haven't seen a difference. Maybe someone has a link that could
> educate me more better! :-)
A "hub" broadcasts all packets to all port. And yes - that was
the way I choosed, cause it's more simple to setup (I found an
old hub..) and it's working.
thx to Antony.
cu
rasca
--
_______________________________________________________________
| Triad Berlin Projektgesellschaft mbH | http://www.triad.de/ |
next prev parent reply other threads:[~2004-01-22 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 15:45 port forwarding with one interface to trace traffic? Rasca
2004-01-21 16:16 ` Caracal - G. Hostettler
2004-01-21 16:46 ` Rasca
2004-01-21 22:07 ` Antony Stone
2004-01-22 13:16 ` Jeffrey Laramie
2004-01-22 13:36 ` Rasca [this message]
2004-01-22 13:39 ` PPTP and GRE Jan Kaastrup
-- strict thread matches above, loose matches on Subject: below --
2004-01-22 15:33 port forwarding with one interface to trace traffic? Piers Finlayson
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=400FD1E2.8090604@triad.de \
--to=rasca-ml@triad.de \
--cc=JALaramie@Loudoun-Fairfax.com \
--cc=netfilter@lists.netfilter.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 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.