On Fri, Feb 27, 2004 at 02:27:57PM -0800, Richard Bejtlich wrote:
> >From what I've read elsewhere on the lists, I'm not
> seeing what I should using the new IEEE802_11_RADIO
> link type. Tcpdump is compiled --WITH_RADIOTAP:
Don't use monitor mode; it's a misnomer. Try without using monitor
mode
Hello,
>From what I've read elsewhere on the lists, I'm not
seeing what I should using the new IEEE802_11_RADIO
link type. Tcpdump is compiled --WITH_RADIOTAP:
--
orr:/root# uname -a
FreeBSD orr.taosecurity.com 5.2-SECURITY FreeBSD
5.2-SECURITY #0: Thu Feb 5 10:24:52 GMT 2004
[EMAIL PROTECT
Hello. I posted this questions three days ago; I didn't get a reply yet. I
have been fighting the problem today whole day without any luck, and the
more I dig into the problem, the more I feel it should not be a very rare
problem. Perhaps I didn't descirbe my problem clear enough in my last
ema
Hi all,
On Wed, Feb 25, 2004 at 05:21:34PM +0300, Gleb Smirnoff wrote:
> On Wed, Feb 25, 2004 at 04:19:51PM +0200, Iasen Kostov wrote:
> I> >>16:26:23.287642 0:1:2:9>c:cf:e2 0:02:55:b0:90:e4 0800 60: 127.0.0.1.80 >
> I> >>192.168.118.205.1046: R 0:0(0) ack 1959723009 win 0
> I> >
> I> >This is so
Hello,
I found the "problem" with the code shown and can explain it as follows:
When binding a socket to a unicast address you are saying:
- "all received packets with the given unicast dest address and (UDP) port
should be delivered to this socket"
- "and all packets sent from this socket
Hi,
Yes, the bind() succeeded, and in fact the receiver side was able to receive
packets. Only sendto() failed.
Don
> From [EMAIL PROTECTED] Thu Feb 26 21:54:52 2004
>
> > On Thu, 26 Feb 2004 11:27:31 -0500 (EST),
> > Donald McLachlan <[EMAIL PROTECTED]> said:
>
> > In preparation
