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

@meraki_ #ipv6now https://community.meraki.com/t5/Security-SD-WAN/WE-Need-IPV6-Support-in-MX/m-p/28756 @cwstori @tnight @ChuckRobbins ... View more

@Cohort_Networks: i also do think it's time to make this issue public. nothing happens if we continue here on this thread. which twitter accouts shall we write to? ... View more

this article is in german: https://www.heise.de/newsticker/meldung/IPv4-Daemmerung-Telekom-testet-IPv6-only-Kommunikation-im-Mobilfunk-4150047.html   the message ist very clear: IPv6 is already there, also in europe/germany. IPv6 only is being tested. it is the future. RIP IPv4 and - hopefully(!) - not meraki. ... View more

@rachel: will the MV12 be able connect to "any" WLAN (also non-Meraki - maybe with some restrictions at the beginning in case there is a splash page); or will the WiFi connectivity work only within a meraki-WLAN (MRxx, maybe MXyyW)? ... View more

@MilesMeraki, that is true in a fully deployed meraki environment.   i'd like to see the meraki devices (that have WiFi hardware) to connect to the internet in general via WiFi (in client aka station mode). without the need of a deployed meraki-WLAN (i guess the camera will be able to do so). ... View more

hi @MerakiDave,   the use case is, that an employee takes a Z1/Z3 with him on a biz-trip. in the hotel-room, there may no wired connection and there is neither a cellular data card (or USB-LTE-stick) available. BUT, the hotel provides free WLAN access → if a Z1, Z3 could directly use the hotel-WiFi in station/client mode (in addition to AP-mode), the employee would be pretty happy.   if the cameras WiFi can connect in station (aka client) mode to access the internet - and a GUI of some sort, to configure that mode, is developed/available - that code should be integrated into the Z1 / Z3 series as well. it would provide a 3rd way to get an internet connection: ethernet, USB and (new) WiFi (client-mode).   IMHO that feature should be merged into MX64W and MX65W as well.   and yes, the MR products have a similar function: automatically switch to repeater-mode within a meraki-WLAN or bridge a meraki-VLAN to ethernet using a meraki-WLAN. this works nice within a fully deployed meraki environment (which i like and prefer very much, of course!). but it may happen, that you want to bridge a non-meraki WLAN, or use that WLAN as internet connection. (again) if you have a way to setup WLAN-client-mode on the cams, then there are use cases for this feature also on Z1, Z3, MX64W, MX65W and also on the MR.   hope i could explain good enough. ... View more

@rachel: any chance, this wireless feature is also merged into MR / Z1 / Z3 / MX64W / MX65W series?   it would be (VERY!) nice to connect those devices DIRECTLY in wlan-station mode to the internet. ... View more

hi @rachel! thank you for asking!   i hope, that the cams are able to go beyond person recognition, ie: * cam looks at a conveyor belt and learns regular operation (belt moves and transport of items happens every couple of sec). --> as soon as an item is missing, or a wrong item is detected, an alarm is generated (depending on a schedule). --> as soon as the conveyor belt stops or runs too fast, an alarm goes off. * the mic could be used in the same way!!! the machine-learning algorithms learn the "default" noise. as soon as that noise changes, an alarm goes off (depending on a schedule).   it MUST be possible to turn the mic off, to apply to the general data protection regulation (GDPR) more easily. ... View more

@Uberseehandel wrote: Life would be much simpler if we could set up a VLAN as an Isolated VLAN (remember PVLAN options?). @Uberseehandel: you may want to use the new " Layer 2 LAN isolation" feature under Wireless / "Firewall & traffic shaping". i use that successfully from through a segregated VLAN. https://documentation.meraki.com/MR/Firewall_and_Traffic_Shaping/Wireless_Client_Isolation   it is available since firmware 25.8. 25.9 (current) fixed the issue with the splash pages. ... View more

