Leopard Firewall and Azureus

Soldato
Joined
10 Apr 2004
Posts
13,496
How do I get it to work with the incoming connections all blocked silently but still let Azureus work, I've added it to the allowed applications block but still doesn't work :(

Any ideas?

Mainly want wireless security, ill be on the 5 Ghz Band anyway soon, should I worry or with incoming connections fully open on WPA2 ok??

Cheers :)
 
What does your wireless security settings have to do with Azureus not connecting? And I know you've mentioned it a few times already - just run WPA2 PSK on the Airport, just because it's n doesn't mean you don't need to secure it - there's a lot of Pre-N hardware out there, and it will let b and g clients connect anyway.

Also, 802.11n isn't 5GHz, 802.11a is.


The new N standard is 5Ghz, I've set my Airport Extreme to 5GHz N Only, so nothing but N 5Ghz Supporting equipment will find or connect to it. The encryption between my MBP and it is WPA2.

I have a second wireless base (BT HOME HUB) that only supports the "legacy" ones, im using g with it as the Airport is too far away atm (being a gigabit hub). Im using WPA with this.

Thats all fine.

Now, if I turn my Leopard firewall off so to allow all incoming connections (so torrents upload) will my MBP be visible to anyone to connect to? (because if it can't be seen/accessed then I will disable the firewall).

However if they can access it, how do I get Azureus to work with the firewall in place. I've already allowed access to incoming ports for it but it still doesn't want to go green :(

Im currently using it with gigabit ethernet and wireless off with no software firewall.

Basically how can I have a firewall AND Azureus working?

Cheers :)
 
I think the AirPort is causing problems because there's two layers of NAT here. Switch the AirPort into Access Point only mode (I think you have to disable DHCP and turn off routing), then connect it to your BT router using one of the LAN ports. This will rule out any issues being caused by the AirPort.

Already done.

its just the OS X firewall thats the problem.

As it works everywhere with it off, and doesn't when its on... :confused:
 
Back
Top Bottom