Hi,
I would like to see PPPoE snooping feature in ROS. It could allow to identify (at login time) to what AP is an PPPoE user connected to for example.
As I wrote before - if you think the MT box is working improperly, send message to support@mikrotik.com.dada,
and ... what we can do with the sutiation ?
so If you are aware of the NAT - what is the problem with the packet?NAT - is the Mikrotik box under Router OS ...
Yes, please. I would like to say that I got empty password box each time I start the Winbox RC17 - even if previous session was used with manually entered password. (I am using [X] Keep password).We will revert change which set credentials to admin without password.
background radar detection would be even nicerYes, +1. Background scan would be nice. If station can scan, and not disconnect from AP
no I am using Winbox on Windows 7@dada You're using Linux + Wine 1.4.1?
When winbox for Linux? or linbox?
note: you need inspect Last Measured times on client not on APNow with uptime only 22days. P2P link is locked to 6,5Mbit. Customers call - speed is terrible
what is the speed and quality on pure wireless (i.e do the test between IPs assigned to the wireless interfaces - 172.16.0.x in the wiki example)On both sides there are RB 411. CPU is around 10% at station side, and 35% at AP side during the highest traffic.
Every Thing You Always Wanted to Know About Station Modes But Were Afraid to Ask Google:Anybody?
maybe you just filled in the trap community but you didn't add any 'access' community - which is hidden behind the 'Communities' button in ROS 5.X.
Needless to say, SNMP is enabled and there is a ver 1 trap community called public.
what is the RX level after you lowered the TX power? If it is different from the calculated value you should solve the difference problem first (IMHO). The difference approx 5 dBm should be OK.yes i am using grounded cable
and also i have the tx power set to 19Dbm now but same result
Maybe..At 2.4ghz - there isn't the space on a mini pic form factor for a physical filter - wavelength cant be miniaturized
RTS received and RTS xmitted ?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
to my best knowledge the hw-retries are ignored by NV2 (and nstreme too)...Have you tried to increase hw-retries? What data-rates have you selected?
In the first message I described that if the scan-list starts with 5500 (5500-5700) the client connects to the AP. But maybe I didn't understand the question... I didn't try to use 5500 alone in scan-list.If you set 5500 manually to scan-list at the client.
Does it work?
Thanks for the answer.Change TCP Connection Count to 1
It's not a bug, it's a feature. Read changelog!
no sniffer.You are not trying to run sniff or snooper by any chance?
I know. But if the network cards/chips support more details about errors it would be fine if RouterOS displays themInformation that you mention is not available at RouterOS.
what do you mean? The IP(s) of the machine the script is running on?For how to determine the IP address of the source script !!,thanks!!!!!
what cache do you mean?how can i activate the cache in mikrotik version 2.9.27
please and thanks for all