Possibly stupid question. I cant push a default route to a windows client to force all my traffic on the zt network to egress to the internet through a cloud vps set up with snort. The snort box has zt installed and has joined the network. I believe I should be pushing the default route with the configuration below. I am stupefied as to why I get the crazy default route that looks more like a mangled mask than an ip address, on my remote windows client. Appreciate any help available, and I am not thin skinned about missing something obvious, so I don’t mind being called an idiot, but please elaborate on why.
Just disabled IPv6 on the underlying physical if of the windows machine and on the zt interface.
Also attempted to set a static ARP entry on the workstation through some powershell “Get-NetNeighbor”. Seems odd, I would have thought it would be something like “Set-NetNeighbor”, but the MS Forums are clearly saying “Get”. Rebooting windows
Actually tried New-NetNeighbor with power shell to set an statitc ARP entry, but it looks like the zerotier interface doesnt support a link layer address.
I’m really not sure what to tell you. It works fine over here
root@debian:~# ip route
default via 10.95.0.1 dev ens18
10.0.0.0/22 dev ztmjfajgf7 proto kernel scope link src 10.0.1.73
10.95.0.0/16 dev ens18 proto kernel scope link src 10.95.0.38
192.168.192.0/24 dev ztijaz7tkl proto kernel scope link src 192.168.192.73
root@debian:~# zerotier-cli set $networkID allowDefault=1
root@debian:~#ip route
0.0.0.0/1 via 10.0.0.1 dev ztmjfajgf7 proto static
default via 10.95.0.1 dev ens18
10.0.0.0/22 dev ztmjfajgf7 proto kernel scope link src 10.0.1.73
10.95.0.0/16 dev ens18 proto kernel scope link src 10.95.0.38
128.0.0.0/1 via 10.0.0.1 dev ztmjfajgf7 proto static
192.168.192.0/24 dev ztijaz7tkl proto kernel scope link src 192.168.192.73
Perhaps it’s because you’re setting your default route to 0.0.0.0/32??? Try 0.0.0.0/0 instead