updated docs
This commit is contained in:
@@ -23,7 +23,7 @@ Check out our [Integrations](integrations/) to learn how to integrate this into
|
|||||||
|
|
||||||
## How does it work?
|
## How does it work?
|
||||||
|
|
||||||
We've built a special background service that pairs the ZeroTier protocol with a user-space [Lightweight IP (lwIP) stack](http://savannah.nongnu.org/projects/lwip/) to create a new way for you to bring your applications onto your virtual network. For a more in-depth explanation of our technology take a look at our [SDK Primer](docs/zt_sdk.md)
|
We've built a special background service that pairs the ZeroTier protocol with a user-space [Lightweight IP (lwIP) stack](http://savannah.nongnu.org/projects/lwip/) to create a new way for you to bring your applications onto your virtual network. For a more in-depth explanation of our technology take a look at our [SDK Primer](docs/zt_sdk_primer.md)
|
||||||
|
|
||||||
## APIs
|
## APIs
|
||||||
|
|
||||||
@@ -34,7 +34,7 @@ We've built a special background service that pairs the ZeroTier protocol with a
|
|||||||
- Provides an integrated SOCKS5 server alongside the ZeroTier service to proxy connections from an application to resources on a ZeroTier network. For instance, a developer which has built an iOS app using the NSStreams API could add ZeroTier to their application and simply use the SOCKS5 support build into NSStreams to reach resources on their network. An Android developer could do the same using the SOCKS5 support provided in the `Socket` API.
|
- Provides an integrated SOCKS5 server alongside the ZeroTier service to proxy connections from an application to resources on a ZeroTier network. For instance, a developer which has built an iOS app using the NSStreams API could add ZeroTier to their application and simply use the SOCKS5 support build into NSStreams to reach resources on their network. An Android developer could do the same using the SOCKS5 support provided in the `Socket` API.
|
||||||
|
|
||||||
**Direct Call**
|
**Direct Call**
|
||||||
- Directly call the `zt_/zts_` API specified in [SDK.h](../src/SDK.h). For this to work, just use one of the provided headers that specify the interface for your system/architecture and then either dynamically-load our library into your app or compile it right in.
|
- Directly call the `zt_/zts_` API specified in [SDK.h](src/SDK.h). For this to work, just use one of the provided headers that specify the interface for your system/architecture and then either dynamically-load our library into your app or compile it right in.
|
||||||
|
|
||||||
**Changeling**
|
**Changeling**
|
||||||
- This method is still experimental but the idea is to link `libztkq.so` into your app. You call `start_changeling()`. This will set up a separate thread to monitor all files for the process using kqueue. When an event is detected which indicates something is attempting to connect out or something is accepting a connection, we'll perform a sort of "hot-swap" of that socket for a socket that has been administered by ZeroTier.
|
- This method is still experimental but the idea is to link `libztkq.so` into your app. You call `start_changeling()`. This will set up a separate thread to monitor all files for the process using kqueue. When an event is detected which indicates something is attempting to connect out or something is accepting a connection, we'll perform a sort of "hot-swap" of that socket for a socket that has been administered by ZeroTier.
|
||||||
@@ -71,12 +71,6 @@ At this point, simply run your application as you normally would. It will be aut
|
|||||||
If you'd like to know the IP address your service can be reached at on this particular virtual network, use the following:
|
If you'd like to know the IP address your service can be reached at on this particular virtual network, use the following:
|
||||||
`zerotier-cli -D/var/lib/zerotier-one/nc_XXXXXXXXXXXXXXXX listnetworks`
|
`zerotier-cli -D/var/lib/zerotier-one/nc_XXXXXXXXXXXXXXXX listnetworks`
|
||||||
|
|
||||||
|
|
||||||
## Tests
|
|
||||||
|
|
||||||
For info on testing the SDK, take a look at [docs/docker_linux_testing.md](docs/docker_linux_testing.md)
|
|
||||||
|
|
||||||
|
|
||||||
## Installing in a Docker container (or any other container engine)
|
## Installing in a Docker container (or any other container engine)
|
||||||
|
|
||||||
If it's not immediately obvious, installation into a Docker container is easy. Just install `zerotier-sdk-service`, `libztintercept.so`, and `liblwip.so` into the container at an appropriate locations. We suggest putting it all in `/var/lib/zerotier-one` since this is the default ZeroTier home and will eliminate the need to supply a path to any of ZeroTier's services or utilities. Then, in your Docker container entry point script launch the service with *-d* to run it in the background, set the appropriate environment variables as described above, and launch your container's main application.
|
If it's not immediately obvious, installation into a Docker container is easy. Just install `zerotier-sdk-service`, `libztintercept.so`, and `liblwip.so` into the container at an appropriate locations. We suggest putting it all in `/var/lib/zerotier-one` since this is the default ZeroTier home and will eliminate the need to supply a path to any of ZeroTier's services or utilities. Then, in your Docker container entry point script launch the service with *-d* to run it in the background, set the appropriate environment variables as described above, and launch your container's main application.
|
||||||
|
|||||||
@@ -23,9 +23,6 @@ Run application
|
|||||||
|
|
||||||
./myapp
|
./myapp
|
||||||
|
|
||||||
## Via Dynamic-linking at runtime with DYLD
|
|
||||||
|
|
||||||
|
|
||||||
## Via App Framework
|
## Via App Framework
|
||||||
|
|
||||||
***
|
***
|
||||||
|
|||||||
@@ -23,7 +23,7 @@ Check out our [Integrations](integrations/) to learn how to integrate this into
|
|||||||
|
|
||||||
## How does it work?
|
## How does it work?
|
||||||
|
|
||||||
We've built a special background service that pairs the ZeroTier protocol with a user-space [Lightweight IP (lwIP) stack](http://savannah.nongnu.org/projects/lwip/) to create a new way for you to bring your applications onto your virtual network. For a more in-depth explanation of our technology take a look at our [SDK Primer](docs/zt_sdk.md)
|
We've built a special background service that pairs the ZeroTier protocol with a user-space [Lightweight IP (lwIP) stack](http://savannah.nongnu.org/projects/lwip/) to create a new way for you to bring your applications onto your virtual network. For a more in-depth explanation of our technology take a look at our [SDK Primer](docs/zt_sdk_primer.md)
|
||||||
|
|
||||||
## APIs
|
## APIs
|
||||||
|
|
||||||
@@ -34,7 +34,7 @@ We've built a special background service that pairs the ZeroTier protocol with a
|
|||||||
- Provides an integrated SOCKS5 server alongside the ZeroTier service to proxy connections from an application to resources on a ZeroTier network. For instance, a developer which has built an iOS app using the NSStreams API could add ZeroTier to their application and simply use the SOCKS5 support build into NSStreams to reach resources on their network. An Android developer could do the same using the SOCKS5 support provided in the `Socket` API.
|
- Provides an integrated SOCKS5 server alongside the ZeroTier service to proxy connections from an application to resources on a ZeroTier network. For instance, a developer which has built an iOS app using the NSStreams API could add ZeroTier to their application and simply use the SOCKS5 support build into NSStreams to reach resources on their network. An Android developer could do the same using the SOCKS5 support provided in the `Socket` API.
|
||||||
|
|
||||||
**Direct Call**
|
**Direct Call**
|
||||||
- Directly call the `zt_/zts_` API specified in [SDK.h](../src/SDK.h). For this to work, just use one of the provided headers that specify the interface for your system/architecture and then either dynamically-load our library into your app or compile it right in.
|
- Directly call the `zt_/zts_` API specified in [SDK.h](src/SDK.h). For this to work, just use one of the provided headers that specify the interface for your system/architecture and then either dynamically-load our library into your app or compile it right in.
|
||||||
|
|
||||||
**Changeling**
|
**Changeling**
|
||||||
- This method is still experimental but the idea is to link `libztkq.so` into your app. You call `start_changeling()`. This will set up a separate thread to monitor all files for the process using kqueue. When an event is detected which indicates something is attempting to connect out or something is accepting a connection, we'll perform a sort of "hot-swap" of that socket for a socket that has been administered by ZeroTier.
|
- This method is still experimental but the idea is to link `libztkq.so` into your app. You call `start_changeling()`. This will set up a separate thread to monitor all files for the process using kqueue. When an event is detected which indicates something is attempting to connect out or something is accepting a connection, we'll perform a sort of "hot-swap" of that socket for a socket that has been administered by ZeroTier.
|
||||||
6
integrations/apple/README.md
Normal file
6
integrations/apple/README.md
Normal file
@@ -0,0 +1,6 @@
|
|||||||
|
ZeroTierSDK_Apple builds the following targets:
|
||||||
|
|
||||||
|
- iOS framework `make ios_app_framework`
|
||||||
|
- OSX framework `make osx_app_framework`
|
||||||
|
- iOS Unity3D bundle `make ios_unity3d_bundle`
|
||||||
|
- OSX Unity3D bundle `make osx_unity3d_bundle`
|
||||||
@@ -23,9 +23,6 @@ Run application
|
|||||||
|
|
||||||
./myapp
|
./myapp
|
||||||
|
|
||||||
## Via Dynamic-linking at runtime with DYLD
|
|
||||||
|
|
||||||
|
|
||||||
## Via App Framework
|
## Via App Framework
|
||||||
|
|
||||||
***
|
***
|
||||||
|
|||||||
@@ -71,12 +71,6 @@ At this point, simply run your application as you normally would. It will be aut
|
|||||||
If you'd like to know the IP address your service can be reached at on this particular virtual network, use the following:
|
If you'd like to know the IP address your service can be reached at on this particular virtual network, use the following:
|
||||||
`zerotier-cli -D/var/lib/zerotier-one/nc_XXXXXXXXXXXXXXXX listnetworks`
|
`zerotier-cli -D/var/lib/zerotier-one/nc_XXXXXXXXXXXXXXXX listnetworks`
|
||||||
|
|
||||||
|
|
||||||
## Tests
|
|
||||||
|
|
||||||
For info on testing the SDK, take a look at [docs/docker_linux_testing.md](docs/docker_linux_testing.md)
|
|
||||||
|
|
||||||
|
|
||||||
## Installing in a Docker container (or any other container engine)
|
## Installing in a Docker container (or any other container engine)
|
||||||
|
|
||||||
If it's not immediately obvious, installation into a Docker container is easy. Just install `zerotier-sdk-service`, `libztintercept.so`, and `liblwip.so` into the container at an appropriate locations. We suggest putting it all in `/var/lib/zerotier-one` since this is the default ZeroTier home and will eliminate the need to supply a path to any of ZeroTier's services or utilities. Then, in your Docker container entry point script launch the service with *-d* to run it in the background, set the appropriate environment variables as described above, and launch your container's main application.
|
If it's not immediately obvious, installation into a Docker container is easy. Just install `zerotier-sdk-service`, `libztintercept.so`, and `liblwip.so` into the container at an appropriate locations. We suggest putting it all in `/var/lib/zerotier-one` since this is the default ZeroTier home and will eliminate the need to supply a path to any of ZeroTier's services or utilities. Then, in your Docker container entry point script launch the service with *-d* to run it in the background, set the appropriate environment variables as described above, and launch your container's main application.
|
||||||
|
|||||||
Reference in New Issue
Block a user