Solcon IPTV via Ubiquiti USG

  1. Log in op de UniFi omgeving (via ons is dat https://unifi.miruict.nl).
  2. Maak een nieuw VLAN-only netwerk aan.
    In dit voorbeeld gebruiken we IPTV-bridge als naam en 250 als VLAN ID.
    Schakel IGMP-snooping in.

3. Maak in de map “/usr/lib/unifi/data/sites/<sitenaam>” een bestand “config.gateway.json” aan met de volgende inhoud (vervang <sitenaam> met de naam van de site):

{
  "interfaces": {
    "bridge": {
      "br0": {
        "aging": "300",
        "bridged-conntrack": "disable",
        "hello-time": "2",
        "max-age": "20",
        "priority": "32768",
        "promiscuous": "disable",
        "stp": "false"
      }
    },
    "ethernet": {
      "eth0": {
        "vif": {
          "188": {
            "bridge-group": {
              "bridge": "br0"
            }
          }
        }
      },
      "eth1": {
        "vif": {
          "250": {
            "bridge-group": {
              "bridge": "br0"
            }
          }
        }
      }
    }
  }
}

4. Zorg ervoor dat de USG zijn instellingen opnieuw ophaalt door deze opnieuw op te starten of via de provision knop in UniFi.

5. Steek de IPTV kastjes in een switch welke IGMP-snooping ondersteund en verander die poort naar het IPTV netwerk (VLAN 250).

Komt u er niet uit? Wij leveren ook IT consultancy en IT beheer! Neem contact met ons op voor meer informatie.

Controleren welke macOS-versie uw Mac gebruikt

Met ‘Over deze Mac’ kunt u controleren welke versie van het Mac-besturingssysteem op uw Mac is geïnstalleerd.

Welke macOS-versie is geïnstalleerd?

Kies ‘Over deze Mac’ in het Apple-menu  in de linkerhoek van het scherm.
U ziet nu de naam van de macOS-versie, bijvoorbeeld ‘macOS Monterey’ of ‘macOS Big Sur’, gevolgd door het versienummer.

Als u ook het buildnummer wilt weten, klikt u op het versienummer.

Server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

Bij het proberen te updaten van Proxmox 5 (Debian 8 gebasseerd) geeft deze de volgende foutmelding:
Server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

Dit komt omdat het root certificaat van Letsencrypt verlopen is op 30 september 2021.

De oplossing hiervoor is als volgt:

  1. Open (bijvoorbeeld met nano) /etc/ca-certificates.conf en zet een ! voor /mozilla/DST_Root_CA_X3.crt
  2. update ca-certificates met update-ca-certificates

Bovenstaande werkt alleen mits ca-certificates geinstalleerd staat en /usr/share/ca-certificates/mozilla/ISRG_Root_X1.crt in /etc/ca-certificates.conf zit.

Remote Server returned ‘550 5.7.520 Access denied, Your organization does not allow external forwarding. Please contact your administrator for further assistance. AS(7555)’

When trying to use external forwarding on a Shared Mailbox:

user@domain.tld
Remote Server returned ‘550 5.7.520 Access denied, Your organization does not allow external forwarding. Please contact your administrator for further assistance. AS(7555)’

Go to: https://protection.office.com/antispam

Create policy -> Outbound -> user@domain.tld -> Forwarding is enabled.

The command you tried to run isn’t currently allowed in your organization. To run this command, you first need to run the command: Enable-OrganizationCustomization

When trying to add an anti-spam policy in O365 Security Portal the following message occurs:

All the customers where we already added anti-spam policies without this message used Azure AD Connect, I think this activates the OrganizationCustomization option.

On Windows 10, open elevated Powershell:

Install-Module -Name ExchangeOnlineManagement

Import-Module ExchangeOnlineManagement

Connect-ExchangeOnline -UserPrincipalName user@domain.tld

Enable-OrganizationCustomization

Just one extra step there for those who do not use PowerShell, after InstallModule, run this: Set-ExecutionPolicy RemoteSigned

Gareth

“Symantec Endpoint Protection has detected that there are pending system changes that require a reboot. Please reboot the system and rerun the installation.”

When trying to install Symantec Endpoint Security the following error may show up:
“Symantec Endpoint Protection has detected that there are pending system changes that require a reboot. Please reboot the system and rerun the installation.”

The first step would be to reboot, but sometimes this is not possible because of important system services, or after a reboot the error still shows.
Please try the following:

  1. Open the Windows Registry using regedit.exe.
  2. Search for the entry “PendingFileRenameOperations” in:
    • HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession Manager
  3. Restart the SEP installation; the install should finish without error.

Another service operation is currently in progress

When trying to install Symantec Endpoint Protection the following error may popup:
“Aanother service operation is currently in progress”

Try a reboot first, if not possible or problem still exists, try the following:

  1. Open Windows Registry Editor. Click Start > Run, type regedit, and click OK.
  2. Back up the registry.
    Note: For Windows Registry backup and restore instructions, see How to back up and restore the registry in Windows.
  3. In the left pane, navigate to the following key:
    HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstaller.
  4. In the left pane, right-click on the Inprogress key, and click Delete.
  5. Click Yes to permanently delete the entire Inprogress key and all of its subkeys.

Source: https://support.symantec.com/en_US/article.TECH218138.html

Default passwords

Below we will publish default passwords we encounter.

General (vendor):
3Com: admin/admin
Belkin: admin/admin
BenQ: admin/admin
Grandstream: admin/admin
D-Link: admin/admin
Digicom: user/password or admin/michelangelo
Linksys: admin/admin
Netgear: admin/password
Sitecom: sitecom/admin
Thomson: user/user
US Robotics: admin/admin
Zebra: admin/1234

Specific (device):
Brother MFC-L9570CDW: initpass
Brother LP844: admin/1234
Panasonic KX-UT133NE: admin/adminpass

Moving directory to another partition (part 1)

Due to the fact that the primaire virtual disk (containing the Debian OS and currently the /var) of one of our customers servers is on a SSD pool and almost reaching its capacity (>75%) we need to add a second virtual disk and move the /var folder (HDD space costs less and is fast enough to serve websites and email).

First we started with creating the new virtual disk and adding it to the VM.
Secondly we partitioned it:
1. Use “fdisk -l” to get the disk name (in our case vdb)
2. cfdisk /dev/<diskname>
3. Select new
4. Press enter at the “Specify size in MB” to use the whole disk.
5. “mkfs.ext4 /dev/<diskname>”
6. “mkdir /var2”
7. Get the UUID of the disk with the command “blkid”.
8. “echo “UUID=<UUID> /var2 ext4 errors=remount-ro 0 1″ >> /etc/fstab”

Next we can copy the data from /var to /var2 (we use rsync to preserve permissions).
We are currently running the following command to make a first copy:
“rsync -av /var/ /var2”

The next step would be stopping all services (apache, mysql, dovecot etc.) but we will continue on this after the data has been copied (which will take a full night).