• Contact
  • Cookie Policy
  • Helpdesk
Techspark Blogging about technical stuff

Running Sierra Wireless EM7455 on FreeBSD/OPNSense/pfSense

February 27, 2023 5:36 PM / Leave a Comment / XeroX

After some dsl outages I decided to use the SIM card and M.2 slot on the mainboard of my firewall for a LTE WAN failover. The list of supported 4G modems on FreeBSD 13 is short, however it has been extended recently with 13.2 BETA.

I decided getting an Sierra Wireless LTE card as they have an extended documentation and the is a FreeBSD Bug ( Bug 234578 ) on their bugtracker to support EM7455. This card is also known as Dell AirPrime DW5811e or Lenovo Thinkpad EM7455.

The next steps guide you through my experience getting this card running on FreeBSD in serial mode. This technically can work with every Sierra Wireless card. You can convert them to accept qmi mode and AT commands.

The first steps are mentioned in within the bug on FreeBSDs bugtracker. You have to boot a Linux System (I recommend a Debian based distribution, use Rufus with persistent storage) and install the following packages:

sudo apt update
sudo apt-get install libqmi-glib5 libqmi-proxy libqmi-utils curl libuuid-tiny-perl libipc-shareable-perl libjson-perl minicom build-essential -y

Afterwards you may want to stop the ModemManager to not interfere during the process:

systemctl disable ModemManager
systemctl stop ModemManager

Afterwards you want to download the following script and execute it with the appropriate mode. Its mode 6 for the EM7455, it can be different for other cards. You want to change the card to QMI Mode. The device will show up as /dev/cdc-wdm0 or /dev/cdc-wdm1
Download: swi_setusbcomp.pl

sudo perl swi_setusbcomp.pl --device=/dev/cdc-wdm0 --usbcomp=6

Running in MBIM mode (driver=cdc_mbim)
MBIM OPEN succeeded
QMI msg '0x0021' returned status = 1
MBIM QMI support verified
supports 17 QMI subsystems:
  0x00 (1.5)    'QMI_CTL'       - Control service
  0x01 (1.12)   'QMI_WDS'       - Wireless data service
  0x02 (1.7)    'QMI_DMS'       - Device management service
  0x03 (1.21)   'QMI_NAS'       - Network access service
  0x04 (1.3)    'QMI_QOS'       - Quality of service, err, service 
  0x05 (1.4)    'QMI_WMS'       - Wireless messaging service
  0x06 (1.10)   'QMI_PDS'       - Position determination service
  0x07 (1.1)    'QMI_AUTH'      - Authentication service
  0x08 (1.1)    'QMI_AT'        - AT command processor service
  0x09 (2.1)    'QMI_VOICE'     - Voice service
  0x0a (2.0)    'QMI_CAT2'      - Card application toolkit service (new)
  0x0b (1.4)    'QMI_UIM'       - UIM service
  0x0c (1.4)    'QMI_PBM'       - Phonebook service
  0x11 (1.0)    'QMI_SAR'       - Specific absorption rate service
  0x1a (1.0)    'QMI_WDA'       - Wireless data administrative service
  0xe0 (2.0)    'QMI_CAT'       - Card application toolkit service
  0xe1 (1.0)    'QMI_RMS'       - Remote management service
QMI msg '0x0022' returned status = 1
Got QMI DMS client ID '4'
QMI msg '0x555b' returned status = 1
Current USB composition: 14
USB compositions:
   0 - HIP  DM    NMEA  AT    MDM1  MDM2  MDM3  MS      NOT SUPPORTED
   1 - HIP  DM    NMEA  AT    MDM1  MS                  NOT SUPPORTED
   2 - HIP  DM    NMEA  AT    NIC1  MS                  NOT SUPPORTED
   3 - HIP  DM    NMEA  AT    MDM1  NIC1  MS            NOT SUPPORTED
   4 - HIP  DM    NMEA  AT    NIC1  NIC2  NIC3  MS      NOT SUPPORTED
   5 - HIP  DM    NMEA  AT    ECM1  MS                  NOT SUPPORTED
   6 - DM   NMEA  AT    QMI                             SUPPORTED
   7 - DM   NMEA  AT    RMNET1 RMNET2 RMNET3            SUPPORTED
   8 - DM   NMEA  AT    MBIM                            SUPPORTED
   9 - MBIM                                             SUPPORTED
  10 - NMEA MBIM                                        SUPPORTED
  11 - DM   MBIM                                        SUPPORTED
  12 - DM   NMEA  MBIM                                  SUPPORTED
  13 - Config1: comp6    Config2: comp8                 SUPPORTED
* 14 - Config1: comp6    Config2: comp9                 SUPPORTED
  15 - Config1: comp6    Config2: comp10                SUPPORTED
  16 - Config1: comp6    Config2: comp11                SUPPORTED
  17 - Config1: comp6    Config2: comp12                SUPPORTED
  18 - Config1: comp7    Config2: comp8                 SUPPORTED
  19 - Config1: comp7    Config2: comp9                 SUPPORTED
  20 - Config1: comp7    Config2: comp10                SUPPORTED
  21 - Config1: comp7    Config2: comp11                SUPPORTED
  22 - Config1: comp7    Config2: comp12                SUPPORTED
QMI msg '0x555c' returned status = 1
QMI msg '0x0023' returned status = 1

You need to reset the Modem by restarting or unplugging. Now you have the chance doing a firmware update (Downlaod from Sierra Wireless) and execute it with the following commands. While the following IDs for EM7455 match 1199:9071 = Generic Sierra Wireless, 1199:9078 or 9079 for Lenovo EM7455 and 413C:81B6 for Dell.

deviceid=`lsusb | grep -i -E '1199:9071|1199:9079|413C:81B6' | awk '{print $6}'`

sudo qmi-firmware-update --update -d "$deviceid" SWI9X30C_<Version>.cwe SWI9X30C_<Version>_<Generic/Provider>_<Version2>.nvu

You will find the modem as /dev/ttyUSB2 and can access it with minicom now. Technically you can already but back to FreeBSD and use cu -l /dev/cuaUX.2 instead minicom -D /dev/ttyUSB2.

Now we can send AT commands to the modem an convert it to a Generic Sierra Wireless Modem with the following commands. While ENTERCND enables protected commands.

AT!ENTERCND="A710"
OK
AT!USBPID=9071,9070
OK
AT!USBVID=1199

OK
AT!USBPRODUCT="EM7455"

OK
AT!PRIID="9904802","001.001","Generic-Laptop"
OK

Afterwards you maybe able to get a signal info with “AT!GSTATUS?” (assuming the SIM card has no PIN). If this is the case, you’re done and can continue to follow OPNSenses Guide: Configuring Cellular Modems — OPNsense documentation

If this is not the case you have to disable FCC Auth to get this up and running.

AT!GSTATUS?
!GSTATUS:
Current Time:  59588            Temperature: 38
Reset Counter: 8                Mode:        LOW POWER MODE

FCC Auth can only be turned off within the developer menu. The serial can be generated on any device. Send the following commands to you card.

Check for FCCAuth:

AT!PCFCCAUTH?
NV Setting: 1
FCC Auth Enabled: 1
FCC Lock State: 1

OK

Generate Challange:

AT!OPENLOCK?
ABCDEFGHIJ123456

OK

Checkout the following github respository on any Linux system and generate your access key. MDM9x30 matches the EM7455, you can find the full list here: Supported Devices

git clone https://github.com/bkerler/edl

edl/edclient/Tools/sierrakeygen -l ABCDEFGHIJ123456 -d MDM9x30
AT!OPENLOCK="123456ABCDEFGHIJ"
OK
AT!PCFCCAUTH=0
OK
AT!PCFCCAUTH?
NV Setting: 0
FCC Auth Enabled: 1
FCC Lock State: 1

OK
AT!RESET
OK

After a reset the result should be the following:

AT!ENTERCND="A710"
OK
AT!PCFCCAUTH?
NV Setting: 0
FCC Auth Enabled: 0
FCC Lock State: 0

OK

Afterwards the output of “AT!GSTATUS?” should show the reception:


AT!GSTATUS?
!GSTATUS:
Current Time:  59588            Temperature: 38
Reset Counter: 8                Mode:        ONLINE
System mode:   LTE              PS state:    Attached
LTE band:      B1               LTE bw:      20 MHz
LTE Rx chan:   100              LTE Tx chan: 18100
LTE CA state:  NOT ASSIGNED
EMM state:     Registered       Normal Service
RRC state:     RRC Idle
IMS reg state: No Srv

PCC RxM RSSI:  -72              RSRP (dBm):  -104
PCC RxD RSSI:  -65              RSRP (dBm):  -97
Tx Power:      0                TAC:         1234 (12345)
RSRQ (dB):     -11.6            Cell ID:     12345678 (12345678)
SINR (dB):      0.8


OK

Sources:

EM7455, Deactivate Low-Power-Mode – IoT Modules / MC/EM Series – Sierra Wireless Forum

EM Series (sierrawireless.com)

234578 – Support for Sierra Wireless EM7455 modem (freebsd.org)

Update Firmware On EM7455 Chip And Set Device ID To Sierra Wireless | ThinkPenguin.com

edl/sierrakeygen_README.md at master · bkerler/edl (github.com)

danielewood/sierra-wireless-modems: EM7565/EM7455/MC7455 – Modem Configuration (github.com)

Posted in: FreeBSD / Tagged: 4G, EM7455, FreeBSD, LTE, OPNSense, pfSense, Sierra Wireless

Recover ESXi 7.x Bootbank

November 15, 2022 1:06 PM / Leave a Comment / XeroX

During the the installation of a VMware VIB file I lost connectivity to my usb stick containing the installation of esxi. Facing the following errors within ESXi Log:

Could not install image profile: Failed to copy files from /tmp/stagebootbank to /altbootbank: [Errno 5] Input/output error

Device or filesystem with identifier mpx.vmhba32:C0:T0:L0 has entered the All Paths Down Timeout state after being in the All Paths Down state for 140 seconds. I/Os will now be fast failed.

Lost connectivity to storage device mpx.vmhba32:C0:T0:L0. Path vmhba32:C0:T0:L0 is down. Affected datastores: BOOTBANK1″, “BOOTBANK2”, “LOCKER-624c4a59-8a3bf37a-8986-e435c87de92a.

After a reboot I saw the error message “BANK5: not a VMware boot bank” however BOOTBANK2 was intact so ESXi was booting with last working state from BOOTBANK2 (BANK6 in my case). Checking with “ls /altbootbank” I saw that alot of files where missing. I started to check if the filesystem was damaged with:

#Check ESXi bootbank device
vmkfstools -P /altbootbank

#Check and repair filesystem
dosfsck -r -w /dev/disks/mpx.vmhba32:C0:T0:L0:5

While mpx.vmhba32:C0:T0:L0:5 is the output of the previous command and :5 is the partition number. So :5 is BANK5 and :6 is BANK6.

Afterwards you can completely copy over the contents of /bootbank to /altbootbank with “cp”. You need to edit boot.cfg and modify “updated” to a number lower (-1). While the next VIB or update/patch you install on esxi will completely maintain the bootbanks again.

Posted in: ESXi, Hardware, vCenter, VMWare / Tagged: BANK5: not a VMware boot bank, BANK6: not a VMware boot bank, bootbank, bootbank recovery, ESXi, recovery

Microsoft Edge URI List – Open Office Apps without Prompt for SharePoint

September 5, 2022 2:02 PM / Leave a Comment / XeroX

By default Microsoft Edge always prompts when it opens external applications like Microsoft Word or Microsoft OneDrive. You may want this prompt to disappear for your trusted local SharePoint 2013/2016/2019/Subscription Farm.

The list of URI Schemes is published here: Office URI Schemes | Microsoft Docs
I found out these URI schemes are not complete and in some cases not valid anymore.

So how to configure this now? Add the Microsoft Edge Group Policies to your domain controller and search for the following settings: “Define a list of protocols that can launch an external application from listed origins without prompting the user”.

This has the be in json format and will look like the following:

[{"allowed_origins":["sharepoint.example.com","officeonline.example.com"],"protocol":"ms-word"},{"allowed_origins":["sharepoint.example.com","officeonline.example.com"],"protocol":"msoutlook"},{"allowed_origins":["sharepoint.example.com","officeonline.example.com"],"protocol":"ms-excel"},{"allowed_origins":["sharepoint.example.com","officeonline.example.com"],"protocol":"ms-powerpoint"},{"allowed_origins":["sharepoint.example.com","officeonline.example.com"],"protocol":"ms-access"},{"allowed_origins":["sharepoint.example.com","officeonline.example.com"],"protocol":"ms-project"},{"allowed_origins":["sharepoint.example.com","officeonline.example.com"],"protocol":"ms-visio"},{"allowed_origins":["sharepoint.example.com","officeonline.example.com"],"protocol":"onenote"},{"allowed_origins":["sharepoint.example.com","officeonline.example.com"],"protocol":"viewinfileexplorer"},{"allowed_origins":["sharepoint.example.com","officeonline.example.com"],"protocol":"odopen"}]

The following URI Schemes are being used here:

URI SchemeDescriptipon
ms-wordMicrosoft Word
msoutlookMicrosoft Outlook
(not documented)
ms-excelMicrosoft Excel
ms-powerpointMicrosoft PowerPoint
ms-accessMicrosoft Access
ms-projectMicrosoft Project
ms-visioMicrosoft Visio
onenoteMicrosoft OneNote (Phat Client)
viewinfileexplorerExplorer View
(not documented)
odopenMicrosoft OneDrive
(not documented)
Posted in: Microsoft, OfficeWebApps, SharePoint / Tagged: Office, OfficeOnline, OfficeWebApps, SharePoint, URI, URI Scheme

Boot Batocera from HDD/SSD

September 5, 2022 1:47 PM / 14 Comments / XeroX

Recently I acquired a Fujitsu Futro S740. Its sold as a thinclient, but is technically a full blown pc with a small SSD (8 or 16GB). I replaced it with a M.2 2280 B+M Key SSD and planned to use it as “Retrostation”. I tried recalbox, however the S740 only allows GPT/EFI boot, there is no legacy mode anymore. So I tried batocera. It boots well from the USB Stick but after installing to the SSD from the Menu it doesn’t boot.

I got this fixed by booting a Live Linux and set the EFI Partition to label “EFI system partition” and edited the flags to “boot”,”esp”,”legacy boot” (use GParted and Ubuntu Mate Live CD for ex.). After wards you just register it to the BIOS with:

efibootmgr -c -d /dev/sda -p 1 -L "Batocera" -l '\EFI\BOOT\bootx64.efi'

The command won’t work from within Batocera, using a bootable linux of an USB stick is mandatory.

Reboot and have fun.

Posted in: Hardware / Tagged: Batocera, Fujitsu, Futro, S740

Synology iSCSI/LUN SSD Cache with DSM 7.0

September 28, 2021 2:31 PM / Leave a Comment / XeroX

UPDATE: Seems to be gone with ‘Flashcache Version : flashcache-1.0-2021-10-18-20:42’ on 7.0.1. 🙁

With DSM 7.0 Synology removed the feature of accelerating Block-Level LUNs. This is an interesting feature for iSCSI LUNs used for Hypervisors like VMware ESX.

Synology DSM 7.0 Release Notes:

- Creating SSD caches on block-level LUNs is no longer supported. Existing SSD caches for block LUNs will function normally after the update.

However this is valid but you can re-enable acceleration for Block-Level iSCSI LUNs.

Logon to your Synology NAS via SSH and get the root shell via “sudo -i”. Execute the following command to re-enable the cache.

/var/packages/ScsiTarget/target/bin/synoiscsihook --flashcache_enable

This works as long as you’re not rebooting. You can create a task within DSM with trigger at “Boot-Up” to execute this command line to enable the Cache again.

Posted in: ESXi, Synology, VMWare / Tagged: Synology, VMWare

Install EWSManagedAPI NuGet (GitHub) for SharePoint 2013/2016/2019

August 2, 2021 12:37 AM / Leave a Comment / XeroX

Recently I tried to enable SiteMailboxes for SharePoint 2019. The documentation (Configure site mailboxes in SharePoint Server – SharePoint Server | Microsoft Docs) claims to download EWSManagedAPI.msi but this results in a 404, as this project moved to GitHub (OfficeDev/ews-managed-api (github.com)). However on GitHub there is no executable or MSI to install.

You can install the NuGet Package (NuGet Gallery | Microsoft.Exchange.WebServices 2.2.0) on your SharePoint Server with the following command:

Install-Package Microsoft.Exchange.WebServices

Basically you are done and should find the NuGet Package at the following location:

C:\Program Files\PackageManagement\NuGet\Packages\Microsoft.Exchange.WebServices.2.2\lib\40\

However the Setup Scripts within the SharePoint Documentation will fail as the DLLs are not registered in GAC (Globaly Assembly Cache).

Verfiy with:

$assm = [System.Reflection.Assembly]::LoadFile("C:\Program Files\PackageManagement\NuGet\Packages\Microsoft.Exchange.WebServices.2.2\lib\40\Microsoft.Exchange.WebServices.dll")
$assm.GlobalAssemblyCache

This should return “False”. Claim gacutil.exe from a Visual Studio (Free Community Edition maybe fine, check Terms and License) Installation with for ex. Windows 10 SDK. Copy it over and run:

gacutil.exe -i  C:\Program Files\PackageManagement\NuGet\Packages\Microsoft.Exchange.WebServices.2.2\lib\40\Microsoft.Exchange.WebServices.dll 
gacutil.exe -i  C:\Program Files\PackageManagement\NuGet\Packages\Microsoft.Exchange.WebServices.2.2\lib\40\Microsoft.Exchange.WebServices.Auth.dll

Restart your powershell console and rerun the commands above. It will return “True” and the Setup Scripts run through without an issue.

Posted in: Microsoft, SharePoint

open-vm-tools: Unknown ioctl 1976

November 25, 2020 6:12 PM / 3 Comments / XeroX

Recently I setup my Raspberry Pi 4B 8GB ESXi Cluster. After compling and installing the open-vm-tools for Arm64/AArch64 I got alot of messages regarding “Unknown ioctl 1976”. This happens due to missing “VMCI_SOCKETS” module load during startup. You can simply fix this by adding the following lines to /etc/modprobe.d/blacklist.conf:

blacklist vsock_loopback
blacklist vmw_vsock_virtio_transport_common
install vsock_loopback /usr/bin/true
install vmw_vsock_virtio_transport_common /usr/bin/true

Posted in: ESXi, VMWare / Tagged: AArch64, ARM64, ESXi, open-vm-tools, VMWare

Synology Virtual Machine Manager increase vDisk Limit

November 25, 2020 4:11 PM / 2 Comments / XeroX

Recently I tried to run a VMware vCenter Appliance (vCSA) on my Synology. Trying to import the provided OVA File results in an unplausible error, so I tried to convert it with the OVFTool thats provided by VMware on the installation disk. I converted or extracted the vmdk diskimages via OVFTool, its basically achieveable by calling ovftool.exe <ova> file.

After that I imported all vmdk images to my Virtual Machine Manager via Images -> Disk Images and started “importing” a virtual machine with the uploaded diskimages. Sadly Synology limits the maximum vDisks for new and imported virtual machines to 8. This is not a hard limit as Virtual Machine Manager is run by qemu and qemu limit is 256 disks.

So how about trying to add the disks after the virtual machine creation via command line? I was messing around with this but the vdisks are added via virtio-scsi and I found this hard to add the disks manually.

So lets see if we can achieve this a different way. I analysed the JavaScript used by Virtual Machine Manager. This can be found here “/volume1/@appstore/Virtualization/ui/virtualization.js”. There is even a check in it, that prompts you with an error if a machine has more than 8 vDisks. So how can we increase the maximum virtual machine attachable disks?

Open “/volume1/@appstore/Virtualization/ui/virtualization.js” and edit the value of “this.maxVdiskNum=8” from 8 to 16. Save the file, gzip it again via gzip -k virtualization.js and restart Virtual Machine Manager or your whole NAS.

However for a vCenter it takes sometime to setup the machine. Keep the first two disks with VirtIO and all other disks on SATA Setting.

Good Luck.

Posted in: Synology, vCenter, VMWare / Tagged: QEMU, Synology, vCenter, Virtual Machine Manager, VMWare

Error while trying to Access “Details” of a SharePoint App

November 6, 2015 1:22 PM / Leave a Comment / XeroX

Recently we added Access Services to our SharePoint 2013 environment. After the initial setup we started testing the new implementation and stumbled over an error while accessing the details page of an app. This has nothing to do with access itself, more with apps in general.

2015-11-06_13-03-54

After clicking on details you get an error message with the correlation id. So nothing easier to get the log regarding that error.

