RE: port forwarding with one interface to trace traffic?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Also be warned that many "hubs" on the market are actually switches.  I find
this terribly annoying.

Cheers,
Piers

-----Original Message-----
From: Rasca [mailto:rasca-ml@xxxxxxxx]
Sent: 22 January 2004 13:37
To: Jeffrey Laramie
Cc: netfilter@xxxxxxxxxxxxxxxxxxx
Subject: Re: port forwarding with one interface to trace traffic?


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/ |



[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux