Tom Murphy <[email protected]> wrote: > ext_if=em0 > ext_xmpp_addr=aaa.bbb.ccc.ddd > > table <xmppServers> { 192.168.1.1 192.168.1.2 192.168.1.3 } > redirect xmpp { > listen on $ext_xmpp_addr port 5222 interface $ext_if > tag xmpp > forward to <xmppServers> port 5222 mode roundrobin sticky-address > check tcp }
I'm pretty certain this breaks things if you don't have server-support for load-balancing. If all the servers listen for the same domain and each server thinks it is resposible for the domain and thinks it is resposible alone, you will have the following problems: (Let's assume you have servers A, B and C, all handling the domain foobar.org) * A user on A can't send a message to a user on B or C * When server A is connected to Server qux.org, servers B and C can't connect to qux.org. You can interchange A, B and C here. Thus, the servers need to do some communication to allow load-balancing. Just distributing all incoming connections among servers A, B and C is not going to work. If you read the XMPP RFC, you will see why exactly. -- Jonathan [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
