Skip to content

Commit 50d3339

Browse files
committed
fix(apple): add config details
1 parent 8516597 commit 50d3339

File tree

5 files changed

+61
-1
lines changed

5 files changed

+61
-1
lines changed
101 KB
Loading
80.1 KB
Loading
2.39 KB
Loading

bare-metal/apple-silicon/how-to/use-private-networks.mdx

Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,65 @@ Private Networks are disabled, and you are returned to your Mac mini's **Overvie
6464

6565
The Mac mini is attached to the Private Network, and you are returned to the **Private Networks** tab. The IPv4 and the IPv6 addresses for the Mac mini on the Private Network are displayed, along with the ID of the VLAN interface that was created.
6666

67+
Once you have attached the resource, some manual configuration of the network interface is required. See the next section for full details.
68+
69+
## How to configure the VLAN interface on your Mac mini for Private Networks
70+
71+
You must configure the virtual network interface on each Mac mini you have attached to a Private Network. Traffic from the public internet and traffic from a Private Network will pass through the same network interface of the Mac mini. We must therefore separate the traffic by adding a VLAN interface.
72+
73+
To configure the interface, you must connect to your Mac mini, either via SSH or the remote desktop and carry out the instructions given.
74+
75+
### Via SSH and networksetup
76+
77+
1. Make a note of your Mac mini's **VLAN ID**. You can view this in the Scaleway console, in the **Private Networks** tab of the Mac mini in question.
78+
2. [Connect to your Mac mini via SSH](/bare-metal/apple-silicon/how-to/connect-to-mac-mini-ssh/).
79+
3. Use the following command to bring up the interface. Ensure you replace `<VLAN_ID>` with the VLAN_ID from step one.
80+
```
81+
sudo networksetup -createVLAN pn en0 <VLAN_ID>
82+
```
83+
4. Check that the interface has been brought up with the following command:
84+
```
85+
sudo networksetup -listVLANs
86+
```
87+
You should see a response similar to the following:
88+
```
89+
VLAN User Defined Name: pn
90+
Parent Device: en0
91+
Device ("Hardware" Port): vlan0
92+
Tag: 3548
93+
```
94+
95+
No configuration is required for your Mac mini's IP address on the Private Network, as this is automatically managed by Scaleway DHCP. You can view the IP address in the Scaleway console, in the Mac mini's **Private Networks** tab.
96+
97+
<Message type="tip">
98+
If you have any issues with bringing up the VLAN interface or the IP address, the following commands may be helpful.
99+
100+
To delete the VLAN, so you can attempt re-creation;
101+
```
102+
sudo networksetup -deleteVLAN pn en0 <VLAN_ID>
103+
```
104+
To renew the DHCP lease:
105+
```
106+
sudo ipconfig set en0 BOOTP && sudo ipconfig set en0 DHCP
107+
```
108+
</Message>
109+
110+
### Via remote desktop
111+
112+
1. Make a note of your Mac mini's **VLAN ID**. You can view this in the Scaleway console, in the **Private Networks** tab of the Mac mini in question.
113+
2. [Access the Mac mini's remote desktop](/bare-metal/apple-silicon/how-to/access-remote-desktop-mac-mini/).
114+
3. Go to **System Settings** > **Network**, then click **...v** and select **Manage Virtual Interfaces** from the menu that displays.
115+
<Lightbox src="scaleway-m1-network.webp" />
116+
4. Click **+** > **New VLAN** to add a new virtual interface.
117+
<Lightbox src="scaleway-m1-vlan.webp" />
118+
5. Enter a **VLAN name** of your choice, the VLAN ID from step 1 in the **Tag** field, and **Ethernet** as the interface. Click **Done**.
119+
120+
The VLAN interface is created. You can check its status in the **Network** tab, and see its full details by clicking on it.
121+
122+
<Lightbox src="scaleway-m1-vlan-details.webp" />
123+
124+
No configuration is required for your Mac mini's IP address on the Private Network, as this is automatically managed by Scaleway DHCP.
125+
67126
## How to detach a Mac mini from a Private Network
68127

69128
1. Click **Apple silicon** in the **Bare Metal** section of the side menu. The Apple silicon splash page displays.

network/vpc/how-to/attach-resources-to-pn.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,6 +85,8 @@ You can also attach a resource to a Private Network from the resource's own sect
8585
Note that for Kubernetes Kapsules and Managed Databases for Redis™, you can only attach the resource to a Private Network at the time of creating the resource itself.
8686
</Message>
8787

88+
For Elastic Metal servers and Apple silicon Mac minis, manual configuration of the network interface is required. This is not required for Instances or other types of resources. See the relevant documentation for [Elastic Metal](/bare-metal/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks) or [Apple silicon](/bare-metal/apple-silicon/how-to/use-private-networks/) for full instructions.
89+
8890
## How to view the resource's IP address
8991

9092
When you attach a resource to a Private Network, it gets a private IPv4 address on that network (and also an IPv6 address, if supported by the resource). Private IPs are assigned from the CIDR block defined at the time of the Private Network's creation, either via auto-assignment or specification of a particular [reserved IP](/network/ipam/how-to/reserve-ip/).
@@ -111,7 +113,6 @@ We strongly recommend that you [activate DHCP on the Private Network](/network/v
111113

112114
If you do not see an IP address in the screens above for your resource, and you think you should, check out our [troubleshooting](/network/vpc/troubleshooting/resource-attached-no-ip/) guide. <br /> <br />
113115

114-
Note that in any case, for Elastic Metal servers, some [manual configuration is required](/bare-metal/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks) even after activating DHCP. This is not required for Instances or other types of resources.
115116
</Message>
116117

117118
## How to access a resource on a Private Network via its hostname (DNS)

0 commit comments

Comments
 (0)