vndb/yhdev
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

ncdc 1.15 released

Browse source
This commit is contained in:
Yorhel 2013-03-02 14:49:06 +01:00
parent 94ae88d4b9
commit c99ea0d9fc
10 changed files with 83 additions and 74 deletions
Download patch file Download diff file Expand all files Collapse all files

33
dat/ncdc-man
View file

@ -113,13 +113,11 @@ automatically, but in the event that this fails, you can also set it yourself:
/set active_ip 13.33.33.7
If you are behind a NAT or firewall, you have to ensure that the port you
configured is somehow allowed and/or forwarded. You have a lot of freedom in
configuring ports within ncdc: The C<active_udp_port> setting is used for
incoming UDP messages, the C<active_tls_port> setting is used for incoming
encrypted TCP connections, and the C<active_port> setting is used as a default
for the other two and for all incoming and unencrypted connections. Unlike
other currently available Direct Connect clients, ncdc allows the TLS and TCP
port to be the same, which tends to ease NAT configuration.
configured is somehow allowed and/or forwarded. The C<active_port> setting is
used for incoming TCP connections and UDP messages. You can configure a
different UDP port with the C<active_udp_port> setting. Contrary to many toher
Direct Connect clients, ncdc only uses a single port for incoming TCP and TLS
connections; There is no separate port for TLS.
The C</listen> command can tell you which ports it expects to be forwarded, and
for which hubs these ports will be used. It only lists hubs on which you are
@ -374,15 +372,13 @@ Enables or disables active mode. You may have to configure your router and/or fi
=item B<active_ip> <string>
Your public IP address for use in active mode. If this is not set, ncdc will try to automatically get your IP address from the hub. If you do set this manually, it is important that other clients can reach you using this IP address. If you connect to a hub on the internet, this should be your internet (WAN) IP. Likewise, if you connect to a hub on your LAN, this should be your LAN IP.
Your public IP address for use in active mode. If this is not set or set to '0.0.0.0' for IPv4 or '::' for IPv6, then ncdc will try to automatically get your IP address from the hub. If you do set this manually, it is important that other clients can reach you using this IP address. If you connect to a hub on the internet, this should be your internet (WAN) IP. Likewise, if you connect to a hub on your LAN, this should be your LAN IP.
Both an IPv4 and an IPv6 address are set by providing two IP addresses separated with a comma. When unset, '0.0.0.0,::' is assumed. Only the IP version used to connect to the hub is used. That is, if you connect to an IPv6 hub, then the configured IPv6 address is used and the IPv4 address is ignored.
=item B<active_port> <integer>
The listen port for incoming connections in active mode. Set to `0' to automatically assign a random port. This setting is by default also used for the UDP and TLS ports, see the `active_udp_port' and `active_tls_port' settings to change those. If you are behind a router or firewall, make sure that you have configured it to forward and allow these ports.
=item B<active_tls_port> <integer>
The listen port for incoming TLS connections in active mode. Incoming TLS connections by default use the same port as non-TLS connections, but when traffic shaping is in effect it may be beneficial to separate these ports. This setting has no effect when the `tls_policy' setting has been disabled.
The listen port for incoming connections in active mode. Set to `0' to automatically assign a random port. This setting is by default also used for the UDP port, see the `active_tls_port' settings to change that. If you are behind a router or firewall, make sure that you have configured it to forward and allow these ports.
=item B<active_udp_port> <integer>
@ -423,6 +419,7 @@ The settings starting with the `color_' prefix allow you to change the interface
log_join - color of join messages
log_quit - color of quit messages
separator - the list separator/footer bar
tab_active - the active tab in the tab list
tabprio_low - low priority tab notification color
tabprio_med - medium priority tab notification color
tabprio_high - high priority tab notification color
@ -502,7 +499,9 @@ The directory where incomplete downloads are stored. This setting can only be ch
=item B<local_address> <string>
Specifies the address of the local network interface to use for connecting to the outside and for accepting incoming connections in active mode. When unset, ncdc will use the default gateway interface to connect to the outside world, and will bind to all interfaces (address 0.0.0.0) for incoming connections in active mode.
Specifies the address of the local network interface to use for connecting to the outside and for accepting incoming connections in active mode. Both an IPv4 and an IPv6 address are set by providing two IP addresses separated with a comma. When unset, '0.0.0.0,::' is assumed.
If no IPv4 address is specified, '0.0.0.0' is added automatically. Similarly, if no IPv6 address is specified, '::' is added automatically. The address that is actually used depends on the IP version actually used. That is, if you're on an IPv6 hub, then ncdc will listen on the specified IPv6 address. Note that, even if the hub you're on is on IPv6, ncdc may still try to connect to another client over IPv4, at which point the socket will be bound to the configured IPv4 address.
=item B<log_debug> <boolean>
@ -818,7 +817,7 @@ directory at the same time.
=head1 LICENSE
Copyright (C) 2011-2012 Yoran Heling <projects@yorhel.nl>
Copyright (C) 2011-2013 Yoran Heling <projects@yorhel.nl>
ncdc is distributed under the MIT license, please read the COPYING file for
more information.
@ -833,7 +832,3 @@ development hub at adc://dc.blicky.net:2780/.
ncdc is written by Yoran Heling <projects@yorhel.nl>
Web: L<http://dev.yorhel.nl/ncdc>
=head1 SEE ALSO
L<ncdc-db-upgrade(1)>.