And suddenly:seems that Normis is drinking from february )) no news letter no devices no nothing xD
They are on the RB960PGS, so I would expect the same with the RB960PGS-PB. As far as I can tell, it's the same device, in an outdoor case.With the powerbox pro, are the PoE ports individually controllable?
Doing this would run the risk of the DHCP server assigning the same IP to a second device, before the first device has released it.You can make and scheduler each minute to invoke this script/ip dhcp-server lease remove [find dynamic]
This issue is discussed at length earlier in this thread, so your less than helpful reply is also less than accurate.Wrong thread, sorry
Wait: SwOS has tftp/bootp recovery? Why didn't I know this?!We have tha same situation. Only tftp recovery helped. O course after recovery you have to configure it like a new one... :/
I've been seeing the same thing since they resumed x86 support with the separate package, FWIW.I get huge discrepancy in Ping latency using the Dude on a CHR 6.35. Pings from Winbox are good. Pings from Dude client are bad.
++This.+1 Please give us DHCP and a subnet/gateway.Why not add dhcp client option in swos? There are many situations in wich Rb can't be accessed because of static IP and the lack of subnet mask and gateway.
The release notes for 6.20 suggest that Dude on ROS wasn't completely off their minds:The Dude hasn't been supported on ROS for quite some time, the package isn't even available for download anymore.
When I set the UPA to poe-out=forced-on, the 1100 powers up fine.The RB1100 power consumption are not sufficently covered by OmniTik...
Do you use AWG24 cable ? Patchcables are only AWG26 and with 30 meters of cable you will get problems..
Cat5 (24 AWG solid-conductor, foil-shieded CMX)
30m (100ft.)Is that 100 ft about 30meters or 100 meters?Around 100' to the OmniTik UPA, then another 100' to the most distant unit (the others are 20-80' away).
Yes, that much I know.r52 does not support 802.11n as hardware changes are required for that.
FWIW, most of the WDS issues I have encountered were finally fixed as of 5.18. (better late than never)I also have the same bridging/WDS issues, which has put me off MikroTik AP's... WDS systems since 4.17 it just doesn't work...
Maybe a more recent thread will yield some answers, or at least posting there might draw more attention to the problem.Is anyone out there listening?
And invest in a Cat5 cable tester! Even one of the inexpensive ones (~$10) will save you some big headaches.Then I changed the cabling and connectors to two RB433... Everything worked like a charm since then. I still have to change one cable... Try using a different cable
Maybe he has a bunch of single-pol panels on hand, and wants to reduce the recommended 10' separation when using the same polarity?Sure ,it is no problem .but I don't understand why you want to do that.
The OP is concerned that an "unnaturally" low noise floor might indicate a defective receiver. And he has a point. Even with low-power cards with no antenna connected, internal RF is usually enough to keep the noise floor above -100....this is very good result. Nothing for worry about it.
It would be helpful to know the nature of the problem(s):yes