@Meraki-PM-Team: thanks for letting us know you brought on board a top talented IPv6-taskforce. this is very well required and - at the same time - a pity that it has not happened earlier [2012 would have been the right time, but that's just my humble opinion and can't be changed 😉].   also, very much appreciated(!!), that you're aiming to to bring the full glory of IPv6 to the meraki stack, not just a FRITZ!Box like "experience".   but please, PLEASE, don't tell us the next update is going to be in 2 month, after letting us wait for so long already. this thread started ‎08-31-2017! any message from your IPv6-taskforce will help. let them speak, even if it is just a "hi, i am xxx from the IPv6-taskforce". ... View more

5 points 🙂 ... View more

my inventory: MX64, MS225-24P, MR18, MR72 ... View more

this thread https://community.meraki.com/t5/Security-SD-WAN/MX67C-external-LTE-antenna/td-p/27765 says RP-SMA connector. ... View more

thank you, but pls don't forget to focus on IPv6! ... View more

this is a bug, not a missing feature. i think that's unclear to them. ... View more

A customer asked his internet provider to setup a cost-free, public IP address (as of EU-VO2015/2120 Art3 Abs1/2).   Answer: You'll get an IPv6 net for free, but an IPv4 address only for $$. That's already clarified with the Austrian regulatory authority (RTR).   Meraki: ACT!   The actual email follows (German): Betreff: [XXX #NNN] Bitte um Öffentliche IP Adresse Datum: Tue, 21 May 2019 09:16:44 +0200 Von: AAA BBB via RT <CCC@XXX.at> Sehr geehrter DDD, allen unseren Kunden wird ein öffentliches IPv6-Netz zugewiesen. Die öffentliche IP-Adresse muss nicht IPv4 sein, so steht es in den BEREC Leitlinien zur Netzneutralität und ist auch mit der RTR (Rundfunk und Telekom Regulierung) so abgeklärt. Auf Grund der Knappheit von IPv4 Adressen könnten viele - insbesondere noch nicht so lange am Markt befindliche - Anbieter sonst keine Internetzugangsleistungen anbieten. Wir weisen bei der Bestellung sowie in der Leistungsbeschreibung ausdrücklich darauf hin, dass es sich bei den Privat-Produkten von CCC um IPv6 sowie im IPv4 Bereich Carrier-NAT handelt und auf Wunsch eine statische öffentliche IPv4 Adresse um 2,40 Euro dazugebucht werden kann: ...Die Anbindung des Anschlusses an das Internet erfolgt über ein öffentliches IPv6-Netz sowie über eine betreiberinterne IPv4-Adresse (Carrier-Grade-Nat – CGN).... Es gibt kostenfreie und kommerzielle Dienste, die einzelne Ports von IPv4 auf IPv6 (IPv4 zu IPv6 Port Mapping) weiterleiten. Zwei Beispiele: Freier Dienst: https://myonlineportal.net/portmapper Kommerzieller Dienst: http://www.feste-ip.net/dslite-ipv6-portmapper/allgemeine-informationen/ Alternativ bieten wir die statische öffentliche IPv4 Adresse um 2,40 Euromonatlich an. Mit freundlichen Grüßen, EEE ... View more

be default, the maraki AP (MRxx) transfers its management traffic over native VLAN (or access port).   if you want your SSID(s) in a different network segment: 1) use Meraki NAT: nothing else is required on the switch (access mode/port is enough) 2) use bridge mode: 2a) configure additional VLAN(s) on your meraki AP switch port (trunk mode). 2b) make sure you have a DHCP server within the additional VLAN(s) 2c) setup the additional VLAN(s) in the 'access control' setting, section VLAN tagging / VLAN id ... View more

i'd contact support. this may be tricky to debug. ... View more

as @PhilipDAth said, the throughput test is not very sophisticated (only downstream is tested) and it can't be scheduled. just connect a device to the switch an run tests from there.   maybe the ping tool on the switch can be helpful as well: ... View more

too many ... View more

i've all APs in the same (management)VLAN, but i do create specific a VLAN for each SSID. ... View more

if you configure a "trunk", you can have more then one VLAN (separated network / IP-address-range) on one cable. a "trunk" tags the ethernet data by so called VLAN-tags. it may also have "untagged" ethernet data, that is called "native VLAN" usually.   if a port has "untagged" ethernet data only, it is called "access port" (instead of "trunk port"). usually you have to define which VLAN is put onto such a port (without any VLAN-tag on the ethernet data).   an "access port" may have a voice VLAN, which turns the port basically in a "trunk port", with one tag for voice and no tag ("native VLAN" / "access port") for regular data. [if i am wrong on this, pls correct me - never used it].   your ports connecting MX and MS shall be configured in the exact same way.   i am not exactly sure what you mean by "VLAN Server". there is sthg like a "VLAN Server" on cisco classic (which is called VTP - VLAN trunk protocol), but that's not supported by meraki and i think you mean sthg else. ... View more

"when selecting it"? as in, as soon as you checkmark it?     you have to checkmark the subnet, then press the 'Delete' button. another popup will ask, if you're sure. ... View more

  as you can see here (Switch / ACL) IPv6 support can be implemented - in some cases - extremely simple (at least in the UI). if IPv4 is chosen, source and destination are validated in the traditional way; otherwise (IPv6) some different validation rules apply.   this should/could/must go into Security & SD-WAN / Configure Firewall and Wireless / Configure / Firewall & traffic shaping / Block IPs and ports as well. ... View more

@MerakiDave@CarolineSBRILLIANT! took about 1.5years, that's very ok! can i send you my contact details to get a free cam for sharing the idea? i'd love to get my hands on it! ... View more

this is silly. if meraki has the data, it must be possible to export/download it.   "download as", as it is, is almost useless.   should be very simple to implement downloading a filtered timerange. ... View more

@Bovie2K: that's great news. porting/extending/replacing/updating some packages may take some time and get the GUI and logic ready as well. i still have some hope, that they have already gotten the shouting and have some surprise for all of us in 2018. ... View more

@MRCUR: i disagree. sales, in my case, does actively ignore *all* my IPv6 comments. if there is a response, it is this: https://documentation.meraki.com/zGeneral_Administration/Other_Topics/IPv6_Device_Compatibility. i am pretty sure, most of sales have no clue what i am / we are talking about.   but, the support teams know ***exactly*** what i am / we are talking about! and they may have the power to raise a hand.   i see two possible reasons for this situation: a) cisco wants to keep the meraki produkt line "low"; maybe irrelevant in the future. (meraki may have been seen as a real competition, so they acquired them back in 2012). b) the hardware may be cheap/old and no IPv6 stacks are available. not sure, if all MR/MX/… run linux. i hope i am wrong with both points.   at least, i did not get an immediate, standard answer to my last post in case 03249519. for the record: the lack of an IPv6 full stack is not a missing feature. that's a BUG!!!   i suggest, if anyone is still interested in meraki, open a supportcase (example above) and tweet/message Todd Nightingale, as @JPAWELCHAK suggests:  Twitter: https://twitter.com/tnight  LinkedIn: https://www.linkedin.com/in/todd-nightingale-a106b510/ if you want, also create a feature request / wish and contact sales. maybe that helps as well. ... View more

As of 2018: The lack of an IPv6 stack is a BUG, not a missing feature!!! ... View more