Category Archives: Security

Cameras, Security, surveillance

New RCA HSDB2A 3MP Doorbell IP Camera | Page 101 | IP Cam Talk

HIKVISION DOORBELL101
HIKVISION (DS-HD1), RCA (HSDB2A), EZVIZ (DB1), LAVIEW (LV-PDB1630-U), NELLY’S (NSC-DB2), LTS (LTH-7132-WIFI)

* NEW RCA OWNERS READ WARNINGS: SECTION *
(DO NOT UPGRADE TO ANOTHER BRAND’S FIRMWARE WITHOUT READING WARNINGS FIRST)​

COMMON FREQUENTLY ASKED QUESTIONS/ANSWERS (FAQ):
Q. Is there a difference in the internal hardware between the different brands?
A. NO, they are All the same Hikvision Doorbell just re-branded, only difference is the (color/number of) face plate(s) included in the box with the install/mounting hardware.

Q. Can I change my Doorbell’s Password (Verification Code)?
A. NO, DO NOT CHANGE YOUR PASSWORD (see WARNINGS: in CONFIGURING DOORBELL TIPS: Section)

Q. Does 2 Way Audio work with this Doorbell in Blue Iris?
A. NO, it is not yet supported at this time.

Q. Can the Lens (Fish-Eye) view be changed?
A. NO, the 180 degree Vertical / 105 degree Horizontal FOV is a Fixed Lens.

Q. When the Doorbell button is pressed, what does the Doorbell Speaker sound like?
A. See OUTDOOR CHIME TIPS: section – EMiks5 (The (Ding-Dong) Sound is actually Much Louder than the recording)

Q. Does the Doorbell work on Mesh networks?
A. YES – Google/Nest – xaudiblex, Eero – gnuB, TP-Link – alexdelprete, Ruckus – pete_c

Q. Can I move the location of the “date/time” in iMVS-4200 or Batch Config Tool?
A. NO, unfortunately, even though the option appears it does not work.

Q. Why do I need to install the Power Kit if I have a Chime (Mechanical or Digital/Electronic)?
A. Here are some great answers – TechBill – klunkerbus, klunkerbus – fredkruger (Power Kit opened)

Q. How many RTSP Video streams can I have running simultaneously?
A. THREE – rafale

INSTALL TIPS:
⦁ Take a picture (keep record) of the back of your Doorbell, you will need the Password (Verification Code – 6 Capital Characters) for future streaming (Blue Iris, NVR, NAS, VLC, etc.)
⦁ TURN OFF POWER before/during install (Locate your existing Doorbell’s breaker by having someone push your Doorbell button while you try each breaker)
⦁ Angle of Install; if you are mounting on a side wall of your door you will need a wedge, the Doorbell comes with wedges; 2 angled/1 flat (See HARDWARE INCLUDED: below) If these do not work for you, search Nest Hello mounts on Amazon, they are not a direct fit but can be modified to work. POPMAS is one that several here on this Forum has used.
(NOTE: After I got my Doorbell connected to my network and the App viewing the Doorbell video fed, I used my phone to help figure what angle I needed to mount Doorbell)
⦁ Transformers; this is one of the big questions with Smart Doorbells, what size do I need or do I even need to change it at all? Well it is all up to your existing Transformer and Chime, there are many different brands of Transformers all putting out different voltages/loads than what their label states. It will be hit or miss if your Transformer can handle the extra Load created by the Smart Doorbell (when the Doorbell button is pushed). There are two types of Chimes out there, Mechanical and Digital and many brands. Most here tried their existing transformers first, if they had problems with the Chime not working properly, Doorbell randomly disconnecting from the network, random reboots, etc., they changed theirs out. The general rule is, if your existing transformer is 16v then replace with 16v, if 24v then buy a 24v (Some have reported going from 16v to 24v increased their Chime volume). But what needs to increase to fix the above stated problems is the Volts/Amps (va), since your Smart Doorbell requires constant power (which is not a problem since your Chime uses no power until your Doorbell button is pushed) the Smart Doorbell will increase the Load, which depending on your Chime, may or may not work properly. Several owners here are using their 16v 10va with no problems, mine worked also with no problems. But if you have problems, 16v 30va or 24v 30va is a common replacement, you could use a 40va too.
Summary; By adding a Smart Doorbell to an existing Doorbell/Chime system, pressing the new Smart Doorbell button will now increase the Load so in most cases you need a transformer that can handle this increased draw/load, this is why you would go with a higher rated (va) transformer.
For Mechanical Chimes, here is a video to help explain transformers:
16v 10va vs. 16v 30va Doorbell Transformer
* IF YOU DO NOT FEEL COMFORTABLE CHANGING OUT YOUR TRANSFORMER, HIRE AN ELECTRICIAN *
⦁ Wiring; If you do not have an existing Doorbell/Wiring and plan to run wire yourself, proper planning will help in this endeavor. Most Doorbells use 20 gauge solid 2 conductor (2 wires) 20/2 Bell Wire. A good place to start planning is to find a continuous power source for your transformer, a central place (Usually in an Attic or Basement), a place where you will be bringing two cable runs to (one cable from the Doorbell and one from the Chime). Be sure and find your Breaker as mentioned above before installing the transformer. Most Chimes are located in a central place within a House/Dwelling in order to hear it from most anywhere within. The Smart Doorbell Wiring Diagram below illustrates how the wiring terminates.
⦁ Power Kit; Be sure and install the Power Kit for Mechanical Chimes (it regulates power and fixes low hum issues) If you have a Digital/Electronic Chime, several users/owners here have confirmed having to install the Power Kit to get there DB to work properly.

1578366270530.png

⦁ If you have problems connecting to your Network on your Initial Install, try connecting with 2.4GHz or for 5GHz try – VorlonFrog‘s post.
⦁ CHIMES: This Compatible Chime Chart List is from Hikvision’s Data Sheet.
⦁ If you have two Chimes, one Doorbell, you will most likely need two Power Kits.

1578057339684.png

Friedland by Honeywell D3126 (EUR) Chime is compatible (It is suggested to change out its transformer) – croustx

HARDWARE INCLUDED:
(Face Plates will differ depending on which company you buy the Doorbell from but all hardware is the same in every box)

1578569973557.png

1578570873963.png