SqlError: ‘The EXECUTE permission was denied on the object ‘prc_CountAppInstanceData’, database ‘SharePoint_Logging’, schema ‘dbo’.’    Source: ‘.Net SqlClient Data Provider’ Number: 229 State: 5 Class: 14 Procedure: ‘prc_CountAppInstanceData’ LineNumber: 1 Server: ‘Database.fqdn.com’ f2ec3e9d-ac28-80f1-8d80-1d89f5d672a9
11/06/2015 12:50:34.93  w3wp.exe (Servername.fqdn.com:0x5DE4)            0x5D34 SharePoint Foundation          Database                       5214 Critical Insufficient SQL database permissions for user ‘Name: NT AUTHORITY\IUSR SID: S-1-5-17 ImpersonationLevel: Impersonation’ in database ‘SharePoint_Logging’ on SQL Server instance ‘Database.fqdn.com’. Additional error information from SQL Server is included below.  The EXECUTE permission was denied on the object ‘prc_CountAppInstanceData’, database ‘SharePoint_Logging’, schema ‘dbo’. f2ec3e9d-ac28-80f1-8d80-1d89f5d672a9

This leads us to a permission issue. We tried granting the App Management Service Account “SPDataAccess” permission on our logging database, which did not help.

As you can see in the log there is an user specified IUSR SID: S-1-5-17. This leads to a permission issue from IIS WebServer. Makes sense as all SharePoint Applications are running within the IIS and their Application Pools. As our App Management Service Account wasn’t the issue we granted our Application Pool Account under which the Web Applications are running, the “SPDataAccess” permission on our logging database.

2015-11-06_13-04-42

Et voila, this fixed the issue.

Problem: App Details do not work.

Solution: Grant SPDataAccess Permisson to your Web Application Pool Account on your SharePoint Logging Database.

Posted in: Microsoft, SharePoint / Tagged: Logging Database, Permissions, SharePoint Database

Reinstall WSUS and keep downloaded content

June 3, 2015 8:37 PM / 1 Comment / XeroX

Our scenario was that we wanted to upgrade our WSUS running on Windows Server 2012 to Windows Server 2012 R2 and changing the database to WID. The database wasn’t that important for us, as all computers placed in one group where all patches are approved. But we wanted to keep the content of 800 Gigabyte without redownloading all that stuff.

A huge advantage is if you have the data on a seperate drive or partition. Before you start, shutdown the WSUS Service and rename the WsusContent folder or move it to a different location.

Then you’re good to go. Reinstall or setup a new machine and install WSUS. During the initial configuration wizard its important that you choose “synchronize manually” and do not trigger a sync before or at the end of the wizard. Then copy the previous saved WsusContent folder to the location you’ve chosen in the wizard and replace everything. After that you can manually start your synchronization and WSUS is reindexing the whole content without downloading a huge amount of data. It should take around 3-4 hours, depending on your hardware and disk. You can see the status on synchronization tab.

Good luck!

Posted in: Microsoft, Windows Server / Tagged: keep content, Reinstall, Reinstall WSUS, Setup, Setup WSUS, WSUS

Post Navigation

1 2 3 Next »

Recent Posts

  • Running Sierra Wireless EM7455 on FreeBSD/OPNSense/pfSense
  • Recover ESXi 7.x Bootbank
  • Microsoft Edge URI List – Open Office Apps without Prompt for SharePoint
  • Boot Batocera from HDD/SSD
  • Synology iSCSI/LUN SSD Cache with DSM 7.0

Recent Comments

  • XeroX on Boot Batocera from HDD/SSD
  • Dom on Boot Batocera from HDD/SSD
  • XeroX on Boot Batocera from HDD/SSD
  • mhmuc on Boot Batocera from HDD/SSD
  • mhmuc on Boot Batocera from HDD/SSD

Archives

  • February 2023
  • November 2022
  • September 2022
  • September 2021
  • August 2021
  • November 2020
  • November 2015
  • June 2015
  • February 2015
  • August 2014
  • June 2014
  • March 2014
  • February 2014
  • January 2014
  • November 2013
  • September 2013
  • August 2013

Categories

  • ESXi
  • FreeBSD
  • Hardware
  • Hyper-V
  • iOS
  • Microsoft
  • OfficeWebApps
  • Operations Manager
  • SharePoint
  • Synology
  • vCenter
  • VMWare
  • Webserver
  • Windows Server
© Copyright 2023 - Techspark
Infinity Theme by DesignCoral / WordPress
This website uses Cookies and Matomo to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept Reject Opt-Out
Cookies Policy

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Functional
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytics
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
CookieDurationDescription
_pk_id.1.03ee1 year 27 daysMatamo set this cookie to store a unique user ID.
_pk_ses.1.03ee30 minutesThis cookie is used to store a unique session ID for gathering information on how the users use the website.
Advertisement
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Others
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
SAVE & ACCEPT
Powered by CookieYes Logo