The host is the host of the bot. It can be either the alpha-form, or the actual IP address. And finally, the port is the port that the bot listens on for user connections. Now, for the askops part: This part assumes you added in a DCC to the bot as shown above.
If you don't have partyline access, you can still add an askop, but I'll get to that later. Now, if you don't have partyline access, you can add the askop in this way:. A hostmask, for the uninformed, is formed like this: username! Multiple Networks One of my other favorite things about psyBNC Do you have a bunch of channels you hang in on efnet, but also one or two channels on dalnet that you like to go to? If you're like me, you do Fret no more!
For this section I'll assume that you're familiar with most of the commands in psy. If not, get familiar with them before you try to do this. Ok, let's get into the commands. The first thing you need to do is add in another network:. Keep in mind that network names are case-sensitive. Furthermore, you'll be typing the name a lot, so if you're adding in dalnet, use the name dal or dn or something similar. Once you have the network added, you need to choose your vhost for that network.
If you don't choose one, it'll default to the IP the bnc is on, usually something gay like "my-shell-company. See this command? This is the format for all commands used on multiple networks. Simply prefix the syntax of the command with [network]. You'll just appear to be a regular schmoe. You head over to dalnet, and he's there in fxp. If you try to msg him by dbl-clicking on his nick int he dalnet channel, you'll really be sending a msg to him on efnet.
Some final things. Maybe you don't always want to be on more than one network. I prefer to always be on efnet, and then head to my other networks when I want to talk with ppl there. You'll still be connected to your primary network. OK, multiple networks also includes the psy internal network. Think of it as an ircd inside your bnc. By using the network name int you can create private channels that only ppl connected to your bnc can access.
Linking A cool aspect of psy is the ability form a psy-net through the linkage of multiple psybncs. The benefit of this is to create a private internal network secure from snooping, and secure from takeovers! Furthermore, you can let ppl on other bouncers use your machine's vhosts if you wish.
I love to have everything encrypted, including my links. Final note: If you use hostmasks to restrict connections to your bnc, you must add the other bnc's IP as an allowed host!! Variables are shown in this style. Use HOSTx for multiple hosts. This can include masks. This is encrypted as of version 2. Was this answer helpful?
Yes No. Bouncers have It is capable of proxying IRC Tag Cloud. Please enter a number between 8 and 64 for the password length. Password Length. The only thing that this configuration will not work for, in fact, is when you are serving different content based on differing IP addresses or ports. The server has two IP addresses. On one Any request to an address other than A request to The server machine has two IP addresses The machine is sitting between an internal intranet network and an external internet network.
Outside of the network, the name server. On the internal network, one can just use the name server rather than the fully qualified host name server. You have multiple domains going to the same IP and also want to serve multiple ports. The example below illustrates that the name-matching takes place after the best matching IP address and port combination is determined.
The server has two IP addresses In each case, we want to run hosts on ports 80 and Any address mentioned in the argument to a virtualhost that never appears in another virtual host is a strictly IP-based virtual host. The following example allows a front-end machine to proxy a virtual host through to a server running on another machine. In the example, a virtual host of the same name is configured on a machine at The ProxyPreserveHost On directive is used so that the desired hostname is passed through, in case we are proxying multiple hostnames to a single machine.
Catching every request to any unspecified IP address and port, i. Using such a default vhost with a wildcard port effectively prevents any request going to the main server. You can use AliasMatch or RewriteRule to rewrite any request to a single information page or script. The default vhost for port 80 which must appear before any default vhost with a wildcard port catches all requests that were sent to an unspecified IP address. The main server is never used to serve a request. A request to an unspecified address on port 80 is served from the default vhost.
Any other request to an unspecified address and port is served from the main server. The name-based vhost with the hostname www. To avoid problems with name servers or proxies who cached the old IP address for the name-based vhost we want to provide both variants during a migration phase.
The solution is easy, because we can simply add the new IP address The vhost can now be accessed through the new address as an IP-based vhost and through the old address as a name-based vhost.
We have a server with two name-based vhosts. In order to match the correct virtual host a client must send the correct Host: header.
0コメント