CONFIGURING DOORBELL TIPS:
⦁ Software (Windows) used to configure Doorbell include: iVMS-4200 (I personally like version 2 legacy), Batch Configuration Tool (BC Tool 101 Help).
iVMS-4200 for MAC, Batch Configuration Tool for MAC
(NOTE: In the Batch Config. Tool, If your Doorbell shows Offline hit Refresh to bring it Online, Sometimes in iVMS-4200 the CCD section does not show up.)
⦁ Other useful Hikvision Tools.
⦁ Frame Rate: (FPS); the default is 15, to change to Full Frame (30FPS) in iVMS-4200 or Batch Config. Tool under Remote Configuration/Image/Video & Audio – JoshJ
⦁ Using iVMS-4200 or Batch Config. Tool in the Remote Configuration/CCD section you will be able to turn WDR On/Off, change brightness, contrast, etc.
⦁ Available Apps (Allows Remote Access):
iO/S: Hik-Connect, RCA Security, EZVIZ, LaView One, Guarding Vision
Android: Hik-Connect, RCA Security, EZVIZ, LaView ONE, Guarding Vision
⦁ Android 9 Hik-Connect Setup Help – Dewcal
⦁ In App be sure and change Hi-Def to Ultra HD

WARNINGS:
⦁ IF YOU JUST RECENTLY (End of 2019 or 2020) PURCHASED A RCA (HSDB2A) DO NOT UPGRADE TO Nelly’s FIRMWARE at this time, we have had Four RCA owners who have bricked their Doorbell doing so: – acmonster – rkulp89 – elvisthedj – jrinco11 NOTE 1: Here is a list of RCA Owners who are successfully running LaView 190716 firmware and Hikvision 200321 firmware. We are not sure that if for some reason Nelly’s firmware is not compatible with the RCA or there is another reason for the bricking when upgraded to Nelly’s firmware. IF YOU INSTALL LaView’s or Hivision firmware on your new RCA (purchased in 2020), and are successful, please let us know.
NOTE 2: We do have new RCA owners (see last RCA Owners on our list) who have successfully upgraded to LaView and Hikvision firmware. JUST BEWARE THERE IS STILL THE POSSIBILITY OF BRICKING YOUR DB UNIT!!!
⦁ DO NOT change the admin Password in iVMS-4200 or Batch Config. Tool. We found when loading the Batch Configuration Tool for the first time and your Doorbell is Discovered, it will show as “not activated” under security (IGNORE THIS), DO NOT Click the Activate Button. It will force you to set a NEW admin Password on your device (Doorbell) which for most Hikvision Cameras would be a normal process but in this case it disrupts future re-inclusions/configuration through the Mobile Apps. Once done, it is not reversible and cannot be Reset either by Factory Settings Reset or Firmware Reload. – rafale, rafale, – Mtoo22 (Hikvision Partner) Note: digdoug has had a different experience, his DB’s password Reset back to it’s original password.
⦁ Here is a more Advanced Step-by-Step Procedure to Upgrade/Change your Firmware – alexdelprete
⦁ RESETTING Your Doorbell (THIS MAY NO LONGER APPLY 06-2020 see above Step-by-Step by alexdelprete); If you have changed your Doorbell’s firmware to another brand’s firmware (ex. You own a RCA Doorbell but have upgraded to LaView’s firmware) DO NOT Reset Your Doorbell without changing your firmware back to your Doorbell brand’s firmware. If you Reset without changing it back you will be unable to continue the setup process when coming to scanning the OR Scan Code step. There is a fix if you missed this Warning: – rafale

FIRMWARE INSTALL/UPGRADE TIPS: (Thanks to – JSnP, JSnP & Chadsturgill) (BEWARE: THERE IS ALWAYS A CHANCE OF BRICKING YOUR DOORBELL!!!)
⦁ Most of us here has had no problems installing the different firmwares listed below (Except for Recent RCA Owners (Jan. 2020), see WARNINGS: section above. If you are going to upgrade, be sure you are within your Return Policy, worse case you have a year warranty.
⦁ For ONVIF support use LaView’s, Nelly’s or Hikvision (DS-HD1) latest firmware.
⦁ It is a good idea to make Note of which firmware build you have prior to upgrading to another brand’s firmware in case you run into any issues.
⦁ Firmware can be Installed/Upgraded with the Batch Configuration Tool:

1576768338110.png

⦁ Here is a more Advanced Step-by-Step Procedure to Upgrade/Change your Firmware – alexdelprete

FIRMWARE LIST (DOWNLOAD LINKS INCLUDED):

DOORBELL MODEL PREVIOUS FIRMWARE LATEST FIRMWARE ONVIF ALEXA GOOGLE OUTDOOR BELL SOUND (ON/OFF)
HIKVISION (DS-HD1)​
191017​
200321 (2020-03-31)​
YES​
NO​
NO​
???​
RCA (HSDB2A)
180809 (????-??-??), 180703 (????-??-??)​
190124 (2019-01-30)​
NO​
NO​
NO​
NO​
EZVIZ (DB1)
191211 (2020-01-05), 190708 (2019-07-21)​
200220 (2020-04-02) EU Firmware Link​
NO​
YES​
YES​
YES​
LAVIEW (LV-PDB1630-U)
190103 (????-??-??)​
190716 (2019-07-29)​
YES​
YES​
NO​
NO​
NELLY’S (NSC-DB2)
190122 (2019-03-04), 190412 (2019-??-??), 190625 (2019-06-25)&(2019-11-22)​
191216 (2019-12-16)​
YES​
NO​
NO​
NO​
LTS (LTH-7132-WIFI)
​
??????​
???​
???​
???​
???​

FIRMWARE LINKS/DESCRIPTIONS:
LaView Halo ONE (LV-PDB1630-U):

(Jul 29, 2019) Build 190716 (ONVIF Support)

Nelly’s (NSC-DB2):

(Nov. 22, 2019) Build 190625 (ONVIF Support)

Hikvision (DS-HD1):

(Mar. 31, 2020) Build 200321 (ONVIF Support)

EZVIZ (DB1) {STILL OLD 191211 build as of 04-30-20, to get new 200220 build D/L from EU Site below}:

(Apr. 02, 2020) Build 200220 (NO ONVIF Support) – Jack007
OR
EZVIZ (DB1):

(Apr. 02, 2020) Build 200220 (NO ONVIF Support) – JSnP

RCA (HSDB2):

(Jan 30, 2019) Build 190124

OLDER FIRMWARE LINKS:

EZVIZ (DB1)(OLD VERSION):
usdownload.ezvizlife.com/device/CS-DB1-A0-1B3WPFR/2.0/CS-DB1-A0-1B3WPFR.dav (Jan, 5 2020) Build 191211 (NO ONVIF Support, ADDED Outdoor Bell Sound (Ding-Dong) On/Off – Jack007) – Pilot04

EZVIZ (DB1) (OLD VERSION):
usdownload.ezvizlife.com/device/CS-DB1-A0-1B3WPFR/2.0/CS-DB1-A0-1B3WPFR.dav (Jul 21, 2019) Build 190708 (NO ONVIF Support)

EZVIZ (DB1) (OTHER):

(Nov 28, 2018) Build 190708 (Possibly International Version)

Nelly’s (NSC-DB2) (OLDER VERSION):

(Mar 4, 2019) Build 190122

RCA (HSDB2) (OTHER):

(Nov 28, 2018) Build 190124 (Possibly International Version)

To get the above File Dates use GNU Wget
ex. (see Last-Modified)

1579311545053.png

STREAMING VIDEO TIPS (Thanks – JSnP):

1576764779744.png

NOTE: “<username>” is admin, “<password>” is the “Verification Code” on the back of your Doorbell (Usually 6 Capital Characters), “<IP Address>” is your Doorbell’s IP Address.
(One way to find your Doorbell’s “<IP Address>” is by looking up your Doorbell’s MAC address in your router.)

COPY/PASTE:
rxxp:/admin:<Enter password>@<Enter IP Address>:554/Streaming/Channels/101
(Change rxxp to rtsp)

⦁ RTSP Streaming for Blue Iris (BI) Add new camera / Find/inspect… (Use ONVIF)
⦁ RTSP Streaming for NVR (Use ONVIF to find Doorbell and setup)
⦁ RTSP Streaming for NAS (Use ONVIF to find Doorbell and setup)
⦁ RTSP Streaming for VLC (VideoLAN Media Player) Under Media/Open Network Stream (Ctrl+N)…Enter your RTSP Link/Info for Live Video Stream

It has been mentioned the Doorbell has a 3 Stream limit, 4 Streams is too much for it’s processor – rafale

SNAP SHOTS: To Obtain a live JPG Snap Shot, enter this URL in your browser (you do not need to add :554 port number with your IP Address) – pete_c
http://<IP Address>/onvif/snapshot.jpg
ex.

ACCESS VIDEO(s) ON SD-CARD:
⦁ Recommended Micro SD Card; Get a Video Rated Card, V30 works great…
SanDisk 128GB Extreme MicroSDXC
⦁ In iVMS-4200 or Batch Config. Tool, under Device Management/Storage/File you can set a Date/Time Range and Download Video File(s)

OUTDOOR CHIME TIPS:
⦁ To hear what the Outdoor (Ding-Dong) Chime sounds like – Emiks5

⦁ Outdoor Chime Settings (EZVIZ Firmware/App Only) – alexdelprete, alexdelprete

AMAZON ALEXA, GOOGLE HOME/ASSISTANT, & APPLE HOMEKIT:
EZVIZ DB1 (Alexa & Google works)
LaView ONE Halo (Alexa works)

ALEXA SKILLS/TIPS:​
⦁ To Display on Alexa; RTSP feed from Doorbell to Amazon Echo Show via/thru Monocle – Threads to Follow; Old Monocle Thread or New Monocle Thread – pete_c​
Turn Off Doorbell’s Image/Video Encryption​
(LINK LaView to Alexa) – It Works!​
(LINK EZVIZ to Alexa) – It Works! (Note: IFTTT works for Motion Detection Alerting via Email/SMS or to turn On/Off camera for the HSDB2A) – Pilot04​
(LINK RCA to Alexa) – Does Not Work unless you use secondary software like Monocle or MotionEye​
⦁ Home Assistant help – pete_c​
​
GOOGLE TIPS:​
⦁ To Display on Google; Link EZVIZ account to Google Assistant via Google Home App, ReSync Google Devices in App, Turn off Doorbell’s Image/Video Encryption in Doorbell App Settings, then Display Doorbell on Chromecast/TV or Levono Display – xaudiblex, xaudiblex, xaudiblex (FYI, I have not been successful to get this to work with LaView 190716 firmware on my LaView Doorbell), xaudiblex (upped screenshots) running EZVIZ 190708 firmware on his EZVIZ Doorbell and his works) (Seems to Only work on EZVIZ Doorbells – Mtoo22)​
Nelly’s firmware 190625 has been confirmed to work on a EZVIZ DB with Google Assistant, displaying on Google Hub and Chromecast/TV – lekham, lekham​
​
APPLE TIPS:​
⦁ To Display on HomeKit; via HomeBridge, HomeBridge FFMEG Plugin – bigrob444​

NETWORKING TIPS:
⦁ In your Firewall settings, allow ICMP from the Doorbell to your router, otherwise the doorbell will disconnect/reconnect the WiFi – ronin1, ronin1 – alexdelprete, alecdelprete-ronin1
⦁ In order to view the video from Ezviz app allow traffic from your local_devices_ip TO any external IP at port : 6500, 7100 and 10554 –cool77
⦁ In order to answer a ring call from Ezviz app allow traffic from your local_devices_ip TO any external IP at port : 9664 – cool77
⦁ For Streaming (RTSP) add a rule that allows traffic from your local_devices_ip TO all_internal_IP at port : 554 – cool77
⦁ For Remote Access using (iVMS-4200 or Batch Configuration Tool) allow traffic from your local_devices_ip TO any external IP at port : 8000
⦁ It is always a good idea, for security reasons, to Disable UPnP in your router too – Emilks5

IFTTT Tips:
⦁ IFTTT works with EZVIZ and Alexa for motion detection alerting via Email/SMS or to turn On/Off camera for the HSDB2A – Pilot04

HOME ASSISTANT Tips:
⦁ Nabu Casa (Home Assistant Cloud Service with Alexa/Google Support) – Olddawg
⦁ Home Assistant (Alexa) help – pete_c

SYNOLOGY TIPS:
⦁ Configuring Synology without ONVIF Support – KlaverBoer
⦁ Motion Detection with ONVIF (Hikvision Firmware) – alexdelprete, alexdelprete
⦁ Configuring Synology – alexdelprete

OTHER SOFTWARE TO CONSIDER:
⦁ Monocle (Alexa) – pete_c – scroberts72 – pete_c
⦁ tinyCam Pro, Link for those using ActionTiles (Android), JPG Snapshot in tinyCam Pro – aralos1999
⦁ MotionEye Wiki , MotionEyeOS, MotionEye Android (No Audio – Pilot04)
⦁ HomeBridge (iO/S), HomeBridge FFMEG Plugin

