El día jueves, julio 18, 2019 a las 12:41:42p. m. +0200, Matthias Apitz
escribió:
> I compiled net/tcpdump to look into that and it supports:
>
> # /usr/local/sbin/tcpdump -ni wlan0 -y IEEE802_11_RADIO
>
> and the OpenBSD man page explains what IEEE802_11_RADIO is. I think,
> ...
This morning
-L List the known data link types for the interface and exit.
# tcpdump -ni wlan0 -L
Data link types for wlan0 (use option -y to set):
EN10MB (Ethernet)
IEEE802_11_RADIO (802.11 plus radiotap header)
чт, 18 июл. 2019 г. в 13:41, Matthias Apitz :
> El día jueves, julio 18, 2019 a las 12:04:2
El día jueves, julio 18, 2019 a las 12:04:27p. m. +0200, Matthias Apitz
escribió:
> El día miércoles, julio 17, 2019 a las 11:45:49p. m. -0700, Adrian Chadd
> escribió:
>
> > Hi!
> >
> > So, you don't set the monitor flag like you do on linux. you create a
> > monitor VAP instead or you just u
El día miércoles, julio 17, 2019 a las 11:45:49p. m. -0700, Adrian Chadd
escribió:
> Hi!
>
> So, you don't set the monitor flag like you do on linux. you create a
> monitor VAP instead or you just use tcpdump with the right flags.
>
> Try:
>
> tcpdump -ni wlan0 -y IEEE802_11_PROTO
>
> That'll
On Thu, 18 Jul 2019 08:20:33 +0200
Matthias Apitz wrote:
> El día miércoles, julio 17, 2019 a las 11:13:14p. m. +0200, Vladimir Botka
> escribió:
>
> >
> > FreeBSD is not needed to analyse the the problem.
> > Use whatever system is able
> > to set wifi card into the "monitor" mode and sniff
Hi!
So, you don't set the monitor flag like you do on linux. you create a
monitor VAP instead or you just use tcpdump with the right flags.
Try:
tcpdump -ni wlan0 -y IEEE802_11_PROTO
That'll put the NIC into monitor mode on the current channel, even in
station mode, and let you do normalt raffi
El día miércoles, julio 17, 2019 a las 11:13:14p. m. +0200, Vladimir Botka
escribió:
> > I only have FreeBSD laptops (and an older Ubuntu) and the question was
> > not if FreeBSD is needed, but if FreeBSD is *able* to capture Wifi.
> > Thanks
> > matthias
>
> Yes. FreeBSD is able to capture
On Wed, 17 Jul 2019 20:53:24 +0200
Matthias Apitz wrote:
> El día miércoles, julio 17, 2019 a las 08:26:02p. m. +0200, Vladimir Botka
> escribió:
>
> > > I installed wireshark-2.6.5_2 in my FreeBSD (CURRENT from December last
> > > year). I tried to enable from
> > > View --> [x] Wireless Too
El día miércoles, julio 17, 2019 a las 08:26:02p. m. +0200, Vladimir Botka
escribió:
> > I installed wireshark-2.6.5_2 in my FreeBSD (CURRENT from December last
> > year). I tried to enable from
> > View --> [x] Wireless Toolbar
> > but this gives an error about "Failed to initialize ws80211"
On Wed, 17 Jul 2019 19:35:32 +0200
Matthias Apitz wrote:
> El día miércoles, julio 17, 2019 a las 09:05:43a. m. +0200, Vladimir Botka
> escribió:
> > On Wed, 17 Jul 2019 07:38:26 +0200
> > Matthias Apitz wrote:
> >
> > > ... The association requests are always rejected with a package
> > > C
El día miércoles, julio 17, 2019 a las 09:05:43a. m. +0200, Vladimir Botka
escribió:
> Hello,
>
> On Wed, 17 Jul 2019 07:38:26 +0200
> Matthias Apitz wrote:
>
> > ... The association requests are always rejected with a package
> > CTRL-EVENT-ASSOC-REJECT with 'status_code=1'...
> > Do we have
Hello,
On Wed, 17 Jul 2019 07:38:26 +0200
Matthias Apitz wrote:
> ... The association requests are always rejected with a package
> CTRL-EVENT-ASSOC-REJECT with 'status_code=1'...
> Do we have any tool in FreeBSD to monitor/debug this problem between the
> device in question and the AP? Any othe
Hello,
I have at home the problem that all my Wifi devices (four FreeBSD laptops,
one Ubuntu laptop and three Ubuntu mobile phones) can connect fine to my AP.
Only one can't anymore (it worked fine in the past but since some months can't
associate anymore). The association requests are always rej
13 matches
Mail list logo
