BNC (software): Difference between revisions
ClueBot NG (talk | contribs) m Reverting possible vandalism by 103.214.79.138 to version by Wavelength. Report False Positive? Thanks, ClueBot NG. (3004690) (Bot) |
Rescuing 2 sources and tagging 0 as dead. #IABot (v1.6.1) (Balon Greyjoy) |
||
Line 1: | Line 1: | ||
{{use mdy dates|date=June 2013}} |
{{use mdy dates|date=June 2013}} |
||
A '''BNC''' (short for '''Bounced Network Connection''') is a piece of software that is used to relay traffic and connections in [[computer network]]s, much like a [[Proxy server|proxy]]. Using a BNC allows a user to hide the original source of the user's connection, providing [[privacy]] as well as the ability to route traffic through a specific location. A BNC can also be used to hide the true target to which a user connects.<ref name="ircjunkie">Lederer, Christian (phrozen77). (December 22, 2009). [http://www.irc-junkie.org/2009-12-22/irc-bouncer-comparison/ "IRC bouncer comparison"]. IRC-Junkie. December 22, 2009.</ref> |
A '''BNC''' (short for '''Bounced Network Connection''') is a piece of software that is used to relay traffic and connections in [[computer network]]s, much like a [[Proxy server|proxy]]. Using a BNC allows a user to hide the original source of the user's connection, providing [[privacy]] as well as the ability to route traffic through a specific location. A BNC can also be used to hide the true target to which a user connects.<ref name="ircjunkie">Lederer, Christian (phrozen77). (December 22, 2009). [http://www.irc-junkie.org/2009-12-22/irc-bouncer-comparison/ "IRC bouncer comparison"] {{webarchive|url=https://web.archive.org/web/20150214205206/http://www.irc-junkie.org/2009-12-22/irc-bouncer-comparison/ |date=February 14, 2015 }}. IRC-Junkie. December 22, 2009.</ref> |
||
== IRC == |
== IRC == |
||
Line 17: | Line 17: | ||
A list of bouncer software. |
A list of bouncer software. |
||
* '''Bip IRC Proxy''' maintains a persistent connection and shows a backlog on reconnect.<ref name="nat">[[Nat Friedman|Friedman, Nat]] (June 17, 2011). [http://nat.org/blog/2011/06/instant-company/ "Instant company"]. nat.org.</ref> |
* '''Bip IRC Proxy''' maintains a persistent connection and shows a backlog on reconnect.<ref name="nat">[[Nat Friedman|Friedman, Nat]] (June 17, 2011). [http://nat.org/blog/2011/06/instant-company/ "Instant company"] {{webarchive|url=http://webarchive.loc.gov/all/20110624102902/http%3A//nat.org/blog/2011/06/instant%2Dcompany/ |date=June 24, 2011 }}. nat.org.</ref> |
||
* '''bnc''' is the original IRC bouncer.<ref name="tldp">[http://tldp.org/HOWTO/IRC/bouncers.html "Linux IRC mini-HOWTO: IRC Bouncers (IRC Proxy)"]. The [[Linux Documentation Project]]. TLDP.org.</ref> |
* '''bnc''' is the original IRC bouncer.<ref name="tldp">[http://tldp.org/HOWTO/IRC/bouncers.html "Linux IRC mini-HOWTO: IRC Bouncers (IRC Proxy)"]. The [[Linux Documentation Project]]. TLDP.org.</ref> |
||
* '''ezbounce''''s features include password protection, remote administration, logging and listening on multiple ports.<ref name="tldp" /> |
* '''ezbounce''''s features include password protection, remote administration, logging and listening on multiple ports.<ref name="tldp" /> |
Revision as of 13:12, 15 December 2017
A BNC (short for Bounced Network Connection) is a piece of software that is used to relay traffic and connections in computer networks, much like a proxy. Using a BNC allows a user to hide the original source of the user's connection, providing privacy as well as the ability to route traffic through a specific location. A BNC can also be used to hide the true target to which a user connects.[1]
IRC
![](http://upload.wikimedia.org/wikipedia/commons/thumb/a/ab/Ircnetz-Schema.svg/220px-Ircnetz-Schema.svg.png)
One common usage is over Internet Relay Chat (IRC) via a BNC running on remote servers. In such an environment, where it is very easy to ascertain a user's IP address a BNC may help to hide the original connection source, as well as providing the opportunity for "vhosts" or "virtual hosts". The use of a vhost does not conceal the connection any better, but merely adds a statement as the hostname.
Many BNCs remain connected to an IRC server in the event the client should disconnect from the Internet. Often state changes are tracked so that they may be relayed to the client upon reconnection. Some implementations opt to store all messages sent across the network that the client would have normally received, and send them upon the clients reconnection; this is often considered to be much too resource dependent for commercial hosting services to provide. Other logging features and bot like functions may be included with various implementations but are not standard.
Example
- User A logs onto IRC directly and appears as USER!user@users.reverse.dns
- User A logs onto IRC indirectly through a BNC and appears as USER!user@bnc.net
Software
A list of bouncer software.
- Bip IRC Proxy maintains a persistent connection and shows a backlog on reconnect.[2]
- bnc is the original IRC bouncer.[3]
- ezbounce's features include password protection, remote administration, logging and listening on multiple ports.[3]
- JBouncer for IRC, written in Java. Supports logging.[4]
- muh bnc is a smart and versatile irc-bouncing tool that will also go on IRC as soon as it is launched, guarding or attempting to get one's nick.[3]
- psyBNC is said to be the oldest and most well-known IRC bouncer.[1] It is easy to use, runs on Linux[5] and became popular on FreeBSD,[6] supports IPv4, IPv6, SSL, logging, multiple users and networks etc. Although psyBNC is like any other IRC proxy, it is often installed on compromised systems by the attacker.[7]
- shroudBNC (IRC) supports SSL connections and offers a web interface. [8]
- ZNC (IRC) is easy to use,[1] supports SSL connections, IPv6 and logging and offers a web interface. It is extendible by modules and scripts in C++, Python, Perl and Tcl.
- Bouncer written in Java is a generic bouncer/proxy. Supports SSL tunneling, Failover and LoadBalancing of destinations.[9]
- dircproxy
FTP
BNCs are also often used for File Transfer Protocol (FTP), again to hide the user and server from each other and to route traffic through a specific location. FTP bouncers can be divided into two different categories, entry and traffic.
Entry bouncer acts as a gateway to the server, but it does not hide the existence of the actual server. Entry bouncers, like cubnc, can be used in a multi-server setup for easy access to each server and load balancing. This removes the need to select which FTP server to log into, when trying to access the server farm.
Traffic bouncers relay traffic through the host they are installed on, and when used, it appears as the bouncer is actually the FTP server, thus hiding the real location of the server completely. Multiple traffic bouncers can be installed parallel, in order to balance traffic load across different links. Most elaborate bouncers can even bounce secure SSL/TLS connections.
See also
References
- ^ a b c Lederer, Christian (phrozen77). (December 22, 2009). "IRC bouncer comparison" Archived February 14, 2015, at the Wayback Machine. IRC-Junkie. December 22, 2009.
- ^ Friedman, Nat (June 17, 2011). "Instant company" Archived June 24, 2011, at the Library of Congress Web Archives. nat.org.
- ^ a b c "Linux IRC mini-HOWTO: IRC Bouncers (IRC Proxy)". The Linux Documentation Project. TLDP.org.
- ^ "JBouncer". Jibble.org. Retrieved May 24, 2012.
- ^ "psyBNC documentation". Ubuntu.com. Retrieved September 14, 2008.
- ^ "irc/psyBNC". Freshports. Retrieved September 14, 2008.
- ^ Mierau, Caspar Clemens (April 2007). "Looking for intruders with lsof" (PDF). Linux Magazine.
- ^ "shroudBNC". shroudbnc.info.
- ^ "Bouncer". Github. Retrieved November 2, 2012