OTHER HARDWARE TO CONSIDER:
⦁ FRENCK (USA) Relay (Works with Home Assistant)
⦁ Xiaomi Aqara Door Window Sensor Zigbee Wireless Connection (Works with Home Assistant) – Olddawg
⦁ Finder (EUR) Relay, 344Mhz Transmitter – KlaverBoer, KlaverBoer / Finder (EUR) Relay, 344Mhz Transmitter – Jack007
⦁ uxcell (BC) Ice Cube Relay – Ford
⦁ Doorbell Monernizer (EUR) – Fietspomp
⦁ Sage Sensor – TechBill – alexdelprete – TechBill (Sage with SmartThings)
⦁ ELK-960 Delay Timer, ELK930 Doorbell Detector – pete

API LINKS:
⦁ ONVIF Event API – dromero
⦁ ONVIF2MQTT Docker Hub, GitHub – dfarkov

HELPFUL LINKS:
⦁ Doorbell Comparsion Chart – silencery
⦁ EZVIZ Chime Compatibility List
⦁ Hikvision SDK
⦁ Picture Frame Camera Viewing Station

HELP VIDEOS:
⦁ DS-HD1 3 MP Outdoor Wi-Fi Smart Doorbell Camera – Unboxing and Installation
⦁ DS-HD1 3 MP Outdoor Wi-Fi Smart Doorbell Camera – Install Hik-Connect App and Add/Configure Device
⦁ DS-HD1 3 MP Outdoor Wi-Fi Smart Doorbell Camera – Operation and Incident Sharing

BLUE IRIS TIPS:
⦁ Record Tab Basics
⦁ Working with Profiles
⦁ Triggers: Basics of Motion Detection
⦁ Zones and Hotspots
⦁ Review and Exporting Video Clips

ADDITIONAL TIPS:
⦁ For RCA owners (ONLY); if you want to remove the RCA Logo, we found a trick in doing so. You will need to install EZVIZ firmware build 190708 first, then turn ON Logo in Batch Config. Tool (Remote Configuration/Image/Video Display), then load LaView’s firmware (which will turn Logo OFF)
⦁ For EZVIZ owners (ONLY); if you plan to install/upgrade your firmware to LaView’s firmware you NEED to be sure and follow these steps: First Check your firmware in your App under Settings. If you have firmware build 190304 DO NOT install LaView’s firmware (If you do you will end up with a RCA Logo). If have the 190304 build you will NEED to update your firmware to EZVIZ build 191211 first. Next; with the 191211 build installed/confirmed go to Batch Config. Tool (Remote Configuration/Image/Video Display) check to see if the Logo is checked ON, if so, you will need to uncheck it Off before installing/upgrading to LaView’s firmware.
⦁ You can choose which App you want to use. EZVIZ, LaView ONE, Hik-Connect, etc. Some Apps require you remove the device (Doorbell) from the previous App first, you would then add it with the QR Scan Code. Each App is a little different but they all function pretty much the same.
⦁ FCC Registrations: Search FCC ID Database
FCC ID 2ADTD-DSHD1 3MP Wi-Fi Doorbell Camera by Hangzhou Hikvision Digital Technology Co., Ltd. (Info on Hikvision Doorbell)
FCC ID VIXHSDB2 Video Doorbell by Voxx Accessories Corp. (Info on RCA Doorbell)
FCC ID 2APV2-CSDB1 Wi-Fi Doorbell Camera by Hangzhou Ezviz Software Co., Ltd. (Info on EZVIZ Doorbell)
FCC ID 2APYR-PDB1630 Wi-Fi Doorbell Camera by LaView Eagle-Eye Technology Inc. (Info on LaView Doorbell)
FCC ID 2ADTD-DOORBELL 3MP Wi-Fi Doorbell Camera by Hangzhou Hikvision Digital Technology Co., Ltd. (Info on Nelly’s Doorbell)
⦁ You can turn On Continuous Recording (All-day Template) to your SD-Card in Batch Config. Tool (Remote Configuration/Event/Schedule/Recording Schedule), just be aware your SD-Card will fill up fast…
⦁ Face Plates can be painted, best to use a good spray paint for plastic. Also, the face plates do fit each other (brands), only exception is the RCA only works with their own face places, but you can use a RCA face plate on a LaView, EZVIZ, Nelly’s, etc. FYI – TechBill
⦁ Face Plates Buttons can be swapped out. It is common on a Black or Dark Face Plate to replace the Button Cover with a White one (see CONS: section about PIR Lens issue) – danli, danli, danli, NOAMattD

TROUBLESHOOTING TIPS:
⦁ SOLID RED BUTTON LIGHT; = BRICKED!!! (So Far (as of Jan. 2020) NO ONE to date has been able to recover their Doorbell past this point/problem) – COtto1984 (EZVIZ (DB1) Owner updated to LaView’s firmware) – acmonster (RCA (HSDB2A) Owner upgraded to Nelly’s firmware) – rkulp89 (RCA (HSDB2A) Owner upgraded with Nelly’s firmware – Replaced DB with EZVIZ DB1) – elvisthedj (RCA (HSDB2A) Owner upgraded with Nelly’s firmware) – jrinco11 (RCA (HSDB2A) Owner upgraded with Nelly’s firmware)
⦁ FLASHING RED BUTTON LIGHT;
⦁ FLASHING BLUE BUTTON LIGHT;
⦁ If you are unable to get your Doorbell to RESET; try completely Removing Power to the Doorbell (Turn off your breaker or physically disconnect your Doorbell from Power) for at least One Hour. The Doorbell has an internal battery that needs to drain enough to properly do a Full Reset. – VorlonFrog – Tomgar – NickTheGreat, NickTheGreat
⦁ If you tried to RESET your Doorbell without changing your firmware back to your brand’s firmware first, see WARNINGS: section (ex. You own a RCA Doorbell with LaView’s firmware installed) and you are unable to get pass the OR Scan Code step. Here is your fix: – rafale
⦁ If your Doorbell keeps losing it’s WiFi connection, read this: rafale (Also see NETWORKING TIPS:)
⦁ If you are having problems with receiving Phone Calls from your Doorbell trying cleaning your phone: – flynreelow – Several here, including myself, have reported this to randomly work/not work. We have not been able to pin it down to a specific App/Version or phone (iPhone/Android and/or their O/S version) or if it is just a random Cloud issue. UPDATE: Users are having success using the Guarding Vision App – jmcu – David L – TechBill – mitchapp – bob2701
⦁ EZVIZ PC Studio; If you are unable to see NETWORK/ADVANCED Buttons here is your fix – alexdelprete
⦁ If you having trouble casting your Doorbell to Chromecast via Google, try this – cw-kid
⦁ If you are unable to Preview Video in the Apps or PC Software see this post – alexdelprete
⦁ If you are having problems with Batch Config Tool version 3.0.3.8 crashing, download version 3.0.2.6 for fix – just2bad

CONS:
⦁ HEAT; yes, these Doorbells do run hot. Ours has been running 6 months now beginning in the Heat of Summer (100 degrees) to now mild Winter. Time will only tell us if this is a problem. There has been a lot of discussion about this matter, some have lowered heat by lowering voltage, others have lowered heat with custom mounts. Even read one guy added a fan. Our Doorbell read 140 degrees during the Summer with a Temp. Gun. I would just say make sure it is not in direct Sunlight. From what I have been told/read these type of cameras (IP too) tend to run hot.
⦁ PIR Lens; It has been mentioned here by several that people are mistakenly pressing the PIR Lens (Middle) instead of Doorbell Button (Bottom). I have witnessed this a few times myself. Chadsturgill here has reported his Lens is now cracked. This seems to happen more when the LED Button light is turned Off (some of us have turned it Off because it is very bright at night).
⦁ Receiving Phone Calls from your Doorbell when the Doorbell Button is pressed has been known to not always be consistent, for more info on this see TROUBLESHOOTING TIPS:

Attachments:

Source: New RCA HSDB2A 3MP Doorbell IP Camera | Page 101 | IP Cam Talk

Security, Software, sysadmin

HTTP response status codes – HTTP | MDN | https://developer.mozilla.org/

HTTP response status codes indicate whether a specific HTTP request has been successfully completed. Responses are grouped in five classes:

  1. Informational responses (100–199),
  2. Successful responses (200–299),
  3. Redirects (300–399),
  4. Client errors (400–499),
  5. and Server errors (500–599).

The below status codes are defined by section 10 of RFC 2616. You can find an updated specification in RFC 7231.

If you receive a response that is not in this list, it is a non-standard response, possibly custom to the server’s software.

Information responses

100 Continue
This interim response indicates that everything so far is OK and that the client should continue the request, or ignore the response if the request is already finished.
101 Switching Protocol
This code is sent in response to an Upgrade request header from the client, and indicates the protocol the server is switching to.
102 Processing (WebDAV)
This code indicates that the server has received and is processing the request, but no response is available yet.
103 Early Hints
This status code is primarily intended to be used with the preloading resources while the server prepares a response.

Successful responses

200 OK
The request has succeeded. The meaning of the success depends on the HTTP method:
  • GET: The resource has been fetched and is transmitted in the message body.
  • HEAD: The entity headers are in the message body.
  • PUT or POST: The resource describing the result of the action is transmitted in the message body.
  • TRACE: The message body contains the request message as received by the server
201 Created
The request has succeeded and a new resource has been created as a result. This is typically the response sent after POST requests, or some PUT requests.
202 Accepted
The request has been received but not yet acted upon. It is noncommittal, since there is no way in HTTP to later send an asynchronous response indicating the outcome of the request. It is intended for cases where another process or server handles the request, or for batch processing.
203 Non-Authoritative Information
This response code means the returned meta-information is not exactly the same as is available from the origin server, but is collected from a local or a third-party copy. This is mostly used for mirrors or backups of another resource. Except for that specific case, the “200 OK” response is preferred to this status.
204 No Content
There is no content to send for this request, but the headers may be useful. The user-agent may update its cached headers for this resource with the new ones.
205 Reset Content
Tells the user-agent to reset the document which sent this request.
206 Partial Content
This response code is used when the Range header is sent from the client to request only part of a resource.
207 Multi-Status (WebDAV)
Conveys information about multiple resources, for situations where multiple status codes might be appropriate.
208 Already Reported (WebDAV)
Used inside a <dav:propstat> response element to avoid repeatedly enumerating the internal members of multiple bindings to the same collection.
226 IM Used (HTTP Delta encoding)
The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.

Redirection messages

300 Multiple Choice
The request has more than one possible response. The user-agent or user should choose one of them. (There is no standardized way of choosing one of the responses, but HTML links to the possibilities are recommended so the user can pick.)
301 Moved Permanently
The URL of the requested resource has been changed permanently. The new URL is given in the response.
302 Found
This response code means that the URI of requested resource has been changed temporarily. Further changes in the URI might be made in the future. Therefore, this same URI should be used by the client in future requests.
303 See Other
The server sent this response to direct the client to get the requested resource at another URI with a GET request.
304 Not Modified
This is used for caching purposes. It tells the client that the response has not been modified, so the client can continue to use the same cached version of the response.
305 Use Proxy
Defined in a previous version of the HTTP specification to indicate that a requested response must be accessed by a proxy. It has been deprecated due to security concerns regarding in-band configuration of a proxy.
306 unused
This response code is no longer used; it is just reserved. It was used in a previous version of the HTTP/1.1 specification.
307 Temporary Redirect
The server sends this response to direct the client to get the requested resource at another URI with same method that was used in the prior request. This has the same semantics as the 302 Found HTTP response code, with the exception that the user agent must not change the HTTP method used: If a POST was used in the first request, a POST must be used in the second request.
308 Permanent Redirect
This means that the resource is now permanently located at another URI, specified by the Location: HTTP Response header. This has the same semantics as the 301 Moved Permanently HTTP response code, with the exception that the user agent must not change the HTTP method used: If a POST was used in the first request, a POST must be used in the second request.

Client error responses

