User Tools

Site Tools


installing_irc_at_home

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
installing_irc_at_home [2020/07/04 01:03] – [inspircd.conf] waxphilosophicinstalling_irc_at_home [2020/07/04 01:28] – [inspircd.conf] waxphilosophic
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, with a single server, this will never happen.
 +
 +So, find these lines:
 +
 +<code>
 +<bind address="" port="7000,7001" type="servers">
 +<bind address="1.2.3.4" port="7005" type="servers" ssl="openssl">
 +</code>
 +
 +Comment them by adding a hash as the first character so they look like this:
 +
 +<code>
 +#<bind address="" port="7000,7001" type="servers">
 +#<bind address="1.2.3.4" port="7005" type="servers" ssl="openssl">
 +</code>
 + 
 === CONNECTIONS CONFIGURATION === === CONNECTIONS CONFIGURATION ===
  
-No changes are needed for the PORT CONFIGURATION, so we can move on to CONNECTIONS CONFIGURATION. The changes here involve changing resolvehostnames="yes" to resolvehostnames="no".+After commenting out the last two lines of PORT CONFIGURATION, so we can move on to CONNECTIONS CONFIGURATION. The changes here involve changing resolvehostnames="yes" to resolvehostnames="no".
  
 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="no" will instruct InspIRCd to not even try, sparing you countless warning messages. 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="no" will instruct InspIRCd to not even try, sparing you countless warning messages.
Line 82: Line 100:
  
 It needs to be uncommented if you want to enable users to gain administrative privileges. If you don't remove the leading hash, any attempt to use the /OPER command will result in the message "Invalid oper credentials". It needs to be uncommented if you want to enable users to gain administrative privileges. If you don't remove the leading hash, any attempt to use the /OPER command will result in the message "Invalid oper credentials".
 +
 +It should look like this when you're done:
 +
 +<code>
 +<include file="opers.conf">
 +</code>
  
 === Sections left as default === === Sections left as default ===
Line 342: Line 366:
 --- ---
 >        email="beastie@beastie.home.lan"> >        email="beastie@beastie.home.lan">
 +225,226c225,226
 +< <bind address="" port="7000,7001" type="servers">
 +< <bind address="1.2.3.4" port="7005" type="servers" ssl="openssl">
 +---
 +> #<bind address="" port="7000,7001" type="servers">
 +> #<bind address="1.2.3.4" port="7005" type="servers" ssl="openssl">
 313c313 313c313
 <          resolvehostnames="yes" <          resolvehostnames="yes"
Line 350: Line 380:
 --- ---
 >          resolvehostnames="no" >          resolvehostnames="no"
 +497c497
 +< #<include file="opers.conf">
 +---
 +> <include file="opers.conf">
 1044c1044 1044c1044
 < #<include file="modules.conf"> < #<include file="modules.conf">
installing_irc_at_home.txt · Last modified: 2020/07/13 01:01 by waxphilosophic