ISP Blocking Gnutella? I can get around it.....
 

Are you all interested or what? I have the solution but I don't want to type all this **** it unless some of you respond with interest. Let me know

Also check out my post about getting gnutella to work off a proxy/firewall/home/office/network whatever.

Hey - Of course I/We want to Know!!!!
It may come very handy one day......

\thanks
JD

I think my ISP is blocking gnutella too!!! Can you share the information on how to work around this?
Thanks!

Please share info re: how to get around isp blocking
 

I think my ISP has recently blocked gnotella please let us know how to get around this. thanks

why don't u just post it?
 

why don't u just post it instead of being hassled by a bunch of newbies like myself, that way i don't have to bitch a moan at you and i get what i want! + you don't get bugged because this is in a forum that is popular on the internet...
l8r
-prolly never be back because i dn't care n e m0rez

Please tell us how to get around ISP blocking
 

If I can't get Gnutella to work again, I'll have to get a new ISP...

Aaaaaaahaha
 

You guys kill me - especially unregistered with a little light on his head. Anyways, heres my theory as I have residing as a text file in my shared directories (which you all should do after reading this)



HOW TO GET GNUTELLA TO WORK EVEN IF YOUR ISP HAS BLOCKED PORT 6346

I thought up this little doozy while taking a ****, which is where I usually have all my ideas (Hmmmm....). It sort of relates to the concept of port mapping and the forced IP features you'd need to use in order to get gnutella to work off a proxy.

I'm assuming that you're on high-speed dsl or cable or something, and that your ISP or admin has blocked port 6346 so you can't get on the network. If you're using a dial-up the answer is really simple - go get netzero or something. The steps below are kind of specific to an office type environment, but if you on cable/dsl at home and being restricted you can do the same thing as long as you have another computer hooked up to the LAN and a phone line.

The slightly sad part of this little trick is that somehow, someway, you need to find one other computer on your LAN capable of dialing up an internet connection. The good part about that is that it needs to be only 1 computer dialing any free internet service or whatever doesn't have port 6346 blocked, and that it can be anywhere on your lan as long as you're able to connect to it via your computer on the LAN.

Step 1:

The trick is relatively simple - you're going to use the dial-up computer to be your gnutella host for searches and stuff. You basically dial-up to your free isp, use some kind of keeplive or whatever you want to stay on longer, and run gnutella on it. You can also use the gnutella reflector at clip2 or whatever that website is, if you plan on sharing this trick with more people on your lan and want to keep the network noise down to avoid the admin noticing.

Step 2:

Once a gnutella client or the reflector is running off the dial-up computer, go on over to yours and run up your own client. When it pops up set the incoming connections to disabled and the max connections to 1 just to keep it clean, then in the 'connect to' host field or whatever, enter the IP address of the other computer running gnutella on dial-up. Once you've connected to it you should be able to use the search feature and benefit from all the connections its made.

Step 3:

Once you can search all you need to do is get those direct connections going - ooops, only problem is that port 6346 is blocked - which is why you're reading this. In order to fix that its very very very simple really - go into the 'force ip' section and enter the IP address of the dsl/cable/high speed computer that you're on, and some random port thats not being blocked. Then set the option where it says something like, "port to listen for other hosts on" or just the 'listen port' for you, set it to that port. Whats its doing is telling the gnutella network, "ok even though I'm clearly browsing from that dial-up address, I want you to direct connect to me for transfers to my dsl line at this odd port"

NOTE FOR BROADBANDERS WITH ONLY 1 COMPUTER

I would suggest maybe signing on to a free account like juno, netzero, or bluelight, getting your searches done (set max searches to like 10 so you can get more done in 1 shot)... then disconnecting, signing on to cable/dsl again, and THEN, with your searches still up, use the force ip and 'listen on port' options to route your downloads outside of the port your isp has blocked. This part is just a theory so let me know if it works.

SUMMARY

In a nutshell you're browsing with the unblocked SLOW dial-up, but when its time for the downloads and uploads everyone will come knocking on your dsl line's door...Great part is that they're knocking with a port your ISP hasn't blocked. If this is confusing try it, laugh at your admin or your isp, then figure it out later.

ENJOY!!!!!!!




------ALSO!! If you benefitted from this tutorial please please remember that great things like this can only happen if people try to put back into the community. All it takes is 1 person to think up a sweet new trick or tutorial and upload it to a good website and the whole WORLD gets to benefit from it. All I did was take 30 minutes of my time to share what I've learned and all the poor people who couldn't get this to work before can now enjoy it.. So if you have a trick you can do to some program, or you figured out something that you think others will have a hard time with, open your notepad, type it up, and upload it to a related website or someone you trust to distribute it. You will feel really really good I promise you :) :) Also feel free to take this paragraph and add it in to your own tutorial, thereby spreading this message of good-will.

------One final note - A good friend of mine ;) writes alternative music and has his own website where you can download his music, see band pictures, and see upcoming gig dates. If you're into this kind of music head on down to http://www.mikeperalta.com and listen to the stories he has to tell. Its pretty cool.


Ok I'm out - Peace!

why not just everyone use some port ... whatever you want
between 1024 and 65000 ... as example ... than nobody can
block a specified port ...

Hmmmm
 

I thought of that before, but if I'm correct, would that divide the network? Its my understanding that all connected hosts need to have the same port....so random ports would only seperate us. What are all your thoughts?

PS keep bumping this thread yahoo

Re: Hmmmm
 

Wonderful typing, please keep up the good work, but you are not correct.

Points are:

