installing_irc_at_home
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
installing_irc_at_home [2020/07/04 01:06] – [inspircd.conf] waxphilosophic | installing_irc_at_home [2020/07/11 16:40] – [Summary] 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 57: | Line 57: | ||
Again, this is all just a made-up tribute to the FreeBSD mascot. You can enter whatever you like for your set-up. | Again, this is all just a made-up tribute to the FreeBSD mascot. You can enter whatever you like for your set-up. | ||
+ | === PORT CONFIGURATION === | ||
+ | |||
+ | Most of the PORT CONFIGURATION section can be left as it is. However, the last two lines are used to open ports allowing other IRC servers to connect to ours. In a home LAN environment, | ||
+ | |||
+ | So, find these lines: | ||
+ | |||
+ | < | ||
+ | <bind address="" | ||
+ | <bind address=" | ||
+ | </ | ||
+ | |||
+ | Comment them by adding a hash as the first character so they look like this: | ||
+ | |||
+ | < | ||
+ | #<bind address="" | ||
+ | #<bind address=" | ||
+ | </ | ||
+ | |||
=== CONNECTIONS CONFIGURATION === | === CONNECTIONS CONFIGURATION === | ||
- | No changes are needed for the 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 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=" | ||
Line 168: | Line 186: | ||
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 213: | Line 231: | ||
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 348: | Line 380: | ||
--- | --- | ||
> email=" | > email=" | ||
+ | 225, | ||
+ | < <bind address="" | ||
+ | < <bind address=" | ||
+ | --- | ||
+ | > #<bind address="" | ||
+ | > #<bind address=" | ||
313c313 | 313c313 | ||
< resolvehostnames=" | < resolvehostnames=" | ||
Line 356: | Line 394: | ||
--- | --- | ||
> resolvehostnames=" | > resolvehostnames=" | ||
+ | 497c497 | ||
+ | < #< | ||
+ | --- | ||
+ | > <include file=" | ||
1044c1044 | 1044c1044 | ||
< #< | < #< | ||
Line 383: | Line 425: | ||
==== 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 398: | Line 462: | ||
* 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. | ||
installing_irc_at_home.txt · Last modified: 2024/09/05 00:05 by hc9