Topic: IPTables and Wildfire (need help setting rules)

[tias]

I installed the rpm:s from the wildfire webpage. Got the server up and running but my problem is the iptable...

I have no problem connecting to mine wildfire server within the local net. But if I try to comunicate with other jabber servers or if someone should connect to mine jabber server it will not be permitted. I have traced the problem to iptables because if I temporary disable the firewall everything works just fine.

Mine SME is running in server-only mode and is behind a router (which is correct configured with port-forw) but SME wouldn't let any outside enters the wildfire server.

How shall I set up the iptables to accept mine wildfire and connections from the web? To disable the firewall on SME is something I will not do.

Would be great if someone could help me set up the rules for iptables, it's kind of a mess now. Haven't any knowledge about iptables.

[raem]

tias

> Mine SME is running in server-only mode and is behind a router...

Perhaps your issue is opening a port on sme server so Wildfire can use that.
See the FAQ
http://no.longer.valid/phpwiki/index.php/SME7FAQs#Firewallx2f.Portx20.Fowardingx2c.Openingx2c.Blocking

or search the forums for the db commands to do this ie search on port opening


>...Haven't any knowledge about iptables.

....and that's a good reason you shouldn't be changing them !

[egerards]

See the FAQ
http://no.longer.valid/phpwiki/index.php/SME7FAQs#Firewallx2f.Portx20.Fowardingx2c.Openingx2c.Blocking

or search the forums for the db commands to do this ie search on port opening

Just recently I was also running my SME server in server-only mode and the described ways of opening a port didn't work. Since the beginning of this week  I switched my adsl modem from router to bridge and my SME box from server-only to server-gateway. Now the port opening procedures do work.

So I'm afraid that this won't help tias much. A temporary workaround could be to disabe firewalling (/etc/init.d/masq stop), but beware of potential security risks!