I am just launching into using some Groove 2’s and don’t seem to be able to route correctly. I have setup many RB411’s as clients and RB433’s as AP’s, thought I had it down pat. Looking to using Grooves in lieu of Bullets and RB411’s if these are as good as reported here.
Setting up my first Groove as a client, I can login to the AP, get an IP, AP shows correct connection, jut like some 30 odd other clients. I have DHCP server to Eth1, IP’s being issued OK. From the Groove I can ping the world, I can ping all inside IP’s, but from the inside, (notebook), I cannot ping anything past Eth1 (192.168.88.1).
Naturally one would blame routing or NAT in the Firewall. But these settings are identical to working RB411’s.
RB411’s and RB433’s are either V3.xx or 4.xx, the Groove is 5.11. The Groove has several other more settings and options than earlier versions, but have scoured through these. I usually use Winbox.
Have attached supout.rtf file if someone can help please.
Unless I’m misunderstanding your application, don’t you need to masquerade traffic originating from clients on the wlan1 interface? (The masquerade rule in your rsc applies to traffic going to clients.)
Thanks again Hotz1, my application is to use the Groove as a wireless client, (set as Station). In the past I have always needed to set the firewall srcnat, out i/f wlan1, and masquerade.
Like I hve said, I have checked again and again the settings of all RB’s as clients, and applied the same settings, but have failed in geting through traffic.
in Groove we have the Quickset which will quickly set your router up for this task. Open the IP address from the LAN side, and it will launch Quickset configuration page in your browser. Choose the option to reset the device. After that is done, simply choose “CPE” from the dropdown, and the device will be as good as done. Just IP and encryption settings will need to be set there.
Wellllllllllll, how easy is that normis??? Thank you, in Australia we say, “I owe you a beer”.
I had to upgrade to 5.17, (your screen showed 5.18rc1). THEN and only then did I see Quickset. Or was/is there a bug in 5.11?
All works OK, will go through the .rsc file to see any differences I may have missed.
BUUUUT, have now lost the signal strength lights??? Yet have good connection strengths. Had the lights before upgrade.
Have probably 50 odd Bullets in service, much more convenient than rb’s in enclosures etc, so will see how these go now. Always liked ROS over AirOS anyway.
It is really great to see you got it working. Yes, Quickset is a new feature - it allows you to configure devices with a few clicks. We only added it recently (RouterOS v5.14). We plan to add more features, and more modes (in addition to CPE/AP). I will check why you lost the signal LEDs, will get a Groove to test it.
I have done a bit of playing around myself with this Groove, altered the wireless protocol that was setup in quickset from ‘Nv2 nstreme 802.11’ to only 802.11. The lights suddenly work, signal strength from -65 to -61, actual throughput very little change, Tx/Rx rate only 5.5mbs/2mbs though, from 11/11. (I have all my AP’s set to only B 11mbs) I don’t have Nstreme running on the AP’s, only for backhaul, RB to RB. There are too many non RB clients to have Nstreme for the AP’s.
As a suggestion for future Quickset modes, “load-balancing router” (implementing PCC) gets my vote: designate LAN & WAN interfaces, and Quickset adds the rules.
