13-05-2021

Microsoft Au Daemon Mac Os X

-->

2008-1-3 The application that does the checking and updating is Microsoft AutoUpdate.app, and it's usually found at the top level of the Applications folder. Oddly, it looks like setting it to 'Manually' doesn't remove that daemon from the Login Items list, which is mildly annoying. Then again, it is Microsoft. Microsoft Autoupdate Helper 3.18(180410) + legacy SilverLight insecure installer package EoP. This issue affects Microsoft Office for Mac 2016, and SkypeForBusiness (16.17.0.65). Office for Mac. Microsoft au daemon是干什么用的？使用Macbook，发现进程里常有个叫Microsoft AU Daemon，却不知干什么用的。.

You can build Azure Service Fabric applications to run on Linux clusters by using Mac OS X. This document covers how to set up your Mac for development.

Prerequisites

Azure Service Fabric doesn't run natively on Mac OS X. To run a local Service Fabric cluster, a pre-configured Docker container image is provided. Before you get started, you need:

At least 4 GB of RAM.
The latest version of Docker.

Tip

To install Docker on your Mac, follow the steps in the Docker documentation. After installing, verify your installation.

Create a local container and set up Service Fabric

To set up a local Docker container and have a Service Fabric cluster running on it, perform the following steps:

Update the Docker daemon configuration on your host with the following settings and restart the Docker daemon:
You can update these settings directly in the daemon.json file in your Docker installation path. You can directly modify the daemon configuration settings in Docker. Select the Docker icon, and then select Preferences > Daemon > Advanced.
Note
Modifying the daemon directly in Docker is recommended because the location of the daemon.json file can vary from machine to machine. For example,~/Library/Containers/com.docker.docker/Data/database/com.docker.driver.amd64-linux/etc/docker/daemon.json.
Tip
We recommend increasing the resources allocated to Docker when testing large applications. This can be done by selecting the Docker Icon, then selecting Advanced to adjust the number of cores and memory.
In a new directory create a file called Dockerfile to build your Service Fabric Image:
Note
You can adapt this file to add additional programs or dependencies into your container.For example, adding RUN apt-get install nodejs -y will allow support for nodejs applications as guest executables.
Tip
By default, this will pull the image with the latest version of Service Fabric. For particular revisions, please visit the Docker Hub page
To build your reusable image from the Dockerfile open a terminal and cd to the directly holding your Dockerfile then run:
Note
This operation will take some time but is only needed once.
Now you can quickly start a local copy of Service Fabric, whenever you need it, by running:
Tip
Provide a name for your container instance so it can be handled in a more readable manner.
If your application is listening on certain ports, the ports must be specified by using additional -p tags. For example, if your application is listening on port 8080, add the following -p tag:
docker run -itd -p 19080:19080 -p 8080:8080 --name sfonebox microsoft/service-fabric-onebox
The cluster will take a moment to start. When it is running, you can view logs using the following command or jump to the dashboard to view the clusters health http://localhost:19080:
To stop and cleanup the container, use the following command. However, we will be using this container in the next step.

Known Limitations

The following are known limitations of the local cluster running in a container for Mac's:

DNS service does not run and is not supported Issue #132

Set up the Service Fabric CLI (sfctl) on your Mac

Follow the instructions at Service Fabric CLI to install the Service Fabric CLI (sfctl) on your Mac.The CLI commands support interacting with Service Fabric entities, including clusters, applications, and services.

To connect to the cluster before deploying applications run the command below.

Create your application on your Mac by using Yeoman

Service Fabric provides scaffolding tools that help you to create a Service Fabric application from the terminal by using the Yeoman template generator. Use the following steps to ensure that the Service Fabric Yeoman template generator is working on your machine:

Node.js and Node Package Manager (NPM) must be installed on your Mac. The software can be installed by using HomeBrew, as follows:
Install the Yeoman template generator on your machine from NPM:
Install the Yeoman generator that you prefer by following the steps in the getting started documentation. To create Service Fabric applications by using Yeoman, follow these steps:
After you install the generators, create guest executable or container services by running yo azuresfguest or yo azuresfcontainer, respectively.
To build a Service Fabric Java application on your Mac, JDK version 1.8 and Gradle must be installed on the host machine. The software can be installed by using HomeBrew, as follows:
Important
Current versions of brew cask install java may install a more recent version of the JDK.Be sure to install JDK 8.

