[Slackware 10.2] Cannot send files through amsn or mercury
 

Hello people! I use Slackware 10.2 and I am being able to connect normally, but I am not being able to send any file through amsn or mercury (but I am being able to receive). I am connecting to the internet through NAPT, but it doesn't seem to be the problem, as in Windows I can send files normally. I have already tried:

ipchains --flush

But also no success...

Is there anything I can do? Thanks!

please don't double post!

You are probably behind some other firewall. You didn't say how you are connecting to the internet, or if any other incoming connections work. I don't know how those programs sends files, but it sounds like dcc.

You will need to provide more information.

..aaron

Sorry for the double post, drkstr. But no one seemed to know how to help me on Slackware Forum. Ok, here is a little about my network:

I am connecting 2 PCs (192.168.0.2 and 192.168.0.3 - the first one is mine) to a router (D-Link DI-604). The router has a firewall, but I "disabled" it by allowing ports 1 - 65535. I also indicated 192.168.0.2 as the IP. The router goes into a 10.0.0.X network. The router is 10.0.0.1 and my ADSL modem, 10.0.0.138. On ADSL modem, I NAPTed some ports to the router (so yes, the modem is the real "firewall"). The modem is a Speedtouch 510 ADSL. So, here is the config:

PC1 + PC2 -> DI-604 -> Speedtouch 510 -> Internet

I don't know if it is a network error, because as I said on Windows the things work fine. I can send files not only through default Microsoft's MSN client, but also through Trillian, another third-party MSN program. So, if it would be a network problem, why would Windows work and Linux not, if the config. is the same:

IP: 192.168.0.2
Mask: 255.255.255.0
Gateway: 192.168.0.1
DNS: 192.168.0.1

As I said, I tried on linux amsn and mercury, so 2 different clients work on windows, but 2 different clients doesn't work on Linux...?

I don't receive any error message, it is just timeout while trying to send file. I can receive files normally. I don't know acting as a server because I didn't try it yet on Linux, but shouldn't be problem on the ports that were NAPTed on the modem, as on Windows I have been able to work as http server.

Thanks! :)

Update: I am also having some problems to receive files...
Update2: I can only receive files when I do iptables --flush . But still cannot send them.

First, you need to open port 6891-6900 on you linux box
where eth0 is the correct ethernet device. You then need to change the settings in the client and tell it to use the routers IP (the external one) instead of the IP to your NAT'ed Linux box.


regards,
...aaron

**edit**
ALso make sure those ports are being forwarded to you Linux box. Although this should be ok since it works OK in Windows.

drkstr,

Thanks for the help! I have already opened the port with the command you gave me but I didn't understand the second part...?

Another thing: I don't know if it can be a modules issue. I am a little new about kernel compiling and tried to compile my own kernel.

The IP address configuration, or the port forwarding on the router? I'm going to assume the IP address.

You need to open up the options, or settings or whatever it's called on your client ( amsn? ) change the setting so it will send your external IP address instead of your private IP address.

It appears that you're client is using the old' school method of file transfer where it sends an IP address and port # to the receiver, at which point they connect to you at the desired location. In order for this to work, you need to A) give them an IP address they can actually connect to, and B) make sure it is possible to connect to the box hosting the file via this IP address.

IE: tell your router to forward incoming traffic on this port to your Linux box.

regards,
...aaron

Let me see if I understood...I need to change the configs to send my real IP address, the one that my ADSL modem got?

Edit: Yes, I am in dynamic IP config, which means that everytime my modem gets a different IP.

What does this mean? Are you telling me that your dsl is not a static IP or that you told your amsn client to grab the IP from the gateway (your router) and not your linux box? I am not familiar with amsn so I can not tell you which option to set specifically, but you need to either give it the specific external IP address or tell it to use your gateways IP address. (note: If you have not done so already, you may need to specify the default gateway in you /etc/rc.d/rc.inet1.conf, for the later to work)

...aaron

Let me make myself a little more clear. I have:

1. My Computer's IP - 192.168.0.2
2. The router (gateway) IP - 192.168.0.1
3. The router (gateway) IP on the modem network - 10.0.0.1
4. The modem internal IP - 10.0.0.138
5. The modem external IP given by ISP (dynamic, not static): XXX.XXX.XXX.XXX

Should I give to the program the 2nd or the 5th IP? Thanks! :)

ultimately you need to give the adr from #5 to the file receiver, but it might resolve it automatically if you tell it to grab the IP address from the gateway (either #2 or #4). If you tell it to grab the IP from #2, then #2 needs to be set up to grab it from #4. It will probably do this for you with no extra configuration, but if not, you will need to give the gateway address of #4.

Hope that was a little more clear (good idea with the numbering!)

...aaron

Aaron and guys.

I am so sorry for the delay answering this. I've spent some days off the internet to solve personal problems but I am back. Unfortunately, I don't bring good news: I tried to specify #2 or #5, but it didn't solve the problem. Amsn auto-detects my ip address, and when it does, gives me #5 but I tried to specify it manually and didn't solve too. I really don't know what to do, I am totally lost. As I said, this can't be my modem or my router because it works fine on windows. So, what it could be...any help will be still appreciated, I am not willing to give up so early anyway...

I tried iptables --flush again...no results.

Tried to recompile the kernel without any iptables module. Disabled: Networking - Networking Options - Network Packet Filtering (replaces ipchains)

Still NOTHING!