Skip to content
This repository was archived by the owner on Jun 6, 2021. It is now read-only.

Explain SASL access only IP ranges #430

Merged
tomaw merged 1 commit into from
Feb 14, 2020
Merged

Explain SASL access only IP ranges #430

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions content/kb/using/sasl.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,3 +30,12 @@ If you know of any additions or corrections to the lists above, or would like to

Documentation on how to create certificates and add their fingerprints to NickServ for SASL EXTERNAL
can be found in [the article on NickServ and certificates](kb/using/certfp).

SASL access only IP ranges
==========================

Some IP address ranges are configured to require SASL authentication to an existing NickServ account with a **verified email address**. Connections from these ranges will be refused with the message `SASL access only`. You can follow the instructions above to configure many commonly used clients.

To [create a NickServ account](https://freenode.net/kb/answer/registration) from a restricted IP address, you can first connect to the [freenode webchat](https://webchat.freenode.net). Webchat is not affected by the SASL restriction. Once your NickServ account's email address has been verified you can use that account to satisfy the SASL requirement.

SASL access only restrictions are typically applied to addresses ranges that are the source of frequent policy violations due to providing easy access to dynamic addresses to a wide range of users. These ranges are typically used by VPN, cloud-computing, and mobile network providers. *These restrictions are not targeted at individual users.*