400 Bad Request
The server could not understand the request due to invalid syntax.
401 Unauthorized
Although the HTTP standard specifies “unauthorized”, semantically this response means “unauthenticated”. That is, the client must authenticate itself to get the requested response.
402 Payment Required 
This response code is reserved for future use. The initial aim for creating this code was using it for digital payment systems, however this status code is used very rarely and no standard convention exists.
403 Forbidden
The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401, the client’s identity is known to the server.
404 Not Found
The server can not find requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 to hide the existence of a resource from an unauthorized client. This response code is probably the most famous one due to its frequent occurrence on the web.
405 Method Not Allowed
The request method is known by the server but has been disabled and cannot be used. For example, an API may forbid DELETE-ing a resource. The two mandatory methods, GET and HEAD, must never be disabled and should not return this error code.
406 Not Acceptable
This response is sent when the web server, after performing server-driven content negotiation, doesn’t find any content that conforms to the criteria given by the user agent.
407 Proxy Authentication Required
This is similar to 401 but authentication is needed to be done by a proxy.
408 Request Timeout
This response is sent on an idle connection by some servers, even without any previous request by the client. It means that the server would like to shut down this unused connection. This response is used much more since some browsers, like Chrome, Firefox 27+, or IE9, use HTTP pre-connection mechanisms to speed up surfing. Also note that some servers merely shut down the connection without sending this message.
409 Conflict
This response is sent when a request conflicts with the current state of the server.
410 Gone
This response is sent when the requested content has been permanently deleted from server, with no forwarding address. Clients are expected to remove their caches and links to the resource. The HTTP specification intends this status code to be used for “limited-time, promotional services”. APIs should not feel compelled to indicate resources that have been deleted with this status code.
411 Length Required
Server rejected the request because the Content-Length header field is not defined and the server requires it.
412 Precondition Failed
The client has indicated preconditions in its headers which the server does not meet.
413 Payload Too Large
Request entity is larger than limits defined by server; the server might close the connection or return an Retry-After header field.
414 URI Too Long
The URI requested by the client is longer than the server is willing to interpret.
415 Unsupported Media Type
The media format of the requested data is not supported by the server, so the server is rejecting the request.
416 Requested Range Not Satisfiable
The range specified by the Range header field in the request can’t be fulfilled; it’s possible that the range is outside the size of the target URI’s data.
417 Expectation Failed
This response code means the expectation indicated by the Expect request header field can’t be met by the server.
418 I'm a teapot
The server refuses the attempt to brew coffee with a teapot.
421 Misdirected Request
The request was directed at a server that is not able to produce a response. This can be sent by a server that is not configured to produce responses for the combination of scheme and authority that are included in the request URI.
422 Unprocessable Entity (WebDAV)
The request was well-formed but was unable to be followed due to semantic errors.
423 Locked (WebDAV)
The resource that is being accessed is locked.
424 Failed Dependency (WebDAV)
The request failed due to failure of a previous request.
425 Too Early
Indicates that the server is unwilling to risk processing a request that might be replayed.
426 Upgrade Required
The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol. The server sends an Upgrade header in a 426 response to indicate the required protocol(s).
428 Precondition Required
The origin server requires the request to be conditional. This response is intended to prevent the ‘lost update’ problem, where a client GETs a resource’s state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.
429 Too Many Requests
The user has sent too many requests in a given amount of time (“rate limiting”).
431 Request Header Fields Too Large
The server is unwilling to process the request because its header fields are too large. The request may be resubmitted after reducing the size of the request header fields.
451 Unavailable For Legal Reasons
The user-agent requested a resource that cannot legally be provided, such as a web page censored by a government.

Server error responses

500 Internal Server Error
The server has encountered a situation it doesn’t know how to handle.
501 Not Implemented
The request method is not supported by the server and cannot be handled. The only methods that servers are required to support (and therefore that must not return this code) are GET and HEAD.
502 Bad Gateway
This error response means that the server, while working as a gateway to get a response needed to handle the request, got an invalid response.
503 Service Unavailable
The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded. Note that together with this response, a user-friendly page explaining the problem should be sent. This responses should be used for temporary conditions and the Retry-After: HTTP header should, if possible, contain the estimated time before the recovery of the service. The webmaster must also take care about the caching-related headers that are sent along with this response, as these temporary condition responses should usually not be cached.
504 Gateway Timeout
This error response is given when the server is acting as a gateway and cannot get a response in time.
505 HTTP Version Not Supported
The HTTP version used in the request is not supported by the server.
506 Variant Also Negotiates
The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process.
507 Insufficient Storage (WebDAV)
The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request.
508 Loop Detected (WebDAV)
The server detected an infinite loop while processing the request.
510 Not Extended
Further extensions to the request are required for the server to fulfil it.
511 Network Authentication Required
The 511 status code indicates that the client needs to authenticate to gain network access.

Browser compatibility

Update compatibility data on GitHub

Desktop Mobile
Chrome Edge Firefox Internet Explorer Opera Safari Android webview Chrome for Android Firefox for Android Opera for Android Safari on iOS Samsung Internet
100 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
200 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
201 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
204 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
206 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
301 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
302 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
303 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
304 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
307 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
308 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
401 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
403 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
404 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
406 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
407 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
409 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
410 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
412 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
416 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
418 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
425 ? ? Full support 58 ? ? ? ? ? Full support 58 ? ? ?
451 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
500 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
501 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
502 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
503 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes
504 Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes Full support Yes

Thank you!

Report sent

What happens next?

Our team will review your report. Once we verify the information you have supplied we will update this browser compatability table accordingly.

Can I keep track of my report?

You can join the GitHub repository to see updates and commits for this table data:

https://github.com/mdn/browser-compat-data

Tell us what’s wrong with this table

Our goal is to provide accurate, real values for all our compatibility data tables. Notifying MDN of inaccurate data or supplying new data pushes us further towards our goal of providing 100% real values to the developer community.
Thank you for helping.

What are we missing?

Legend

Full support  
Full support
Compatibility unknown  
Compatibility unknown
See implementation notes.
See implementation notes.

See also

 

Security, sysadmin, VPN, Win10, Windows

Preventing Network and DNS Traffic Leaks – SparkLabs

Preventing Network and DNS Traffic Leaks

A traffic “leak” is when network traffic that should only ever travel over a VPN connection instead travels over the normal network connection, thereby potentially exposing the contents of the traffic to others. This could also potentially expose your true IP address to services you are connecting to. For the vast majority of VPN users network and DNS leaks are not a concern. This article has been written for users who connect to VPN Service Providers, with all traffic directed over the VPN connection, who are concerned about the possibility of a leak occurring.

We are currently working on adding a feature to Viscosity to easily block traffic leaks from occurring. We hope to have such a feature available in a future version of Viscosity, however please be aware that this is not something that will be available soon. In the meantime this article details how you can manually setup Viscosity to prevent traffic leaks from occurring.

Traffic Leak Introduction

Most VPN Service Providers configure their VPN setup to direct all network traffic over a VPN connection while it is active. However in some situations, or for poorly configured setups, network traffic can potentially travel over the normal network connection, even if the VPN connection is active. Traffic leaks typically fall into two categories depending on how you deal with them: network leaks and DNS leaks.

