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:06] – [inspircd.conf] waxphilosophicinstalling_irc_at_home [2020/07/10 20:49] – [Pidgin for GUI clients] Note about passwords. 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 348: 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 356: 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">
Line 398: Line 426:
  
   * Choose a protocol of IRC.   * Choose a protocol of IRC.
-  * Fill in the loginserver, and password with the information you use to log into the FreeBSD server+  * Fill in the login and server that you use on your LAN
-  * Check the remember password if you likebut be aware that it is saved in clear text in the %APPDATA% directory.+  * Password is not required for IRCand be aware that it is saved in clear text in the %APPDATA% directory if you use it.
   * 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: 2020/07/13 01:01 by waxphilosophic