SlackwareThis Forum is for the discussion of Slackware Linux.
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.
this clearly has nothing to do with slackware. just because you use slackware doens't make it relevant to slackware as a linux distribution. and google has plenty of hits to help you with getting bitorrent seeding going. of course you don't need to open any ports to just download stuff.
A Redhat moderator in a Slackware forum? How odd...
I assume the poster wants to use bittorrent to retrieve the freshly released Slackware 11.0 ISO images, and in sofar it is a Slackware related question.
Anyway, acid_kewpie said it already, for downloading you don't need to open up ports on the firewall. Although your speeds will improve if you instruct your firewall to forward bittorrent traffic to your computer's IP address (use port range 6881-6889) so that your bittorrent peers have direct access to your client.
Thanks Bob
actually i had the first four disks downloaded last night and I wanted to start them with the bittorrent client so I could give something back ie my bandwidth
Using the client in 10.2 extra it verifys the 100% file that I downloaded and then stalls, it just sets there
When I turn off guard dog the upload takes off
I have the normal ports opened both ways in Guard dog ie 6881 thru 6889 and 6969, but it wont hook up when Guard Dog is enabled
I thought maybe there were some undocumented ports I didn't know about.
AlleyTrotter actually you can set any port, if you use the command line client, you can specify it.
Example, i've a simple bash script to start downloading:
A Redhat moderator in a Slackware forum? How odd...
how is that odd?? i should stick to my own "patch" should i? and that patch isn't RedHat anyway, i don't moderate that forum... and clearly here this is not a slackware question, it's either a networking question, which *IS* my forum, of a general software question.
this clearly has nothing to do with slackware. just because you use slackware doens't make it relevant to slackware as a linux distribution. and google has plenty of hits to help you with getting bitorrent seeding going.
Fwiw, I hope I dont get banned I love these forums, and I respect that you did notice that the thread was in the 'wrong' place. But would not a simple note from you to the writer indicting that the thread is going to be moved and advising the user to follow the forum rules suffice. Your post was kind of, well 'sharp'. Granted things do not always come out as we intend in writing; and this may not have been your notion.
Secondly, and this is a rhetorical question/gripe of mine. Why do people refer an honest, and well written question like the original writer of this thread, to google. As advertised, is not LQ a place for new comer's to linux. Is not LQ the official sanctioned home forums for slackware? I grew up and believe to this day that no question is stupid, except un-asked. As we all know, a lot of information out there is old, wrong or somewhere in the middle. I belive we should not shame any writer for asking a question that we think is 'stupid'. Are we are a community or are we not. If LQ's policy has changed, then please let me know, and I'll stop coming here and go to ubuntu and use their lovely happy forums and sniff flower's and listen to some Shania Twain . Google has their own linux forums, should we all go there for posts and let LQ die? I just don't get it.
I wouldn't be using linux if LQ's userbase edit/ wasn't willing to put up with this old fool's dumb noob questions. And I greatly appreciate that people have not shamed me in this manner and shamed me. But I see a trend here, and it does not make me 'warm n fuzzy'. If you don't like a question, you don't have to reply, just move on
If you can slag me off as eloquently as that you've no fear of being banned... I absolutely agree with you, and i did reply effectively imho... i guess it's all in the way you read things back in your head. seems fine to me at the time.
That was very well said Old_Fogie.
Unfortunately what you said is sadly becoming true here. The constant "go to google with your way too easy question" is one of the reasons why I and many others left JustLinux (formerly the beloved LinuxNewbie.org) forums. It's like it's happening all over again. The community atmosphere, where everyone is welcome, is vanishing. And now not only are you required to search google first but you must research the forums and choose an appropriate forum for your problem. And God help you if your post gets moved to one of the Sub-Forums, cause no one looks there. And moving posts doesn't help get them the exposure like many mods claim. There are too many forums and they are burried too deep here for many theads to get any attention at all. Fortuneately there are new Linux Forums popping up all the time.
Besides, I love the easy questions. If it wasn't for them my post count would be around 2
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.