× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi David -

At 14:11 12/26/2006, David Gibbs wrote:
Ken Sims wrote:
> You're going to need INPUT and OUTPUT rules with -j ACCEPT to allow port
> 5222 as a destination port and source port respectively.

Explicitly?

My default rule is ACCEPT anyways (I firewall at the router).

Not explicitly if they will get ACCEPTed by default, however you could put explicit rules at the tops of the chains and see if that makes a difference. If it does, then something already in the chain is blocking them.

> If you're still having problems, I recommend adding logging rules temporarily.

Bleh, I hate firewall logging.

No argument from me on "Bleh", but sometimes it's the best/only way to figure out what's going on.

If you're testing from a specific PC, you can put in logging rules just for that PC's IP address. Otherwise just for destination port 5222 and source port 5222.

Ken


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.