On Wed, 2003-06-25 at 14:14, [EMAIL PROTECTED] wrote: > I am sorry, but I have no idea what you are talking about. Can you > please try to explain your problem with a little more detail, or add > examples? Thank You
Ok. Let's say that I have two clients running. Client1 is connected to Net1 and Net2. Client2 is connected to Net3. I /set irssiproxy_ports Net1=10001 Net2=10002 Net3=10003 Now i load the proxymodule on Client1. Cool, no visible errors :) Now i lood it on Client2. Irssi: Proxy: Listen in port 10001 failed: Address already in use Irssi: Proxy: Listen in port 10002 failed: Address already in use Irssi: Proxy: Listen in port 10003 failed: Address already in use Irssi: Loaded module proxy/irc Ouch. Logical because Client1 binds all 3 ports to itself. When I try to connect on 10001 it goes fine (ofcource). Same with 10002. When I try to connect to 10003 it will connect to Client1 (that ins't connected to Net3) and I will get something like: !Net3.proxy Not connected to server Kinda logical aswell but bogus. Now a solution would be to bind the proxyport to Net3 (and the others) when I actually connect to Net3 in the client. A problem with this approach is what is going to happen when I connect to Net3 in two clients (but thats a problem now aswell). Also what will happen when I disconnect from a net? Should the socket stay connected or should we disconnect the client using the proxy (if any)? I hope this will help.. I find this to be a very annoying problem in this very nice module. Kindly regards -- Christian Axelsson [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