Deploy your application on your Mac from the terminal

After you create and build your Service Fabric application, you can deploy your application by using the Service Fabric CLI:

Connect to the Service Fabric cluster that is running inside the container instance on your Mac:
From inside your project directory, run the install script:

Set up .NET Core 2.0 development

Install the .NET Core 2.0 SDK for Mac to start creating C# Service Fabric applications. Packages for .NET Core 2.0 Service Fabric applications are hosted on NuGet.org, which is currently in preview.

Install the Service Fabric plug-in for Eclipse on your Mac

Azure Service Fabric provides a plug-in for Eclipse Neon (or later) for the Java IDE. The plug-in simplifies the process of creating, building, and deploying Java services. To install or update the Service Fabric plug-in for Eclipse to the latest version, follow these steps. The other steps in the Service Fabric for Eclipse documentation are also applicable: build an application, add a service to an application, uninstall an application, and so on.

The last step is to instantiate the container with a path that is shared with your host. The plug-in requires this type of instantiation to work with the Docker container on your Mac. For example:

The attributes are defined as follows:

/Users/sayantan/work/workspaces/mySFWorkspace is the fully qualified path of the workspace on your Mac.
/tmp/mySFWorkspace is the path that is inside of the container to where the workspace should be mapped.

Note

If you have a different name/path for your workspace, update these values in the docker run command.

If you start the container with a name other than sfonebox, update the name value in the testclient.sh file in your Service Fabric actor Java application.

Next steps

-->

Azure Pipelines | Azure DevOps Server 2019 | TFS 2018 | TFS 2017 | TFS 2015

Note

In Microsoft Team Foundation Server (TFS) 2018 and previous versions,build and release pipelines are called definitions,runs are called builds,service connections are called service endpoints,stages are called environments,and jobs are called phases.

To build and deploy Xcode apps or Xamarin.iOS projects, you'll need at least one macOS agent. This agent can also build and deploy Java and Android apps.

Before you begin:

If your pipelines are in Azure Pipelines and a Microsoft-hosted agent meets your needs, you can skip setting up a self-hosted macOS agent.
Otherwise, you've come to the right place to set up an agent on macOS. Continue to the next section.

Learn about agents

If you already know what an agent is and how it works, feel free to jump right in to the following sections. But if you'd like some more background about what they do and how they work, see Azure Pipelines agents.

Check prerequisites

Make sure your machine has these prerequisites:

macOS Sierra (10.12) or higher
Git 2.9.0 or higher (latest version strongly recommended - you can easily install with Homebrew)

These prereqs are required for agent version 2.125.0 and higher.

These prereqs are required for agent version 2.124.0 and below.If you're able, we recommend upgrading to a newer macOS (10.12+) and upgrading to the newest agent.

Make sure your machine has these prerequisites:

OS X Yosemite (10.10), El Capitan (10.11), or macOS Sierra (10.12)
Git 2.9.0 or higher (latest version strongly recommended)
Meets all prereqs for .NET Core 1.x

If you'll be using TFVC, you will also need the Oracle Java JDK 1.6 or higher.(The Oracle JRE and OpenJDK are not sufficient for this purpose.)

Prepare permissions

If you're building from a Subversion repo, you must install the Subversion client on the machine.

You should run agent setup manually the first time.After you get a feel for how agents work, or if you want to automate setting up many agents, consider using unattended config.

Decide which user you'll use

As a one-time step, you must register the agent. Someone with permission toadminister the agent queuemust complete these steps. The agent will not use this person'scredentials in everyday operation, but they're required to complete registration.Learn more about how agents communicate.

