hi, I have 7 mikrotik cpes at clients and all are connectiong to mikrotik AP.
I set rts cts treshold to 1 at all clients to check if there is rts packets with wireshark and mikrotik packet sniffer but there are none.
What can be the problem?
hi, I have 7 mikrotik cpes at clients and all are connectiong to mikrotik AP.
I set rts cts treshold to 1 at all clients to check if there is rts packets with wireshark and mikrotik packet sniffer but there are none.
What can be the problem?
What is the communication protocol? Is it just plain802.11x or Nstreme/Nv2 is used over it? RTS/CTS protection is used only when you are using 802.11x alone.
We are using RTS/CTS for packets with length over 500 bytes and it does work.
Plain wireless no Nv protocols.
How do you see it is working? i tried wireshark and cannot find any rts neither cts packet.
My setting is 512. At clients. Also tried with 1 to see if there is any rts. Not just MT cpes but various wireless AP clients do not send rts requests, at least I cannot detect them with wireshark.
No setting on AP.
use nstream
leave rts/cts as default
nstream automaticlly resolve hidden node problem
the throughput on AP significantly improved and we checked it using a wireless sniffer too.
I am not sure you can see management packets just by using wireshark. I think you need a special wifi driver/card for it which allows you to catch all packets properly including the management ones (if we are talking about windows). I am using wireshark only for ethernet traffic …
Here (http://wiki.wireshark.org/Wi-Fi) you can find an article which says there are 2 types of wifi card/drivers so it can happen you don’t get the managements frames…
Note: we verified the RTS/CTS behavior some time ago - on ROS 3.xx and wireless-test package. I believe the 4.x a 5.x ROS branches are OK too.
I guess this control packets are done in Hardware. So the PC will not even see this packets.
We’ve had not much success with RTS/CTS. Better use nstreme/nv2 instead.
I cannot use nstreme. As for the rtspackets there must be a way in wireshark to see them because there are filters for displaying just rts or just cts or any management packets.
I cannot use nstreme. As for the rtspackets there must be a way in wireshark to see them because there are filters for displaying just rts or just cts or any management packets.
You can do a packet dump on a MT-Router and load it into wireshark. But you will not see
rts/cts packets. May be there are special debugging cards/debugging mode for cards to get
this packets?? As it is time critical this will be done by the card.
I cannot use nstreme. As for the rtspackets there must be a way in wireshark to see them because there are filters for displaying just rts or just cts or any management packets.
Maybe this will help you http://revision3.com/search/search?q=wifi101
pussuns dont spam link is not usable it shows nothing just empty search through a site.
Ok so I cannot detect it with mikrotik sniffer neither wireshark and plain wifi card.
Ill search more on MONITOR mode then ![]()
pussuns dont spam link is not usable it shows nothing just empty search through a site.
Ok so I cannot detect it with mikrotik sniffer neither wireshark and plain wifi card.
Ill search more on MONITOR mode then
maybe this will interest you:
"If you have trouble getting Wireshark working with existing client cards, then consider purchasing AirPcap, which is a USB-based 802.11 radio designed to work effectively with Wireshark. It comes with drivers tuned to Wireshark and operates very well. An external antenna is also included with AirPcap, which increases the listening ability of the tool. "
a citation from http://www.wireless-nets.com/resources/tutorials/sniff_packets_wireshark.html
Or maybe you can try to find which wifi cards works with ‘pro’ sniffers like Airopeek etc and try them with wireshark
airodump and linux did the trick. tried it late yesterday. I saw RTS and CTS.
And then something confusing came out. RTS_TX RTS_RX :X
airodump and linux did the trick. tried it late yesterday. I saw RTS and CTS.
And then something confusing came out. RTS_TX RTS_RX :X
RTS received and RTS xmitted ?
Ah yes, possibile. ![]()