@@ -15,11 +15,29 @@ Building and installing from source:
15
15
16
16
Consult ` man kirc ` for a full list and explanation of available arguments.
17
17
18
- kirc [-s hostname] [-p port] [-c channels] [-n nickname] [-r realname]
19
- [-u username] [-k password] [-a token] [-o logfile] [-e|x|v|V]
18
+ kirc [-s hostname] [-p port] [-c channels] [-n nickname] [-r realname] [-a auth]
19
+ [-u username] [-k password] [-a token] [-o logfile] [-D directory] [-4|6|d| e|x|v|V]
20
20
21
21
## DCC
22
- DCC transfers are always accpeted without user interaction and downloaded to the current directory.
22
+ DCC transfers are only accepted if the -d flag is passed to kirc.
23
+ If -d is passed to kirc, DCC transfers are always accpeted without user interaction
24
+ and downloaded to the configured directory.
25
+ If no directory is set with the -D option, files are downloaded to the current directory.
26
+
27
+ ## DCC SEND
28
+ DCC SEND is only enabled if the -d flag is passed to kirc.
29
+ You can send files via DCC SEND using the folowing command:
30
+ /dcc <target nick> <path to file> <internal ip> <external ip> <port>
31
+ If you are sending files to clients outside of your lan, you must
32
+ make sure that the chosen port is open and forwarded to
33
+ the sending machine's internal address.
34
+ Thus is usually done from your router's settings.
35
+ For example:
36
+ /dcc dcc_client /home/user/upload/file.txt 192.168.1.100 12.34.56.78 10000
37
+ This command would send the file located at /home/user/upload/file.txt to the nick
38
+ dcc_client, assuming the sending machine's local ip is 192.168.1.100, and
39
+ the sending machine's external ip is 12.34.56.78, and that the port 10000
40
+ is open and forwarded to the sending machine's local address.
23
41
24
42
## Command Aliases
25
43
0 commit comments