Difference between revisions of "BIP"
Jump to navigation
Jump to search
m (Update latest version) |
|||
| (9 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
[[File:bip.png|200px | {{Software|name=BIP | ||
|logo=[[File:bip.png|200px]] | |||
|release=0.8.9 | |||
|homepage= http://bip.milkypond.org/ | |||
|platform=Linux, Unix | |||
|status=Active | |||
}} | |||
'''Bip''' is an IRC proxy, which means it keeps connected to your preferred IRC servers, can store the logs for you, and even send them back to your IRC client(s) upon connection. You may want to use bip to keep your logfiles (in a unique format and on a unique computer) whatever your client is, when you connect from multiple workstations, or when you simply want to have a playback of what was said while you were away. | |||
==Features== | |||
* | ===General=== | ||
:* Transparent detaching and attaching of clients | |||
:* Proxy multiple users and IRC connections (multiuser, multiserver) | |||
:* Automatically join channels upon connection | |||
:* Backlog events (messages, nick changes, quits, …) upon client connection (optional) | |||
:* Optional timestamp backlogs | |||
:* Limit backlog to N lines per channel or backlog since since last client-quit or client-message | |||
:* Logging support – can be disabled for low disk space servers/accounts. It can even be done in memory if you want backlog without file on disk (think wrt54g and the like) | |||
:* Configurable logfile format using bip user, bip network name, channel name, and month/day (rotate logs) | |||
:* Complete text file configuration (+vim syntax file) | |||
:* Multiple IRC clients can access to the same IRC connection (same network, same nick) transparently | |||
:* SSL support on the port Bip listens to (client SSL) | |||
:* Oidentd support for multiple identities (oidentd spoofing) | |||
:* bip runs in one process and tries hard not to hog your CPU for no reason | |||
:* Low memory usage | |||
===Per user stuff=== | |||
* | :* Hashed password-based authentication | ||
:* SSL certificate check against a per user list of certificates, ca (optional), allows ssh-like security scheme through SSL certificates | |||
===Per connection stuff=== | |||
:* Stays in your joined channels | |||
:* Optional away nick when no client is attached | |||
:* Optional away status when no client is attached | |||
:* Send raw IRC commands upon connection to the network | |||
:* Configurable management of your nick when there’s a disconnection to the server | |||
:* Network stuff | |||
:* SSL support for server connections | |||
:* Multiple IP/hostnames, DNS round robin support | |||
:* IRC command interface, allowing to control or push some runtime configuration options. | |||
==Latest Release== | |||
0.8.9 and that can be downloaded [https://projects.duckcorp.org/attachments/download/61/bip-0.8.9.tar.gz here] | |||
==See Also== | |||
* [[jbouncer]] | |||
* [[Miau]] | |||
* [[ZNC]] | |||
[[Category:Software]][[Category:Bouncers]][[Category:Active]] | |||
Latest revision as of 16:59, 2 February 2014
| BIP | |
|---|---|
| |
| Platform: | Linux, Unix |
| Status: | Active |
| Latest release: | 0.8.9 |
| Homepage: | http://bip.milkypond.org/ |
Bip is an IRC proxy, which means it keeps connected to your preferred IRC servers, can store the logs for you, and even send them back to your IRC client(s) upon connection. You may want to use bip to keep your logfiles (in a unique format and on a unique computer) whatever your client is, when you connect from multiple workstations, or when you simply want to have a playback of what was said while you were away.
Features
General
- Transparent detaching and attaching of clients
- Proxy multiple users and IRC connections (multiuser, multiserver)
- Automatically join channels upon connection
- Backlog events (messages, nick changes, quits, …) upon client connection (optional)
- Optional timestamp backlogs
- Limit backlog to N lines per channel or backlog since since last client-quit or client-message
- Logging support – can be disabled for low disk space servers/accounts. It can even be done in memory if you want backlog without file on disk (think wrt54g and the like)
- Configurable logfile format using bip user, bip network name, channel name, and month/day (rotate logs)
- Complete text file configuration (+vim syntax file)
- Multiple IRC clients can access to the same IRC connection (same network, same nick) transparently
- SSL support on the port Bip listens to (client SSL)
- Oidentd support for multiple identities (oidentd spoofing)
- bip runs in one process and tries hard not to hog your CPU for no reason
- Low memory usage
Per user stuff
- Hashed password-based authentication
- SSL certificate check against a per user list of certificates, ca (optional), allows ssh-like security scheme through SSL certificates
Per connection stuff
- Stays in your joined channels
- Optional away nick when no client is attached
- Optional away status when no client is attached
- Send raw IRC commands upon connection to the network
- Configurable management of your nick when there’s a disconnection to the server
- Network stuff
- SSL support for server connections
- Multiple IP/hostnames, DNS round robin support
- IRC command interface, allowing to control or push some runtime configuration options.
Latest Release
0.8.9 and that can be downloaded here