Sign in with the user account you plan to use in your Team Foundation Server web portal (https://{your-server}:8080/tfs/).

Sign in with the user account you plan to use in you Azure DevOps Server web portal (https://{your-server}/DefaultCollection/).

Sign in with the user account you plan to use in your Azure DevOps organization (https://dev.azure.com/{your_organization}).

From your home page, open your profile. Go to your security details.
Create a personal access token.
For the scope select Agent Pools (read, manage) and make sure all the other boxes are cleared.If it's a deployment group agent, for the scope select Deployment group (read, manage) and make sure all the other boxes are cleared.
Select Show all scopes at the bottom of the Create a new personal access token window window to see the complete list of scopes.
Copy the token. You'll use this token when you configure the agent.

Authenticate as a Windows user (TFS 2015 and TFS 2017)

As an alternative, on TFS 2017, you can use either a domain user or alocal Windows user on each of your TFS application tiers.

On TFS 2015, for macOS and Linux only,we recommend that you create a local Windows user on each of your TFS application tiers and dedicate that user for the purpose of deploying build agents.

Confirm the user has permission

Make sure the user account that you're going to use has permission to register the agent.

Is the user an Azure DevOps organization owner or TFS or Azure DevOps Server administrator? Stop here, you have permission.

Otherwise:

Open a browser and navigate to the Agent pools tab for your Azure Pipelines organization or Azure DevOps Server or TFS server:
1. Choose Azure DevOps, Organization settings.
2. Choose Agent pools.
1. Choose Azure DevOps, Collection settings.
2. Choose Agent pools.
1. Navigate to your project and choose Settings (gear icon) > Agent Queues.
2. Choose Manage pools.
1. Navigate to your project and choose Settings (gear icon) > Agent Queues.
2. Choose Manage pools.
1. Navigate to your project and choose Manage project (gear icon).
2. Choose Control panel.
3. Select Agent pools.
Click the pool on the left side of the page and then click Security.
If the user account you're going to use is not shown, then get an administrator to add it. The administrator can be an agent pool administrator, an Azure DevOps organization owner, or a TFS or Azure DevOps Server administrator.
If it's a deployment group agent, the administrator can be an deployment group administrator, an [Azure DevOps organization owner, or a TFS or Azure DevOps Server administrator.
You can add a user to the deployment group administrator role in the Security tab on the Deployment Groups page in Azure Pipelines.

Note

Daemon X Machina

If you see a message like this: Sorry, we couldn't add the identity. Please try a different identity., you probably followed the above steps for an organization owner or TFS or Azure DevOps Server administrator. You don't need to do anything; you already have permission to administer the agent queue.

Download and configure the agent

Azure Pipelines

Log on to the machine using the account for which you've prepared permissions as explained above.
In your web browser, sign in to Azure Pipelines, and navigate to the Agent pools tab:
1. Choose Azure DevOps, Organization settings.
2. Choose Agent pools.
Select the Default pool, select the Agents tab, and choose New agent.
On the Get the agent dialog box, click macOS.
Click the Download button.
Follow the instructions on the page.
Unpack the agent into the directory of your choice. cd to that directory and run ./config.sh. Make sure that the path to the directory contains no spaces because tools and scripts don't always properly escape spaces.

Azure DevOps Server 2019

Log on to the machine using the account for which you've prepared permissions as explained above.
In your web browser, sign in to Azure DevOps Server 2019, and navigate to the Agent pools tab:
1. Choose Azure DevOps, Collection settings.
2. Choose Agent pools.
Click Download agent.
On the Get agent dialog box, click macOS.
Click the Download button.
Follow the instructions on the page.
Unpack the agent into the directory of your choice. cd to that directory and run ./config.sh. Make sure that the path to the directory contains no spaces because tools and scripts don't always properly escape spaces.

TFS 2017 and TFS 2018

Log on to the machine using the account for which you've prepared permissions as explained above.
In your web browser, sign in to Azure Pipelines or TFS, and navigate to the Agent pools tab:
1. Navigate to your project and choose Settings (gear icon) > Agent Queues.
2. Choose Manage pools.
Click Download agent.
On the Get agent dialog box, click macOS.
Click the Download button.
Follow the instructions on the page.
Unpack the agent into the directory of your choice. cd to that directory and run ./config.sh. Make sure that the path to the directory contains no spaces because tools and scripts don't always properly escape spaces.

TFS 2015

Browse to the latest release on GitHub.
Follow the instructions on that page to download the agent.
Configure the agent.

Server URL

Azure Pipelines: https://dev.azure.com/{your-organization}

TFS 2015: http://{your_server}:8080/tfs

Authentication type

Azure Pipelines

Choose PAT, and then paste the PAT token you created into the command prompt window.

Note

When using PAT as the authentication method, the PAT token is used only for the initial configuration of the agent. Learn more at Communication with Azure Pipelines or TFS.

TFS or Azure DevOps Server

Important

Make sure your server is configured to support the authentication method you want to use.

When you configure your agent to connect to TFS, you've got the following options:

Alternate Connect to TFS or Azure DevOps Server using Basic authentication. After you select Alternate you'll be prompted for your credentials.
Integrated Not supported on macOS or Linux.
Negotiate (Default) Connect to TFS or Azure DevOps Server as a user other than the signed-in user via a Windows authentication scheme such as NTLM or Kerberos. After you select Negotiate you'll be prompted for credentials.
PAT Supported only on Azure Pipelines and TFS 2017 and newer. After you choose PAT, paste the PAT token you created into the command prompt window. Use a personal access token (PAT) if your Azure DevOps Server or TFS instance and the agent machine are not in a trusted domain. PAT authentication is handled by your Azure DevOps Server or TFS instance instead of the domain controller.

Note

When using PAT as the authentication method, the PAT token is used only for the initial configuration of the agent on Azure DevOps Server and the newer versions of TFS. Learn more at Communication with Azure Pipelines or TFS.

Run interactively

For guidance on whether to run the agent in interactive mode or as a service, see Agents: Interactive vs. service.

To run the agent interactively:

If you have been running the agent as a service, uninstall the service.
Run the agent.

To restart the agent, press Ctrl+C and then run run.sh to restart it.

To use your agent, run a job using the agent's pool.If you didn't choose a different pool, your agent will be in the Default pool.

Run once

For agents configured to run interactively, you can choose to have the agent accept only one job. To run in this configuration:

Agents in this mode will accept only one job and then spin down gracefully (useful for running on a service like Azure Container Instances).

Run as a launchd service

We provide the ./svc.sh script for you to run and manage your agent as a launchd LaunchAgent service. This script will be generated after you configure the agent. The service has access to the UI to run your UI tests.

Note

If you prefer other approaches, you can use whatever kind of service mechanism you prefer. See Service files.

Tokens

In the section below, these tokens are replaced:

{agent-name}
{tfs-name}

For example, you have configured an agent (see above) with the name our-osx-agent. In the following examples, {tfs-name} will be either:

Daemon X Machina Ign

Azure Pipelines: the name of your organization. For example if you connect to https://dev.azure.com/fabrikam, then the service name would be vsts.agent.fabrikam.our-osx-agent
TFS: the name of your on-premises TFS AT server. For example if you connect to http://our-server:8080/tfs, then the service name would be vsts.agent.our-server.our-osx-agent

Commands

Change to the agent directory

For example, if you installed in the myagent subfolder of your home directory:

What Is Microsoft Au Daemon Mac Os X

Install

Command:

This command creates a launchd plist that points to ./runsvc.sh. This script sets up the environment (more details below) and starts the agent's host.

Start

Command:

Output:

The left number is the pid if the service is running. If second number is not zero, then a problem occurred.

Status

Command:

Output:

The left number is the pid if the service is running. If second number is not zero, then a problem occurred.

Stop

Command:

Output:

Uninstall

You should stop before you uninstall.

Command:

Automatic login and lock

Normally, the agent service runs only after the user logs in. If you want the agent service to automatically start when the machine restarts, you can configure the machine to automatically log in and lock on startup. See Set your Mac to automatically log in during startup - Apple Support.

Note

For more information, see the Terminally Geeky: use automatic login more securely blog. The .plist file mentioned in that blog may no longer be available at the source, but a copy can be found here: Lifehacker - Make OS X load your desktop before you log in.

Update environment variables

When you configure the service, it takes a snapshot of some useful environment variables for your current logon user such as PATH, LANG, JAVA_HOME, ANT_HOME, and MYSQL_PATH. If you need to update the variables (for example, after installing some new software):

The snapshot of the environment variables is stored in .env file under agent root directory, you can also change that file directly to apply environment variable changes.

Run instructions before the service starts

You can also run your own instructions and commands to run when the service starts. For example, you could set up the environment or call scripts.

Edit runsvc.sh.
Replace the following line with your instructions:

Service Files

When you install the service, some service files are put in place.

.plist service file

A .plist service file is created:

For example:

sudo ./svc.sh install generates this file from this template: ./bin/vsts.agent.plist.template

.service file

./svc.sh start finds the service by reading the .service file, which contains the path to the plist service file described above.

Alternative service mechanisms

We provide the ./svc.sh script as a convenient way for you to run and manage your agent as a launchd LaunchAgent service. But you can use whatever kind of service mechanism you prefer.

You can use the template described above as to facilitate generating other kinds of service files. For example, you modify the template to generate a service that runs as a launch daemon if you don't need UI tests and don't want to configure automatic log on and lock. See Apple Developer Library: Creating Launch Daemons and Agents.

Replace an agent

To replace an agent, follow the Download and configure the agent steps again.

When you configure an agent using the same name as an agent that already exists,you're asked if you want to replace the existing agent. If you answer Y,then make sure you remove the agent (see below) that you're replacing. Otherwise,after a few minutes of conflicts, one of the agents will shut down.

Remove and re-configure an agent

To remove the agent:

Stop and uninstall the service as explained above.
Remove the agent.
Enter your credentials.

After you've removed the agent, you can configure it again.

Unattended config

The agent can be set up from a script with no human intervention.You must pass --unattended and the answers to all questions.

To configure an agent, it must know the URL to your organization or collection and credentials of someone authorized to set up agents.All other responses are optional.Any command-line parameter can be specified using an environment variable instead:put its name in upper case and prepend VSTS_AGENT_INPUT_.For example, VSTS_AGENT_INPUT_PASSWORD instead of specifying --password.

Required options

--unattended - agent setup will not prompt for information, and all settings must be provided on the command line
--url <url> - URL of the server. For example: https://dev.azure.com/myorganization or http://my-azure-devops-server:8080/tfs
--auth <type> - authentication type. Valid values are:
- pat (Personal access token)
- negotiate (Kerberos or NTLM)
- alt (Basic authentication)
- integrated (Windows default credentials)

Authentication options

If you chose --auth pat:
- --token <token> - specifies your personal access token
If you chose --auth negotiate or --auth alt:
- --userName <userName> - specifies a Windows username in the format domainuserName or userName@domain.com
- --password <password> - specifies a password

Pool and agent names

--pool <pool> - pool name for the agent to join
--agent <agent> - agent name
--replace - replace the agent in a pool. If another agent is listening by the same name, it will start failing with a conflict

Agent setup

--work <workDirectory> - work directory where job data is stored. Defaults to _work under theroot of the agent directory. The work directory is owned by a givenagent and should not share between multiple agents.
--acceptTeeEula - accept the Team Explorer Everywhere End User License Agreement (macOS and Linux only)

Windows-only startup

--runAsService - configure the agent to run as a Windows service (requires administrator permission)
--runAsAutoLogon - configure auto-logon and run the agent on startup (requires administrator permission)
--windowsLogonAccount <account> - used with --runAsService or --runAsAutoLogon to specify the Windows username in the format domainuserName or userName@domain.com
--windowsLogonPassword <password> - used with --runAsService or --runAsAutoLogon to specify Windows logon password
--overwriteAutoLogon - used with --runAsAutoLogon to overwrite the existing auto logon on the machine
--noRestart - used with --runAsAutoLogon to stop the host from restarting after agent configuration completes

Deployment group only

--deploymentGroup - configure the agent as a deployment group agent
--deploymentGroupName <name> - used with --deploymentGroup to specify the deployment group for the agent to join
--projectName <name> - used with --deploymentGroup to set the project name
--addDeploymentGroupTags - used with --deploymentGroup to indicate that deployment group tags should be added
--deploymentGroupTags <tags> - used with --addDeploymentGroupTags to specify the comma separated list of tags forthe deployment group agent - for example 'web, db'

./config.sh --help always lists the latest required and optional responses.

Diagnostics

If you're having trouble with your self-hosted agent, you can try running diagnostics.After configuring the agent:

This will run through a diagnostic suite that may help you troubleshoot the problem.The diagnostics feature is available starting with agent version 2.165.0.

Help on other options

To learn about other options:

The help provides information on authentication alternatives and unattended configuration.

Capabilities

Your agent's capabilities are cataloged and advertised in the pool so that only the builds and releases it can handle are assigned to it. See Build and release agent capabilities.

In many cases, after you deploy an agent, you'll need to install software or utilities. Generally you should install on your agents whatever software and tools you use on your development machine.

For example, if your build includes the npm task, then the build won't run unless there's a build agent in the pool that has npm installed.

Important

After you install new software on an agent, you must restart the agent for the new capability to show up in the pool so that the build can run.

Q & A

How do I make sure I have the latest v2 agent version?

Navigate to the Agent pools tab:
1. Choose Azure DevOps, Organization settings.
2. Choose Agent pools.
1. Choose Azure DevOps, Collection settings.
2. Choose Agent pools.
1. Navigate to your project and choose Settings (gear icon) > Agent Queues.
2. Choose Manage pools.
1. Navigate to your project and choose Settings (gear icon) > Agent Queues.
2. Choose Manage pools.
1. Navigate to your project and choose Manage project (gear icon).
2. Choose Control panel.
3. Select Agent pools.
Click the pool that contains the agent.
Make sure the agent is enabled.
Navigate to the capabilities tab:
1. From the Agent pools tab, select the desired agent pool.
2. Select Agents and choose the desired agent.
3. Choose the Capabilities tab.
  Note
  Microsoft-hosted agents don't display system capabilities. For a list of software installed on Microsoft-hosted agents, see Use a Microsoft-hosted agent.
1. From the Agent pools tab, select the desired pool.
2. Select Agents and choose the desired agent.
3. Choose the Capabilities tab.
Select the desired agent, and choose the Capabilities tab.
Select the desired agent, and choose the Capabilities tab.
From the Agent pools tab, select the desired agent, and choose the Capabilities tab.
Look for the Agent.Version capability. You can check this value against the latest published agent version. See Azure Pipelines Agent and check the page for the highest version number listed.
Each agent automatically updates itself when it runs a task that requires a newer version of the agent. If you want to manually update some agents, right-click the pool, and select Update all agents.

Can I update my v2 agents that are part of an Azure DevOps Server pool?

Mac Os X 10.11 Download Free

Yes.Beginning with Azure DevOps Server 2019, you can configure your server to look for the agent package files on a local disk.This configuration will override the default version that came with the server at the time of its release.This scenario also applies when the server doesn't have access to the internet.

From a computer with Internet access, download the latest version of the agent package files (in .zip or .tar.gz form) from the Azure Pipelines Agent GitHub Releases page.
Transfer the downloaded package files to each Azure DevOps Server Application Tier by using a method of your choice (such as USB drive, Network transfer, and so on). Place the agent files under the %ProgramData%MicrosoftAzure DevOpsAgents folder.
You're all set! Your Azure DevOps Server will now use the local files whenever the agents are updated. Each agent automatically updates itself when it runs a task that requires a newer version of the agent. But if you want to manually update some agents, right-click the pool, and then choose Update all agents.

Where can I learn more about how the launchd service works?

I'm running a firewall and my code is in Azure Repos. What URLs does the agent need to communicate with?

If you're running an agent in a secure network behind a firewall, make sure the agent can initiate communication with the following URLs and IP addresses.

For organizations using the `*.visualstudio.com` domain:

For organizations using the `dev.azure.com` domain:

To ensure your organization works with any existing firewall or IP restrictions, ensure that dev.azure.com and *dev.azure.com are open and update your allow-listed IPs to include the following IP addresses, based on your IP version. If you're currently allow-listing the 13.107.6.183 and 13.107.9.183 IP addresses, leave them in place, as you don't need to remove them.

IPv4 ranges

13.107.6.0/24
13.107.9.0/24
13.107.42.0/24
13.107.43.0/24

IPv6 ranges

2620:1ec:4::/48
2620:1ec:a92::/48
2620:1ec:21::/48
2620:1ec:22::/48

How do I run the agent with self-signed certificate?

How do I run the agent behind a web proxy?

How do I restart the agent

If you are running the agent interactively, see the restart instructions in Run interactively. If you are running the agent as a service, follow the steps to Stop and then Start the agent.

How do I configure the agent to bypass a web proxy and connect to Azure Pipelines?

If you want the agent to bypass your proxy and connect to Azure Pipelines directly, then you should configure your web proxy to enable the agent to access the following URLs.

For organizations using the `*.visualstudio.com` domain:

For organizations using the `dev.azure.com` domain:

IPv4 ranges

13.107.6.0/24
13.107.9.0/24
13.107.42.0/24
13.107.43.0/24

IPv6 ranges

2620:1ec:4::/48
2620:1ec:a92::/48
2620:1ec:21::/48
2620:1ec:22::/48