A network leak can occur due to a poorly configured VPN setup (where not all traffic is routed correctly through the VPN connection), or during periods where the VPN connection is not active (for example a dropout has occurred and the VPN connection is in the process of reconnecting). To prevent network leaks it is necessary to ensure that all traffic is correctly flowing through the VPN connection when it is active, and to block network traffic from using the normal network connection when it is not active.

A DNS leak occurs when DNS requests are made to a DNS server on the local network (instead of to a DNS server over the VPN connection) potentially exposing what sites or servers your computer is accessing. This is easily avoided by overriding your local DNS servers with DNS servers that are accessed through the VPN connection.

Checking All Traffic Is Routed Over The VPN Connection

The first step to ensuring that there are no network leaks is checking that all traffic is being directed through your VPN connection while it is connected. This can be done by examining the routing on your computer while connected:

Mac

  1. Connect your VPN connection using Viscosity.
  2. Open the Terminal application. This can be easily done by entering “Terminal” into the Spotlight search field. It can also be found at “/Applications/Utilities/Terminal.app”.
  3. Enter the command “route get 0/1” and press Enter. Make a note of the “interface” entry.
  4. Enter the command “route get 128.0/1” and press Enter. Make a note of the “interface” entry.
  5. If both of the interfaces returned above start with “tun” or “tap”, all traffic is flowing through the VPN connection by default.

Windows

  1. Connect your VPN connection using Viscosity.
  2. Open command prompt. This can be done by pressing Windows + R, type ‘cmd’ into the new dialog and click OK, or go to Start, type ‘cmd’ into search and open Command Prompt.
  3. Enter the command “tracert 1.2.3.4” and press Enter. Let the first hop complete, and take note of the IP Address that appears on the right. You can press ctrl+c to cancel the tracert once the first hop is complete.
  4. Open the Viscosity Details window and select the active connection. If the Client IP that appears in the details window matches, or the first three octets (first three dot parts) of the IP match, all traffic is flowing through the VPN connection by default.
  5. If not, type ‘route print’ into command prompt and locate the IPv4 Route table. If you can locate the IP address returned by tracert under Network Destination, and the Interface value is the same as the Client IP displayed by Viscosity, all traffic is flowing through the VPN connection by default.

If you find that all network traffic isn’t routed through the VPN connection you can change this behaviour like so:

  1. From the Viscosity menu select Preferences to open Viscosity’s Preferences window.
  2. Select your connection from the Connections list and click the Edit button.
  3. Click on the Networking tab. Tick the “Send all traffic over VPN connection” checkbox.
  4. Click the Save button.

Preventing Network Leaks When A Drop-out/Disconnect Occurs

If a VPN connection drops, your computer may use your normal network connection until the VPN connection is re-established. In most cases this is desired behaviour, however to prevent network leaks it is recommended that all traffic is blocked when a drop-out or disconnect occurs. This can most easily be achieved by the scripting technique below. For this technique to work, please ensure the “Reset network interfaces on disconnect” option is disabled under Preferences->Advanced.

Viscosity 1.7.1 and later have a new option that allows you to use OpenVPN scripts without needing to enable Unsafe Commands. These scripts are run elevated which means you do not need to put your credentials into AppleScripts or run Viscosity Windows as an Administrator. For security, the scripts used by this method must be in a designated area in your file system, and must be locked down so they can only be edited by an elevated or administrative user.

Mac

To get started, you will need to enable the AllowOpenVPNScripts option in Viscosity. To enable this option run the following command in the Terminal (/Applications/Utilities/Terminal) application and enter your administrator details when prompted:

/Applications/Viscosity.app/Contents/MacOS/Viscosity -setSecureGlobalSetting YES -setting AllowOpenVPNScripts -value YES

Next, you’ll need to create a script that disables the network connection when a drop-out occurs. You can write a custom shell script in any language supported by macOS, however we recommend using the example script below to get started. This script will automatically disable all active network connections, and it’s not necessary to make any changes to it.

#!/usr/bin/python
import subprocess, re
services = re.findall("\(\d+?\) (.+?)\n\(Hardware Port: (.+?), Device: (.+?)\)\n",
  subprocess.check_output(["/usr/sbin/networksetup", "-listnetworkserviceorder"]))
for service in services:
  if service[1] == "Wi-Fi":
    subprocess.check_output(["/usr/sbin/networksetup", "-setairportpower", service[2], "off"])
  else:
    subprocess.check_output(["/usr/sbin/networksetup", "-setnetworkserviceenabled", service[0], "off"])

To use it copy-paste the code above into a new document in a text editor (such as TextEdit), and save it as a text file to your Desktop with the name “disablenetwork.py”. If using the TextEdit application please make sure it’s saved as plain text by going to the “Format” menu and selecting “Make Plain Text” before saving.

Next you will need to create the folder where the script will be stored, and then copy your script into this location. This can be achieved by running the following commands in the Terminal. Enter your administrator password when requested.

sudo mkdir "/Library/Application Support/ViscosityScripts"
sudo cp ~/Desktop/disablenetwork.py "/Library/Application Support/ViscosityScripts"
sudo chown -R root:wheel "/Library/Application Support/ViscosityScripts"
sudo chmod -R 755 "/Library/Application Support/ViscosityScripts"

Before adding the script to your VPN connection it’s recommend you test it manually to ensure it works as intended. To do this run the following command in the Terminal. If it works your network connection/s should become disabled. If not it means there is a problem in the script or it has not been copied into the correct location.

sudo "/Library/Application Support/ViscosityScripts/disablenetwork.py"

Now you’re ready to add it to your connection in Viscosity. To set the script, edit your connection, go to the Advanced tab, and on a new line add the following command, then click Save:

route-pre-down "/Library/Application\\ Support/ViscosityScripts/disablenetwork.py"

The “route-pre-down” command ensures our script is run before the VPN network’s routing is removed to prevent packet leaks. Other commands that can be used for running scripts at different times include “up”, “down”, and “route-up”. More information on these commands can be found in the Advanced Configuration Commands article.

And that’s it. You can test what happens when your VPN connection drops out by manually disconnecting your VPN connection.

To re-enable a wired (Ethernet) connection after this script has been run simply open up System Preferences and select the “Make Service Active” option. To re-enable a Wi-Fi (Airport) connection simply go to the Wi-Fi icon in the menu bar and select “Turn Wi-Fi On”.

Windows

