Subj : Firewall settings
To   : Jerry Schwartz
From : Paul Quinn
Date : Wed Mar 17 2004 01:01 pm

Hi! Jerry,

In a message to All you wrote:

 JS> Admittedly, I'm weak in this area, but whenever I set up my firewall
 JS> to allow only port 24554 for BinkD it doesn't accept incoming
 JS> sessions. Only if I leave it wide open, does it work properly. Is
 JS> this because BinkD uses other ports for other purposes?

If you've left the BinkP port configured as per a default BinkD config file, 
then everything should be hunky-dory.  If you're running HTTP* or SOCKS? 
servers as well on the firewall machine, then you'll have to specify that in 
the config file ("HTTPS or SOCKS settings").

I've had a BinkD/linux machine call out through a Windows firewalled (Proxy+) 
machine, using port-forwarding/mapping on the standard BinkP port.  Currently 
Radius does it as such, on all configured ports.

Double-check your BinkD config file (iport/oport entries, I think) and your 
firewall's setup.

Cheers,
Paul.

--- Radius v4.010/03.02.04Jan_Beta
 * Origin: Quis caveam tuam quassit?            (IP 1200-1500 UTC) (3:640/384)

.