Downloaded Amule and did a check on ID status using port test it came back telling me the port 4662 was unreachable probable due to firewall.

However using emule on 4662 and bit tornado on 6881 in xp with no problem both ports are forwarded and router set up fine.

In Suse I have dissabled the firewall in yast but this does not sort out the problem.

what do I need to do in Suse to port forward if you know what I meen.

I regularly use this site http://corz.org/comms/hardware/route...ter.how-to.php

in order to make changes in telnet for nat rules is there any rule I have to create for amule.

can anyone help??

Ok let me refrase things!

why is it that using win XP I have NO problems running things like p2p with all specified ports open / forwarding, but when I run Suse 9.2 and previously 9.1 I am told that there is a nat error or firewalled when I know for a fact that this is not the case?

How do I check ipconfig cos the only thing I can think of is that I have a different ip address in linux (but that can't be can it?)

Or could it be that I need to ad the same rules to linux telnet??? this is compleatly alien in linux.

One problem I do know is that even though I have assigned my own IP addy I have had to restart DHCP other whise Suse can not access any network.

So to reitterate ( Win XP ) My nat rules are ok, the ports are forwarding and the firewall is not the problem.

So why is it that I am getting these problems in Suse? I have installed Azureus and set nat rules to 49210 as Amule is supposed to be using 4662 but still again the nat error.

If anyone can advise on this problem it would be appreciated.

The different ip address of linux could be a problem. When you define port forwarding you must define where the protocol will end up going to.

So, let's say your WinXp has Ip 192.168.0.50 and linux has 192.168.0.51, then if you have already set a port-forwarding rule says external-Ip:4662 <=> 192.168.0.50:4662, then obviously 192.168.0.51 will not be able to get the packets.

Besides, whenever you change the DHCP server, you only need to use dhclient to update your ip address. (If I understand your problem properly...)

And I see no connection between the stuff above and "linux telnet"

Only mentioned telnet grasping at straws? and because I set a lot of nat rules to sites where I can just cut and paste into telnet to save time rather than going through the router each time, So lets forget telnet I didn't think that would be the prob.

So anyway how do I check my ip addy in linux in windoz it's through cmd then ipconfig as you know, but not sure how to check the ip addy in linux. At least then if I know that the ip in linux is different I can then set that ip in nat.

Ok found ip addy so no probs So straight to the point!

How do I do port forwarding in Suse? do I need to touch DHCP and routing in yast? if so how do I configure them? or do I have to do it through terminal? Same thing how do I do it??????

I am almost ready and willing to move over from Windoz completely to Linux. but want to be able to take continue where I left of in windoz.

Checked suse's main site for info but it ain't very indept.

basically port-forwarding in suse is all about firewall setup.

I personally like to use shorewall (http://www.shorewall.net/index.htm)

Simple to setup.

But there are many similar package. Google for linux firewall shall give you a lot of information.

Thanks.

I have been getting a lot of help from suse linux forum on this matter I will check out the suggested package and get back to everyone when i've sorted things out.