To get started, you will need to enable the AllowOpenVPNScripts option in Viscosity. To enable this option you will require Administrator rights on your computer. Run the following from Start -> Run, or a command prompt, and click Yes to the User Account Control (UAC) prompt that appears:

"C:\Program Files\Viscosity\Viscosity.exe" SetPref AllowOpenVPNScripts true

Next, you’ll need to create a script that disables the network connection when a drop-out occurs. On Windows you should use a batch (*.bat) script, however any script Windows can run natively is supported. We recommend using the script below which disables your network interface to get started:

netsh interface set interface "Ethernet" admin=DISABLED

To use this script copy-paste the code above into a new document in a text editor (we recommend using Notepad++, but Notepad is fine). You will need to replace “Ethernet” with the name of your network adapter. This could be “Wi-Fi” if you use a wireless network, or “Local Area Connection” on older versions of Windows, however on most modern PCs it is named “Ethernet” for a wired connection. To disable more than one adapter, simply copy-paste the script again onto a new line and replace “Ethernet” with the name of the second adapter.

Once you have finished making changes, save it to your Documents or Desktop as “disable-network.bat”. You will need to enable the interface manually when you want to use your internet connection or reconnect to a VPN.

Once your script is created, copy (do not move or drag/drop the script file) to the following directory. You may have to create this directory first if it does not already exist. To do this, open an Explorer window and navigate to your main disk drive, then go into Program Files, then Common Files. If the Viscosity folder does not exist, right click in empty space, select New -> Folder, click Continue when prompted to provide Administrator rights, then rename the folder ‘Viscosity’. Then enter the Viscosity folder and repeat these steps to create a folder ‘Scripts’.

C:\Program Files\Common Files\Viscosity\Scripts

Replace ‘C:\’ above and in the following steps if your main disk drive where Windows is installed has a different drive letter.

Before adding the script to your VPN connection it’s recommended you test it manually to ensure it works as intended. To do this, open a Command Prompt as Administrator and run the script with the following command. If it works, your network adapter/s should become disabled and you will not longer be able to access the internet. If it does not there is a problem or the script has not been copied to the correct location.

"C:\Program Files\Common Files\Viscosity\Scripts\disable-network.bat"

Now you’re ready to add it to your connection in Viscosity. To set the script, edit your connection, go to the Advanced tab and on a new line add the script command, then click Save. Ensure that the path is complete and quoted, on Windows, backslashes need to be doubled as below.

route-pre-down "C:\\Program Files\\Common Files\\Viscosity\\Scripts\\disable-network.bat"

The “route-pre-down” command ensures our script is run before the VPN network’s routing is removed to prevent packet leaks. Other commands that can be used for running scripts at different times include “up”, “down”, and “route-up”. More information on these commands can be found in the Advanced Configuration Commands article.

And that’s it. You can test what happens when your VPN connection drops out by manually disconnecting your VPN connection.

To re-enable your disabled network adapter/s after this script has been run, go to Control Panel -> Network and Sharing Center -> Change adapter settings (on the left), right click your adapter and select Enable.

Preventing IPv6 Network Leaks

Many modern Internet Service Providers are beginning to offer both IPv4 (IP version 4) and IPv6 (IP version 6) connectivity on their networks. However if your VPN connection is not configured to take this into account it’s possible to leak IPv6 traffic.

Most users are familiar with IPv4 addresses, which are represented as a series of numbers in the format x.x.x.x. IPv4 has long been the default IP version for the Internet and local networks. However the number of available unique IPv4 addresses is limited and has almost run out. IPv6 is designed to solve this problem by offering many more unique addresses. Hence Internet Service Providers are beginning to enable IPv6 on their networks as an eventual replacement for IPv4. An IPv6 address consists of a series of letters and numbers separated by colons, for example 2001:db8:85a3::8a2e:370:7334.

However many VPN Providers have been slow to adopt IPv6 support through their VPN networks. This means that if your ISP provides IPv6, however your VPN connection only supports IPv4 traffic, IPv6 traffic can still go over your normal network connection even while connected to a VPN.

VPN Providers can easily solve this problem, while also preparing for the future, by enabling support for IPv6 traffic through their networks. However if your VPN Provider only supports IPv4 it is possible to block IPv6 traffic while connected to the VPN.

Viscosity provides an option which blocks IPv6 traffic while you are connected to a VPN which does not support IPv6. To enable this option, open Preferences and go to the Advanced Tab, then tick “Block IPv6 traffic while connected to IPv4-only VPN connections”.

You will need to reconnect any connections after changing this option.

If you are unsure if your normal network connection supports IPv6 you can use an IPv6 test connectivity test such as Test IPv6.

Preventing DNS Leaks

DNS leaks can be preventing by ensuring that Viscosity’s DNS support is enabled for your connection, and that a DNS server has been set. For information on how to check that it is enabled and specify DNS servers please see the Configuring DNS and WINS settings article.

Windows Multi-Homed DNS

By default, Windows uses a DNS resolution technique called multi-homed DNS. A very simple explanation of this is Windows will ask every DNS server defined on the system to resolve an address, and send these requests out of ever adapter on the system, and then use the first response. This is quite bad for anonymity and effectively means all DNS lookups leak using Windows default DNS system.

Viscosity for Windows uses it’s own DNS system when you are connected to a VPN to prevent this. However, some users prefer the multi-homed Windows DNS system for various reasons. For this, we have an option available in Preferences -> Advanced called “Use Windows DNS System for Full DNS”. Simply tick this option before connecting to a VPN which uses Full DNS mode and the Windows DNS system will be used instead of Viscosity’s.

Are There Any Third Party Tools For This?

Most firewall software will allow rules to be put in place to block traffic from leaking. Any such rules should block all traffic on the standard network interface with the exception of traffic for the VPN connection itself.

Source: Preventing Network and DNS Traffic Leaks – SparkLabs

Security, Win10, Windows

Configure Windows diagnostic data in your organization (Windows 10) | Microsoft Docs

Endpoints The Microsoft Data Management Service routes data back to our secure cloud storage. Only Microsoft personnel with a valid business justification are permitted access. The following table defines the endpoints for Connected User Experiences and Telemetry component: Windows release Endpoint Windows 10, versions 1703 and 1709 Diagnostics data: v10.vortex-win.data.microsoft.com/collect/v1 Functional: v20.vortex-win.data.microsoft.com/collect/v1 Windows Advanced Threat Protection is country specific

Source: Configure Windows diagnostic data in your organization (Windows 10) | Microsoft Docs