Synchronet v3.19b-Win32 (install) has been released (Jan-2022).

You can donate to the Synchronet project using PayPal.

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
service:ircd [2018/12/20 17:03] – [Installation] code tags around conf lines for readability wkitty42service:ircd [2020/11/13 21:25] – [Using JSexec to run the IRCd] with systemd mlong
Line 81: Line 81:
 (3) Edit your ircd.conf and include a C/N line pair for connecting to 'vert.synchro.net'.  These should be commented out in the stock ircd.conf, and will look like this: (3) Edit your ircd.conf and include a C/N line pair for connecting to 'vert.synchro.net'.  These should be commented out in the stock ircd.conf, and will look like this:
  
 +<code>
 #C:vert.synchro.net:QWK_PASSWORD:*.synchro.net:6667:30 #C:vert.synchro.net:QWK_PASSWORD:*.synchro.net:6667:30
 #N:vert.synchro.net:*:*.synchro.net::30 #N:vert.synchro.net:*:*.synchro.net::30
 +</code>
  
 Remove the '#' from each line, and replace 'QWK_PASSWORD' with the password you were assigned (or selected) when registering for a QWK-ID.  The ircd.conf contains a description of what each of the lines (and fields) mean. It is very important that you leave the asterisks as they are, especially on the N:Line.  This is because the server you're connecting to may be randomly Remove the '#' from each line, and replace 'QWK_PASSWORD' with the password you were assigned (or selected) when registering for a QWK-ID.  The ircd.conf contains a description of what each of the lines (and fields) mean. It is very important that you leave the asterisks as they are, especially on the N:Line.  This is because the server you're connecting to may be randomly
Line 89: Line 91:
 (4) Restart your BBS (or, if you know how to become an IRC operator, simply use the /REHASH command), and you should see a message similar to the following in your Synchronet console: (4) Restart your BBS (or, if you know how to become an IRC operator, simply use the /REHASH command), and you should see a message similar to the following in your Synchronet console:
  
 +<code>
 srvc 0008 IRC Routing: Auto-connecting to rrx.synchro.net srvc 0008 IRC Routing: Auto-connecting to rrx.synchro.net
 srvc 0008 IRC Routing: Connected!  Sending info... srvc 0008 IRC Routing: Connected!  Sending info...
 srvc 0008 IRC 0018 Accepted new connection: 154.5.119.21 port 6667 srvc 0008 IRC 0018 Accepted new connection: 154.5.119.21 port 6667
 srvc 0008 IRC Routing: Link with rrx.synchro.net established, states: TS srvc 0008 IRC Routing: Link with rrx.synchro.net established, states: TS
 +</code>
  
 If you see any messages in regards to "Server not configured" or "Connection reset by peer", it's highly likely that you've mistyped your QWK password into the C:Line in your ircd.conf.  Double-check to make sure that the password is correct, and that you haven't otherwise malformed the C/N line pair.  In particular, make sure all the asterisks (as per the default) are where they should be. If you see any messages in regards to "Server not configured" or "Connection reset by peer", it's highly likely that you've mistyped your QWK password into the C:Line in your ircd.conf.  Double-check to make sure that the password is correct, and that you haven't otherwise malformed the C/N line pair.  In particular, make sure all the asterisks (as per the default) are where they should be.
Line 110: Line 114:
 The above command is typed from within the Synchronet 'exec' directory. All console commands and errors are logged to the terminal that JSexec was started from.  You should see the standard IRCd startup messages, which means that the IRCd is now operational through JSexec.  Connecting to the IRCd should now work as per normal. The above command is typed from within the Synchronet 'exec' directory. All console commands and errors are logged to the terminal that JSexec was started from.  You should see the standard IRCd startup messages, which means that the IRCd is now operational through JSexec.  Connecting to the IRCd should now work as per normal.
  
 +====== Using JSexec with systemd ======
 +
 +Create a file /etc/systemd/system/ircd.service containing:
 +<code>
 +[Unit]
 +  Description=Synchronet BBS IRCD
 +  After=syslog.target network.target
 +
 +[Service]
 +  Type=simple
 +  Environment=SBBSROOT=/sbbs SBBSCTRL=/sbbs/ctrl SBBSEXEC=/sbbs/exec/
 +  User=sbbs
 +  Group=sbbs
 +  StandardOutput=file:/sbbs/data/logs/ircd.log
 +  StandardError=file:/sbbs/data/logs/ircd.err
 +  ExecStart=/sbbs/exec/jsexec -A -S -l /sbbs/exec/ircd.js
 +
 +[Install]
 +  WantedBy=default.target
 +</code>
 +
 +Then run:
 +systemctl enable ircd
 +systemctl daemon-reload
 +systemctl start ircd
 ====== About the Synchronet IRC Network (irc.synchro.net) ====== ====== About the Synchronet IRC Network (irc.synchro.net) ======
  
Line 240: Line 269:
     would execute the command like this: '/OPER Sysop <syspass>'.     would execute the command like this: '/OPER Sysop <syspass>'.
     Also check out the O:Line section in ircd.conf.     Also check out the O:Line section in ircd.conf.
 +
 + Q: My ipv6 O:Line isn't working even if I surround the address with
 +    square brackets.
 +        
 + A: You need to enclose the whole netmask within the square brackets. Do
 +    include leading zeros in the netmask. It should match your /whois netmask.
 +    For example:
 +    [~jsmith@2001:440:1fff:b0:99d2:3cde:43e7:c96]
  
  Q: I've been forced off of the server with a "Terminated." message.  Q: I've been forced off of the server with a "Terminated." message.
Line 294: Line 331:
     theory (especially as it relates to IRC3 proposals,) or general     theory (especially as it relates to IRC3 proposals,) or general
     banter among long-standing IRC users.     banter among long-standing IRC users.
 +
 +
  
 ===== See Also ===== ===== See Also =====

Trace: