BNC4FREE - User contributions [en-gb]

Request

2026-06-07T13:25:50Z

Russell: BNC4FREE is no longer taking account requests

Requesting an IRC Bouncer from us is easy and simple provided that you fill in the required fields and provide the necessary details accurately and correctly so we can set-up your account. By following the steps on this page, you will be able to successfully request a bouncer with us.

== How to Request an Account ==



BNC4FREE is no longer taking requests for new accounts. Support is still available for existing users and we will accept network requests. Please see the section below regarding this.

== How to Request Additional Networks for Your Account ==

If you already have an account with us, you can request up to 2 additional networks to be added to your account (bringing the total to 3 on your account). To do this, choose a network from our Official Network List, connect to the network and join the channel “#bnc4free”.

Once you have done this, you will need to type <code>!network request</code> in the channel. You will be asked to fill in the following fields:

* Username – This is the username that you will use to login and authenticate to the bouncer.
* IRC Server – This is the IRC server address that you will want the bouncer to connect to. (e.g: irc.efnet.org). You can add more servers after you’re request has been accepted. More details on this soon
* IRC Port – This is the IRC port that you usually connect to on the server which is usually 6667. For SSL Ports please prefix the port with a “+” (e.g: 6667 – SSL e.g: +6697)

The command you will enter in the IRC Channel should then look like
!network request someusername irc.test.net 6667
Once you have entered this into the channel, you will be sent an email containing a code of which must be entered onto IRC or can be entered on the [https://bnc4free.com/?page_id=715 Verify your Email] page in order to validate that you have requested the new network for your account.

When you have verified your email address, your network request is officially pending review from the staff team. You can check the status of your request by using the following command on IRC:
!network check [request id]
You will receive an email from us when the request has been accepted or rejected.

== Frequently Asked Questions ==

=== I don’t want everyone to see my request or email address, Can i request privately? ===

Yes. You can join ##bnc4free on Espernet and LiberaChat where the channels are moderated so that only our staff team and our services bot can see your messages.

=== Can i request by email? ===

Requests via email are not supported at this time.

=== When will my request be accepted? ===

At present, we will be able to process requests within 24 to 48 hours of your request. In most cases it will take less time for us to process your request.
If you request has not been processed within 48 hours, please contact our [mailto:support@bnc4free.com support team] quoting your username or request ID and we will look into this.

LiberaChat Cloaks

2023-11-10T21:42:09Z

Russell: /* The Cloak Hierarchy */ Make this a bit clearer

The cloaking method on LiberaChat works a bit different than other networks. This article will explain how they work.

= Types of Cloak =

There are 2 types of cloak that a user can possibly obtain but each one is obtained differently. These are as follows:

== User and Project Cloaks ==

Project cloaks are offered to users that are part of one of the projects on the LiberaChat network. These typically take the form project/role/user, for instance 'bnc4free/someuser' (though some take other forms). They are designed to demonstrate that the user is connected to a project in some way. Different projects use cloaks for various roles and some are offered to users of a project as-well.

Normal user cloaks which can be requested from [https://web.libera.chat/ #libera-cloak] take the form user/accountname. They indicate that the user is not affiliated with any specific project on LiberaChat. Bots can also be cloaked subject to approval from operators on the network.

== Gateway Cloaks ==

Gateway cloaks are cloaks that are put on a the user if they are connecting from larger organisations and webchats, such as Mibbit, KiwiIRC and many bouncer providers. These hosts tend to take the form of 'gateway/shell/providername/x-*' or gateway/web/provider/ip.1.2.3.4'

= The Cloak Hierarchy =

Gateway cloaks are applied when you connect to the network from a larger organisation or webchat· However, you may already have a user or project cloak assigned to your nickname. LiberaChat interprets this as follows:

* User Cloaks: If you have a user cloak (user/accountname), this will not work and you will be assigned the gateway cloak
* Project Cloaks: If you have a project cloak (project/role/user), this will be applied when you authenticate to NickServ or use SASL and will over-ride the gateway cloak

LiberaChat's services will allow ChanServ flags and akicks to be set to these cloaks for the purposes of channel management and user bans.

LiberaChat Cloaks

2023-11-10T21:34:41Z

Russell: Edited with gateway cloaks removed until consultation with LiberaChat regarding assigning gateway cloaks to BNC providers

The cloaking method on LiberaChat works a bit different than other networks. This article will explain how they work.

= Types of Cloak =

There are 2 types of cloak that a user can possibly obtain but each one is obtained differently. These are as follows:

== User and Project Cloaks ==

Project cloaks are offered to users that are part of one of the projects on the LiberaChat network. These typically take the form project/role/user, for instance 'bnc4free/someuser' (though some take other forms). They are designed to demonstrate that the user is connected to a project in some way. Different projects use cloaks for various roles and some are offered to users of a project as-well.

Normal user cloaks which can be requested from [https://web.libera.chat/ #libera-cloak] take the form user/accountname. They indicate that the user is not affiliated with any specific project on LiberaChat. Bots can also be cloaked subject to approval from operators on the network.

== Gateway Cloaks ==

Gateway cloaks are cloaks that are put on a the user if they are connecting from larger organisations and webchats, such as Mibbit, KiwiIRC and many bouncer providers. These hosts tend to take the form of 'gateway/shell/providername/x-*' or gateway/web/provider/ip.1.2.3.4'

= The Cloak Hierarchy =

Gateway cloaks are applied when you connect to the network from a larger organisation, webchat and bouncer providers such as ourselves. However, you may already have a user or project cloak assigned to your nickname. LiberaChat interprets this as follows:

* User Cloaks: If you have a user cloak (user/accountname), this will not work and you will be assigned the gateway cloak
* Project Cloaks: If you have a project cloak (project/role/user), this will be applied when you authenticate to NickServ or use SASL and will over-ride the gateway cloak

LiberaChat's services also take this into account and therefore the same principal can be applied to ChanServ flags and akicks.

LiberaChat Cloaks

2023-11-10T21:28:42Z

Russell: Russell moved page Freenode Cloaks to LiberaChat Cloaks without leaving a redirect: Change to LiberaChat, page update pending

The cloaking method on Freenode works a bit different than other networks. This article will explain how they work.

= Types of Cloak =

There are 2 types of cloak that a user can possibly obtain but each one is obtained differently. These are as follows:

== User and Project Cloaks ==

Project cloaks are offered to users that are part of one of the projects on the Freenode network. These typically take the form project/role/user, for instance 'wikimedia/someuser' (though some take other forms). They are designed to demonstrate that the user is connected to a project in some way. Different projects use cloaks for various roles and some are offered to users of a project aswell.

Normal user cloaks which can be requested from [https://webchat.freenode.net/#freenode #freenode] take the form unaffiliated/accountname. They indicate that the user is not affiliated with any specific project on Freenode. Bots can also be cloaked to indicate their owner and take the form of 'unaffiliated/owneraccountname/bot/botaccountname'.

== Gateway Cloaks ==

Gateway cloaks are cloaks that are put on a the user if they are connecting from larger organisations and webchats, such as Mibbit, KiwiIRC and many bouncer providers. These hosts tend to take the form of 'gateway/shell/providername/x-*' or gateway/web/provider/ip.1.2.3.4'

= The Cloak Hierarchy =

Gateway cloaks are applied when you connect to the network from a larger organisation, webchat and bouncer providers such as ourselves. However, you may already have a user or project cloak assigned to your nickname. Freenode interprets this as follows:

* User Cloaks: If you have a user cloak (unaffiliated/accountname), this will not work and you will be assigned the gateway cloak
* Project Cloaks: If you have a project cloak (project/role/user), this will be applied when you authenticate to NickServ or use SASL and will over-ride the gateway cloak

= Notes on Spoofing/Cloaking =

Because of the way gateway cloaks are assigned to users, it is sometimes possible for users to evade bans that are set. For example you issue the following:
/mode +b *!*@gateway/shell/bnc4free/x-89327

The issue with this is that the number after the 'x' always changes and does not remain the same which means that all the user has to do is reconnect to the network to evade the ban.

It is possible to ban all users of the BNC4FREE gateway using the following
/mode +b *!*@gateway/shell/bnc4free/session
or
/mode +b *!*@gateway/shell/bnc4free/*
'''but''' this will also ban any users using the BNC4FREE gateway cloak that have a project cloak aswell. Freenode spoofs the IP during connection to the network before applying the cloak. It looks a bit like this in a WHOIS:

[MyUser] (test@wikimedia/MyUser): My Name
[MyUser] egan.freenode.net :Miami, US
[MyUser] is using a secure connection
[MyUser] is connecting from *@gateway/shell/bnc4free/session 255.255.255.255
[MyUser] is logged in as MyUser

As we can see here, Freenode interprets the user as connecting from host "gateway/shell/bnc4free/session" but with a gateway cloak of 'wikimedia/MyUser'. Because of this they are affected by the bans set on the BNC4FREE gateway.

Freenode's services also take this into account and therefore the same principal can be applied to ChanServ flags and akicks.

Frequently Asked Questions

2023-11-10T21:24:22Z

Russell: /* I'm going to be away for a while, will my account be deleted? */ Remove reference to freenode and be a bit more open that the list is not exhaustive

More often that not we are frequently asked the same questions or similar questions by a large number of users or those that are interested in our service. This FAQ will hopefully answer many of the common questions that you may have relating to your IRC Bouncer. We have split these into sections which can be quickly navigated to using the contents section below.

= General =

This section relates to questions that are generic to the service and don't fall into any other category.

== Is this service free and will I ever have to pay for anything? ==

This service is 100% free and we intend to be able to keep it this way for as long as possible. We do not ask or force anyone to pay for our service but if you would like to contribute, it is possible to donate. Information on this can be found on our [https://bnc4free.com/?page_id=35 Donation Page].

== I need an IRC Bouncer for my IRC Bot, is this possible? ==

In theory yes this is possible as long as the bot complies with our [https://bnc4free.com/?page_id=10 Terms of Service] however you do need to be aware that as your bots features are client side, they will not work when the bot disconnects from the IRC Bouncer.

= Requesting =

This section relates to questions that have been asked regarding requesting an IRC Bouncer and the process involved.

== How do I request an IRC Bouncer ==

In order to request an IRC Bouncer, you will need to join the #bnc4free on one of the networks we have a service bot operating in. These networks are listed on our [https://bnc4free.com/?page_id=23 Official Networks] list and we have linked each network to the webchat to make it easier.

Once you have joined the channel, you will need to request your bouncer using the ‘!request’ command in the channel. You will be asked to fill in the following fields:

{| class="wikitable"
|- style="font-weight:bold;"
! Field
! Description
! Example Value
|-
| Username
| This will be the username that you will use to login to the bouncer. Please note that this doesn't have to be your nickname, realname or anything you would normally use on IRC as you'll be able to set these up in your account once it has been accepted
| MyUsername
|-
| Email Address
| The email address that we will send your details to once the request has been processed. Please note as per our Terms of Service, this must not be a disposable email address.
| its.me@example.com
|-
| IRC Server
| The IRC Server that you wish to be connected to. Note that this must not a network listed under "Prohibited Networks" on our [https://bnc4free.com/?page_id=63 known and prohibited networks] list
| irc.libera.chat
|-
| IRC Port
| The IRC Port that will be used to connect to the IRC Server. (Typically 6667, or +6697 for SSL)
| +6697
|}

The command you will enter in the IRC Channel should look like the following:

Once you have entered this into the channel, you will be sent an email containing a verification code of which also must be entered onto IRC in order to validate your email address. The command you need to enter will typically look like the example below:
!verify 0e12c4544ddff0b3e9a0b5c984d19de0

Once you have completed this, your request is officially pending review from the staff team. You will receive an email when the request has been accepted or rejected.

== I don't want everyone to see my email address/request. Can i request privately? ==

Absolutely, You can join the channel ##bnc4free on the [https://webchat.esper.net/ Espernet] or [https://web.libera.chat/?nick=BNC-?&channel=#bnc4free LiberaChat] network where the channels are moderated so that only our staff team and our services bot can see your request.

== Is it possible to request by email? ==

At this time, it is not possible as we are working on a system that will be able to read the emails sent in a specific format and automatically input the data into our request system. We will update you once we have this up and running!

== I haven't received an email with a verification to verify my request. Can you resend it? ==

We are able to resend the verification email to you so that you can verify you're request but this can only be resent to the email you requested with initially. We will not send the email to an alternative address. Please also ensure that you have checked all your email folders (not just Inbox, Junk, Deleted etc...) as in some cases it is possible that an email filter may have placed the message elsewhere. If you are unable to locate the email, please feel free to email [mailto:support@bnc4free.com support] or poke us in #bnc4free on one of our [https://bnc4free.com/?page_id=23 Official Networks] and we'll resend it for you.

== How long does it take for my request to be processed? ==

We aim to have processed requests within 24 to 48 hours of the request being email verified. In some cases this is not always possible to due bank holidays such as Christmas and other events. In rare circumstances we may take considerably longer to process a request if we believe that the bouncer may be used for abuse as we often check with networks if this is the case. If we haven't processed your request within 72 hours, please feel free to email [mailto:support@bnc4free.com support] or poke us in #bnc4free on one of our [https://bnc4free.com/?page_id=23 Official Networks] and we'll look into it.

== How can I request/add more networks to my account? ==

Each account can currently have up to 3 networks. Usually this will be the network you initially requested when your account was setup and 2 additional networks. To request additional networks you will need to join the #bnc4free channel on one of the networks we have a service bot operating in. These networks are listed on our [https://bnc4free.com/?page_id=23 Official Networks] list and we have linked each network to the webchat to make it easier.

Once you have joined the channel, you will need to request your bouncer using the ‘!network request’ command in the channel. You will be asked to fill in the following fields:

{| class="wikitable"
|- style="font-weight:bold;"
! Field
! Description
! Example Value
|-
| Username
| This will be the username of the account you have with us
| MyUsername
|-
| IRC Server
| The IRC Server that you wish to be connected to. Note that this must not a network listed under "Prohibited Networks" on our [https://bnc4free.com/?page_id=63 known and prohibited networks] list and cannot be a network that you already have on your account
| irc.rizon.net
|-
| IRC Port
| The IRC Port that will be used to connect to the IRC Server. (Typically 6667, or +6697 for SSL)
| +6697
|}

The command you will enter in the IRC Channel should look like the following:
!network request MyUsername irc.rizon.net +6697

Once you have entered this into the channel, you will be sent an email containing a verification code of which also must be entered onto IRC in order to validate that it is the account owner that has requested the additional network. The command you need to enter will typically look like the example below:
!network verify 0e12c4544ddff0b3e9a0b5c984d19de0

Once you have completed this, your network request is officially pending review from the staff team. You will receive an email when the request has been accepted or rejected.

== I have mistyped my email address when I made the request what should I do? ==

Send the request again using the <code>request</code> command and the correct email address. Your pending request with the incorrect email address will automatically expire within 7 days if not verified and will not prevent you from being accepted for an account.

= Accounts =

This section relates to questions about your account and the various configuration settings.

== I have forgotten my password, How can I get it reset? ==

If you have forgotten your password and need this to be reset, Please ask us to reset it in the channel #bnc4free on one of our [https://bnc4free.com/?page_id=23 Official Networks] or send us an email from the email address you used for your account to [mailto:support@bnc4free.com support]. Please note if you are requesting a reset on IRC, we will send you an email so that we can confirm you are the account holder.

== I have configured Allowed Hosts and no longer have access to the hosts I specified, How can i get this fixed? ==

If you have misconfigured the 'Allowed Hosts' setting in your account or no longer have access to the addresses you have configured there, Please ask us to reset your allowed hosts in the channel #bnc4free on one of our [https://bnc4free.com/?page_id=23 Official Networks] or send us an email from the email address you used for your account to [mailto:support@bnc4free.com support].

== How can I change my realname, ident or nickname? ==

If you run /whois on your own nickname, it should look something like this:

[''MyNickname''] ('''ident'''@some.host.name): '''''My Realname'''''
[''MyNickname''] irc.server.network :Some IRC Server
[''MyNickname''] End of WHOIS list.

To change your realname, nickname or ident permanently on a network so that the values are set if you reconnect to the IRC Network, you will need to load the controlpanel module using the following command:
/msg *status loadmod controlpanel

Once the module is loaded, to change your ''nickname'' use the following:
/msg *controlpanel setnetwork nick $user $network ''MyNewNickname''
Replacing ''MyNewNickname'' with the nickname of your choice. You can also change your nick while connected to the network using:
/nick ''MyNewNickname''

To change your '''ident''' use the following:
/msg *controlpanel setnetwork ident $user $network '''MyNewIdent'''
Replacing '''MyNewIdent''' with the ident of your choice. Once it has been set, you will need to reconnect to the IRC network using:
/msg *status jump

To change your '''''realname''''' use the following:
/msg *controlpanel setnetwork realname $user $network '''''MyNewRealName'''''
Replacing '''''MyNewRealName''''' with the realname of your choice. Once it has been set, in a majority cases you will need to reconnect to the IRC network using:
/msg *status jump
On some networks you may be able to set your realname to the new realname until you next reconnect to IRC by using:
/setname '''''MyNewRealName'''''

These settings can also be changed via the [https://panel.bnc4free.com/ webpanel]

== How can i change my password? ==

You can change your password by using the [https://panel.bnc4free.com/ webpanel] or by using the [[Module:controlpanel|controlpanel]] module. To change your password using the module, use the following command:
/msg *controlpanel Set password <new password>

<div id="Reset_By_Peer"></div>
== I keep getting the message "Connection reset by peer" ==

This error usually occurs when you try to connect to the SSL port of the bouncer (1339). On most clients, you '''must''' use port '''+1339''', including the plus before the port number in order to use SSL. Some other clients do not require the plus before the port to be specified but may have a tickbox if using a client such as [[Connect:HexChat|HexChat]] which needs to be ticked to enable SSL or a <code>-ssl</code> or <code>-tls</code> command line argument if using a client such as [[Connect:irssi|Irssi]].

You can find out how to connect using SSL for your client [[Connect|here]]

<div id="Reconnecting_Too_Fast"></div>
== I keep getting the message "Closing Link: [Please try again later - reconnecting too fast]" ==

This means exactly what it says in the message, you are reconnecting too fast. This is normally triggered by 3 failed logins within 1 minute and when triggered will prevent you from authenticating to the bouncer for 5 minutes. This can also be triggered if your host is listed on a DNS Blacklist or your account has been disabled as these are classed as failed logins.

<div id="Listed_On_DNSBL"></div>
== I keep getting the message "Closing Link: [Your host is listed on (DNSBL Name). Please visit (DNSBL Link) for further information]" ==

Unfortunately this means that the IP address you are using is listed in one of the many DNS Blacklists that our bouncer users. The reason that the IP/Host is blacklisted usually means the IP is a proxy, vpn, TOR exit node, exploitable host or has been used for abuse at some point. We do not have any control over IP's that are added to the DNS blacklist. You may be able to request removal of the IP from the DNS Blacklist by following the DNS Blacklist link displayed in the message.

<div id="Account_Disabled"></div>
== I am getting the message "Closing Link: [Your account has been disabled. (Reason: (a reason))]" ==

This message means that your account has been disabled and normally means that you have violated the Terms of Service. A brief reason for why the account has been disabled is usually given in the message. For further information on why your account has been disabled or to have the account re-enabled should you feel that this is a mistake, you will need to email our [mailto:support@bnc4free.com Support Team]

<div id="Session_Error"></div>
== When I try to access the webpanel, I get the error "Access Denied - This session does not belong to your IP." ==

This normally means that you are trying to access the web panel from a web browser you have used before but your IP address in the meantime has changed. This most commonly occurs with users who have a dynamic ip or when your using a portable device that connects to different wireless access points or mobile networks. To resolve the issue, you will need to clear your cookies. Further information can be found below:
* [https://support.mozilla.org/en-US/kb/clear-cookies-and-site-data-firefox#w_clear-cookies-for-the-current-website Clear Cookies on Firefox]
* [https://support.mozilla.org/en-US/kb/clear-browsing-history-firefox-ios#w_clear-individual-site-data Clear Cookies on Firefox (Mobile Devices)]
* [https://support.google.com/chrome/answer/95647 Clear Cookies on Chrome]
* [https://support.google.com/accounts/answer/32050?co=GENIE.Platform%3DAndroid Clear Cookies on Chrome (Mobile & Android Devices)]
* [https://support.google.com/accounts/answer/32050?co=GENIE.Platform%3DiOS Clear Cookies on Chrome (iPhone & iPad Devices)]
* [https://support.microsoft.com/en-us/microsoft-edge/delete-cookies-in-microsoft-edge-63947406-40ac-c3b8-57b9-2a946a29ae09 Clear Cookies on Microsoft Edge]
* [https://support.microsoft.com/en-us/topic/delete-and-manage-cookies-168dab11-0753-043d-7c16-ede5947fc64d Clear Cookies on Internet Explorer]
* [https://support.apple.com/en-gb/HT201265 Clear Cookies on Safari (iPhone & iPad)]

<div id="The_connection_was_reset"></div>

== When I try to access the webpanel, I get the error "The connection was reset" ==

This normally happens if you have tried to access the webpanel using HTTP (rather than HTTPS) on the bouncers SSL Port. The bouncers web panels can only be accessed in the following ways:

* Bouncer Non-HTTPS¹: <nowiki>http://servername.bnc4free.com:1337/</nowiki>
* Bouncer HTTPS¹: <nowiki>https://servername.bnc4free.com:1339/</nowiki>
* Generic Webpanel²: https://panel.bnc4free.com/

¹ <span style="font-size:88%">Replace "servername" with the relevant server name (e.g apple)</span><br/>
² <span style="font-size:88%">Logs in to the selected server name using HTTPS</span>

== I'm going to be away for a while, will my account be deleted? ==

Generally, your account should be fine and will remain if you are aware for a period of time however if you will be away for 60 days or more, your account will be removed in accordance with our inactive accounts policy mentioned in our [https://bnc4free.com/?page_id=10 Terms of Service]. Your account will only be deleted if there have been no logins during that period, logging in for even a few minutes once in the 60 day period is sufficient enough for the account to be considered active.

'''Note:''' If your account is on one the more popular networks (LiberaChat, Rizon, EFNet, IRCNet... this list is not exhaustive), the account is normally deleted after 30 days of inactivity rather than 60 days.

If you plan to be away more than 60 days (or 30 days for popular networks) and IRC access will not be possible, please let our [mailto:support@bnc4free.com Support Team] know and we will ensure that the account is not removed prior to your return.

== What is the maximum number of lines the bouncer can keep in its channel or query buffer? ==

Our bouncers are currently set to keep a maximum of 1000 lines for each channel and query you receive while away. Buffers for individual channels, all channels and queries can be changed via the [https://panel.bnc4free.com/ webpanel] or using the [[Module:controlpanel|controlpanel]] module.

BNC4FREE:About

2023-11-10T21:22:16Z

Russell: /* Any Questions? */ Fix an incorrect link

== Who are we? ==

BNC4FREE is a non-profit organization that specializes in providing Free IRC Bouncers. [https://en.wikipedia.org/wiki/BNC_%28software%29 IRC Bouncers] are used to connect to [https://en.wikipedia.org/wiki/Internet_Relay_Chat Internet Relay Chat] (IRC) networks primarily but can be configured so that you stay online 24 hours a day, 7 days a week and also log messages that were said while you were away. Our objective is to be able to provide IRC Bouncers to nearly every [https://en.wikipedia.org/wiki/Internet_Relay_Chat Internet Relay Chat] Network in the world completely free of charge while ensuring that our services are as stable and secure as possible unlike some of the other unstable and insecure providers out there.

== The History ==

BNC4FREE started in August 2007 and originally ran completely on donated servers and donated money from its users. When BNC4FREE was started, the founder, Russell didn’t know much about Linux or programming and spent numerous days, nights and months learning more about Linux and programming in order to improve the service and offer more to the users. During this time, we were using [http://www.psybnc.at/ psyBNC] for bouncer software and had 3 servers with around 50 vhosts on each. As time progressed, it was obvious that [http://www.psybnc.at/ psyBNC] could not be customised enough or wasn’t dynamic enough for what we wanted to do. At this point, we decided to switch to another bouncer software known as [http://www.shroudbnc.info/ sBNC] and continued for a while running this. Later down the line we discovered that there was a new bouncer software available that had more features than the previous 2 we had used. This was called [http://wiki.znc.in/ZNC ZNC] and we decided to switch to it to offer our users more customisation of their bouncer and more features. Ever since the switch to [http://wiki.znc.in/ZNC ZNC], the service has been funded solely by the founder however we have taken numerous donations along the way which have helped us to get better servers and services so that we can provide a better service to the end user. The founder has spent numerous weeks and months customizing the software to fit the needs of BNC4FREE. This included features such as removing the ability for users to change server, numerous administration modules and some bug fixes. The founder also coded an entire module for BNC4FREEs’ IRC Bot during this time so that the handling of accounts and more could be managed from IRC.

In July 2011, BNC4FREE and SurgeHost partially teamed up allowing us to offer Premium IRC Bouncers with more features under the name of BNCFTW/SurgeHost. Since teaming up with SurgeHost/BNCFTW, The company was renamed to EvoSurge and started to provide more services. An executive decision was made in September 2012 that BNC4FREE and EvoSurge should no longer be linked to ensure that BNC4FREE could continue to be represented and work as an entirely non profit organization. Considerable work has been done since then by the staff of BNC4FREE and its founder in order to improve and better our service quality and standard.

BNC4FREE unfortunately closed in 2016 due to lack of funding and time from staff members including the founder. In March 2020, Coronavirus (COVID-19) struck the world and communication via the internet became as important as ever. On that basis, the founder of BNC4FREE using free time and spare money available set about re-launching BNC4FREE as a free service to keep people connected during these difficult times.

== Any Questions? ==

BNC4FREE will always provide a free service with customer service and quality being the main objective. If you are interested in knowing more about BNC4FREE, You can contact us via the following methods:

* Email: [mailto:support@bnc4free.com Support]
* IRC: [ircs://irc.libera.chat/ irc.libera.chat] OR [https://web.libera.chat/ Webchat]
* Facebook: [https://bnc4free.com/facebook https://bnc4free.com/facebook]
* Twitter: [https://bnc4free.com/twitter https://bnc4free.com/twitter]
* Reddit: [https://bnc4free.com/reddit https://bnc4free.com/reddit]

== Credits ==

Many thanks go to all the companies and individuals listed on our [https://bnc4free.com/?page_id=72 Credits Page] for keeping this service alive for as long as it has been.

Main Page

2023-01-01T09:34:09Z

Russell: Goodbye for another year

[[File:Logo.png]]

== Welcome to BNC4FREE ==
Welcome to BNC4FREE Wiki. This is the place where you can find information regarding our IRC (Internet Relay Chat) Bouncers and how to use them.

Were still writing much of the documentation here at the moment bit if you think we have missed something or need to edit something, let us know by emailing our [mailto:support@bnc4free.com support] team and we will endeavor to update the wiki accordingly. At some point in the near future, we will allow users to request access to the wiki to make updates and keep our pages up to date.

== Useful Links & Information ==
* [[Frequently_Asked_Questions|Frequently Asked Questions]]
* [[Connect|How to Connect]]
* [https://bnc4free.com/?page_id=63 Known & Prohibited Networks]
* [[:Category:Modules|Module Documentation]]
* [https://bnc4free.com/?page_id=23 Official Networks]
* [[Staff_Team|Our Staff Team]]
* [[Request|How to Request]]
* [https://bnc4free.com/terms Terms of Service]

== Follow us on Social Media ==

We regularly use Social Media as well as the IRC Channels on our [https://bnc4free.com/?page_id=23 Official Networks] to post updates and other important information. You can follow us on:

* [https://bnc4free.com/facebook Facebook]
* [https://bnc4free.com/twitter Twitter]
* [https://bnc4free.com/reddit Reddit]

Main Page

2022-12-18T10:27:15Z

Russell: Festive Logo change

[[File:Logo-christmas.png]]

== Welcome to BNC4FREE ==
Welcome to BNC4FREE Wiki. This is the place where you can find information regarding our IRC (Internet Relay Chat) Bouncers and how to use them.

Were still writing much of the documentation here at the moment bit if you think we have missed something or need to edit something, let us know by emailing our [mailto:support@bnc4free.com support] team and we will endeavor to update the wiki accordingly. At some point in the near future, we will allow users to request access to the wiki to make updates and keep our pages up to date.

== Useful Links & Information ==
* [[Frequently_Asked_Questions|Frequently Asked Questions]]
* [[Connect|How to Connect]]
* [https://bnc4free.com/?page_id=63 Known & Prohibited Networks]
* [[:Category:Modules|Module Documentation]]
* [https://bnc4free.com/?page_id=23 Official Networks]
* [[Staff_Team|Our Staff Team]]
* [[Request|How to Request]]
* [https://bnc4free.com/terms Terms of Service]

== Follow us on Social Media ==

We regularly use Social Media as well as the IRC Channels on our [https://bnc4free.com/?page_id=23 Official Networks] to post updates and other important information. You can follow us on:

* [https://bnc4free.com/facebook Facebook]
* [https://bnc4free.com/twitter Twitter]
* [https://bnc4free.com/reddit Reddit]

Staff Team

2022-02-13T20:53:12Z

Russell: /* Responsibilities */ Changes to the RACI table

BNC4FREE is made up of several volunteer’s who donate their time and efforts into making the service better. Our staff carry out day to day tasks such as assisting users, processing requests and sometimes other more complex tasks such as updating the website, developing new features, updating the IRC Services bot and managing the servers and their security.

== Our Staff Team ==

Our Staff team is currently organised as follows:

{| class="wikitable" style="text-align:center;"
|- style="text-align:left;"
! colspan="4" style="text-align:center; font-size:100%; background-color:#cbcefb;" | Founder (Russell)
|- style="background-color:#ffccc9;"
| Staff Team
| Bot Development Team
| Bouncer Development Team
| Technical Team
|-
| style="background-color:#9aff99; color:#333333;" | Russell
| style="background-color:#9aff99; color:#333333;" | Russell
| style="background-color:#9aff99; color:#333333;" | Russell
| style="background-color:#9aff99; color:#333333;" | Russell
|-
| style="background-color:#9aff99; color:#333333;" | Centrixx
| style="background-color:#9aff99; color:#333333;" | Centrixx
|
|
|-
| style="background-color:#9aff99; color:#333333;" | MetaNova
|
|
|
|}

== Our Structure ==

Our Staff team is currently organised as set out below:

{| class="wikitable" style="text-align:center;"
|- style="text-align:left;"
! colspan="4" style="text-align:center; font-size:100%; background-color:#cbcefb;" | The Founder
|- style="background-color:#ffccc9;"
| Staff Team Leader/Expert
| colspan="2" | Development Team Leader/Expert
| Technical Team Leader/Expert
|- style="background-color:#ffce93;"
| style="background-color:#9aff99; color:#333333;" | Staff Team Members
| Bot Development Team Leader/Expert
| Bouncer Development Team Leader/Expert
| style="background-color:#9aff99; color:#333333;" | Technical Team Members
|-
| style="background-color:#ffffc7; color:#333333;" | IRC Helpers
| style="background-color:#9aff99; color:#333333;" | Bot Development Team Members
| style="background-color:#9aff99; color:#333333;" | Bouncer Development Team Members
| style="text-align:left;" |
|}

== Responsibilities ==

Each team has a set of responsibilities, these are defined using the RACI model. RACI is outlined as follows
* '''R'''esponsible
* '''A'''ccountable
* '''C'''onsulted
* '''I'''nformed

Those who are '''''responsible''''' are those that do the work to and complete the tasks expected within role or team and carry out day to day operations. On occasion, those that are responsible can be delegated to assist in the tasks required for their role.

Those who are '''''accountable''''' are those who are answerable for the correct and thorough completion of tasks, delegates the tasks to those responsible and ensures that day to day operations are maintained.

Those who are '''''consulted''''' are those whose opinions or information are sought and are typically experts in their area

Those who are '''''informed''''' are those who are kept up-to-date on progress, daily operations and other changes.

The responsibilities of each area are set out below:

{| class="wikitable"
|- style="font-weight:bold;"
! Tasks
! Founder
! Staff <br />Team Leader/Expert
! Development <br />Team Leader/Expert
! Technical Team <br />Leader/Expert
! Bot Development <br />Team Leader/Expert
! Bouncer Development<br />Team Leader/Expert
! Bot Development<br />Team Members
! Bouncer Development<br />Team Members
! Technical<br />Team Members
! Staff<br />Team Members
! IRC Helpers
|-
| Ensuring objectives and targets are met
| R/A/C/I
| R/A/C/I
| R/A/C/I
| R/A/C/I
| R/A/C/I
| R/A/C/I
| R/A/I
| R/A/I
| R/A/I
| R/A/I
| R/A/I
|-
| Ensuring a quality service is maintained
| R/A/C/I
| R/A/C/I
| R/A/C/I
| R/A/C/I
| R/A/C/I
| R/A/C/I
| R/A/I
| R/A/I
| R/A/I
| R/A/I
| R/A/I
|-
| Changes to policies & procedures
| R/A/C/I
| C/I
| C/I
| C/I
| C/I
| C/I
| C/I
| C/I
| C/I
| C/I
| C/I
|-
| Development of Bouncer/Bot Software
| R/A/C/I
| C/I
| R/A/C/I
| I
| R/A/C/I
| R/A/C/I
| R/A/I
| R/A/I
| C/I
| C/I
| I
|-
| Rollout of new or updated software
| R/A/C/I
| C/I
| R/A/C/I
| R/A/C/I
| A/I
| A/I
| C/I
| C/I
| R/A/I
| C/I
| I
|-
| Changes to Servers & Security
| R/A/C/I
| C/I
| C/I
| R/A/C/I
| C/I
| C/I
| I
| I
| R/A/I
| I
| I
|-
| Processing of Requests
| R/A/C/I
| R/A/C/I
|
|
|
|
|
|
|
| R/A/C/I
| I
|-
| Enforcement of Blacklisting & Bans
| R/A/C/I
| R/A/C/I
|
|
|
|
|
|
|
| R/A/C/I
| R/I
|-
| Supporting IRC users with queries
| R/A/C/I
| R/A/C/I
|
|
|
|
|
|
|
| R/A/C/I
| R/I
|-
| Responding to email queries or requests
| R/A/C/I
| R/A/C/I
|
|
|
|
|
|
|
| R/A/C/I
| C/I
|}

Main Page

2022-02-13T20:38:36Z

Russell: /* Useful Links & Information */ Add a link to the staff team page

Staff Team

2022-02-13T20:34:43Z

Russell: /* Our Staff Team */ Update Staff Team structure

BNC4FREE is made up of several volunteer’s who donate their time and efforts into making the service better. Our staff carry out day to day tasks such as assisting users, processing requests and sometimes other more complex tasks such as updating the website, developing new features, updating the IRC Services bot and managing the servers and their security.

== Our Staff Team ==

Our Staff team is currently organised as follows:

{| class="wikitable" style="text-align:center;"
|- style="text-align:left;"
! colspan="4" style="text-align:center; font-size:100%; background-color:#cbcefb;" | Founder (Russell)
|- style="background-color:#ffccc9;"
| Staff Team
| Bot Development Team
| Bouncer Development Team
| Technical Team
|-
| style="background-color:#9aff99; color:#333333;" | Russell
| style="background-color:#9aff99; color:#333333;" | Russell
| style="background-color:#9aff99; color:#333333;" | Russell
| style="background-color:#9aff99; color:#333333;" | Russell
|-
| style="background-color:#9aff99; color:#333333;" | Centrixx
| style="background-color:#9aff99; color:#333333;" | Centrixx
|
|
|-
| style="background-color:#9aff99; color:#333333;" | MetaNova
|
|
|
|}

== Our Structure ==

Our Staff team is currently organised as set out below:

{| class="wikitable" style="text-align:center;"
|- style="text-align:left;"
! colspan="4" style="text-align:center; font-size:100%; background-color:#cbcefb;" | The Founder
|- style="background-color:#ffccc9;"
| Staff Team Leader/Expert
| colspan="2" | Development Team Leader/Expert
| Technical Team Leader/Expert
|- style="background-color:#ffce93;"
| style="background-color:#9aff99; color:#333333;" | Staff Team Members
| Bot Development Team Leader/Expert
| Bouncer Development Team Leader/Expert
| style="background-color:#9aff99; color:#333333;" | Technical Team Members
|-
| style="background-color:#ffffc7; color:#333333;" | IRC Helpers
| style="background-color:#9aff99; color:#333333;" | Bot Development Team Members
| style="background-color:#9aff99; color:#333333;" | Bouncer Development Team Members
| style="text-align:left;" |
|}

== Responsibilities ==

Each team has a set of responsibilities, these are defined using the RACI model. RACI is outlined as follows
* '''R'''esponsible
* '''A'''ccountable
* '''C'''onsulted
* '''I'''nformed

Those who are '''''responsible''''' are those that do the work to and complete the tasks expected within role or team and carry out day to day operations. On occasion, those that are responsible can be delegated to assist in the tasks required for their role.

Those who are '''''accountable''''' are those who are answerable for the correct and thorough completion of tasks, delegates the tasks to those responsible and ensures that day to day operations are maintained.

Those who are '''''consulted''''' are those whose opinions or information are sought and are typically experts in their area

Those who are '''''informed''''' are those who are kept up-to-date on progress, daily operations and other changes.

The responsibilities of each area are set out below:

{| class="wikitable"
|- style="font-weight:bold;"
! Tasks
! Founder
! Staff <br />Team Leader/Expert
! Development <br />Team Leader/Expert
! Technical Team <br />Leader/Expert
! Bot Development <br />Team Leader/Expert
! Bouncer Development<br />Team Leader/Expert
! Bot Development<br />Team Members
! Bouncer Development<br />Team Members
! Technical<br />Team Members
! Staff<br />Team Members
! IRC Helpers
|-
| Ensuring objectives and targets are met
| R/A/C/I
| R/A/C/I
| R/A/C/I
| R/A/C/I
| R/A/C/I
| R/A/C/I
| R/A/I
| R/A/I
| R/A/I
| R/A/I
| R/A/I
|-
| Ensuring a quality service is maintained
| R/A/C/I
| R/A/C/I
| R/A/C/I
| R/A/C/I
| R/A/C/I
| R/A/C/I
| R/A/I
| R/A/I
| R/A/I
| R/A/I
| R/A/I
|-
| Changes to policies & procedures
| R/A/C/I
| C/I
| C/I
| C/I
| C/I
| C/I
| I
| I
| I
| I
| I
|-
| Development of Bouncer/Bot Software
| R/A/C/I
| I
| R/A/C/I
|
| R/A/C/I
| R/A/C/I
| R/A/I
| R/A/I
|
| I
|
|-
| Rollout of new or updated software
| R/A/C/I
| I
| R/A/C/I
| R/A/C/I
| A/I
| A/I
| I
| I
| R/A/I
| I
|
|-
| Changes to Servers & Security
| R/A/C/I
| I
|
| R/A/C/I
|
|
|
|
| R/A/I
| I
|
|-
| Processing of Requests
| R/A/C/I
| R/A/C/I
|
|
|
|
|
|
|
| R/A/I
|
|-
| Enforcement of Blacklisting & Bans
| R/A/C/I
| R/A/C/I
|
|
|
|
|
|
|
| R/A/I
| R/I
|-
| Supporting IRC users with queries
| R/A/C/I
| R/A/C/I
|
|
|
|
|
|
|
| R/A/I
| R/I
|-
| Responding to email queries or requests
| R/A/C/I
| R/A/C/I
|
|
|
|
|
|
|
| R/A/I
|
|}

Main Page

2022-02-13T20:16:07Z

Russell: /* Useful Links & Information */ Change Terms of Service link to the shorter and more memorable version

[[File:Logo.png]]

== Welcome to BNC4FREE ==
Welcome to BNC4FREE Wiki. This is the place where you can find information regarding our IRC (Internet Relay Chat) Bouncers and how to use them.

Were still writing much of the documentation here at the moment bit if you think we have missed something or need to edit something, let us know by emailing our [mailto:support@bnc4free.com support] team and we will endeavor to update the wiki accordingly. At some point in the near future, we will allow users to request access to the wiki to make updates and keep our pages up to date.

== Useful Links & Information ==
* [[Frequently_Asked_Questions|Frequently Asked Questions]]
* [[Connect|How to Connect]]
* [https://bnc4free.com/?page_id=63 Known & Prohibited Networks]
* [[:Category:Modules|Module Documentation]]
* [https://bnc4free.com/?page_id=23 Official Networks]
* [[Request|How to Request]]
* [https://bnc4free.com/terms Terms of Service]

== Follow us on Social Media ==

We regularly use Social Media as well as the IRC Channels on our [https://bnc4free.com/?page_id=23 Official Networks] to post updates and other important information. You can follow us on:

* [https://bnc4free.com/facebook Facebook]
* [https://bnc4free.com/twitter Twitter]
* [https://bnc4free.com/reddit Reddit]

MediaWiki:Sidebar

2022-02-13T20:14:27Z

Russell: Change Terms of Service Link to the shorter and more memorable version

Frequently Asked Questions

2021-07-12T18:20:29Z

Russell: Repair the page

More often that not we are frequently asked the same questions or similar questions by a large number of users or those that are interested in our service. This FAQ will hopefully answer many of the common questions that you may have relating to your IRC Bouncer. We have split these into sections which can be quickly navigated to using the contents section below.

= General =

This section relates to questions that are generic to the service and don't fall into any other category.

== Is this service free and will I ever have to pay for anything? ==

This service is 100% free and we intend to be able to keep it this way for as long as possible. We do not ask or force anyone to pay for our service but if you would like to contribute, it is possible to donate. Information on this can be found on our [https://bnc4free.com/?page_id=35 Donation Page].

== I need an IRC Bouncer for my IRC Bot, is this possible? ==

In theory yes this is possible as long as the bot complies with our [https://bnc4free.com/?page_id=10 Terms of Service] however you do need to be aware that as your bots features are client side, they will not work when the bot disconnects from the IRC Bouncer.

= Requesting =

This section relates to questions that have been asked regarding requesting an IRC Bouncer and the process involved.

== How do I request an IRC Bouncer ==

In order to request an IRC Bouncer, you will need to join the #bnc4free on one of the networks we have a service bot operating in. These networks are listed on our [https://bnc4free.com/?page_id=23 Official Networks] list and we have linked each network to the webchat to make it easier.

Once you have joined the channel, you will need to request your bouncer using the ‘!request’ command in the channel. You will be asked to fill in the following fields:

{| class="wikitable"
|- style="font-weight:bold;"
! Field
! Description
! Example Value
|-
| Username
| This will be the username that you will use to login to the bouncer. Please note that this doesn't have to be your nickname, realname or anything you would normally use on IRC as you'll be able to set these up in your account once it has been accepted
| MyUsername
|-
| Email Address
| The email address that we will send your details to once the request has been processed. Please note as per our Terms of Service, this must not be a disposable email address.
| its.me@example.com
|-
| IRC Server
| The IRC Server that you wish to be connected to. Note that this must not a network listed under "Prohibited Networks" on our [https://bnc4free.com/?page_id=63 known and prohibited networks] list
| irc.libera.chat
|-
| IRC Port
| The IRC Port that will be used to connect to the IRC Server. (Typically 6667, or +6697 for SSL)
| +6697
|}

The command you will enter in the IRC Channel should look like the following:

Once you have entered this into the channel, you will be sent an email containing a verification code of which also must be entered onto IRC in order to validate your email address. The command you need to enter will typically look like the example below:
!verify 0e12c4544ddff0b3e9a0b5c984d19de0

Once you have completed this, your request is officially pending review from the staff team. You will receive an email when the request has been accepted or rejected.

== I don't want everyone to see my email address/request. Can i request privately? ==

Absolutely, You can join the channel ##bnc4free on the [https://webchat.esper.net/ Espernet] or [https://web.libera.chat/?nick=BNC-?&channel=#bnc4free LiberaChat] network where the channels are moderated so that only our staff team and our services bot can see your request.

== Is it possible to request by email? ==

At this time, it is not possible as we are working on a system that will be able to read the emails sent in a specific format and automatically input the data into our request system. We will update you once we have this up and running!

== I haven't received an email with a verification to verify my request. Can you resend it? ==

We are able to resend the verification email to you so that you can verify you're request but this can only be resent to the email you requested with initially. We will not send the email to an alternative address. Please also ensure that you have checked all your email folders (not just Inbox, Junk, Deleted etc...) as in some cases it is possible that an email filter may have placed the message elsewhere. If you are unable to locate the email, please feel free to email [mailto:support@bnc4free.com support] or poke us in #bnc4free on one of our [https://bnc4free.com/?page_id=23 Official Networks] and we'll resend it for you.

== How long does it take for my request to be processed? ==

We aim to have processed requests within 24 to 48 hours of the request being email verified. In some cases this is not always possible to due bank holidays such as Christmas and other events. In rare circumstances we may take considerably longer to process a request if we believe that the bouncer may be used for abuse as we often check with networks if this is the case. If we haven't processed your request within 72 hours, please feel free to email [mailto:support@bnc4free.com support] or poke us in #bnc4free on one of our [https://bnc4free.com/?page_id=23 Official Networks] and we'll look into it.

== How can I request/add more networks to my account? ==

Each account can currently have up to 3 networks. Usually this will be the network you initially requested when your account was setup and 2 additional networks. To request additional networks you will need to join the #bnc4free channel on one of the networks we have a service bot operating in. These networks are listed on our [https://bnc4free.com/?page_id=23 Official Networks] list and we have linked each network to the webchat to make it easier.

Once you have joined the channel, you will need to request your bouncer using the ‘!network request’ command in the channel. You will be asked to fill in the following fields:

{| class="wikitable"
|- style="font-weight:bold;"
! Field
! Description
! Example Value
|-
| Username
| This will be the username of the account you have with us
| MyUsername
|-
| IRC Server
| The IRC Server that you wish to be connected to. Note that this must not a network listed under "Prohibited Networks" on our [https://bnc4free.com/?page_id=63 known and prohibited networks] list and cannot be a network that you already have on your account
| irc.rizon.net
|-
| IRC Port
| The IRC Port that will be used to connect to the IRC Server. (Typically 6667, or +6697 for SSL)
| +6697
|}

The command you will enter in the IRC Channel should look like the following:
!network request MyUsername irc.rizon.net +6697

Once you have entered this into the channel, you will be sent an email containing a verification code of which also must be entered onto IRC in order to validate that it is the account owner that has requested the additional network. The command you need to enter will typically look like the example below:
!network verify 0e12c4544ddff0b3e9a0b5c984d19de0

Once you have completed this, your network request is officially pending review from the staff team. You will receive an email when the request has been accepted or rejected.

== I have mistyped my email address when I made the request what should I do? ==

Send the request again using the <code>request</code> command and the correct email address. Your pending request with the incorrect email address will automatically expire within 7 days if not verified and will not prevent you from being accepted for an account.

= Accounts =

This section relates to questions about your account and the various configuration settings.

== I have forgotten my password, How can I get it reset? ==

If you have forgotten your password and need this to be reset, Please ask us to reset it in the channel #bnc4free on one of our [https://bnc4free.com/?page_id=23 Official Networks] or send us an email from the email address you used for your account to [mailto:support@bnc4free.com support]. Please note if you are requesting a reset on IRC, we will send you an email so that we can confirm you are the account holder.

== I have configured Allowed Hosts and no longer have access to the hosts I specified, How can i get this fixed? ==

If you have misconfigured the 'Allowed Hosts' setting in your account or no longer have access to the addresses you have configured there, Please ask us to reset your allowed hosts in the channel #bnc4free on one of our [https://bnc4free.com/?page_id=23 Official Networks] or send us an email from the email address you used for your account to [mailto:support@bnc4free.com support].

== How can I change my realname, ident or nickname? ==

If you run /whois on your own nickname, it should look something like this:

[''MyNickname''] ('''ident'''@some.host.name): '''''My Realname'''''
[''MyNickname''] irc.server.network :Some IRC Server
[''MyNickname''] End of WHOIS list.

To change your realname, nickname or ident permanently on a network so that the values are set if you reconnect to the IRC Network, you will need to load the controlpanel module using the following command:
/msg *status loadmod controlpanel

Once the module is loaded, to change your ''nickname'' use the following:
/msg *controlpanel setnetwork nick $user $network ''MyNewNickname''
Replacing ''MyNewNickname'' with the nickname of your choice. You can also change your nick while connected to the network using:
/nick ''MyNewNickname''

To change your '''ident''' use the following:
/msg *controlpanel setnetwork ident $user $network '''MyNewIdent'''
Replacing '''MyNewIdent''' with the ident of your choice. Once it has been set, you will need to reconnect to the IRC network using:
/msg *status jump

To change your '''''realname''''' use the following:
/msg *controlpanel setnetwork realname $user $network '''''MyNewRealName'''''
Replacing '''''MyNewRealName''''' with the realname of your choice. Once it has been set, in a majority cases you will need to reconnect to the IRC network using:
/msg *status jump
On some networks you may be able to set your realname to the new realname until you next reconnect to IRC by using:
/setname '''''MyNewRealName'''''

These settings can also be changed via the [https://panel.bnc4free.com/ webpanel]

== How can i change my password? ==

You can change your password by using the [https://panel.bnc4free.com/ webpanel] or by using the [[Module:controlpanel|controlpanel]] module. To change your password using the module, use the following command:
/msg *controlpanel Set password <new password>

<div id="Reset_By_Peer"></div>
== I keep getting the message "Connection reset by peer" ==

This error usually occurs when you try to connect to the SSL port of the bouncer (1339). On most clients, you '''must''' use port '''+1339''', including the plus before the port number in order to use SSL. Some other clients do not require the plus before the port to be specified but may have a tickbox if using a client such as [[Connect:HexChat|HexChat]] which needs to be ticked to enable SSL or a <code>-ssl</code> or <code>-tls</code> command line argument if using a client such as [[Connect:irssi|Irssi]].

You can find out how to connect using SSL for your client [[Connect|here]]

<div id="Reconnecting_Too_Fast"></div>
== I keep getting the message "Closing Link: [Please try again later - reconnecting too fast]" ==

This means exactly what it says in the message, you are reconnecting too fast. This is normally triggered by 3 failed logins within 1 minute and when triggered will prevent you from authenticating to the bouncer for 5 minutes. This can also be triggered if your host is listed on a DNS Blacklist or your account has been disabled as these are classed as failed logins.

<div id="Listed_On_DNSBL"></div>
== I keep getting the message "Closing Link: [Your host is listed on (DNSBL Name). Please visit (DNSBL Link) for further information]" ==

Unfortunately this means that the IP address you are using is listed in one of the many DNS Blacklists that our bouncer users. The reason that the IP/Host is blacklisted usually means the IP is a proxy, vpn, TOR exit node, exploitable host or has been used for abuse at some point. We do not have any control over IP's that are added to the DNS blacklist. You may be able to request removal of the IP from the DNS Blacklist by following the DNS Blacklist link displayed in the message.

<div id="Account_Disabled"></div>
== I am getting the message "Closing Link: [Your account has been disabled. (Reason: (a reason))]" ==

This message means that your account has been disabled and normally means that you have violated the Terms of Service. A brief reason for why the account has been disabled is usually given in the message. For further information on why your account has been disabled or to have the account re-enabled should you feel that this is a mistake, you will need to email our [mailto:support@bnc4free.com Support Team]

<div id="Session_Error"></div>
== When I try to access the webpanel, I get the error "Access Denied - This session does not belong to your IP." ==

This normally means that you are trying to access the web panel from a web browser you have used before but your IP address in the meantime has changed. This most commonly occurs with users who have a dynamic ip or when your using a portable device that connects to different wireless access points or mobile networks. To resolve the issue, you will need to clear your cookies. Further information can be found below:
* [https://support.mozilla.org/en-US/kb/clear-cookies-and-site-data-firefox#w_clear-cookies-for-the-current-website Clear Cookies on Firefox]
* [https://support.mozilla.org/en-US/kb/clear-browsing-history-firefox-ios#w_clear-individual-site-data Clear Cookies on Firefox (Mobile Devices)]
* [https://support.google.com/chrome/answer/95647 Clear Cookies on Chrome]
* [https://support.google.com/accounts/answer/32050?co=GENIE.Platform%3DAndroid Clear Cookies on Chrome (Mobile & Android Devices)]
* [https://support.google.com/accounts/answer/32050?co=GENIE.Platform%3DiOS Clear Cookies on Chrome (iPhone & iPad Devices)]
* [https://support.microsoft.com/en-us/microsoft-edge/delete-cookies-in-microsoft-edge-63947406-40ac-c3b8-57b9-2a946a29ae09 Clear Cookies on Microsoft Edge]
* [https://support.microsoft.com/en-us/topic/delete-and-manage-cookies-168dab11-0753-043d-7c16-ede5947fc64d Clear Cookies on Internet Explorer]
* [https://support.apple.com/en-gb/HT201265 Clear Cookies on Safari (iPhone & iPad)]

<div id="The_connection_was_reset"></div>

== When I try to access the webpanel, I get the error "The connection was reset" ==

This normally happens if you have tried to access the webpanel using HTTP (rather than HTTPS) on the bouncers SSL Port. The bouncers web panels can only be accessed in the following ways:

* Bouncer Non-HTTPS¹: <nowiki>http://servername.bnc4free.com:1337/</nowiki>
* Bouncer HTTPS¹: <nowiki>https://servername.bnc4free.com:1339/</nowiki>
* Generic Webpanel²: https://panel.bnc4free.com/

¹ <span style="font-size:88%">Replace "servername" with the relevant server name (e.g apple)</span><br/>
² <span style="font-size:88%">Logs in to the selected server name using HTTPS</span>

== I'm going to be away for a while, will my account be deleted? ==

Generally, your account should be fine and will remain if you are aware for a period of time however if you will be away for 60 days or more, your account will be removed in accordance with our inactive accounts policy mentioned in our [https://bnc4free.com/?page_id=10 Terms of Service]. Your account will only be deleted if there have been no logins during that period, logging in for even a few minutes once in the 60 day period is sufficient enough for the account to be considered active.

'''Note:''' If your account is on one the more popular networks (Freenode, LiberaChat, Rizon, EFNet, IRCNet etc...), the account is normally deleted after 30 days of inactivity rather than 60 days.

If you plan to be away more than 60 days (or 30 days for popular networks) and IRC access will not be possible, please let our [mailto:support@bnc4free.com Support Team] know and we will ensure that the account is not removed prior to your return.

== What is the maximum number of lines the bouncer can keep in its channel or query buffer? ==

Our bouncers are currently set to keep a maximum of 1000 lines for each channel and query you receive while away. Buffers for individual channels, all channels and queries can be changed via the [https://panel.bnc4free.com/ webpanel] or using the [[Module:controlpanel|controlpanel]] module.

Request

2021-06-12T19:09:39Z

Russell: /* Frequently Asked Questions */ Freenode replaced with LiberaChat due to recent widely known issues

Requesting an IRC Bouncer from us is easy and simple provided that you fill in the required fields and provide the necessary details accurately and correctly so we can set-up your account. By following the steps on this page, you will be able to successfully request a bouncer with us.

== How to Request an Account ==

In order to request an IRC Bouncer, you will need to join one of our IRC Channels. To do this, choose a network from our Official Network List, connect to the network and join the channel “#bnc4free”.

Once you have done this, you will need to type <code>!request</code> in the channel. You will be asked to fill in the following fields:

* Username – This is the username that you will use to login and authenticate to the bouncer.
* Email Address – This is the email address that we will send details to when your request is accepted.
* IRC Server – This is the IRC server address that you will want the bouncer to connect to. (e.g: irc.efnet.org). You can add more servers after you’re request has been accepted. More details on this soon
* IRC Port – This is the IRC port that you usually connect to on the server which is usually 6667. For SSL Ports please prefix the port with a “+” (e.g: 6667 – SSL e.g: +6697)

The command you will enter in the IRC Channel should then look like
!request someusername myemail@example.com irc.test.net 6667
Once you have entered this into the channel, you will be sent an email containing a verify code of which must be entered onto IRC or can be entered on the [https://bnc4free.com/?page_id=715 Verify your Email] page in order to validate your email address.

When you have verified your email address, your request is officially pending review from the staff team. You can check the status of your request on the [https://bnc4free.com/check Check Your Request] page or by using the following command on IRC:

!check [username/request id]

You will receive an email from us when the request has been accepted or rejected.

== How to Request Additional Networks for Your Account ==

If you already have an account with us, you can request up to 2 additional networks to be added to your account (bringing the total to 3 on your account). To do this, choose a network from our Official Network List, connect to the network and join the channel “#bnc4free”.

Once you have done this, you will need to type <code>!network request</code> in the channel. You will be asked to fill in the following fields:

* Username – This is the username that you will use to login and authenticate to the bouncer.
* IRC Server – This is the IRC server address that you will want the bouncer to connect to. (e.g: irc.efnet.org). You can add more servers after you’re request has been accepted. More details on this soon
* IRC Port – This is the IRC port that you usually connect to on the server which is usually 6667. For SSL Ports please prefix the port with a “+” (e.g: 6667 – SSL e.g: +6697)

The command you will enter in the IRC Channel should then look like
!network request someusername irc.test.net 6667
Once you have entered this into the channel, you will be sent an email containing a code of which must be entered onto IRC or can be entered on the [https://bnc4free.com/?page_id=715 Verify your Email] page in order to validate that you have requested the new network for your account.

When you have verified your email address, your network request is officially pending review from the staff team. You can check the status of your request by using the following command on IRC:
!network check [request id]
You will receive an email from us when the request has been accepted or rejected.

== Frequently Asked Questions ==

=== I don’t want everyone to see my request or email address, Can i request privately? ===

Yes. You can join ##bnc4free on Espernet and LiberaChat where the channels are moderated so that only our staff team and our services bot can see your messages.

=== Can i request by email? ===

At this time, it is not possible as we are working on a system that will be able to read the emails sent in a specific format and automatically input the data into our request system. We will update you once we have this up and running!

=== When will my request be accepted? ===

At present, we will be able to process requests within 24 to 48 hours of your request. In most cases it will take less time for us to process your request.
If you request has not been processed within 48 hours, please contact our [mailto:support@bnc4free.com support team] quoting your username or request ID and we will look into this.

API:Network/TrustedFP/Add

2021-05-26T17:21:14Z

Russell: Replace references to Freenode

== Resource URI ==
https://api.bnc4free.com/network/trustedfp/add
== Parameters ==
{| class="wikitable"
! style="font-weight:bold;" | Variable
! style="font-weight:bold;" | Required
! style="font-weight:bold;" | Description
! style="font-weight:bold;" | Example
|-
| server
| required
| The name of the server
| Apple
|-
| username
| required
| Your Username
| TestyTest
|-
| key
| required
| Your API Key
| d681883383bcf7963427b1629d0b9963cf6335b5
|-
| network
| required
| The name of the network that requires the fingerprint adding
| LiberaChat
|-
| fp
| required
| The trusted fingerprint to be added for the network
| ec:6f:7a:15:4a:e8:e9:b2:aa:fc:1f:f4:22:9d:4c:2e:90:80:3c:ec:04:25:e2:04:99:2c:3a:ef:5e:13:dc:a6
|-
| user
| optional
| '''(Staff Only)''' The username of the person of whom needs the fingerprint adding to the network
| AnotherTestyTest
|}

== Example Request ==

curl -XPOST
--url https://api.bnc4free.com/network/trustedfp/add
-d server=Apple
-d username=TestyTest
-d key=d681883383bcf7963427b1629d0b9963cf6335b5
-d network=LiberaChat
-d fp=ec:6f:7a:15:4a:e8:e9:b2:aa:fc:1f:f4:22:9d:4c:2e:90:80:3c:ec:04:25:e2:04:99:2c:3a:ef:5e:13:dc:a6

== Example Response ==
{
"status" : "success",
"username" : "TestyTest",
"trustedfps" : {
"ec:6f:7a:15:4a:e8:e9:b2:aa:fc:1f:f4:22:9d:4c:2e:90:80:3c:ec:04:25:e2:04:99:2c:3a:ef:5e:13:dc:a6"
}
}

[[Category:API_Functions]]

API:Network/Info

2021-05-26T17:20:48Z

Russell: Replace references to Freenode

== Resource URI ==
https://api.bnc4free.com/network/info
== Parameters ==
{| class="wikitable"
! style="font-weight:bold;" | Variable
! style="font-weight:bold;" | Required
! style="font-weight:bold;" | Description
! style="font-weight:bold;" | Example
|-
| server
| required
| The name of the server
| Apple
|-
| username
| required
| Your Username
| TestyTest
|-
| key
| required
| Your API Key
| d681883383bcf7963427b1629d0b9963cf6335b5
|-
| network
| required
| The name of the network you wish to retrieve the information of
| LiberaChat
|-
| username
| optional
| '''(Staff Option)''' The username to retrieve information for
| AnotherTestyTest
|}

== Example Request ==

curl -XPOST
--url https://api.bnc4free.com/network/info
-d server=Apple
-d username=TestyTest
-d network=LiberaChat
-d key=d681883383bcf7963427b1629d0b9963cf6335b5

== Example Response ==
{
"LiberaChat" : {
"ident" : "test",
"trustedfps" : [],
"trustallcerts" : true,
"floodprotect" : {
"enabled" : true,
"joindelay" : 0,
"floodburst" : 9,
"floodrate" : 2
},
"ircaway" : false,
"connected" : true,
"realname" : "TestyTest",
"manageservers" : false,
"trustpki" : true,
"vhost" : "10.0.0.6",
"nickname" : "TestyTest",
"quitmsg" : "Goodbye dear friends",
"usermask" : "TestyTest!test@my.host.name",
"alternate" : "TestTesty",
"name" : "LiberaChat",
"irc.libera.chat" : {
"host" : "irc.libera.chat",
"port" : 6667,
"password" : "",
"current" : true
},
"modules" : {
"modules_online" : {
"loaded" : false,
"description" : "Makes ZNC's *modules to be \"online\".",
"name" : "modules_online"
},
"autoreply" : {
"name" : "autoreply",
"description" : "Reply to queries when you are away",
"loaded" : false
},
"log" : {
"loaded" : false,
"description" : "Writes IRC logs.",
"name" : "log"
},
"stickychan" : {
"loaded" : false,
"description" : "configless sticky chans, keeps you there very stickily even",
"name" : "stickychan"
},
"buffextras" : {
"loaded" : true,
"name" : "buffextras",
"description" : "Adds joins, parts etc. to the playback buffer"
},
"sasl" : {
"loaded" : false,
"description" : "Adds support for sasl authentication capability to authenticate to an IRC server",
"name" : "sasl"
},
"kickrejoin" : {
"loaded" : false,
"description" : "Autorejoins on kick",
"name" : "kickrejoin"
},
"block_motd" : {
"name" : "block_motd",
"description" : "Block the MOTD from IRC so it's not sent to your client(s).",
"loaded" : false
},
"alias" : {
"description" : "Provides bouncer-side command alias support.",
"name" : "alias",
"loaded" : false
},
"perform" : {
"description" : "Keeps a list of commands to be executed when ZNC connects to IRC.",
"name" : "perform",
"loaded" : true
},
"keepnick" : {
"name" : "keepnick",
"description" : "Keeps trying for your primary nick",
"loaded" : false
},
"autovoice" : {
"description" : "Auto voice the good people",
"name" : "autovoice",
"loaded" : false
},
"cert" : {
"loaded" : false,
"name" : "cert",
"description" : "Use a ssl certificate to connect to a server"
},
"raw" : {
"loaded" : false,
"name" : "raw",
"description" : "View all of the raw traffic"
},
"q" : {
"loaded" : false,
"name" : "q",
"description" : "Auths you with QuakeNet's Q bot."
},
"away" : {
"description" : "This module will automatically set you away on IRC while you are disconnected from the bouncer.",
"name" : "away",
"loaded" : false
},
"route_replies" : {
"loaded" : false,
"description" : "Send replies (e.g. to /who) to the right client only",
"name" : "route_replies"
},
"autoop" : {
"description" : "Auto op the good people",
"name" : "autoop",
"loaded" : false
},
"autocycle" : {
"loaded" : false,
"name" : "autocycle",
"description" : "Rejoins channels to gain Op if you're the only user left"
},
"modtcl" : {
"name" : "modtcl",
"description" : "Loads Tcl scripts as ZNC modules",
"loaded" : false
},
"nickserv" : {
"description" : "Auths you with NickServ (prefer SASL module instead)",
"name" : "nickserv",
"loaded" : false
},
"chansaver" : {
"name" : "chansaver",
"description" : "Keeps config up-to-date when user joins/parts.",
"loaded" : false
},
"stripcontrols" : {
"name" : "stripcontrols",
"description" : "Strips control codes (Colors, Bold, ..) from channel and private messages.",
"loaded" : false
},
"autoattach" : {
"name" : "autoattach",
"description" : "Reattaches you to channels on activity.",
"loaded" : false
},
"watch" : {
"loaded" : false,
"name" : "watch",
"description" : "Copy activity from a specific user into a separate window"
}
},
"autoconnect" : true,
"clientsconnected" : 0,
"attached" : false,
"clients" : [],
"clientencoding" : ""
},
"status" : "success",
"username" : "TestyTest"
}

[[Category:API_Functions]]

API:Network/TrustedFP/Delete

2021-05-26T17:19:56Z

Russell: Replace references to Freenode

== Resource URI ==
https://api.bnc4free.com/network/trustedfp/delete
== Parameters ==
{| class="wikitable"
! style="font-weight:bold;" | Variable
! style="font-weight:bold;" | Required
! style="font-weight:bold;" | Description
! style="font-weight:bold;" | Example
|-
| server
| required
| The name of the server
| Apple
|-
| username
| required
| Your Username
| TestyTest
|-
| key
| required
| Your API Key
| d681883383bcf7963427b1629d0b9963cf6335b5
|-
| network
| required
| The name of the network that the fingerprint is to be deleted from
| LiberaChat
|-
| fp
| required
| The trusted fingerprint to be deleted from the network
| ec:6f:7a:15:4a:e8:e9:b2:aa:fc:1f:f4:22:9d:4c:2e:90:80:3c:ec:04:25:e2:04:99:2c:3a:ef:5e:13:dc:a6
|-
| user
| optional
| '''(Staff Only)''' The username of the user that has the network and requires the deletion of the fingerprint
| AnotherTestyTest
|}

== Example Request ==

curl -XPOST
--url https://api.bnc4free.com/network/trustedfp/delete
-d server=Apple
-d username=TestyTest
-d key=d681883383bcf7963427b1629d0b9963cf6335b5
-d network=LiberaChat
-d fp=ec:6f:7a:15:4a:e8:e9:b2:aa:fc:1f:f4:22:9d:4c:2e:90:80:3c:ec:04:25:e2:04:99:2c:3a:ef:5e:13:dc:a6

== Example Response ==
{
"status" : "success",
"username" : "LiberaChat",
"trustedfps" : {
"ec:6f:7a:15:4a:e8:e9:b2:aa:fc:1f:f4:22:9d:4c:2e:90:80:3c:ec:04:25:e2:04:99:2c:3a:ef:5e:13:dc:a6"
}
}

[[Category:API_Functions]]

API:Network/Server/Add

2021-05-26T17:19:02Z

Russell: Replace references to Freenode

== Resource URI ==
https://api.bnc4free.com/network/server/add
== Parameters ==
{| class="wikitable"
! style="font-weight:bold;" | Variable
! style="font-weight:bold;" | Required
! style="font-weight:bold;" | Description
! style="font-weight:bold;" | Example
|-
| server
| required
| The name of the server
| Apple
|-
| username
| required
| Your Username
| TestyTest
|-
| key
| required
| Your API Key
| d681883383bcf7963427b1629d0b9963cf6335b5
|-
| network
| required
| The name of the network to be added
| LiberaChat
|-
| ircserver
| required
| The IRC server to be added to the network
| irc.libera.chat
|-
| ircport
| required
| The IRC port to be added to the network that corresponds with the server to be added
| +6697
|-
| ircpassword
| optional
| The IRC password that may be required to connect to the server being added
| password123
|-
| user
| optional
| '''(Staff Only)''' The username to add a server to a network for
| AnotherTestyTest
|}

== Example Request ==

curl -XPOST
--url https://api.bnc4free.com/network/server/add
-d server=Apple
-d username=TestyTest
-d key=d681883383bcf7963427b1629d0b9963cf6335b5
-d network=LiberaChat
-d ircserver=irc.libera.chat
-d ircport=+6697

== Example Response ==
{
"status" : "success",
"LiberaChat" : {
"irc.libera.chat" : {
"host" : "irc.libera.chat",
"port" : "+6697",
"password" : ""
}
},
"networks" : "LiberaChat"
}

[[Category:API_Functions]]

API:User/Network/Add

2021-05-26T17:18:02Z

Russell: Replace references to Freenode

== Resource URI ==
https://api.bnc4free.com/user/network/add
== Parameters ==
{| class="wikitable"
! style="font-weight:bold;" | Variable
! style="font-weight:bold;" | Required
! style="font-weight:bold;" | Description
! style="font-weight:bold;" | Example
|-
| server
| required
| The name of the server
| Apple
|-
| username
| required
| Your Username
| TestyTest
|-
| key
| required
| Your API Key
| d681883383bcf7963427b1629d0b9963cf6335b5
|-
| network
| required
| The name of the network to be added
| LiberaChat
|-
| username
| optional
| '''(Staff Only)''' The username to add a network to
| AnotherTestyTest
|-
| vhost
| optional
| '''(Staff Only)''' The IP/Vhost that the user will use when connecting to the IRC Network
| 10.0.0.6
|}

== Example Request ==

curl -XPOST
--url https://api.bnc4free.com/user/network/add
-d server=Apple
-d username=TestyTest
-d key=d681883383bcf7963427b1629d0b9963cf6335b5
-d network=LiberaChat

== Example Response ==
{
"status" : "success",
"username" : "TestyTest",
"networks" : "LiberaChat"
}

[[Category:API_Functions]]

API:Network/Server/Delete

2021-05-26T17:17:29Z

Russell: /* Example Response */ Replace references to Freenode

== Resource URI ==
https://api.bnc4free.com/network/server/delete
== Parameters ==
{| class="wikitable"
! style="font-weight:bold;" | Variable
! style="font-weight:bold;" | Required
! style="font-weight:bold;" | Description
! style="font-weight:bold;" | Example
|-
| server
| required
| The name of the server
| Apple
|-
| username
| required
| Your Username
| TestyTest
|-
| key
| required
| Your API Key
| d681883383bcf7963427b1629d0b9963cf6335b5
|-
| network
| required
| The name of the network to be added
| LiberaChat
|-
| ircserver
| required
| The IRC server to be deleted from the network
| irc.libera.chat
|-
| ircport
| required
| The IRC port that corresponds with the server to be deleted
| +6697
|-
| ircpassword
| optional
| The IRC password that was added with the server (if any)
| password123
|-
| user
| optional
| '''(Staff Only)''' The username to delete a server from a network for
| AnotherTestyTest
|}

== Example Request ==

curl -XPOST
--url https://api.bnc4free.com/network/server/delete
-d server=Apple
-d username=TestyTest
-d key=d681883383bcf7963427b1629d0b9963cf6335b5
-d network=LiberaChat
-d ircserver=irc.libera.chat
-d ircport=+6697

== Example Response ==
{
"status" : "success",
"username" : "TestyTest",
"LiberaChat" : {
"irc.libera.chat" : {
"host" : "irc.libera.chat",
"port" : "+6697",
"password" : ""
}
},
"networks" : "LiberaChat"
}

[[Category:API_Functions]]

API:Network/Server/Delete

2021-05-26T17:17:06Z

Russell: Replace references to Freenode

API:User/Network/Delete

2021-05-26T17:16:07Z

Russell: Replace references to Freenode

== Resource URI ==
https://api.bnc4free.com/user/network/delete
== Parameters ==
{| class="wikitable"
! style="font-weight:bold;" | Variable
! style="font-weight:bold;" | Required
! style="font-weight:bold;" | Description
! style="font-weight:bold;" | Example
|-
| server
| required
| The name of the server
| Apple
|-
| username
| required
| Your Username
| TestyTest
|-
| key
| required
| Your API Key
| d681883383bcf7963427b1629d0b9963cf6335b5
|-
| network
| required
| The name of the network to be added
| LiberaChat
|-
| username
| optional
| '''(Staff Only)''' The username to delete the network from
| AnotherTestyTest
|}

== Example Request ==

curl -XPOST
--url https://api.bnc4free.com/user/network/delete
-d server=Apple
-d username=TestyTest
-d key=d681883383bcf7963427b1629d0b9963cf6335b5
-d network=LiberaChat

== Example Response ==
{
"status" : "success",
"username" : "TestyTest",
"networks" : "LiberaChat"
}

[[Category:API_Functions]]

Connect:mIRC

2021-05-26T17:13:47Z

Russell: /* Connecting */ Replace references to Freenode

= Connecting with mIRC =

This guide will tell you how to connect to our bouncers using the mIRC Client which is available at [https://www.mirc.com/get.html https://www.mirc.com/get.html].

For the purposes of this guide, we have used '''[https://www.mirc.com/get.html mIRC v7.61]'''

Please see notes regarding SSL [[Connect:mIRC#Notes_Regarding_SSL|here]]

== Configuration ==

mIRC needs to be configured to connect to our bouncer, so to do this we need to bring up the "Server List". If this hasn't appeared automatically when starting mIRC, navigate to "File -> Select Server...". You should be presented with a window, on this window press the "Add" button and you should see something like this:

[[File:Mirc-serverlist-blank.png|500px|Screenshot of mIRC's server options]]

The options in this window need to be configured/changed as follows:

{| class="wikitable"
! style="font-weight:bold;" | Option
! style="font-weight:bold;" | Description
! style="font-weight:bold;" | Value / Recommended Value
|-
| Description
| The name of the server that will be added (Can be anything)
| MyBouncer
|-
| Address
| The server that your account has been added to (i.e apple.bnc4free.com)
| <server>.bnc4free.com
|-
| Ports
| Port 1337 for Non-SSL / Port +1339 for SSL (Don't forget the '+')
| +1339
|-
| Group
| The name of the server that will be added (Can be anything).
Note: By setting this, you will be able to use ''"/server [ChosenName]"'' to connect
| Bouncers
|-
| Password
| This must be the username and password you use to authenticate to the bouncer

OR

This must be the username, password and network name you use to authenticate to the bouncer
| MyUsername:MyPassword

OR

MyUsername/Network:MyPassword
|-
| Login Method
| This is the login method mIRC will use to authenticate to the bouncer.
Selecting 'None' is sufficient enough to send PASS to authenticate to the bouncer
| None
|}

Once completed, the window should look like this:

[[File:Mirc-serverlist-filled.png|500px|Screenshot of mIRC's server options]]

Press "OK" on the "Add Server" window and "OK" on the server list (mIRC Options) window.

== Connecting ==

If you have added the bouncer to the Server List as outlined in the steps above, assuming that you have set a group a name, you will be able to connect using the following command:
/server [GroupName]
''Replacing [GroupName] with the Group name you set up in the steps above''

Alternatively you can navigate to "File -> Select Server..." and double click the network you have added. This should bring up a window as shown below:

[[File:Mirc-options-window.png|300px|Screenshot of the mIRC options window]]

Press "Connect" on this window to connect to the bouncer.

You can also manually connect to your bouncer should you need to by using one of the following commands in mIRC's server window.
/server <server>:<port> <username>:<password>
or
/server <server>:<port> <username>/<network name>:<password>

Examples of this are shown below:
/server apple.bnc4free.com:+1339 TestOne:foo
or
/server apple.bnc4free.com:+1339 TestOne/LiberaChat:foo

== Notes Regarding SSL ==

Older versions of mIRC did not support SSL natively and therefore require you to have the [http://www.openssl.org/ Open SSL] libraries installed in order for it work. You will know if your version of mIRC does not support SSL if you recieve the following message while connecting to an SSL Port.

[12:34:56] SSL Error: SSL not available

If this is the case, either update mIRC to the [https://www.mirc.com/get.html latest version] or install the [http://www.openssl.org/ Open SSL] libraries required.

=== Where do I install the OpenSSL library? ===
You will need to install it either in the mIRC folder (typically C:\Program Files\mIRC or C:\Program Files (x86)\mIRC) or in the Windows System folder (typically C:\Windows\System32).

If you install it in the mIRC folder, OpenSSL will be usable only by mIRC.

If you install it in the Windows System folder, OpenSSL will be usable by all applications.

=== Steps after OpenSSL is installed ===

After installing OpenSSL restart or start mIRC. It should use the OpenSSL library automatically. To confirm whether mIRC has loaded the OpenSSL library, you can open the Options dialog and look in the Connect/Options section to see if the "SSL" button is enabled. You can also confirm if SSL is enabled by running the following:

//echo -a $sslready

Please note that SSL ports whether in a <code>/server</code> command or in the server list '''must''' be prefixed with a '+'. (e.g +1339 and not 1339)

Connect:HexChat

2021-05-26T17:13:20Z

Russell: /* Connecting */ Replace references to Freenode

= Connecting with HexChat =

This guide will tell you how to connect to our bouncers using the Hexchat IRC Client which is available at [https://hexchat.github.io/downloads.html https://hexchat.github.io/downloads.html]. This client can also be downloaded on most variations of linux using the following command:
apt-get install hexchat

For the purposes of this guide, we have used '''[https://hexchat.github.io/downloads.html HexChat 2.14.1]'''

== Configuration ==

HexChat needs to be configured to connect to our bouncer, so to do this we need to bring up the "Network List". If this hasn't appeared automatically when starting HexChat, navigate to "File -> Network List". You should be presented with a window like this:

[[File:Hexchat-networks.png|350px|Screenshot of the HexChat network list while adding a new network ]]

Click the add button and this will add a new entry to the list called "New Network". Double click the new entry and enter a name for your new network (i.e My BNC4FREE Bouncer). After that, hit return and then press the "Edit" button. You should now be presented with a window that looks like the below:

[[File:Hexchat-editnetwork.png|350px|Screenshot of the Hexchat's Edit Network ]]

The options in this window need to be configured/changed as follows:

{| class="wikitable"
! style="font-weight:bold;" | Option
! style="font-weight:bold;" | Description
! style="font-weight:bold;" | Value / Recommended Value
|-
| Server
| The server that your account has been added to (i.e apple.bnc4free.com) including the port number
Port 1337 for Non-SSL / Port 1339 for SSL
| <server>.bnc4free.com/1339
|-
| Connect to selected server only
| There should only be 1 server in the networks list as mentioned above but you can tick this to ensure only this server is connected to
| Checked
|-
| Connect to this network automatically
| This option will automatically connect to the network when you start Hexchat if it is checked
If this is not checked, you will need to manually open the network list and connect.
| Checked
|-
| Use SSL for all servers on this networks
| This option should be checked if you are using Port 1339 (SSL Port)This option should not be checked if you are using Port 1337 (Non-SSL Port)
| Checked
|-
| Accept invalid SSL certificates
| This option should only be checked if you recieve errors while connecting to the bouncer using SSL. (Please let us know if you do)
As of 2020, all our servers have valid SSL certificates that automatically update so this option is not required.
| Not Checked
|-
| Login Method
| This should be set to "Default" which sends the PASS command to Authenticate.
This can alternatively be set to "Server password (/PASS password)" which will authenticate as well.
| Default
|-
| Password
| This must be the username and password you use to authenticate to your bouncer
Alternatively if your account has multiple networks, this must be the username, password and
network name you wish to connect to on your account
| MyUserName:MyPassword
OR
MyUserName/NetworkName:MyPassword
|}

Once completed, press "Close".

== Connecting ==

If you have added the bouncer to the Network List as outlined in the steps above, open the network list using "File -> Network List" and select the network you have created then press the "Connect" button. If you have filled in all the fields correctly, you should now be connected and authenticated successfully to the bouncer.

You can also manually connect to your bouncer should you need to by using one of the following commands in Hexchat's server window.
/server <server> <port> <username>:<password>
or
/server <server> <port> <username>/<network name>:<password>

Examples of this are shown below:
/server apple.bnc4free.com +1339 TestOne:foo
or
/server apple.bnc4free.com +1339 TestOne/LiberaChat:foo

=== Note regarding HexChat Password Bug ===

Hexchat has a bug whereby if your username, client name, network name and password equate to over 86 characters, the password field is truncated and logins to the bouncer will fail. For example, a login of
MyUsername@MyClientName/SomeNetwork:ThisIsMyPasswordAndIWillNotEverForgetItBecauseImCool
will fail and be truncated to
MyUsername@MyClientName/SomeNetwork:ThisIsMyPasswordAndIWillNotEverForgetItBecauseImCo

The easiest work around to this is to use shorter client names or passwords. This has been raised as a bug report and can be viewed [https://github.com/hexchat/hexchat/issues/1296 here]

Connect:irssi

2021-05-26T17:12:44Z

Russell: /* Connecting */ Replace references to Freenode

= Connecting with irssi =

This guide will tell you how to connect to our bouncers using the irssi command line IRC client which is available at [https://irssi.org/download/ https://irssi.org/download/]. This client can also be downloaded on most variations of linux using the following command:
apt-get install irssi

For the purposes of this guide, we have used '''[https://irssi.org/download/ Irssi v1.0.5]'''

== Configuration ==

irssi needs to be configured to connect to our bouncer, so to do this we need to add the network and server. Firstly we need to add a server using the ''"/network add"'' command. The syntax is as follows:
/network add <name>
The network name can be named anything for example "MyNewBouncer"
/network add MyNewBouncer

We then need to add the server to the network using ''"/server add"''. The syntax of the command is as follows:
/server add [options] [server] [port] [username/network:password]

The options that can and need to be used are as follows:

{| class="wikitable"
! style="font-weight:bold;" | Option
! style="font-weight:bold;" | Required
! style="font-weight:bold;" | Description
|-
| -network [network name]
| Required
| This is the name of the network you added using "/network add"
|-
| -auto
| Optional
| If this is specified, irssi will automatically connect to the network whenever it is started
|-
| -noauto
| Optional
| If this is specified, irssi will not automatically connect to the network whenever it is started
|-
| -tls
| Optional
| If this option is specified, you will connect to the bouncer using SSL (Note: Port 1339 must be used)
|-
| -tls_verify
| Optional
| If this option is specified, irssi will verify that our bouncers certificate is valid (Recommended)
|}

Below is an example of the ''"/server add"'' command that will add the bouncer to the network that we have created:

[[File:irssi-serveradd.png|700px|Screenshot of a /server add command in irssi ]]

Once the server has been added. You will be able to connect to the bouncer. See Section Below.

== Connecting ==

If you have added the bouncer to irssi using the above method, you can connect using the following command:
/connect <name>

You can also manually connect to your bouncer should you need to by using one of the following commands:
/server -tls <server> <port> <username>:<password>
or
/server -tls <server> <port> <username>/<network name>:<password>

Examples of this are shown below:
/server -tls apple.bnc4free.com +1339 TestOne:foo
or
/server -tls apple.bnc4free.com +1339 TestOne/LiberaChat:foo

=== Note regarding TLS/SSL ===

You may find that when connecting to the bouncer, you receive several messages in the status window relating to SSL (If you are using the SSL port) that look like the below:
-!- Irssi: Certificate Chain:
-!- Irssi: Subject: CN: apple.bnc4free.com
-!- Irssi: Issuer: C: US, O: Let's Encrypt, CN: Let's Encrypt Authority X3
-!- Irssi: Subject: C: US, O: Let's Encrypt, CN: Let's Encrypt Authority X3
-!- Irssi: Issuer: O: Digital Signature Trust Co., CN: DST Root CA X3
-!- Irssi: Protocol: TLSv1.3 (256 bit, TLS_AES_256_GCM_SHA384)
-!- Irssi: EDH Key: 253 bit Unknown
-!- Irssi: Public Key: 2048 bit RSA, valid from Apr 22 10:17:40 2020 GMT to Jul 21 10:17:40 2020 GMT
-!- Irssi: Public Key Fingerprint: 45:92:4B:89:E5:9F:AD:9D:ED:E9:32:D8:A7:4D:C7:3A:A9:59:DD:56:28:6F:47:C7:56:AB:BB:E5:29:43:F0:1D (SHA256)
-!- Irssi: Certificate Fingerprint: B7:23:B2:E4:BC:D1:AC:7B:FA:70:CB:D7:8D:EF:B8:3F:5F:DC:66:46:14:D0:27:69:DB:98:34:3E:20:17:1E:6D (SHA256)
-!- Irssi: Connection to apple.bnc4free.com established

These messages can be safely ignored or can be disabled completely using the following command:
/set tls_verbose_connect off

ExpandString

2021-05-26T17:12:14Z

Russell: /* Expand Strings */ Replace references to Freenode

Some features support variable-like strings.

=Expand Strings=
{| class="wikitable"
! Variable
! Value
! Sample output
|-
| %user%
| Your bouncer username
| MyUsername
|-
| %nick%
| the current nick that is being used
| MyNickname
|-
| %defnick%
| the default nick, as specified in the config/web panel
| MyNickname
|-
| %altnick%
| the alternate nick, as specified in the config/web panel
| NimNom
|-
| %realname%
| the realname, as specified in the config/web panel
| Bacon Man
|-
| %ident%
| the ident, as specified in the config/web panel
| hello
|-
| %vhost%
| The VHost/Bindhost that has been assigned to your account or network
| 10.0.0.6
|-
| %bindhost%
| The VHost/Bindhost that has been assigned to your account or network
| 10.0.0.6
|-
| %time%
| The current time (can be used for ''CTCP TIME'' replies)
| Mon Jun 15 13:36:08 2020
|-
| %uptime%
| The bouncers uptime
| 1w 2d 4h 20m 27s
|-
| %version%
| The bouncers version string
| fBNC - https://bnc4free.com
|-
| %bnc%
| The bouncers name and website, optionally with version, <br />depending on whether the "Hide version" setting is enabled globally
| fBNC - https://bnc4free.com/
|-
| %empty%
| Empty string, can be used e.g. as a poor man's way to insert %nick% literally, without expanding it to the current nick: <code>%ni%empty%ck%.
|
|-
| %network%
| The name of IRC network as specified in the config/web panel
| LiberaChat
|}

=Features that support expand strings=
Expand strings can be used in various places and on some modules. The following is a list of of the modules that accept expand strings.

; Modules
* [[Module:alias]]
* [[Module:autoattach]]
* [[Module:autoreply]]
* [[Module:away]]
* [[Module:perform]]
* [[Module:watch]]

Expand strings can also be used for:
* CTCP Replies
* Quit Messages
* Realnames

Connect

2021-05-26T17:11:06Z

Russell: /* Most Clients */ Replace references to Freenode

= How to Connect =

This page provides information on how to connect to your IRC Bouncer using an IRC Client.

== Most Clients ==

Most clients come with a "/server" command that can be used to connect. The syntax of the command is usually as follows:
/server <server>:<port> <password>

Below is an example of the "/server" command that would be used to connect the Apple server on the SSL port (1339), authenticate as "TestOne" with the password "foo":

/server apple.bnc4free.com:+1339 TestOne:foo

If the account has multiple networks and you want to attach to a specific network such as "LiberaChat" for example, the command would be as follows:

/server apple.bnc4free.com:+1339 TestOne/LiberaChat:foo

'''Note¹''' Some clients require a space between the server and the port ''(i.e "/server apple.bnc4free.com +1339 ...")''

'''Note²''' Some clients require an ssl option in the "/server" command ''(i.e "/server -ssl apple.bnc4free.com 1339 ...")''

== Specific Clients ==

Information for specific clients can be found using one the links below:

'''Desktop Clients'''
* [[Connect:eMule|eMule]]
* [[Connect:Konversation|Konversation]]
* [[Connect:HexChat|HexChat]]
* [[Connect:irssi|irssi]]
* [[Connect:KVIrc|KVIrc]]
* [[Connect:mIRC|mIRC]]
* [[Connect:Pidgin|Pidgin]]
* [[Connect:Weechat|Weechat]]

'''Mobile Clients'''
* [[Connect:AndroIRC|AndroIRC]]
* [[Connect:Colloquy|Colloquy]]
* [[Connect:RevolutionIRC|RevolutionIRC (Beta)]]

Module:ClientBuffer

2021-05-15T17:17:18Z

Russell: Changed protection level for "Module:ClientBuffer": This shouldn't have protection ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite))

This module will enable client specific playback buffers allowing you to configure certain clients to play back lines from a specific time period.

= Usage =

In order to make it possible for the module to control client specific buffers, you must disable the <code>AutoClearChanBuffer</code> and <code>AutoClearQueryBuffer</code> config options that are enabled by default on your account. This can be done via the [[Module:controlpanel|controlpanel]] module or via webadmin.

== Arguments ==

This module takes 2 arguments

{| class="wikitable"
! style="font-weight:bold;" | Argument
! style="font-weight:bold;" | Type
! style="font-weight:bold;" | Description
|-
| autoadd
| Optional
| If specified, causes any clients that haven't been previously registered to be automatically registered, thus making it unnecessary to use the addclient command.
|-
| timelimit
| Optional
| Does not playback any lines in the buffer older than the specified number of seconds.
|}

== Commands ==

The following command can be used to add a client to the client buffer module:
/msg *clientbuffer addclient <name/identifier>

For example if you wanted to add a client named 'laptop', you would use the following:
/msg *clientbuffer addclient laptop

To delete a client so it is no longer recognised by this module, use the following:
/msg *clientbuffer delclient <name/identifier>

To change what is played back to a client use the following command:
/msg *clientbuffer setclienttimelimit <name/identifier> <seconds>

To list which clients are recognised by the module, use the following command:
/msg *clientbuffer listclients

== Identifiers ==

Our bouncers support passing a client identifier in the password line you use to authenticate as follows:

YourUsername@ChosenIdentifier/Network:Password

== Example Use Case ==

In this setup, 2 clients are configured using this module. One will be used on a PC to playback the whole of the buffer everytime the client connects and the other is configured for a mobile client where playing back the entire buffer causes client issues and the client disconnects frequently so we will only play back an hours worth of playback to that client.

For the PC client, use the following command to add it to the module:
/msg *clientbuffer addclient PC

For the mobile client, use the following commands to add it to the module:
/msg *clientbuffer addclient Mobile
/msg *clientbuffer setclienttimelimit Mobile 3600

What should happen now is when you connect to your PC client, the entire buffer will be played back and when you connect to the Mobile client, only an hours worth of buffer will be played back. To login to the PC client, you need to use the following password line:

YourUsername@PC/Network:Password

To login to the Mobile client use the following line:

YourUsername@Mobile/Network:Password

== Useful Timeframes ==

The following timeframes are most commonly used with the <code>setclienttimelimit</code> command:

{| class="wikitable"
! style="font-weight:bold;" | Timeframe
! style="font-weight:bold;" | Seconds
|-
| 10 Minutes
| 600
|-
| 30 Minutes
| 1800
|-
| 1 Hour
| 3600
|-
| 2 Hours
| 7200
|-
| 6 Hours
| 21600
|-
| 12 Hours
| 43200
|-
| 1 Day
| 86400
|}

[[Category:Modules]] [[Category:Network_Modules]]

Module:ClientBuffer

2021-05-15T17:13:07Z

Russell: Protected "Module:ClientBuffer": Core Module ([Edit=⧼protect-level-staff⧽] (indefinite) [Move=⧼protect-level-staff⧽] (indefinite))

Module:Clientbuffer

2021-02-06T11:09:04Z

Russell: Protected "Module:Clientbuffer": Core Module: Affects Redirect from Webpanels ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

#Redirect [[Module:ClientBuffer]]

Module:Clientbuffer

2021-02-06T11:08:43Z

Russell: Redirect to ClientBuffer

#Redirect [[Module:ClientBuffer]]

Module:clientbuffer

2021-02-06T11:02:17Z

Russell: Protected "Module:clientbuffer": Core Module: Affects Redirect from Webpanels ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

#Redirect [[Module:ClientBuffer]]

Module:clientbuffer

2021-02-06T11:01:38Z

Russell: Redirect to ClientBuffer

#Redirect [[Module:ClientBuffer]]

Module:ClientBuffer

2021-02-06T11:00:08Z

Russell: Add documentation for the clientbuffer module

BNC4FREE:General disclaimer

2021-01-14T20:47:39Z

Russell: Protected "BNC4FREE:General disclaimer": Important Information ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

== General Disclaimer ==
We (BNC4FREE as part of R M Bradford Ltd) reserve the right not to be responsible for the topicality, correctness, completeness or quality of the information provided on this wiki. Liability claims regarding damage caused by the use of any information provided, including any kind of information which is incomplete or incorrect,will therefore be rejected. All offers are not-binding and without obligation. Parts of the pages or the complete publication including all offers and information might be extended, changed or partly or completely deleted by the content author without separate announcement.

== Copyright ==
We intend not to use any copyrighted material for the publication or, if not possible, to indicate the copyright of the respective object. The copyright for any material created by the author of the content is reserved. Any duplication or use of objects such as images, diagrams, sounds or texts in other electronic or printed publications is not permitted without the content author's agreement.

== Privacy Policy ==

Our privacy policy can be viewed [[BNC4FREE:Privacy_policy|here]]

Module:ControlPanel

2021-01-12T13:57:15Z

Russell: /* CTCP Replies */ Delete not List...

This module allows you to edit your user and network settings on the fly via IRC messages.

= Usage =

== Arguments ==
This module takes no arguments

== Commands ==

There are a large number of commands that can be used to manage your accounts and its networks of which are listed below. The list of commands can also be accessed using the following command:
/msg *controlpanel help

The following variables are available for most commands:

{| class="wikitable"
|- style="font-weight:bold;"
! Variable
! Description
|-
| $user
| This variable is replaced with the username of your account
|-
| $network
| This variable is replaced with the name of the network that you are currently attached to.<br />You can replace this with a specific network name if configuring other networks (not the currently attached one) within your account
|}

=== Loading & Unloading Modules ===

To list the available modules that can be loaded on your account, the following command can be used:
/msg *controlpanel ListMods

To list the available modules that can be loaded for individual networks on your account, the following command can be used:
/msg *controlpanel ListNetMods

To load a module on your account, the following command can be used:
/msg *controlpanel LoadModule $user <module name> [module arguments]

To load a module on a network that is on your account, use the following command:
/msg *controlpanel LoadNetModule $user <module name> [module arguments]

The following commands can be used to unload account and network modules respectively:
/msg *controlpanel UnloadModule $user <module name>
/msg *controlpanel UnloadNetModule $user <module name>

=== Account Settings ===

To view an accounts current setting, the following command can be used:
/msg *controlpanel Get <variable>

To set a new value for an account setting, the following command can be used:
/msg *controlpanel Set <variable> <new value>

The account settings (variables) can be used with these commands:

{| class="wikitable"
|- style="font-weight:bold;"
! Variable
! Type
! Description
|-
| MultiClients
| Bool
| If set to true, allows multiple clients to connect to your account.<br />If set to false, you will only be able to connect one client to your account
|-
| AutoClearChanBuffer
| Bool
| If set to true, the channel buffers will be cleared once they have been played back to your client<br />If set to false, the channel buffers will be kept and the full buffer will be played back every time your client connects
|-
| AutoClearQueryBuffer
| Bool
| If set to true, the query buffers (private messages) will be cleared once they have been played back to your client<br />If set to false, the query buffers (private messages) will be kept and the full buffer will be played back every time your client connects
|-
| AppendTimestamp
| Bool
| If set to true, a timestamp will be appended to each playback buffer message when it is played back<br />If set to false, no timestamp will be appended to playback buffer messages<br />The timestamp format and timezone can be set using the TimestampFormat and Timezone settings
|-
| PrependTimestamp
| Bool
| If set to true, a timestamp will be prepended to each playback buffer message when it is played back<br />If set to false, no timestamp will be prepended to playback buffer messages<br />The timestamp format and timezone can be set using the TimestampFormat and Timezone settings
|-
| ChanBufferSize
| Integer
| The maximum number of lines that can be kept in the channel buffer per channel (Maximum: 1000)
|-
| QueryBufferSize
| Integer
| The maximum number of lines that can be kept in the query buffer per private message from a user (Maximum: 1000)
|-
| JoinTries
| Integer
| The amount of times the bouncer will attempt to rejoin a channel if blocked by a ban or any other mode that restricts the user from joining
|-
| MaxJoins
| Integer
| The maximum number of channels the bouncer will try to join at once (including after a reconnect)<br />The recommended value for this is between 3 and 5 as higher values may trigger 'Excess Flood'
|-
| MaxQueryBuffers
| Integer
| The maximum number of query buffers (private messages) that can be stored (by default this is unlimited)
|-
| NoTrafficTimeout
| Integer
| How much time the bouncer waits (in seconds) until it receives something from network or declares a connection timeout.<br />The recommended value for this is 180 seconds. Other values may cause unexpected behavior and frequent disconnects from the network
|-
| Nick
| String
| The default primary nickname that your account will use when connecting to networks<br />This can be over-ridden per network by using network settings
|-
| AltNick
| String
| The default alternative nickname that your account will use if your primary nickname is not available<br />This can be over-ridden per network by using network settings
|-
| Ident
| String
| The default ident that your account will use when connecting to networks<br />This can be over-ridden per network by using network settings
|-
| RealName
| String
| The default realname that your account will use when connecting to networks<br />This can be over-ridden per network by using network settings
|-
| DefaultChanModes
| String
| The default channel modes that will be applied to empty channels when you join them
|-
| QuitMsg
| String
| The default quit message that will be shown when you disconnect the bouncer from IRC<br />This can be over-ridden per network by using network settings
|-
| Password
| String
| Changes the password for your account. See [[Password_Security#General_Password_Security|here]] for general password recommendations.
|-
| Timezone
| String
| The timezone for timestamps used in buffer playback messages (except for networks supporting the 'server-time' capability)<br />Example Values: Europe/Berlin, Europe/London, Australia/Brisbane, US/Eastern, Canada/Pacific, Asia/Tokyo<br />See the [https://en.wikipedia.org/wiki/List_of_tz_database_time_zones list of timezones] for a full list of available timezones
|-
| TimestampFormat
| String
| The timestamp format for timestamps used in the buffer playback messages (except for networks supporting the 'server-time' capability)<br />Please see [[Timestamps|Timestamp Formats]] for a list of valid variables than can be used
|-
| StatusPrefix
| String
| The prefix for the status module and all other modules to be used. Changing this will change the way you query modules
|-
| Language
| String
| Changes the language used in some of the bouncers messages and the web interface. By default this is set to English
|-
| ClientEncoding
| String
| The Client encoding that will be used
|}

=== Network Settings ===

To view the network settings for the network you are currently attached to, the following command can be used:
/msg *controlpanel GetNetwork <variable>

To set a new value for an network you are currently attached to, the following command can be used:
/msg *controlpanel SetNetwork <variable> <new value>

To view the network settings for another network on your account, the following command can be used:
/msg *controlpanel GetNetwork <variable> $user <network name>

To set a new value for another network on your account, the following command can be used:
/msg *controlpanel SetNetwork <variable> $user <network name> <new value>

The network settings (variables) can be used with these commands:

{| class="wikitable"
|- style="font-weight:bold;"
! Variable
! Type
! Description
|-
| TrustAllCerts
| Bool
| Enable or Disable the validation of SSL certificates when connecting to a network.<br />Due to the amount of invalid/self-signed certificates on networks, it is recommended to keep this set to true
|-
| TrustPKI
| Bool
| Enable or Disable the validation of SSL certificates when connecting to a network.<br />Due to the amount of invalid/self-signed certificates on networks, it is recommended to keep this set to false
|-
| JoinDelay
| Integer
| The delay in seconds before channels are joined after the bouncer has reconnected to IRC
|-
| FloodBurst
| Integer
| The maximum amount of lines that the bouncer will send at once<br />The recommended value for this is 3 to 5. Other values may cause unexpected behaviour
|-
| FloodRate
| Integer
| The number of seconds each line from the bouncer will be sent after the FloodBurst limit has been hit<br />The recommended value for this is 1 to 3 seconds. Other values may cause unexpected behaviour
|-
| Nick
| String
| The default primary nickname that will be used when connecting to networks
|-
| AltNick
| String
| The default alternative nickname that will be used if your primary nickname is not available
|-
| Ident
| String
| The default ident that will be used when connecting to networks
|-
| RealName
| String
| The default realname that will be used when connecting to networks
|-
| Encoding
| String
| The network encoding that will be used
|-
| QuitMsg
| String
| The default quit message that will be shown when you disconnect the bouncer from IRC
|}

=== Channel Settings ===

To view the channel settings for a given channel on a given network, the following command can be used:
/msg *controlpanel GetChan <variable> $user <network name> <channel name>

To set a new value for a given channel on a given network, the following command can be used:
/msg *controlpanel SetChan <variable> $user <network name> <channel name> <new value>

The channel settings (variables) can be used with these commands:

{| class="wikitable"
|- style="font-weight:bold;"
! Variable
! Type
! Description
|-
| AutoClearChanBuffer
| Bool
| If set to true, the channel buffer this channel will automatically be cleared once it has been played back to the client<br />If set to false, the channel buffer for this channel will be kept and re-played each time the client reconnects
|-
| Detached
| Bool
| If set to true, the channel will be detached and not shown in the channel list to the client. It can be re-attached by using the join command<br />If set to false, the channel will be attached and shown in the channel list as normal
|-
| InConfig
| Bool
| If set to true, the channel will be saved to the bouncers config and you will be rejoined to the channel if you reconnect to the IRC network<br />If set to false, the channel will not be saved to the bouncers config and may be lost during bouncer restarts or when reconnected to the IRC network
|-
| BufferSize
| Integer
| The maximum number of buffer lines that will be kept for this specific channel (Maximum: 1000)
|-
| DefModes
| String
| The default modes that will be set on the channel when joined/rejoined if it is empty or you have the relevant channel permissions to do so
|-
| Key
| String
| The key for the channel (if the channel requires a keyword to join)
|}

=== CTCP Replies ===

To list your CTCP replies, the following command can be used:
/msg *controlpanel ListCTCPs

To add a CTCP reply, the following command can be used:
/msg *controlpanel AddCTCP $user <ctcp> <reply>

To delete a CTCP reply, the following command can be used:
/msg *controlpanel DelCTCP $user <ctcp>

Commonly used CTCP replies that are customisable with the above commands are as follows:

{| class="wikitable"
|- style="font-weight:bold;"
! CTCP Reply
! Description
|-
| VERSION
| Normally sends a CTCP reply with the clients version
|-
| TIME
| Normally sends a CTCP reply with the clients current date and time
|-
| PING
| Normally sends a CTCP reply with the clients ping response time
|}

=== Disconnect/Reconnecting to IRC ===

To reconnect to a specific IRC Network, the following command can be used:
/msg *controlpanel Reconnect $me <network name>

To permanently disconnect from a specific IRC Network the following command can be used:
/msg *controlpanel Disconnect $me <network name>

Both of the above commands can also me be used without specifying '$me' or a network name to disconnect from the currently attached network.

[[Category:Modules]] [[Category:Network_Modules]] [[Category:User_Modules]]

Connect:irssi

2021-01-12T13:26:49Z

Russell: /* Connecting */ The TLS flag is required to connect to SSL on Irssi

= Connecting with irssi =

This guide will tell you how to connect to our bouncers using the irssi command line IRC client which is available at [https://irssi.org/download/ https://irssi.org/download/]. This client can also be downloaded on most variations of linux using the following command:
apt-get install irssi

For the purposes of this guide, we have used '''[https://irssi.org/download/ Irssi v1.0.5]'''

== Configuration ==

irssi needs to be configured to connect to our bouncer, so to do this we need to add the network and server. Firstly we need to add a server using the ''"/network add"'' command. The syntax is as follows:
/network add <name>
The network name can be named anything for example "MyNewBouncer"
/network add MyNewBouncer

We then need to add the server to the network using ''"/server add"''. The syntax of the command is as follows:
/server add [options] [server] [port] [username/network:password]

The options that can and need to be used are as follows:

{| class="wikitable"
! style="font-weight:bold;" | Option
! style="font-weight:bold;" | Required
! style="font-weight:bold;" | Description
|-
| -network [network name]
| Required
| This is the name of the network you added using "/network add"
|-
| -auto
| Optional
| If this is specified, irssi will automatically connect to the network whenever it is started
|-
| -noauto
| Optional
| If this is specified, irssi will not automatically connect to the network whenever it is started
|-
| -tls
| Optional
| If this option is specified, you will connect to the bouncer using SSL (Note: Port 1339 must be used)
|-
| -tls_verify
| Optional
| If this option is specified, irssi will verify that our bouncers certificate is valid (Recommended)
|}

Below is an example of the ''"/server add"'' command that will add the bouncer to the network that we have created:

[[File:irssi-serveradd.png|700px|Screenshot of a /server add command in irssi ]]

Once the server has been added. You will be able to connect to the bouncer. See Section Below.

== Connecting ==

If you have added the bouncer to irssi using the above method, you can connect using the following command:
/connect <name>

You can also manually connect to your bouncer should you need to by using one of the following commands:
/server -tls <server> <port> <username>:<password>
or
/server -tls <server> <port> <username>/<network name>:<password>

Examples of this are shown below:
/server -tls apple.bnc4free.com +1339 TestOne:foo
or
/server -tls apple.bnc4free.com +1339 TestOne/Freenode:foo

=== Note regarding TLS/SSL ===

You may find that when connecting to the bouncer, you receive several messages in the status window relating to SSL (If you are using the SSL port) that look like the below:
-!- Irssi: Certificate Chain:
-!- Irssi: Subject: CN: apple.bnc4free.com
-!- Irssi: Issuer: C: US, O: Let's Encrypt, CN: Let's Encrypt Authority X3
-!- Irssi: Subject: C: US, O: Let's Encrypt, CN: Let's Encrypt Authority X3
-!- Irssi: Issuer: O: Digital Signature Trust Co., CN: DST Root CA X3
-!- Irssi: Protocol: TLSv1.3 (256 bit, TLS_AES_256_GCM_SHA384)
-!- Irssi: EDH Key: 253 bit Unknown
-!- Irssi: Public Key: 2048 bit RSA, valid from Apr 22 10:17:40 2020 GMT to Jul 21 10:17:40 2020 GMT
-!- Irssi: Public Key Fingerprint: 45:92:4B:89:E5:9F:AD:9D:ED:E9:32:D8:A7:4D:C7:3A:A9:59:DD:56:28:6F:47:C7:56:AB:BB:E5:29:43:F0:1D (SHA256)
-!- Irssi: Certificate Fingerprint: B7:23:B2:E4:BC:D1:AC:7B:FA:70:CB:D7:8D:EF:B8:3F:5F:DC:66:46:14:D0:27:69:DB:98:34:3E:20:17:1E:6D (SHA256)
-!- Irssi: Connection to apple.bnc4free.com established

These messages can be safely ignored or can be disabled completely using the following command:
/set tls_verbose_connect off

Connect

2021-01-12T13:02:00Z

Russell: Changed protection level for "Connect": Important Information: Staff should be able to add/edit things here ([Edit=⧼protect-level-staff⧽] (indefinite) [Move=Allow only administrators] (indefinite))

= How to Connect =

This page provides information on how to connect to your IRC Bouncer using an IRC Client.

== Most Clients ==

Most clients come with a "/server" command that can be used to connect. The syntax of the command is usually as follows:
/server <server>:<port> <password>

Below is an example of the "/server" command that would be used to connect the Apple server on the SSL port (1339), authenticate as "TestOne" with the password "foo":

/server apple.bnc4free.com:+1339 TestOne:foo

If the account has multiple networks and you want to attach to a specific network such as "Freenode" for example, the command would be as follows:

/server apple.bnc4free.com:+1339 TestOne/Freenode:foo

'''Note¹''' Some clients require a space between the server and the port ''(i.e "/server apple.bnc4free.com +1339 ...")''

'''Note²''' Some clients require an ssl option in the "/server" command ''(i.e "/server -ssl apple.bnc4free.com 1339 ...")''

== Specific Clients ==

Information for specific clients can be found using one the links below:

'''Desktop Clients'''
* [[Connect:eMule|eMule]]
* [[Connect:Konversation|Konversation]]
* [[Connect:HexChat|HexChat]]
* [[Connect:irssi|irssi]]
* [[Connect:KVIrc|KVIrc]]
* [[Connect:mIRC|mIRC]]
* [[Connect:Pidgin|Pidgin]]
* [[Connect:Weechat|Weechat]]

'''Mobile Clients'''
* [[Connect:AndroIRC|AndroIRC]]
* [[Connect:Colloquy|Colloquy]]
* [[Connect:RevolutionIRC|RevolutionIRC (Beta)]]

MediaWiki:Sidebar

2021-01-11T18:54:00Z

Russell: Fix FAQ link

MediaWiki:Sidebar

2021-01-11T18:53:21Z

Russell: Update Sidebar

Module:Perform

2021-01-11T18:34:25Z

Russell: Removed protection from "Module:Perform": Protection is not necessary here

This module is used to perform or send commands to the IRC server when connecting to the IRC network.

'''Note:''' This module can be loaded either as a user module or a network. We recommend loading this as a network module which will allow you to set different perform commands for different networks however, if you would like the same perform commands sent to all your connected networks, you should load this as a user module.

'''Note²:''' This module supports [[ExpandString|Expandable Strings]]

= Usage =

== Arguments ==
This module takes no arguments

== Commands ==
This module will send perform commands to the IRC server when the bouncer connects to it. Below is a list of commands to manage the list of commands that will be sent.

/msg *perform add <command>
Adds a command to the list of perform commands to be sent to the server

/msg *perform del <number>
Delete a perform command from the perform list. (Number can be obtained from list)

/msg *perform list
List the commands currently on your perform list

/msg *perform execute
Manually execute all of the commands currently on your perform list

/msg *perform swap <number> <number>
Swap two perform commands that are in the perform list (for re-ordering purposes)

/msg *perform help <?search>
Shows the list of available commands for this module with the ability to optionally search for word/phrase in help output.

== Examples ==
Below are a few useful examples of how perform can be used

=== Use with NickServ ===
This module can be used to regain your nickname and identify with NickServ. See <code>/msg NickServ help identify</code> for the syntax that corresponds to the network you are connected to. Most networks use <code>/msg NickServ identify [username] [password]</code> or <code>/msg NickServ identify [password]</code>. These can be added to perform using the following:

/msg *perform add PRIVMSG NickServ :identify [username] [password]

or

/msg *perform add PRIVMSG NickServ :identify [password]

It is also possible to use this module in conjunction with the [[Module:keepnick|keepnick]] module to regain your nickname and identify to services. Most networks will have a command such as <code>/msg NickServ RELEASE [username] [password]</code> or <code>/msg NickServ GHOST [username] [password]</code>. This releasing of your nickname can be added to perform using the following:

/msg *perform add PRIVMSG NickServ :release [username] [password]

or

/msg *perform add PRIVMSG NickServ :ghost [password]

=== Use with Undernet's X Service ===
Perform can be used to identify on the [https://www.undernet.org/ Undernet] IRC Network. Identifying is usually done by sending the command <code>/msg X@Channels.undernet.org LOGIN <username> <password></code>. This can be added to perform using the following command:

/msg *perform add PRIVMSG X@Channels.undernet.org :LOGIN <username> <password>

=== Use with Quakenet's Q Service ===
Perform can be used to identify on the [https://www.quakenet.org/ Quakenet] IRC Network. Identifying is usually done by sending the command <code>/msg Q@CServe.quakenet.org AUTH <username> <password></code>. This can be added to perform using the following command:

/msg *perform add PRIVMSG Q@CServe.undernet.org :AUTH <username> <password>

=== Use with GameSurge's Auth Service ===
Perform can be used to identify on the [https://gamesurge.net/ GameSurge] IRC Network. Identifying is usually done by sending the command <code>/msg AuthServ@Services.GameSurge.net AUTH <username> <password></code>. This can be added to perform using the following command:

/msg *perform add PRIVMSG AuthServ@Services.GameSurge.net :AUTH <username> <password>

=== Setting user modes ===
Perform can be used to set usermodes when you connect to the IRC Server (for example on some networks, setting +R to only allow users registered with services to message you). Lists of user modes can be found for most networks by using <code>/helpop umodes</code>. These modes can be set by using the <code>%nick%</code> [[ExpandString|Expandable String]] in the perform command as follows:

/msg *perform add mode %nick% +R

Multiple modes can be specified on one perform, for example:
/msg *perform add mode %nick +iwxR

=== Opering Up ===
Perform can be used to login as IRC operator on a network. This is often done using <code>/oper [username] [password]</code> and example can be found below:
/msg *perform add oper [username] [password]

This can also be used in conjunction with the [[Module:Perform#Setting_User_Modes|Setting user modes]] section above to set snomasks after you have opered.

=== Identifying to other bots/services ===
Perform can be used to identify to many other bots and services around IRC, for example your own bots, IdleRPG etc... An example of how to send your login command can be found below:
/msg *perform add privmsg [bot name] :login [username] [password]
''* Change the command to suit your needs as necessary''

[[Category:Modules]] [[Category:Network_Modules]] [[Category:User_Modules]]

Module:SASL

2021-01-11T18:33:58Z

Russell: Removed protection from "Module:SASL": Protection is not necessary here

This module allows you to authenticate to an IRC network via SASL. This is the preffered method over using [[Module:nickserv|nickserv]] or [[Module:perform|perform]] as you are able to authenticate to services before you are visible on the IRC server.

This module also supports the EXTERNAL SASL mechanism if you set up a certificate with the [[Module:cert|cert]] module. Once cert is properly enabled and setup, you can set the SASL module to use the EXTERNAL mechanism.

= Usage =

== Arguments ==
This module takes no arguments

== Commands ==
This module works without any form of user interaction when loaded. When your primary nickname isn't available on the network, the module should try to get it for you. It is possible to enable/disable keepnick and check whether the module is trying to regain your primary nickname using commands.

/msg *sasl mechanism [external/plain]
Sets the mechanism to external or plain. External requires a cert to be configured on the [[Module:cert|cert]] module and Plain will use plain text negotiation

/msg *sasl requireauth
Require SASL authentication to be successful when connecting to the network, otherwise disconnect

/msg *sasl set [username] [password]
Set the username and password for the nickserv account you wish to identify to.

/msg *sasl help <?search>
Shows the list of available commands for this module with the ability to optionally search for word/phrase in help output.

== Notes ==
If you don't use SSL (i.e you are connecting to an IRCserver where the port is not prefixed with a '+'), the password is transmitted to the IRC server in plain text. It is therefore recommended that you check you are connecting to an SSL server and port and ask us to change this should you wish to use the plain mechanism.

Many networks support authenticating SASL. You can easily check whether a network has a SASL service by using <code>/whois SASLServ</code> (assuming the network hasn't renamed it)

[[Category:Modules]] [[Category:Network_Modules]]

Module:MissingMOTD

2021-01-11T18:33:03Z

Russell: Removed protection from "Module:MissingMOTD": Protection is not necessary here

This module send a line to your client (422: MOTD File is missing). This fixes clients that expect an MOTD or no MOTD message to be sent to them once connected to a network (in this case the bouncer)

= Usage =

== Arguments ==
This module takes no arguments

== Commands ==
This module has no commands

[[Category:Modules]] [[Category:User_Modules]]

Request

2021-01-11T18:29:36Z

Russell: Changed protection level for "Request": Important Information: Currently matches site information but can be edited by staff here if necessary ([Edit=⧼protect-level-staff⧽] (indefinite) [Move=Allow only administrators] (indefinite))

Requesting an IRC Bouncer from us is easy and simple provided that you fill in the required fields and provide the necessary details accurately and correctly so we can set-up your account. By following the steps on this page, you will be able to successfully request a bouncer with us.

== How to Request an Account ==

In order to request an IRC Bouncer, you will need to join one of our IRC Channels. To do this, choose a network from our Official Network List, connect to the network and join the channel “#bnc4free”.

Once you have done this, you will need to type <code>!request</code> in the channel. You will be asked to fill in the following fields:

* Username – This is the username that you will use to login and authenticate to the bouncer.
* Email Address – This is the email address that we will send details to when your request is accepted.
* IRC Server – This is the IRC server address that you will want the bouncer to connect to. (e.g: irc.efnet.org). You can add more servers after you’re request has been accepted. More details on this soon
* IRC Port – This is the IRC port that you usually connect to on the server which is usually 6667. For SSL Ports please prefix the port with a “+” (e.g: 6667 – SSL e.g: +6697)

The command you will enter in the IRC Channel should then look like
!request someusername myemail@example.com irc.test.net 6667
Once you have entered this into the channel, you will be sent an email containing a verify code of which must be entered onto IRC or can be entered on the [https://bnc4free.com/?page_id=715 Verify your Email] page in order to validate your email address.

When you have verified your email address, your request is officially pending review from the staff team. You can check the status of your request on the [https://bnc4free.com/check Check Your Request] page or by using the following command on IRC:

!check [username/request id]

You will receive an email from us when the request has been accepted or rejected.

== How to Request Additional Networks for Your Account ==

If you already have an account with us, you can request up to 2 additional networks to be added to your account (bringing the total to 3 on your account). To do this, choose a network from our Official Network List, connect to the network and join the channel “#bnc4free”.

Once you have done this, you will need to type <code>!network request</code> in the channel. You will be asked to fill in the following fields:

* Username – This is the username that you will use to login and authenticate to the bouncer.
* IRC Server – This is the IRC server address that you will want the bouncer to connect to. (e.g: irc.efnet.org). You can add more servers after you’re request has been accepted. More details on this soon
* IRC Port – This is the IRC port that you usually connect to on the server which is usually 6667. For SSL Ports please prefix the port with a “+” (e.g: 6667 – SSL e.g: +6697)

The command you will enter in the IRC Channel should then look like
!network request someusername irc.test.net 6667
Once you have entered this into the channel, you will be sent an email containing a code of which must be entered onto IRC or can be entered on the [https://bnc4free.com/?page_id=715 Verify your Email] page in order to validate that you have requested the new network for your account.

When you have verified your email address, your network request is officially pending review from the staff team. You can check the status of your request by using the following command on IRC:
!network check [request id]
You will receive an email from us when the request has been accepted or rejected.

== Frequently Asked Questions ==

=== I don’t want everyone to see my request or email address, Can i request privately? ===

Yes. You can join ##bnc4free on Espernet and Freenode where the channels are moderated so that only our staff team and our services bot can see your messages.

=== Can i request by email? ===

At this time, it is not possible as we are working on a system that will be able to read the emails sent in a specific format and automatically input the data into our request system. We will update you once we have this up and running!

=== When will my request be accepted? ===

At present, we will be able to process requests within 24 to 48 hours of your request. In most cases it will take less time for us to process your request.
If you request has not been processed within 48 hours, please contact our [mailto:support@bnc4free.com support team] quoting your username of request ID and we will look into this.

Timestamps

2021-01-11T18:24:32Z

Russell: Changed protection level for "Timestamps": No need to move the page ([Edit=⧼protect-level-development⧽] (indefinite) [Move=Allow only administrators] (indefinite))

Playback buffers and some other features may require a timestamp format for their output or usage. If you have a modern client which supports <code>server-time</code> capability, timestamps are automatically shown correctly. <br/>
Alternatively you will need to configure the <code>TimestampFormat</code> setting for your account using the [[Module:ControlPanel|controlpanel]] module or via the webpanel.

= Timestamp Formats =

The following variables can be used within the timestamp format

{| class="wikitable"
|- style="font-weight:bold;"
! Variable
! Description
|-
| %a
| The locale's abbreviated weekday name
|-
| %A
| The locale's full weekday name
|-
| %b
| The locale's abbreviated month name
|-
| %B
| The locale's full month name
|-
| %c
| The locale's appropriate date and time representation
|-
| %C
| The century number (the year divided by 100 and truncated to an integer) as a decimal number (00-99)
|-
| %d
| The day of the month as a decimal number (01-31)
|-
| %D
| The same as %m/%d/%y
|-
| %e
| The day of the month as a decimal number (0-31). A single digit is preceded by a space
|-
| %f
| A Sub-second, e.g. %3f is number of milliseconds (the default), and %6f is number of microseconds
|-
| %h
| The same as %b
|-
| %H
| The hour (24-hour clock) as a decimal number (00-23)
|-
| %I
| The hour (12-hour clock) as a decimal number (01-12)
|-
| %j
| The day of the year as a decimal number (001-366)
|-
| %m
| The month as a decimal number (01-12)
|-
| %M
| The minute as a decimal number (00-59)
|-
| %n
| A newline character
|-
| %p
| The locale's equivalent of either a.m. or p.m
|-
| %r
| The time in a.m. and p.m. notation; in the POSIX locale this is equivalent to %I:%M:%S %p
|-
| %R
| The time in 24 hour notation (%H:%M)
|-
| %S
| The second as a decimal number (00-61)
|-
| %t
| A tab character
|-
| %T
| The time (%H:%M:%S)
|-
| %u
| The weekday as a decimal number (1-7), with 1 representing Monday
|-
| %U
| The week number of the year (Sunday as the first day of the week) as a decimal number (00-53)
|-
| %V
| The week number of the year (Monday as the first day of the week) as a decimal number (01-53)
|-
| %w
| The weekday as a decimal number (0-6), with 0 representing Sunday
|-
| %W
| The week number of the year (Monday as the first day of the week) as a decimal number (00-53)
|-
| %x
| The locale's appropriate date representation
|-
| %X
| The locale's appropriate time representation
|-
| %y
| The year without century as a decimal number (00-99)
|-
| %Y
| The year with century as a decimal number
|-
| %Z
| The timezone name or abbreviation, or empty if no timezone information exists
|-
| %%
| The escaped % symbol
|}

Password Security

2021-01-11T18:24:08Z

Russell: Changed protection level for "Password Security": No need to move the page ([Edit=⧼protect-level-staff⧽] (indefinite) [Move=Allow only administrators] (indefinite))

BNC4FREE as a service stores and retains password hashes and understands how important it is to keep passwords safe and secure. This document outlines recommendations for users when setting passwords and also how we store them and ensure they cannot be decrypted.

== General Password Security ==

Your password for your account should be secure. We recommend the following:
* Use atleast one or more upper case letters
* Use atleast one or more lower case letters
* Use atleast one or more numbers
* Use atleast one or more symbols (!"£$%^&* etc...)
* '''DON'T''' keep the default the password that we email you (because if someone hacks your email, they'll find it)

== How we store passwords ==

Our software is based on ZNC which encrypts users passwords into SHA256 using a random salt. This is how it looks in the configuration:

<Pass password>
Hash = 69d186dc7a809157f98f3593c66148331eb57d59de34b40b24716e095c7acd20
Method = SHA256
Salt = I_I/zCQ,mWmr-trTaNKK
</Pass>

Because of the way this is encrypted and salted it is impossible for us to decrypt the password.

== How we can use this information ==

We can use your password hash and salt to allow you to login to our website and wiki. It should be emphasized that we '''don't''' know your password. By knowing the password hash and its salt we are able to verify that the password you enter is correct. What this means (in a nutshell) is that when you enter your password into the password field and its submitted, we encrypt it with the salt from ZNC and if the hash matches, it is a successful login.

== Examples ==

We are able to query ZNC for the password hash and salt to authenticate users. Below are examples of how sha256 along with the hash and salt provided from ZNC can be used to verify whether the password is correct.

Using our [[API|API]] we can use the [[API:User/Info|User/Info]] callback to retrieve the password information. It is returned to us in this format:

{
"status" : "success",
"MyUsername" : {
..other info...
"password" : {
"salt" : "I_I/zCQ,mWmr-trTaNKK",
"hash" : "69d186dc7a809157f98f3593c66148331eb57d59de34b40b24716e095c7acd20",
"type" : 2
}
..other info...
}
}

=== Python ===
The below Python 2 script demonstrates how we can determine a successful login

import sys
import uuid
import hashlib
_hashedText, salt = ("69d186dc7a809157f98f3593c66148331eb57d59de34b40b24716e095c7acd20", "I_I/zCQ,mWmr-trTaNKK")
hashedTexti = hashlib.sha256("ThisIsSparta".encode() + salt).hexdigest()
print "Match From Text: (ZNC Hash: " + _hashedText + " --> HashLib Hash: " + hashedTexti + ")"

The result we get is as follows:
ZNC Hash: 69d186dc7a809157f98f3593c66148331eb57d59de34b40b24716e095c7acd20 --> HashLib Hash: 69d186dc7a809157f98f3593c66148331eb57d59de34b40b24716e095c7acd20

=== PHP ===
Here is a PHP script that demonstrates how we can determine a successful login

<?php
// This will be the password submitted via a form that we never get to see or log... the rest is handled by the API and SHA256
$Username = "TestMe";
$Password = "TestMe";
$APIVars = http_build_query(Array('username' => $Username, 'server' => 'Staging', 'key' => 'a83e9244173a05a041586e47f36d555d87b587467d535bccd57184eb17d81bf7'));
$HTTPOpts = array('http' =>
array(
'method' => 'POST',
'header' => 'Content-Type: application/x-www-form-urlencoded',
'content' => $APIVars,
'ssl' => array(
'verify_peer'=>false,
'verify_peer_name'=>false
),
)
);
$HTTPContext = stream_context_create($HTTPOpts);
$APIResult = file_get_contents('<nowiki>https://api.bnc4free.com/user/info</nowiki>', false, $HTTPContext);
$APIResult = json_decode($APIResult, true);
$api_hash = $APIResult[$Username]['password']['hash'];
$api_salt = $APIResult[$Username]['password']['salt'];
echo "Expected Hash: ".$APIResult[$Username]['password']['hash']."\r\n";
echo "Hash from API: ".hash('sha256', $Password.$api_salt);
?>

The result we get here is:
Expected Hash: 22a61bc477465fef04548c31416b34962ee55e371627ef2007f58a6a08327c7f
Hash from API: 22a61bc477465fef04548c31416b34962ee55e371627ef2007f58a6a08327c7f

Timestamps

2021-01-11T18:11:13Z

Russell: Protected "Timestamps": Developers & Staff should be able to add/edit things here if necessary ([Edit=⧼protect-level-development⧽] (indefinite) [Move=⧼protect-level-development⧽] (indefinite))

Password Security

2021-01-11T18:10:33Z

Russell: Protected "Password Security": Important Information: Staff should be able to add/edit things here if necessary ([Edit=⧼protect-level-staff⧽] (indefinite) [Move=⧼protect-level-staff⧽] (indefinite))

Request

2021-01-08T20:35:27Z

Russell: /* How to Request Additional Networks for Your Account */ More details on verifying your email address and checking the status of your network request

Requesting an IRC Bouncer from us is easy and simple provided that you fill in the required fields and provide the necessary details accurately and correctly so we can set-up your account. By following the steps on this page, you will be able to successfully request a bouncer with us.

== How to Request an Account ==

In order to request an IRC Bouncer, you will need to join one of our IRC Channels. To do this, choose a network from our Official Network List, connect to the network and join the channel “#bnc4free”.

Once you have done this, you will need to type <code>!request</code> in the channel. You will be asked to fill in the following fields:

* Username – This is the username that you will use to login and authenticate to the bouncer.
* Email Address – This is the email address that we will send details to when your request is accepted.
* IRC Server – This is the IRC server address that you will want the bouncer to connect to. (e.g: irc.efnet.org). You can add more servers after you’re request has been accepted. More details on this soon
* IRC Port – This is the IRC port that you usually connect to on the server which is usually 6667. For SSL Ports please prefix the port with a “+” (e.g: 6667 – SSL e.g: +6697)

The command you will enter in the IRC Channel should then look like
!request someusername myemail@example.com irc.test.net 6667
Once you have entered this into the channel, you will be sent an email containing a verify code of which must be entered onto IRC or can be entered on the [https://bnc4free.com/?page_id=715 Verify your Email] page in order to validate your email address.

When you have verified your email address, your request is officially pending review from the staff team. You can check the status of your request on the [https://bnc4free.com/check Check Your Request] page or by using the following command on IRC:

!check [username/request id]

You will receive an email from us when the request has been accepted or rejected.

== How to Request Additional Networks for Your Account ==

If you already have an account with us, you can request up to 2 additional networks to be added to your account (bringing the total to 3 on your account). To do this, choose a network from our Official Network List, connect to the network and join the channel “#bnc4free”.

Once you have done this, you will need to type <code>!network request</code> in the channel. You will be asked to fill in the following fields:

* Username – This is the username that you will use to login and authenticate to the bouncer.
* IRC Server – This is the IRC server address that you will want the bouncer to connect to. (e.g: irc.efnet.org). You can add more servers after you’re request has been accepted. More details on this soon
* IRC Port – This is the IRC port that you usually connect to on the server which is usually 6667. For SSL Ports please prefix the port with a “+” (e.g: 6667 – SSL e.g: +6697)

The command you will enter in the IRC Channel should then look like
!network request someusername irc.test.net 6667
Once you have entered this into the channel, you will be sent an email containing a code of which must be entered onto IRC or can be entered on the [https://bnc4free.com/?page_id=715 Verify your Email] page in order to validate that you have requested the new network for your account.

When you have verified your email address, your network request is officially pending review from the staff team. You can check the status of your request by using the following command on IRC:
!network check [request id]
You will receive an email from us when the request has been accepted or rejected.

== Frequently Asked Questions ==

=== I don’t want everyone to see my request or email address, Can i request privately? ===

Yes. You can join ##bnc4free on Espernet and Freenode where the channels are moderated so that only our staff team and our services bot can see your messages.

=== Can i request by email? ===

At this time, it is not possible as we are working on a system that will be able to read the emails sent in a specific format and automatically input the data into our request system. We will update you once we have this up and running!

=== When will my request be accepted? ===

At present, we will be able to process requests within 24 to 48 hours of your request. In most cases it will take less time for us to process your request.
If you request has not been processed within 48 hours, please contact our [mailto:support@bnc4free.com support team] quoting your username of request ID and we will look into this.