macos26 beta2 when zerotier worker network connected , internet will lose . disconnect zerotier network, internet. come back. no solve ,even uninstall zerotier and reinstall zerotier 1.14.2
macos26 beta2 when zerotier worker network connected , internet will lose . disconnect zerotier network, internet. come back. no solve ,even uninstall zerotier and reinstall zerotier 1.14.2
System Version: 26.0 Beta (25A5306g) When Allow Managed Addresses is turned on, the computer will not be able to connect to the public network, but zerotier’s LAN can be accessed, if this option is turned off, the public network can be accessed, but zerotier’s LAN cannot be accessed. After many attempts I realized that it was the routing part that was wrong.
Here is the routing table with Allow Managed Addresses turned on.You can see that the LAN is assigned the UGScIg flag.
Routing tables
Internet:
Destination Gateway Flags Netif Expire
default 127.0.0.1 UGScg lo0
default 192.168.77.1 UGScIg en0
127 127.0.0.1 UCS lo0
127.0.0.1 127.0.0.1 UHr lo0
169.254 link#11 UCS en0 !
192.168.77 link#11 UCS en0 !
192.168.77.1/32 link#11 UCS en0 !
192.168.77.1 cc:96:a2:47:78:61 UHLWIir en0 1195
192.168.77.5 62:e1:f:ff:39:8b UHLWI en0 658
192.168.77.9 14:ea:63:7f:ea:d9 UHLWIi en0 1180
192.168.77.13 8a:7d:d5:3f:ec:51 UHLWI en0 1086
192.168.77.15/32 link#11 UCS en0 !
192.168.77.15 2a:53:a5:10:61:13 UHLWI lo0
192.168.77.18 6e:91:9e:20:f2:af UHLWI en0 1148
192.168.77.19 56:47:cb:a8:60:9b UHLWI en0 1011
192.168.77.255 ff:ff:ff:ff:ff:ff UHLWbI en0 !
192.168.192 link#25 UC feth1136 !
224.0.0/4 link#11 UmCSI en0 !
224.0.0.251 1:0:5e:0:0:fb UHmLWI en0
255.255.255.255/32 link#11 UCSI en0 !
When I turn off Allow Managed Addresses, the route goes back to normal.
Routing tables
Internet:
Destination Gateway Flags Netif Expire
default 192.168.77.1 UGScg en0
127 127.0.0.1 UCS lo0
127.0.0.1 127.0.0.1 UHr lo0
169.254 link#11 UCS en0 !
192.168.77 link#11 UCS en0 !
192.168.77.1/32 link#11 UCS en0 !
192.168.77.1 cc:96:a2:47:78:61 UHLWIir en0 1168
192.168.77.5 62:e1:f:ff:39:8b UHLWI en0 664
192.168.77.9 14:ea:63:7f:ea:d9 UHLWI en0 1186
192.168.77.13 8a:7d:d5:3f:ec:51 UHLWIi en0 1092
192.168.77.15/32 link#11 UCS en0 !
192.168.77.15 2a:53:a5:10:61:13 UHLWI lo0
192.168.77.18 6e:91:9e:20:f2:af UHLWI en0 1154
192.168.77.19 56:47:cb:a8:60:9b UHLWI en0 1017
192.168.77.255 ff:ff:ff:ff:ff:ff UHLWbI en0 !
224.0.0/4 link#11 UmCS en0 !
224.0.0.251 1:0:5e:0:0:fb UHmLWI en0
239.255.255.250 1:0:5e:7f:ff:fa UHmLWI en0
255.255.255.255/32 link#11 UCS en0 !
I’m not sure if it’s a zerotier issue or a macos beta issue, but this one has been bugging me for a while.
What routes are defined on your network? Post the routes section of zerotier-cli listnetworks -j
What routes are defined on your network? Post the
routessection ofzerotier-cli listnetworks -j您的网络上定义了哪些路由?发布zerotier-cli listnetworks -j的routes部分
just 192.168.7.0/24 and 192.168.192.199/24.
$ zerotier-cli listnetworks -j 130 ↵ ✭main
[
{
"allowDNS": false,
"allowDefault": true,
"allowGlobal": false,
"allowManaged": false,
"assignedAddresses": [
"192.168.192.199/24"
],
"bridge": false,
"broadcastEnabled": true,
"dhcp": false,
"dns": {
"domain": "",
"servers": []
},
"id": "***",
"mac": "0a:c0:5b:07:21:13",
"mtu": 2800,
"multicastSubscriptions": [
{
"adi": 0,
"mac": "01:00:5e:00:00:fb"
}
],
"name": "My-Zerotier",
"netconfRevision": 10,
"nwid": "***",
"portDeviceName": "feth1136",
"portError": 0,
"routes": [
{
"flags": 0,
"metric": 0,
"target": "192.168.192.0/24",
"via": null
},
{
"flags": 0,
"metric": 0,
"target": "192.168.7.0/24",
"via": "192.168.192.1"
}
],
"status": "OK",
"type": "PRIVATE"
}
]
Here's a video of what happened. https://github.com/user-attachments/assets/bf5a93c8-4c5f-4b0c-87fa-b66bbd8ed8f8
thank you we will try to reproduce
The same problem can be reproduced on MacBookPro 2021 and Mac mini 2024.
I encountered the same issue. A temporary workaround is:
1. Disable Allow Managed Addresses.
2. Run: sudo ifconfig feth4133 inet {your_assigned_ip} netmask 255.255.255.0
Replace feth4133 with your own portDeviceName.
Note: this change will not persist after reboot.
I encountered the same issue. A temporary workaround is: 1. Disable Allow Managed Addresses. 2. Run:
sudo ifconfig feth4133 inet {your_assigned_ip} netmask 255.255.255.0Replace feth4133 with your own portDeviceName.
Note: this change will not persist after reboot.
👍 This indeed can temporarily solve this problem.
https://github.com/zerotier/ZeroTierOne/issues/2520 these must be the same issue.
one sign is that this command outputs an empty
scutil --proxy
<dictionary> {
}
the normal one:
dictionary> {
ExceptionsList : <array> {
0 : 127.0.0.1
1 : 192.168.0.0/16
2 : 10.0.0.0/8
3 : 172.16.0.0/12
4 : 172.29.0.0/16
5 : localhost
6 : *.local
7 : *.crashlytics.com
8 : <local>
}
FTPPassive : 1
HTTPEnable : 0
HTTPSEnable : 0
ProxyAutoConfigEnable : 0
SOCKSEnable : 0
}