installing_irc_at_home
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| installing_irc_at_home [2020/07/04 01:28] – [inspircd.conf] waxphilosophic | installing_irc_at_home [2020/07/13 01:01] (current) – waxphilosophic | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| This how-to covers installing and IRC server and clients for a typical home LAN. The hardware and OS used is a Raspberry Pi 2 with FreeBSD 12.1, but any system with a recent BSD variant should work with little need or no modification. | This how-to covers installing and IRC server and clients for a typical home LAN. The hardware and OS used is a Raspberry Pi 2 with FreeBSD 12.1, but any system with a recent BSD variant should work with little need or no modification. | ||
| - | At the time of writing, the SDF servers run InspIRCd for the server side and ircII for the default client. The same software is used in this document. In addition, this how-to covers Pidgin, a Windows/Mac GUI client that can be used for IRC as well as other instant messaging protocols. | + | At the time of writing, the SDF servers run InspIRCd for the server side and ircII for the default client. The same software is used in this document. In addition, this how-to covers Pidgin, a Windows/Mac GUI client that can be used for IRC as well as other instant messaging protocols. Mozilla Thunderbird has IRC capabilities and is covered as well. |
| ===== Installing Server-Side Software ===== | ===== Installing Server-Side Software ===== | ||
| Line 77: | Line 77: | ||
| === CONNECTIONS CONFIGURATION === | === CONNECTIONS CONFIGURATION === | ||
| - | After commenting out the last two lines of PORT CONFIGURATION, | + | After commenting out the last two lines of PORT CONFIGURATION, |
| - | The reason for this is entirely because of DNS. Unless you are running a robust DNS infrastructure on your LAN, chances are good that your ISP's router (the typical home LAN DNS server) will not do reverse look-ups. Setting resolvehostnames=" | + | The reason for changing resolvehostnames |
| If you have a more robust DNS server on your network, you can certainly leave this as-is. If you see errors like "Could not resolve your hostname: Malformed answer" | If you have a more robust DNS server on your network, you can certainly leave this as-is. If you see errors like "Could not resolve your hostname: Malformed answer" | ||
| Line 90: | Line 90: | ||
| Do not give into the temptation to comment the lines out. This is not the same as setting it to no. | Do not give into the temptation to comment the lines out. This is not the same as setting it to no. | ||
| + | |||
| + | As for the IP address range that needs changing, this is in the example < | ||
| + | |||
| + | < | ||
| + | allow=" | ||
| + | </ | ||
| === Enabling Server Operators === | === Enabling Server Operators === | ||
| Line 186: | Line 192: | ||
| What you see under the headings of CLASS CONFIGURATION and OPERATOR COMPOSITION can be left as default. It's the OPERATOR CONFIGURATION section we're interested in. | What you see under the headings of CLASS CONFIGURATION and OPERATOR COMPOSITION can be left as default. It's the OPERATOR CONFIGURATION section we're interested in. | ||
| - | There are a couple examples given using the names Attila and Brian. Look them over to read the comments and then delete them. Yes, delete. Delete everything after the section heading. | + | There are a couple examples given using the names Attila and Brain. Look them over to read the comments and then delete them. Yes, delete. Delete everything after the section heading. |
| When you're done, the opers.conf file should end here: | When you're done, the opers.conf file should end here: | ||
| Line 231: | Line 237: | ||
| It would also be difficult to enforce in an environment were there are no reverse DNS lookups and IPs are handed out from a DHCP server. In other words, neither user@hostname nor user@192.168.x.x would work reliably. " | It would also be difficult to enforce in an environment were there are no reverse DNS lookups and IPs are handed out from a DHCP server. In other words, neither user@hostname nor user@192.168.x.x would work reliably. " | ||
| - | Other than changing the lame password, | + | Other than changing the lame password, |
| + | |||
| + | Right around line 75 of opers.conf, you'll see: | ||
| + | |||
| + | < | ||
| + | vhost=" | ||
| + | </ | ||
| + | |||
| + | Following the naming used in the example, change this to: | ||
| + | |||
| + | < | ||
| + | vhost=" | ||
| + | </ | ||
| + | |||
| + | If you have customized the domain names to something else, by all means use that. | ||
| ==== motd.txt ==== | ==== motd.txt ==== | ||
| Line 372: | Line 392: | ||
| > #<bind address="" | > #<bind address="" | ||
| > #<bind address=" | > #<bind address=" | ||
| + | 278c278 | ||
| + | < allow=" | ||
| + | --- | ||
| + | > allow=" | ||
| 313c313 | 313c313 | ||
| < resolvehostnames=" | < resolvehostnames=" | ||
| Line 411: | Line 435: | ||
| ==== opers.conf ==== | ==== opers.conf ==== | ||
| - | opers.conf | + | This is an abreviated diff of opers.conf since most of the changes involved deleting the bottom third of the file. |
| + | |||
| + | < | ||
| + | 75c75 | ||
| + | < | ||
| + | --- | ||
| + | > | ||
| + | 94,95d93 | ||
| + | < | ||
| + | < # Operator account with a plaintext password. | ||
| + | 97, | ||
| + | < # name: Oper login that is used to oper up (/OPER < | ||
| + | < # Remember: This is case sensitive. | ||
| + | < | ||
| + | --- | ||
| + | > | ||
| + | > | ||
| + | > | ||
| + | > | ||
| + | > | ||
| + | 101, | ||
| + | [Not shown for brevity.] | ||
| + | </ | ||
| ==== motd.txt ==== | ==== motd.txt ==== | ||
| Line 426: | Line 472: | ||
| * Choose a protocol of IRC. | * Choose a protocol of IRC. | ||
| - | * Fill in the login, server, and password with the information | + | * Fill in the login and server |
| - | * Check the remember password if you like, but be aware that it is saved in clear text in the %APPDATA% directory. | + | * Password is not required for IRC, and be aware that it is saved in clear text in the %APPDATA% directory |
| * The remaining tabs may be left with default settings. | * The remaining tabs may be left with default settings. | ||
| Line 441: | Line 487: | ||
| See this WikiHow article for a guided step-by-step with pictures: [[ https:// | See this WikiHow article for a guided step-by-step with pictures: [[ https:// | ||
| + | |||
| + | ===== Thunderbird for GUI clients ===== | ||
| + | |||
| + | In addition to email, Thunderbird also has IRC capabilities. To access, find Chat on the toolbar. It's after Get Messages and Write. Click Chat. | ||
| + | |||
| + | Unless you've set up Thunderbird as a chat client previously, you'll be looking at a message that say you haven' | ||
| + | |||
| + | Follow the set-up wizard. | ||
| + | |||
| + | * Select IRC as the network. | ||
| + | * Enter your nickname and IRC server hostname (beastie.home.lan if you're following the example.) | ||
| + | * You can leave the password blank. | ||
| + | * Change the port to 6667 in the Advanced Options. | ||
| + | * Remove the check for Use SSL in the Advanced Options. | ||
| + | |||
| + | Leave the box checked for connect Connect to This Account Now to test. | ||
| ====== Go Forth and Conquer ====== | ====== Go Forth and Conquer ====== | ||
installing_irc_at_home.1593826116.txt.gz · Last modified: 2020/07/04 01:28 by waxphilosophic