powered by Jive Software

Running Wildfire on Multiple Ports


Some of my users are not allowed to talk on 5223 or 5222. So I was wondering if there’'s a way to run the same instance of wildfire on many ports. (Would like to add port 443 without moving a currently used port.)



Hi Rob,

as far as I know there is no way.

There were rumours of a redesign of the port handling so one should be able to bind multiple ports to multiple interfaces and use probably also ACLs.


If you’‘re running on a linux box, you can create iptables rules to do that. Here’'s a barebones example:

iptables -t nat -I PREROUTING -p tcp --dport 443 -j REDIRECT --to-ports 5223[/code]

That would redirect incoming traffic on port 443 to port 5223.

PS - Let’'s see you Windows weenies do that!

if you have a decent firewall they usually have port redirects

I wouldn’‘t abuse the https port with xmpp. /etc/services and assigned port numbers are there for a reason. A real solution would be either http polling or http binding, although I’‘m not sure how jabber supports that. I think you can get one of them by using an external component. Check jabber.org, they have a list of servers and iirc there’'s a Wildfire column that hints how to do that.

Just my 2cc,


Hi Ben,

as 443 is the SSL port most proxy server and firewalls support connections to this port and so one can use XMPP over a proxy and through firewalls. Ports 5222+2 are usually blocked so this is for a lot of users the only option to connect to a server.

HTTP binding is nice, but I’'m not aware of a Jabber client which supports it - the server admin must add an application like JWCaht or MUCkl and the end users needs a browser to access it.