ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/gvpe/doc/gvpe.conf.5.pod
(Generate patch)

Comparing gvpe/doc/gvpe.conf.5.pod (file contents):
Revision 1.9 by pcg, Mon Mar 14 17:40:01 2005 UTC vs.
Revision 1.10 by pcg, Thu Mar 17 22:24:31 2005 UTC

347 347
348The port to bind the DNS tunnel socket to. Must be C<53> on DNS tunnel servers. 348The port to bind the DNS tunnel socket to. Must be C<53> on DNS tunnel servers.
349 349
350=item enable-dns = yes|true|on | no|false|off 350=item enable-dns = yes|true|on | no|false|off
351 351
352See gvpe.protocol(7) for a description of the DNS transport
353protocol. Avoid this protocol if you can.
354
352Enable the DNS tunneling protocol on this node, either as server or as 355Enable the DNS tunneling protocol on this node, either as server or as
353client (only available when gvpe was compiled with C<--enable-dns>). 356client. Support for this transport protocol is only available when gvpe
357was compiled using the C<--enable-dns> option.
354 358
355B<WARNING:> Parsing and generating DNS packets is rather tricky. The code 359=item enable-icmp = yes|true|on | no|false|off
356almost certainly contains buffer overflows and other, likely exploitable,
357bugs. You have been warned.
358 360
359This is the worst choice of transport protocol with respect to overhead 361See gvpe.protocol(7) for a description of the ICMP transport protocol.
360(overhead can be 2-3 times higher than the transferred data), and probably 362
361the best choice when tunneling through firewalls. 363Enable the ICMP transport using icmp packets of type C<icmp-type> on this
364node.
362 365
363=item enable-rawip = yes|true|on | no|false|off 366=item enable-rawip = yes|true|on | no|false|off
364 367
368See gvpe.protocol(7) for a description of the RAW IP transport protocol.
369
365Enable the RAW IPv4 transport using the C<ip-proto> protocol 370Enable the RAW IPv4 transport using the C<ip-proto> protocol
366(default: C<no>). This is the best choice, since the minimum overhead per 371(default: C<no>).
367packet is only 38 bytes, as opposed to UDP's 58 (or TCP's 60+).
368 372
369=item enable-tcp = yes|true|on | no|false|off 373=item enable-tcp = yes|true|on | no|false|off
370 374
375See gvpe.protocol(7) for a description of the TCP transport protocol.
376
371Enable the TCPv4 transport using the C<tcp-port> port 377Enable the TCPv4 transport using the C<tcp-port> port
372(default: C<no>). Support for this horribly unsuitable protocol is only 378(default: C<no>). Support for this transport protocol is only available
373available when gvpe was compiled using the C<--enable-tcp> option. Never 379when gvpe was compiled using the C<--enable-tcp> option.
374use this transport unless you really must, it is very inefficient and
375resource-intensive compared to the other transports (except for DNS, which
376is worse).
377 380
378=item enable-udp = yes|true|on | no|false|off 381=item enable-udp = yes|true|on | no|false|off
382
383See gvpe.protocol(7) for a description of the UDP transport protocol.
379 384
380Enable the UDPv4 transport using the C<udp-port> port (default: C<no>, 385Enable the UDPv4 transport using the C<udp-port> port (default: C<no>,
381unless no other protocol is enabled for a node, in which case this 386unless no other protocol is enabled for a node, in which case this
382protocol is enabled automatically). This is a good general choice since 387protocol is enabled automatically).
383UDP tunnels well through many firewalls.
384 388
385NOTE: Please specify C<enable-udp = yes> if you want t use it even though 389NOTE: Please specify C<enable-udp = yes> if you want t use it even though
386it might get switched on automatically, as some future version might 390it might get switched on automatically, as some future version might
387default to another default protocol. 391default to another default protocol.
388 392

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines