ZeroTier + Active Directory Authentication
-
@Dashrender said:
https://www.zerotier.com/community/topic/5/bridging-ethernet-to-zerotier-virtual-networks-on-linux
Configure the DHCP Server in the Office LAN to give leases in the range 10.0.0.100-10.0.0.200.
Configure the ZeroTier portal to manage IP addresses in the range range 10.0.1.100-10.0.1.200. Note how the address ranges are in the same 10.0.0.0/16 subnet, but have a unique pool of IP addresses.The instructions have you create a giant subnet /16 the LAN will be on x.x.0.x and the ZT will be on x.x.1.x No routers involved for communication here.
I totally missed that bit before... I think I am going to try it out again.
-
@JaredBusch said:
@Dashrender said:
So if I'm reading this correctly, using bridging means that no ZT devices can ever be on the local network, except the one server providing the bridging, which it's doing through a disconnected NIC port that's acting like a switch port.
The typical ZT clients would need to never be on that same physical network.
There is no reason they cannot be on the same network.
I can have my laptop plugged in to the LAN and WiFi at the same time. they get two different addresses. This is no different with ZT. it is a separate adapter.Basic IP functions here, nothing complicated.
Good point - I've done that before too. Though It's my understanding that the default in Windows - when the LAN is connected, the WLAN is ignored.
-
@dafyre said:
@Dashrender said:
https://www.zerotier.com/community/topic/5/bridging-ethernet-to-zerotier-virtual-networks-on-linux
Configure the DHCP Server in the Office LAN to give leases in the range 10.0.0.100-10.0.0.200.
Configure the ZeroTier portal to manage IP addresses in the range range 10.0.1.100-10.0.1.200. Note how the address ranges are in the same 10.0.0.0/16 subnet, but have a unique pool of IP addresses.The instructions have you create a giant subnet /16 the LAN will be on x.x.0.x and the ZT will be on x.x.1.x No routers involved for communication here.
I totally missed that bit before... I think I am going to try it out again.
Well that might be why your Bridge didn't work
I don't really want a bridge - I want a ZT to LAN router. Then you could have all of your printers on your production network, all of your users on open/free network, and the ZT would still provide IP access to the printers and their real IPs.
The problem with this is putting a route into the local machine that ensures that traffic bound for that routed network goes through ZT, not the default gateway of the end point.
-
@Dashrender said:
@JaredBusch said:
@Dashrender said:
So if I'm reading this correctly, using bridging means that no ZT devices can ever be on the local network, except the one server providing the bridging, which it's doing through a disconnected NIC port that's acting like a switch port.
The typical ZT clients would need to never be on that same physical network.
There is no reason they cannot be on the same network.
I can have my laptop plugged in to the LAN and WiFi at the same time. they get two different addresses. This is no different with ZT. it is a separate adapter.Basic IP functions here, nothing complicated.
Good point - I've done that before too. Though It's my understanding that the default in Windows - when the LAN is connected, the WLAN is ignored.
Not even close to true. Windows does not care about it. You need to set that up in BIOS or have HP/Dell software running to do it automagically.
In Windows, you can set adapter order. But some things like Pertino reinstall the adapter when they update and that puts it back on the top of the list.
This is where you specify it in Windows.
-
@Dashrender said:
@dafyre said:
@Dashrender said:
https://www.zerotier.com/community/topic/5/bridging-ethernet-to-zerotier-virtual-networks-on-linux
Configure the DHCP Server in the Office LAN to give leases in the range 10.0.0.100-10.0.0.200.
Configure the ZeroTier portal to manage IP addresses in the range range 10.0.1.100-10.0.1.200. Note how the address ranges are in the same 10.0.0.0/16 subnet, but have a unique pool of IP addresses.The instructions have you create a giant subnet /16 the LAN will be on x.x.0.x and the ZT will be on x.x.1.x No routers involved for communication here.
I totally missed that bit before... I think I am going to try it out again.
Well that might be why your Bridge didn't work
I don't really want a bridge - I want a ZT to LAN router. Then you could have all of your printers on your production network, all of your users on open/free network, and the ZT would still provide IP access to the printers and their real IPs.
The problem with this is putting a route into the local machine that ensures that traffic bound for that routed network goes through ZT, not the default gateway of the end point.
I've built one of those... I'll do it again and document it this weekend.
-
@Dashrender That's not true. If a ZT device is on the same local network, then it will just have two ports that go to the same network. It would be like putting two NICs in the device and running two cables to the same switch. Confusing, but nothing "wrong" with that.
ZT emulates a smart Ethernet switch. Think of it the way you would think of a switch. An "active bridge" is a port set to permit bridging to another switch (some smart switches let you control that) while a regular ZeroTier endpoint is a port that only goes to a single device.
If you're thinking of it any differently you're over-thinking it. Pertino adds a whole ton of complexity by operating at L3 and none of that applies here. VPNs also add a lot of complexity by fragmenting the network with tunnels and such, and that's also irrelevant. Just imagine a switch with invisible wires going to it.
-
@adam.ierymenko said:
@Dashrender That's not true. If a ZT device is on the same local network, then it will just have two ports that go to the same network. It would be like putting two NICs in the device and running two cables to the same switch. Confusing, but nothing "wrong" with that.
ZT emulates a smart Ethernet switch. Think of it the way you would think of a switch. An "active bridge" is a port set to permit bridging to another switch (some smart switches let you control that) while a regular ZeroTier endpoint is a port that only goes to a single device.
If you're thinking of it any differently you're over-thinking it. Pertino adds a whole ton of complexity by operating at L3 and none of that applies here. VPNs also add a lot of complexity by fragmenting the network with tunnels and such, and that's also irrelevant. Just imagine a switch with invisible wires going to it.
If that were the case, then bridging would be much easier.
(see my latest post on your site.) -
@dafyre I'll take a look, but in my experience bridging is always confusing to set up when you have any boundary between how things like IPs are allocated. One of the things on our to-do list is to ship a preconfigured Raspberry Pi config or image that does bridging easily.
-
@adam.ierymenko said:
@dafyre I'll take a look, but in my experience bridging is always confusing to set up when you have any boundary between how things like IPs are allocated. One of the things on our to-do list is to ship a preconfigured Raspberry Pi config or image that does bridging easily.
If you guys decide to do a straight up Linux image, I'll be happy to help test it. I don't have a Pi to test with at the moment.
-
@dafyre In the shorter term a more detailed HOWTO would probably be best. We can gear it to Debian since the Pi is Debian and makes a great bridge device, but you could also use a Debian VM or regular machine.
-
@adam.ierymenko said:
@dafyre In the shorter term a more detailed HOWTO would probably be best. We can gear it to Debian since the Pi is Debian and makes a great bridge device, but you could also use a Debian VM or regular machine.
I'd be happy to help test them as you write them.
-
@adam.ierymenko said:
@Dashrender That's not true. If a ZT device is on the same local network, then it will just have two ports that go to the same network. It would be like putting two NICs in the device and running two cables to the same switch. Confusing, but nothing "wrong" with that.
ZT emulates a smart Ethernet switch. Think of it the way you would think of a switch. An "active bridge" is a port set to permit bridging to another switch (some smart switches let you control that) while a regular ZeroTier endpoint is a port that only goes to a single device.
If you're thinking of it any differently you're over-thinking it. Pertino adds a whole ton of complexity by operating at L3 and none of that applies here. VPNs also add a lot of complexity by fragmenting the network with tunnels and such, and that's also irrelevant. Just imagine a switch with invisible wires going to it.
Yeah - I was over thinking that. JB set me straight already.
-
Okay, so I took a pot shot at @adam-ierymenko and told him Bridging should be easier... It turns out it is, lol. I blame Microsoft!
Hyper-V has some security features that prevent the system from communicating on the network using a Mac Address that wasn't assigned to it via Hyper-V... There's a fix for that!
In PowerShell, on the Hyper-V host, run the following (it should be typed all on one line... I broke it up for readability)...
*note: This enables the Mac spoofing on ALL NICS attached to the VM.get-vmnetworkadapter -VMName MYVMNAME|where {$_.SwitchName -eq "MY_HYPERV_SWITCH"}| set-vmnetworkadapter -MacAddressSpoofing onEdit: In VMware, you will need to enable Forged Transmits and Promiscuous Mode on the VM that you run things like this on. I don't have access to a VMware system to chek this.
-
@adam.ierymenko I have a Pi (the newest one) to test on if you need more testers
-
Back on the topic of this thread...
I setup ZeroTier on FSLDC02. I put ZeroTier on LT-JARED-01
ZeroTier is IPv6 only at the moment.
I put the IPv6 address of the DC in the laptops's IPv6 config
I rebooted the laptop and then logged in with a domain user that has never been logged onto the device before. Everything worked fine.
AD Authenticaiton works great.
It also works great with IPv4 if you put the ZeroTier IPv4 address in the DNS of the IPv4 adapter.
So AD over ZeroTier is easy to do.
-
The problem I want to resolve now is how to not get DNS for everything.
With ZeroTier connected, if I try and connect to my ownCloud instance, I get the internal DNS back. This is not desired behavior. If I shut of ZeroTier, I properly get the external IP address.
This is my problem. I need/want DNS to only work for AD Auth. I want ownCloud to use the public IP. That is why Pertino and ZeroTier are causing problems for me.
-
@dafyre came up with a solution for this, a manually configured DNS server on ZT. you put in the AD resources you need so you can authenticate, and forward the rest out to an internet based DNS server.
Though, if you have a split horizon DNS, you'll have to specify the IP for ownCloud to the external IP.
-
Did you check your AD DNS, did it have copies of the ZT addresses in it?
-
@Dashrender said:
@dafyre came up with a solution for this, a manually configured DNS server on ZT. you put in the AD resources you need so you can authenticate, and forward the rest out to an internet based DNS server.
Though, if you have a split horizon DNS, you'll have to specify the IP for ownCloud to the external IP.
No, @dafyre came up with a mess based on a work around. Every single thing in his process was extra work to setup, which is not bad. But it was all extra maintenance also, which is horrible.
If you are trying to sell me SDN, then you need to sell me SDN that fulfills the task I need. yes, Pertino and ZeroTier may not be right for this scenario, but then I know of no other solution for this either. That is the point of working on this.
-
@Dashrender said:
Did you check your AD DNS, did it have copies of the ZT addresses in it?
At what point have I stated anyplace that I have ZeroTier on more than 2 devices? I do not. It exists solely on the DC and the test laptop.