you are right, @PhilipDAth! @meraki: please also note, that many of us have to apply to the rules of the GDPR by 2018-05-25. as IP-addresses are considered as personal data, connecting a new MR-device - for now - exposes those to anyone in the wifi range of the MR. so this is not yet compliant to to the following art Article 25 Data protection by design and by default 1.   Taking into account the state of the art, the cost of implementation and the nature, scope, context and purposes of processing as well as the risks of varying likelihood and severity for rights and freedoms of natural persons posed by the processing, the controller shall, both at the time of the determination of the means for processing and at the time of the processing itself, implement appropriate technical and organisational measures, such as pseudonymisation, which are designed to implement data-protection principles, such as data minimisation, in an effective manner and to integrate the necessary safeguards into the processing in order to meet the requirements of this Regulation and protect the rights of data subjects. 2.   The controller shall implement appropriate technical and organisational measures for ensuring that, by default, only personal data which are necessary for each specific purpose of the processing are processed. That obligation applies to the amount of personal data collected, the extent of their processing, the period of their storage and their accessibility. In particular, such measures shall ensure that by default personal data are not made accessible without the individual's intervention to an indefinite number of natural persons. 3.   An approved certification mechanism pursuant to Article 42 may be used as an element to demonstrate compliance with the requirements set out in paragraphs 1 and 2 of this Article. Whereas (78): The protection of the rights and freedoms of natural persons with regard to the processing of personal data require that appropriate technical and organisational measures be taken to ensure that the requirements of this Regulation are met. In order to be able to demonstrate compliance with this Regulation, the controller should adopt internal policies and implement measures which meet in particular the principles of data protection by design and data protection by default. Such measures could consist, inter alia, of minimising the processing of personal data, pseudonymising personal data as soon as possible, transparency with regard to the functions and processing of personal data, enabling the data subject to monitor the data processing, enabling the controller to create and improve security features. When developing, designing, selecting and using applications, services and products that are based on the processing of personal data or process personal data to fulfil their task, producers of the products, servicesand and applications should be encouraged to take into account the right to data protection when developing and designing such products, services and applications and, with due regard to the state of the art, to make sure that controllers and processors are able to fulfil their data protection obligations. The principles of data protection by design and by default should also be taken into consideration in the context of public tenders. thanks for reading and taking a note. should be very simple to implement. ... View more

you are right, @PhilipDAth! @meraki: please also note, that many of us have to apply to the rules of the GDPR by 2018-05-25. as IP-addresses are considered as personal data, connecting a new MR-device - for now - exposes those to anyone in the wifi-range of the MR. so this is not yet compliant to to the following article:   Article 25 Data protection by design and by default 1.   Taking into account the state of the art, the cost of implementation and the nature, scope, context and purposes of processing as well as the risks of varying likelihood and severity for rights and freedoms of natural persons posed by the processing, the controller shall, both at the time of the determination of the means for processing and at the time of the processing itself, implement appropriate technical and organisational measures, such as pseudonymisation, which are designed to implement data-protection principles, such as data minimisation, in an effective manner and to integrate the necessary safeguards into the processing in order to meet the requirements of this Regulation and protect the rights of data subjects. 2.   The controller shall implement appropriate technical and organisational measures for ensuring that, by default, only personal data which are necessary for each specific purpose of the processing are processed. That obligation applies to the amount of personal data collected, the extent of their processing, the period of their storage and their accessibility. In particular, such measures shall ensure that by default personal data are not made accessible without the individual's intervention to an indefinite number of natural persons. 3.   An approved certification mechanism pursuant to Article 42 may be used as an element to demonstrate compliance with the requirements set out in paragraphs 1 and 2 of this Article.   Whereas: (78) The protection of the rights and freedoms of natural persons with regard to the processing of personal data require that appropriate technical and organisational measures be taken to ensure that the requirements of this Regulation are met. In order to be able to demonstrate compliance with this Regulation, the controller should adopt internal policies and implement measures which meet in particular the principles of data protection by design and data protection by default. Such measures could consist, inter alia, of minimising the processing of personal data, pseudonymising personal data as soon as possible, transparency with regard to the functions and processing of personal data, enabling the data subject to monitor the data processing, enabling the controller to create and improve security features. When developing, designing, selecting and using applications, services and products that are based on the processing of personal data or process personal data to fulfil their task, producers of the products, services and applications should be encouraged to take into account the right to data protection when developing and designing such products, services and applications and, with due regard to the state of the art, to make sure that controllers and processors are able to fulfil their data protection obligations. The principles of data protection by design and by default should also be taken into consideration in the context of public tenders.   thanks for reading and taking a note. should be very simple to implement. ... View more