1. If you are connected to ANY other clients/hosts then your ISP isn't blocking you.
2. If you can web browse, your ISP isn't blocking you, Gnutella will work fine.
3. Everyone has a problem geting kick started on the network, gnutellahosts 6346 is too busy, your client reads old IP's first, who knows, but most times if you wait a while it will find a few recent IP's and away you go. You may want to clear your hosts list file and start from scratch, also try the limewire 6346 host list service.
4. ISP's could throttle you, then you would never know and they don't have to hear the complaints. These guys are not stupid.
5. Firewalls do not block Gnutella, see #2 above and read up on push. Push is not needed for you to download files from other clients!
6. Some idiots change to port 80 or 8080 and/or open those ports in their firewall because they have no clue.
7. This is not rocket science.

Port 6436 is for incoming connections, it is where you listen, you can set any port because you tell others that you are on that port so they can find the files you are sharing. You don't need a "public" incoming listen port to operate on the network!

Let me say this again, you don't need this listen port to download, search, or upload!

Once you connect via a "outgoing" connection YOU CREATED AND OPENED to any other host, you are able to receive and send packets, search, request push, whatever. If you download direct, you create a connection to the host server directly! It is on lower ports like 2000 or 1000 range, just like any browser does, so...

IF YOU WERE BLOCKED YOU COULDN'T BROWSE!!!!!

Changng your client to port 80 or 8080 is STUPID because those ports are for web SERVERS! Then you really tell your ISP you have a sever running (if they even bother scanning all the computers hooked up to the network). Hackers are scanning for these ports, don't think it's your ISP, they have better things to do like download DIVX porn via their T3.

ISP's would look for high bandwidth use on a every day basis, if they bother at all. On a 56K line, who cares?

So stop thinking it's your ISP and see if the girl next door is hooked into your phone line and if she is, make a DIVX movie of her naked in the shower and SHARE IT (just kidding).

Let's go over this again. If you CREATE a connection firewalls assume you want to do that and allow the connection because YOU CREATED IT. You could close everything via a firewall and still browse if it allows "outgoing" connections. Gnutella would work just fine! You could still be hacked if you had a program that CREATED a connection to Mr. Hacker, so don't feel so safe and get a better OS and quit using MS "we never fix security holes because we are too busy taking your hard earned $$" products like Outlook.

If you can web browse Gnutella WILL WORK!

Port 80 or 8080 are SERVER PORTS! Servers LISTEN on them for HTTP requests. Your browser DOESN'T USE PORT 80 ! YOU ARN'T RUNNING A WEB SERVER!

Please feel free to post this any time someone asks about this.

Ok but...
 

That covered alot, yeah, but that didn't really answer the quesiton I asked - let me clarify:

(Of Course I'm guessing at all this so my apologies if I'm wrong)

When I talk about an person's ISP blocking you, I mean that they've blocked out the publicly established port 6346... meaning you can't make any outgoing or incoming connections on 6346. This would not effect connecting to clients and hosts that know your 'forced IP' which would be some odd port like 27015 (heee heee)... I'm sure even other hosts would eventually catch on via hosts that already know you, and ask for you on that port instead of 6346 so incomings would work fine too.

What I'm saying is regarding that very first connection you make to any host listening on 6346... Its my understanding that since they're listening on 6346 that you can't make a connection to them on anything else, because they're only listening on 6346. Making those first connections would be blocked by your ISP since router.limewire.com:6346 and such all have to be on 6346. So what I'm saying is how would you get on the network that uses 6346 if you use 1000? ... Maybe write down a few servers you know of that use an odd port and connect to them first, so they can spread the word for more incomings for you? Also, if someone is on dial-up wouldn't no other server even consider incoming them?

I would appreciate all the chiming in possible, as a thread like this only promotes learning for all who read it. Thanks for the feedback, unregistered.

Mike

I can't say I really understood the logic of making the default port 6346.

At the time it came out, one of the advantages Gnutella boasted was that you could change the port to whatever you wanted so that it couldn't be blocked simply by the network admin blocking the application port. This was a good idea.

Unfortunately, almost everyone kept the default of 6346. There is no real reason for this, since it works quite well on whatever port you use. Personally, I normally use port 80 whenever I run it, since I WANT my ISP to think I'm only running a web server.

hmm 2
 

Meridun, you say you connect normally via port 80. How do you establish an initial connection though?
I've been connecting through my work T1 line with no problems, until recently when they must have blocked access to port 6346 (probably after seeing me downloading all day). I get timed out when trying to connect to the routers, and IPs I find from web pages are all on the same port, so I have the same result.
unregistered "If you can web browse, your ISP isn't blocking you, Gnutella will work fine" doesn't make sense, and "gnutellahosts 6346 is too busy" is not the case because I connect at home through netzero in 10 seconds. And "7. This is not rocket science" maybe applies to you since you're probably on the computer 24/7, but for normal users like myself that just want to share it's a @#$% pain in the *** to figure this **** out. So, I'm about to try Mike's lengthy remedy, anyone else have any suggestions or input on this problem that I'm sure many many people are having??

A possible solution!
 

My Reply to this Problem is to tell the deverlopers of the Gnutella-software like limeware that the update hers software with this feature:

Every start of the Gnutella Client, the program must changed automatically the listing incoming port to an another randomized port like 25468 or 80 or each other port until 65536 for instance.

With the same manner must work all Gnutella Clients around the net.

if the hostlist (Gnutella.NET) is update, you can see many hosts with different kinds of Port.

I hope it is manageable.


Sorry about my english. I come from Germany. :-)

Email: chatcafe@firemail.de

moving ahead..
 

got Juno on my system now, and I connected with no problem. I got my searches done, then kept Bearshare up and got back onto my work T1 line. I read Mike's suggestion for forcing an IP, but it's not clear to me where and how to get this to happen. Which IP? I get the picture with two compuers, but it's not clear to me how to do it with one.
Anyone that can help at this point?
>>L