Click to See Complete Forum and Search --> : mutella questions


lonescout
01-01-2003, 04:23 PM
Hi,
I been playing with the concept of using mutella as a P2P. A my machine is quite slow, I really like running as much CLI stuff as possible. I seem to be running into real problems with mutella though, as it appears to be connecting, but won't search (and hence won't download). I've read everything I can get my hands on for documentation, which is scarce, and can't seem to find any real "newbie-friendly" documentation. Was wondering if anyone on here uses this package, and may have any imput as to what I'm doing wrong. Below are the specifics:

____________________________________
I'm running Redhat 8 (sharing an cable internet connection through a Windows XP machine)
The internet connectivity is fine (can browse, get email, run gtk-gnutella, ftp etc...)
The LAN errrr Samba...well lets not get into that...I can see my machine on the windoze machine, but can't browse it, and can't see anything from the Windoze machine from my box...but that's a whole other battle when I get my Valium prescription refilled)

standard setup:
winxp machine 192.168.0.1
linux machine 192.168.0.2
appears to be using braodcast of
192.168.0.186


I'm trying to get Mutella to work, and it appears to be connected to several servers, but then does nothing:

Screenshot after the "info" command (http://www.lonescout.net/screenshots/mutella.png)

Here's the mutellarc setup:

mutellarc page1 (http://www.lonescout.net/screenshots/mutellarc.png)

muttelarc page2 (http://www.lonescout.net/screenshots/mutellarc2.png)

mutellarc page3 (http://www.lonescout.net/screenshots/mutellarc3.png)

If totally disabled the firewall for now (until I get the Samba thing figured out), so don't believe there's any issue there)

If anyone else has seen this problem or has any suggestions, ANY info would be much appreciated.

lito
01-02-2003, 07:43 PM
I downloaded mutella to see what you were talking about. I have nothing configured and don't have a clue what to do with it, but I do notice one difference.

My ifconfig eth0 command tells me that my current IP address is 192.168.0.2.
My mutellarc file shows that my Local IP is the same.

You said that your linux box had an address of 192.168.0.2 ,and yet, on page 1 of your mutellarc file you show a Local IP of 192.168.0.189. Is this what you are calling a broadcast address? I believe ( from my extensive knowledge of mutella ) that these should be the same.

Sorry I can be of no help. I'm off to the mutella page to see what I can do with this, assuming I can get it to work.

lonescout
01-02-2003, 08:49 PM
yeah, after reading the instructions on the mutella page, I'm REALLY confuse as to what address to use.
Part of my problem is, I'm no network expert, and I don't even know what the "broadcast IP" is all about. I've tried changing that to 192.168.0.2, 192.168.0.1 (the XP machine's IP that's providing the 'internet sharing', was playing withe 192.168.0.189 (that's an address that I noticed was be broadcast over the network (coming from my machine) when I was playing with the network analyzer (KDE)... I just assumed that it had to be was was being called the "broadcast address", since I didn't set it. I think that Windoze is taking care of making sure that our cable provider only sees one IP using the connection. Anyway, if used every possible variant of those settings I can think of...sometimes it looks like it's going to logon then, when I type 'info' every 30 seconds more connections have dropped of. with and without the firewall (no change). Even changed IPs to 0.0.0.0/0 still no good. i've pretty much written it off as unusable. Really appreciate the info....lemme know if you find something

deimos
01-03-2003, 01:00 PM
The term 'Broadcast IP' is relative to the context.

In networking terms, it is a combo of the host and network parts of your ip address. Generally, and in your situation, it would be 192.168.0.255.

But mutella's docs might use the term to describe something else. A few possibilities off the top of my head:
1) The external ip of your firewall. Basically this is the ip your client will bcast to the p2p network for the other clients to connect to.
2) The actuall ip addy of your machine.

Whether it's #1 or #2 depends on your network setup. For a soho network, it will generally be #1 as your firewall/router will likely accept all incoming connections and use port forwarding to allow comms to internal hosts.

Assuming we need to set it for #1:
What is the 'external' ip addy of the XP machine? The one you get from your cable service.
Is XP configured to accept incoming connections and handle port forwarding?

I'm sorry if this way off, I am not familiar with mutella.

lonescout
01-03-2003, 04:33 PM
Well, after diggin around through a bunch of posts, this is how I got it to "connect'

I currently run 'gtk-gunutella'. I copied the 'hosts' file from there into ~/.mutella/hosts and it now connects. there are 2 major problems with this:

1. the gtk 'hosts' file is pretty big....mutella recommends < 100...guess I could weed out a bunch, but which one??? decisions desicions... ;)

2. Almost all of the connections end up either being 56K or ISDN (not bad since you can leave it running forever (I am getting alot of hits)

3. Every time I try and download something, i get a permission denied error.

Gonna have to keep playing with it.....

Also get an error on startup "[cannot find /home/spooky/Desktop/shares/part]"... i never created or told it to create this file (so of course it doens't exist, and I can't find anywhere in the configuration that it calls for this... gtk puts partials in /home/spooky/Desktop/shares/partial just fine

Anybody else get anywhere with this?