TheArchive/iodine
1
0
Fork 0
mirror of https://github.com/yarrick/iodine.git synced 2025-12-07 04:41:44 +00:00
Code Issues Packages Projects Releases Wiki Activity

Forward non-tunnel requests to another udp port (fixes #31)

Browse Source
This commit is contained in:
Erik Ekman
2008-08-07 21:18:15 +00:00
committed by Erik Ekman
parent ec2d6657a0
commit 02d40c1a7b
9 changed files with 244 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
man/iodine.8
View File

@@ -157,10 +157,11 @@ To actually use it through a relaying nameserver, see below.
.TP
.B Server side:
To use this tunnel, you need control over a real domain (like mytunnel.com),
and a server with a static public IP number that does not yet run a DNS
server. Then, delegate a subdomain (say, tunnel1.mytunnel.com) to the server.
If you use BIND for the domain, add these lines to the zone file (replace
10.15.213.99 with your server ip):
and a server with a public IP number. If the server already runs a DNS
server, change the listening port and then use the \-b option to let
iodined forward the DNS requests. Then, delegate a subdomain
(say, tunnel1.mytunnel.com) to the server. If you use BIND for the domain,
add these lines to the zone file (replace 10.15.213.99 with your server ip):
.nf
tunnel1host IN A 10.15.213.99