Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Strange behaviour with sniffer filtering
0 views
Skip to first unread message
James
Dec 29, 2009, 1:27:48 PM12/29/09
to
I use Wireshark to sniff a LAN. When I filter a certain address I don't see
any packet but if I don't filter anything I see packets with this specific
address.
Is there any possible explanation to that phenomena?
Regards
James
any packet but if I don't filter anything I see packets with this specific
address.
Is there any possible explanation to that phenomena?
Regards
James
Farooque Khan
Dec 30, 2009, 5:47:25 AM12/30/09
to
What is your filter expression? Is it a capture or display filter? It's
difficult to answer without more info.
difficult to answer without more info.
--
-Farooque
"James" <ja...@mirk.com> wrote in message
news:%23i48cSL...@TK2MSFTNGP05.phx.gbl...
James
Dec 30, 2009, 12:59:10 PM12/30/09
to
Its a very unic enviroment(as suggested in this NG few days ago):
Instead of connceting my NAT router directly to a modem I created a LAN by
using a HUB and conncting both to this LAN. Then , I conected also a nother
PC running a Wireshark to monitor the packets running between the router and
the modem. The public address of the router is 77.126.97.244 I set the
monitor PC address as 77.126.97.200 .
The filter is a capture filter.
I hope this helps.
Regards
James
Instead of connceting my NAT router directly to a modem I created a LAN by
using a HUB and conncting both to this LAN. Then , I conected also a nother
PC running a Wireshark to monitor the packets running between the router and
the modem. The public address of the router is 77.126.97.244 I set the
monitor PC address as 77.126.97.200 .
The filter is a capture filter.
I hope this helps.
Regards
James
"Farooque Khan" <farooqu...@info-spectrum-removenospam.com> wrote in
message news:u5qn01Ti...@TK2MSFTNGP02.phx.gbl...
0 new messages