NSTX is a protocol that utilizes DNS queries to establish IP tunnels. This enables the creation of secure and flexible networks through simple and efficient technology.
NSTX is an innovative protocol that allows for the creation of IP tunnels using DNS queries and replies for IP packet encapsulation. This feature is especially useful in scenarios when IP traffic other than DNS is not possible. To use NSTX, you need to have the ethertap-dev up and running on both sides of the tunnel. The setup process involves configuring a specific IP address (e.g., 192.168.0.1) on one ethertap and another IP address (e.g., 192.168.0.2) on the other side.
After setting up the ethertap, create a netroute for 192.168.0.0/24 via the ethertap on both sides. To ensure that both the client and server know that the ethertap-service is /dev/tap0, you need to specify this in the configuration.
To start the server, run the "./nstxd tun.yomama.com" command on one end, and on the other end, run "./nstxcd tun.yomama.com 125.23.53.12". The IP address 125.23.53.12 should be a DNS server reachable by the client-side.
It's crucial to note that the server must run where an NS-record for tun.yomama.com points to. This means that if the server has the IP 1.2.3.4, there should be an entry in the zonefile of yomama.com: tun IN NS 1.2.3.4
The latest release of NSTX includes several features, including extensive const-poisoning and removal of some of the unused functions. The update also includes a switch from `LINUX' to `linux' - a define provided by the compiler automatically on Linux. To enhance debugging, the update replaces printfs with syslog(3).
Further, the update includes "chroot-ing" into a specified directory and setuid-ing to a specified uid after initialization (for nstxd only, not nstxcd). The daemons should, probably, refuse to run as root after initializing.
In summary, NSTX provides a reliable and efficient way of creating tunnels for IP packet encapsulation where IP traffic other than DNS is not possible. With its recent update, NSTX is a powerful tool for those seeking to create secure and efficient IP tunnels.
After setting up the ethertap, create a netroute for 192.168.0.0/24 via the ethertap on both sides. To ensure that both the client and server know that the ethertap-service is /dev/tap0, you need to specify this in the configuration.
To start the server, run the "./nstxd tun.yomama.com" command on one end, and on the other end, run "./nstxcd tun.yomama.com 125.23.53.12". The IP address 125.23.53.12 should be a DNS server reachable by the client-side.
It's crucial to note that the server must run where an NS-record for tun.yomama.com points to. This means that if the server has the IP 1.2.3.4, there should be an entry in the zonefile of yomama.com: tun IN NS 1.2.3.4
The latest release of NSTX includes several features, including extensive const-poisoning and removal of some of the unused functions. The update also includes a switch from `LINUX' to `linux' - a define provided by the compiler automatically on Linux. To enhance debugging, the update replaces printfs with syslog(3).
Further, the update includes "chroot-ing" into a specified directory and setuid-ing to a specified uid after initialization (for nstxd only, not nstxcd). The daemons should, probably, refuse to run as root after initializing.
In summary, NSTX provides a reliable and efficient way of creating tunnels for IP packet encapsulation where IP traffic other than DNS is not possible. With its recent update, NSTX is a powerful tool for those seeking to create secure and efficient IP tunnels.
What's New
Version 1.1: N/A