iBurst Open DC++ Hub FAQ/GUIDE

riverdusty said:
I'll look into it. The Hubs i've looked at have an option for ssl. Problem is we'd need to enforce it which means tutorials and 'supported ssl clients' and stuff like that. I say we need to enforce it because if anything is unencrypted, iBurst will pick up on it. (we know they dont read these forums, so its safe to discuss lol)
Let me get my server up and running and we can experiment.
Click to expand...

Actually as hard to believe as it is, they DO read these forums. They just don't care about our complaints (or us) at all. The reason I know this is because last year when I (and several others) was cut off for overuse I phoned to find out what the fudge was going on. After giving my username "Basjohn" to one staff member (the fairly high up girly with the name starting with an S....errr...me thinks) she told me she's a big fan of my website and checks it regularly....which was awesome considering she helped make the decision to cut off my internet access and thus my ability to update it.

Further to that is that when speaking to Allan Knott Criz-aig himself he stated "Your hub is congesting my network" when I hadn't even mentioned it to him which shows he already associated me with ownership of the hub whiiiiiich leads us to believe he and his staff read this silly long forum topic right here.

Soooo that's why I'm being a little underground with posting the current test address but I'll still give it out to anyone who wants to come in and help test as just 2 people are not nearly enough to be conclusive yet.

Will look forward to news on the encryption thenzies!
 
QuickDC an ADC/DC++ client for *nix

Ok, been hunting around for a DC++ client for my OpenBSD machine.
Linux-DC++ uses this dumbass python script instead of a Makefile which is just the stupidest thing under the sun, really really, dont try this, it breaks and its stupid, who the hell thought that was a good idea?

So giving up on that I went back to QuickDC which is not complete. It needs work and i'm currently working on getting it up and running.
It actually works, it starts, it connects, i can download.
Biggest Bug so far is that the 'create directory' is incomplete. So everytime you start a download, you have to manually create a directory with the username from whom you're downloading. I'm working on it!
The actual source code has "FIXME:..." where things dont work. lol.
If anybody knows anything about programming i encourage you to go get the source and have a look at it. Lets get this project up and running, get a windows port, and start pwning teh interwebZ.
 
Friendly Reminder

As Basjohn mentioned a few posts up..
There seems to be some hope for the hub yet, but we need more people to test it. So if you are capped and willing to help out, please pm Basjohn, riverdusty or myself for the address.
 
Alright so some good news for the 3 (or optimisically 4) people who read this.

I did some extensive testing with 2 other members in the hub and I can say that the speed boost works just as good as before! (Maybe even better actually)

This means the hub is definitely going to come back into operation. HOWEVER a few points I need some advice about:

1) What should we do server wise? I've contacted an old host in hope he'll help again but I'm not even sure he reads his pms here at all, sooo we need to make a plan. Should it be hosted on a users machine (as it is temporarily now) or does anyone else have a nice server they don't mind setting adc up on for us?

2) Advertising, the hub will need me to be a whore and advertise a bit to regain it's membership but there's the problem of shapeability. I don't want to give the address out if it's easily shapeable once the find out about it. Does anyone have knowledge about the shapeability of adc? Is it shape-proof? Or should I just take the chance and wildly flay the address around once again?

Oh and screeny of the speeds I got in just a few minutes (remember this is WHILE CAPPED)

http://img513.imageshack.us/img513/7624/hubrevivalrf9.jpg
 
TrueTenacity said:
hey there... i keep getting this error...

SSL Error: socket layer receive error (-1, 114)
Click to expand...

Is your ip correctly set in Apex? To check this go

File -> Settings -> Connection Settings and click the big 'ole GET IP ADDRESS BUTTON

(You must be using Apex 1.0.0B5 or another client that supports adc ssl)

Otherwise try Passive mode (Same section as the get ip) and reconnecting.

If nothing helps let me know and we'll look in the help files about your error code.
 
*blinks*

huuuh ;/

Please be sure to use a client compatible with the new adc protocol, like ApexDC++'s current beta or the latest DC++.. (apex is sexier)

aaand also.. check Settings.. Security.. make sure you the paths are set and the certificates are actually there (if not, click the buuuutton to generate)

and finally.. dont forget to include the 'adcs://' prefix and port number
 
Using Ubuntu Linux 7.10

Installed DC GUI DC++ Client. From the repositories. If I try to connect to

adcs://wbs.za.org:5000

I get "hub has closed its connection" is this true. Has iBurst blocked this now?
 
chrispche said:
Installed DC GUI DC++ Client. From the repositories. If I try to connect to

adcs://wbs.za.org:5000

I get "hub has closed its connection" is this true. Has iBurst blocked this now?
Click to expand...

The hub hasn't been blocked or shut down. The problem lies with your dc++ client. You need to use a client that supports ADC. Personally I don't know which linux clients do and most of the hub linux users use Apex on Wine.

Hopefully someone else can tell you about a linux client that works with ADC.
 
Basjohn said:
The hub hasn't been blocked or shut down. The problem lies with your dc++ client. You need to use a client that supports ADC. Personally I don't know which linux clients do and most of the hub linux users use Apex on Wine.

Hopefully someone else can tell you about a linux client that works with ADC.
Click to expand...

Linux-DC++ works fine, on linux.
BSD users can use linuxdc++ as well, but its mightly unstable, espeically when hashing.
 
alloytoo said:
Has anybody else been experiencing timeouts when logging onto hubs?
Click to expand...

"Into hubs" ? I seem to be fine on the iBurst hub. I've logged into a few other hubs, but never experienced timeouts. Most hubs do SSL (TLS) encryption these days so make sure ports are properly forwarded, or turn off windows firewall and try again.
 
the iBurst ADC++ hub was down for some time yesterday. It is now back up! It also appears to work whether you're capped or not. This requires more testing, so if you're uncapped please come on and let us know what speeds you're getting.
 
Interesting quirk with ClarkConnect

Ok, so I had it up and running but wasn't too satisfied that I'd done everything right because it was soooooooo slow, so I added the port forward of 5000 (pointing to my IP) to the CC box and then everything died completely. Removed the forward rule, everything hunky dory again?

On major flu meds so may have missed something, perhaps someone can enlighten me?
 
port 5000 is just a connection port for you to get to the hub. It does not need to be forwarded. When you are port forwarding your TCP, UDP and TLS ports you should know a few things. Firstly, Make your TCP/UDP and the TLS port different. Thats one port for TCP/UDP and another for TLS. I've gone the extra step of having a different port for each.
Secondly, the ports you choose should all be above 5000. iBurst have 'closed' all ports below 5000. And lastly if you are still having problems, re-read the FAQ, its pretty comprehensive, and Basjohn does an excellent job of keeping it up to date
 
Does it still work?

How does all this tie in with the new "excessive usage" policy?

Usage Policy

And by looking at the hub's address (wbs.za.org) is this an official iBurst-owned hub?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X