can anyone say if that's technically possible on the MV71/21? the video-chip is 1080p, right? ... View more

use case: VPN clients with IPv6 only connectivity must be able to connect. ... View more

you can actually connect a LTE/UMTS USB stick to the MX64 and use the cellular service as internet connection: https://documentation.meraki.com/MX-Z/Cellular/3G_-_4G_Cellular_Failover   the supported USB-stick list is quite limited, but i've had success with other USB-sticks as well (huawei).   anyhow, meraki treads the LTE (cellular) uplink as "last resort" (sort of) and some stuff is simply not possible. ie the uplink monitoring (the rtt and packet loss graph) only works on the ethernet uplink(s), not on the cellular uplink. and in case there is a cellular + an ethernet uplink, load sharing can't be done between the two.   i placed my wish already that the cellular uplink should be treated like an additional ethernet uplink. there is countries and places in which cellular is cheaper / faster / as reliable as wired internet connections.   nevertheless, you can also use another device to turn the cellular link into an ethernet connection. in that case you may run into issues with clientVPN and port forwarding, as there will be an additional NAT layer, right in front of the MX. some LTE/UMTS-USB-sticks work in a specific mode in which you get exactly the same issue (additional NAT layer), even if you attach them directly to the MX.   … in case the APN of your provider is not supported, just open a case. the meraki-team is very fast in adding it. ... View more

sorry for posting a link to the competition, but this may answer the question best: https://www.axis.com/us/en/companion/products-and-solutions/axis-companion-360   the cam records with one or more imaging sensor(s). the recorded video stream is usually highly distorted. this is why you need to pan/tilt/zoom digitally (equalization usually happens automatically).   if there was a meraki 360 cam, you could have a couple of virtual cams (equalized parts of the full distorted video stream).   hope i've explained it well enough. ... View more

SteveM wrote: 1080p HD Camera the chip in MV21 / MV71 - i think - can do 1080p HD. i guess the SSD was to small to enable it. now, using motion based retention, it should be ok to record FHD. (data protection laws limit the amount of hours recorded anyway).   in case i am right, that the chip can do 1080p, please enable that as an option!   SteveM wrote: Wireless Option w/WEP/WPA/WPA2 Encryption well, we need power anyway. using PoE we have power and network. but i agree, sometimes it would be nice to avoid the network cable.   not sure if the MV21/71 has a usb bus internally. if yes, then meraki could think about attaching WLAN to MV like attaching LTE to MX (usb-stick).   SteveM wrote: Zoom video on playback should be possible. i'd love to see a 360 hi-res cam and pan/tilt like on youtube 360 videos (there is no zoom in youtube, but i am sure it can be implemented).   SteveM wrote: Off Camera Storage to Cloud - Enough to handle 90 days. well, using motion based retention, you can almost achive 90days without offloading the video. there is great advantage to keep all securely on the cam (bandwidth, data protection) (except for the case the cam is stolen or physically destroyed - recording gone without offload).   i think it can be done technically with the existing hardware: just stream the video to a given IP/port in a defined protocol (like an IP cam) another NVR can read (in addition to local recording).   SteveM wrote: Two-way Audio   has been answered some place else here. can't be done with the existing hardware (MV21/71) and is highly critical in regard to the data protection laws in some countries. in case it is implemented in a HW revision, please make sure the microphone can be turned off!   audio output would create some really intresting possabilities.   SteveM wrote: Motion Detection Alerts to Cell Phone or popup on Dashboard - (highly sensitive areas) please implement! i've requested that from the first day on 🙂 since the release of MV analytics, i know it can be done (and is practically there already). i'd prefere an email notification rather then a phone call.   ... View more

i have to post my statement on this threas also: pls no PTZ. a hi-res 360 will do (PTZ can be implemented fully digital - i am sure that will save quite some $$$). ... View more

pls no PTZ. build a hi-res 360 and do PTZ digitally! ... View more

sooner or later the WAN connection will be reestablished, i'd say. in the worst case you bring the cams back online within another network that has internet connectivity.   most important, i'd say is, that the cams do record while the WAN is not available. ... View more

@BlakeRichardson wrote: Thanks for sharing. Hopefully PTZ cameras won't be to far away! i'd prefer a 360 (and pan/tilt/zoom digitally) ... View more