Meraki

NolanHerring · ‎Nov 8 2019

Hmm...I must have missed something. What arrow to the wall are you talking about for the MR84? I've never seen anything on any Meraki AP that referenced having to aim it or orient it in a certain direction for the location analytics. I doubt it matters for the MR55, since its all omni-directional

NolanHerring · ‎Nov 6 2019

This is expected because people won't want that constant monitoring running as it will consume bandwidth, enough that on cellular you won't want it on.

NolanHerring · ‎Nov 1 2019

@PhilipDAth wrote: I can't find it now (it was in the release notes), but a while ago there was an ARP bug that affected a small number of ISPs. Basically the MX would ARP for the configured default gateway and due to a bug this would fail, so it wouldn't use the configured settings on the WAN port. This sounds very similar. I would have thought it would be long fixed by 14.40. Oh snap really? I have a single site (Spectrum ISP) that has that issue where the devices and MX will randomly show cloud connectivity loss. Not all at once mind you, just an AP here, or a switch there. So it makes the over-all ORG view 'green bar' look real bad. Support said modem wasn't responding to ARPs so I assumed it was the modem from the ISP. They replaced. Still having the issue. Sort of just gave up on trying to fix it. Running 14.39

NolanHerring · ‎Nov 1 2019

Way to go guys !

NolanHerring · ‎Nov 1 2019

Minimum you should need MX64 One of the MR45 or MR55 since you want to exact same model AP. AP models are more finicky than anything else Two MS125, although you might want to verify if that is the switch model you want as they don't support physical stacking (if that is something your going to be doing).

NolanHerring · ‎Nov 1 2019

I would bypass it for now and test it with a laptop with the STATIC IP information on the laptop, verify it works. If it doesn't, that would explain why its falling back to DHCP.

NolanHerring · ‎Oct 28 2019

I've never tested it but I'm pretty sure that the Per-AP VLAN Tagging will not allow smooth roaming. Its going from one subnet to another (one vlan to another), which is forcing the clients to grab a new IP etc. Your best option (what I do) is use a /23 or /22 for the entire 'building' and the SSID drops onto that VLAN which spans everywhere. Assuming your core-to-access layer allows for such a thing

NolanHerring · ‎Oct 25 2019

Thanks for the update. Feel free to post back here if you hear anything else as others such as myself will be curious 😃

NolanHerring · ‎Oct 25 2019

@Fernando_AR Have you reached out to support. Curious if they gave you any feed back yet.

NolanHerring · ‎Oct 25 2019

You will be missed, Sweet Caroline... BAM BAM BAM.

NolanHerring · ‎Oct 24 2019

Also the reign in your TX power level, to add to that. Create a min/max (usually something like 11-17 dBm for 5GHz for example, and 8-11 for 2.4GHz etc.) Depends on the layout and how the survey was done. You won't want an AP blasting

NolanHerring · ‎Oct 24 2019

stair wells are usually 100% brick/concrete. Your not going to have a smooth roam between floors usually. If you did managed to have smooth roaming, you still might have issues because your going from one subnet to another, by issues i mean with real-time applications. If you can make it a /23 or /22 then that would minimize any disconnects due to having to get a new IP on the new subnet etc. Not sure if that matters though if there is no smooth roaming between floors. Actually might matter if the floor to floor seperation is weak. so clients on floor 2 might connect to an AP on floor 1 and vice versa. Floor is just a fancy word for wall afterall 😃 I could see if that happens then it would cause real-time stuff to suffer since its differnet subnets

NolanHerring · ‎Oct 24 2019

Good catch @PhilipDAth , I didn't even notice that snippit

NolanHerring · ‎Oct 24 2019

Shot in the dark here, but how many sites do you have using that /23 broken into /27s ? Your limit is 16, so if you have 17 sites, it's possible that might be the issue Otherwise, as far as I know, this might be a bug? Have you contacted support yet out of curiosity?

NolanHerring · ‎Oct 24 2019

It's from your ORG dashboard from what I've been told, so the devices don't need to be online for them to pull up subnets they'll grab If you give it say 10.10.0.0/16 and you want it to assign /24's to each subnet from that pool, it will be random One VLAN might show 10.10.33.0/24 and another might show 10.10.222.0/24 Key being that the system should never assign a subnet already in use. Are you saying that you ARE seeing that?

NolanHerring · ‎Oct 24 2019

Do not use 80MHz, start with 20MHz. If you can get away with 40MHz feel free, but I find it's best to just stick with 20MHz Reign in your TX power levels You'll want to turn off some 2.4GHz radios most likely as well You might want to take a look at 26.6 firmware that came out recently Use DFS channels (if you can)

NolanHerring · ‎Oct 24 2019

Also, your access points should be on their own VLAN, not the same one your wireless clients are using. This would also help to isolate risks as well.

NolanHerring · ‎Oct 24 2019

Assuming your talking about the local status page Go to your general settings You can edit the login credentials for the local status page In addition, you can disable the local status page and that way nobody can access it.

NolanHerring · ‎Oct 23 2019

As far as model, a 3b or better will work just fine. This was all the information I could find regarding how it was done (a while ago): Setting up a Raspberry Pi as a Wi-Fi <---> to <---> Ethernet Bridge: Configure wireless settings to connect to your SSID Edit the wpa_supplicant.conf Sudo nano /etc/wpa_supplicant/wpa_supplicant.conf Country=US ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev update_config=1 network={ ssid="<your_SSID_here>" key_mgmt=NONE #My SSID in this example is OPEN Download script from: https://github.com/arpitjindal97/raspbian-recipes/blob/master/wifi-to-eth-route.sh You can also create a new file named wifi-to-eth-route.sh in this location /home/pi Paste the code from the link above into this file Edit crontab file to start the script at boot Sudo crontab -e #if asked use nano @reboot sh /home/pi/wifi-to-eth-route.sh & Restart raspberry pi

NolanHerring · ‎Oct 23 2019

We've dabbled with some of the IO gear, not sure what you mean by WPS being required. We set it up on a WPA2/PSK network just fine. However the device sucked and we ended up using a Raspberry Pi instead, much better and more robust. Used it to connect some Arlo cameras to the wireless since they didn't have Wi-Fi support if I remember correctly.

NolanHerring · ‎Oct 7 2019

You can try stencils. Take a look at this thread here: https://community.meraki.com/t5/Off-the-Stack/Visio-Shapes/td-p/721

NolanHerring · ‎Oct 4 2019

At this specific location that has the MR52's, its in a downtown area of a busy city. 2.4GHz is basically un-usable because of all the neighboring networks, so my SSID's are 5GHz only.

NolanHerring · ‎Oct 4 2019

Go to Organization>Firmware Upgrades>All Networks From there you can select your networks you want to upgrade, and choose which version to go to etc.

NolanHerring · ‎Oct 2 2019

MR52 are having issues with 25.X code. I have a site with them and running 26.X code on them because of it, and seems to be working well. That might be why you were prompted to do so.

NolanHerring · ‎Oct 1 2019

Oh snap thanks guys!! That was a surprise lol, I thought it was going to be @PhilipDAth Way to go @CBurkhead and @Network-dad , glad to have more contributors 😃

About NolanHerring

NolanHerring

Nolan Herring

Community Record

Badges