Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
This is the way I would configure it. This should work as long as the following exist.
1. Azureus is configured on tcp port 50505
2. If there is firewall router between computer and the internet, then the wan tcp port 50505 needs to be forwarded to internal lan machine running Azureus. This works best when the lan machine uses static IP versus getting one from the routers DHCP pool.
That should be all that is needed since there is no blocking of outbound connections, so no outbound line is needed.
# Generated by iptables-save v1.2.11 on Fri Nov 11 13:20:40 2005
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:RH-Firewall-1-INPUT - [0:0]
-A INPUT -j RH-Firewall-1-INPUT
-A FORWARD -j RH-Firewall-1-INPUT
-A RH-Firewall-1-INPUT -i lo -j ACCEPT
-A RH-Firewall-1-INPUT -p icmp -m icmp --icmp-type any -j ACCEPT
-A RH-Firewall-1-INPUT -p ipv6-crypt -j ACCEPT
-A RH-Firewall-1-INPUT -p ipv6-auth -j ACCEPT
-A RH-Firewall-1-INPUT -d 224.0.0.251 -p udp -m udp --dport 5353 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A RH-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
-A RH-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 50505 -j ACCEPT
-A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
COMMIT
Hope this helps. Any questions please ask away.
Brian1
No luck Im afraid. Placed exactly what you have written and checked my harware gateway with has the azureus machine listed as a virtual server with port 50505.
Even if I deactivate the CentOS firewall and SELinux nothing changes. I am getting "blue faces" which according to the documentation indicates a NAT error. If that helps?
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
Is htis the default port for Azureus?
If not try setting it to the default on both firewall and router.
It might be best to leave the firewall turned off till you can get the router to port forward to the llinux's lan IP.
It seems some ISPs are wise to BitTorrents and do not like the concept and block the default ports. Users are avised to make their own.
Here is what I have found though. I am running a private lan 192.168.1.* and did not realise that it is sitting in aother private lan 172.26.0.* which has the gateway link to the Internet. I am trying to find out how to login to it as this is where I guess I should set the Azureus details.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.