Something new and interesting... Wirehog.com

[ibneko]

http://www.wirehog.com/

The most interesting... "transfer files through firewalls and NATs"

What is it? looks like a new filesharing program, but based a) around socializing, then b) sharing. And it's integrated with theFaceBook, but I'm not too sure how integrated it is... It could easily be shut down by laq inforcement though, since it _looks_ (at first glance) like it runs off a central server..................

I can send out invites - you'll need one to download the fileserver/client thing - yes, there's MacOS X and windows support - yay for them - it's python based, unless I'm mistaken. If you want an invite, comment. My only requirement is that you be a current friend. I'm not going to give invites to random strangers, 'cause you know, you could be evil people trying to examine and break the nice new system.

I'd like to know how it transfers files through firewalls and NATs. Probably through other clients who are open? Or maybe by adding the request to a message that's transmitting back to someone behind a firewall? I dunno.......

Comments

[fbartho.livejournal.com]

it does a good job at transferring files via firewalls I've played with it a tiny bit I had to get an invitation a couple months back... it was rough, lol because only 3 schools had access to it, so I had to find friends at those schools to invite me...

You should keep your client running though... otherwise it can't retrieve images to post on thefacebook and it can't let other people see your files

its a thing of scope you need to be a friend of someone on wirehog to get their files, and its a direct connection... I'm curious how they handle firewalls on both ends...

I can imagine that each person's client handles getting things in through the firewall, but I don't see how that would work right unless they route files being transferred through their own server... because if firewalls were at both ends... the requester by itself couldn't have an address to connect to to request stuff...

Its not a P2P app... but since its python based maybe you can see the code... unless its a compiled version of it...

go to fbartho.wirehog.com to see my stuff

[ibneko.livejournal.com]

Person A (firewalled) =file list=> Person C (unfirewalled)
Person A understanding that s/he's firewalled periodically checks with Person C for incoming requests.
Person B (firewalled) =file list discover request=> Person C (unfirewalled), who replies with Person A's list.
Person B (still firewalled) =file request=> Person C (unfirewalled), who saves the reqest for Person A and passes it on to Person A on their next check for incoming requests.
Person A begins to send data to Person C, who'll forward it to Person B, each time Person B checks for stuff.

I dunno. That's all I can think of.

otherwise it can't retrieve images to post on thefacebook Eh? Retrieve images....?

[fbartho.livejournal.com]

that would work... except that its not a p2p app, unless I'm mistaken... its nearly only a direct connect from what I was gathering by all I have read about it...

about the italics, if you go to my facebook profile now that my wirehog is on again, you should see some images it has retrieved from my files...

[fbartho.livejournal.com]

update when you browse wirehog friends it retrieves data from 127.0.0.1 at some point during the process... according to firefox... now at least with windows that equates to localhost which equates to your machine, which means your wirehog client is serving it some of the information... which is really interesting...

[fbartho.livejournal.com]

update 2:

looky at the source for the page of some random person I found in wirehog
<frame set><fr ame src="http://127.0.0.1:2533/bounce/yeajews/138.16.27.206:55246:827:0db51ac63e349579/?wirehogisrunning=1&localhost=1&nick=fbartho&access=2&key=8ce1085d07a6c619dbe1a6fdd370671c"></frameset>

the important art of the frame link is where it was served from port 2533 on my computer "bounced" from the server SOMENAME being the person i was visiting with #s replacing their ip address and port at the time... either their ip address or an ip address whose port 55246 was redirecting information from... maybe a webcache??

Also fun detail of wirehog is that if you download say a whole folder off a person's computer, it will compress it for you on the fly... so you can get a whole album of my music or all my music, or a single song... directly via wirehog...

[ibneko.livejournal.com]

Hm.. http://localhost:[port]/bounce/[friend's username]/[their IP]:[port]:[keys]:[morekeys][url to append].
http://138.16.27.206:55246/?wirehogisrunning=1&localhost=1&nick=fbartho&access=2&key=8ce1085d07a6c619dbe1a6fdd370671c
will connect to above person. As you. I think. :D
Loophole #1 found?

I think 138.16.27.206 is their actual address?

Compression on the fly? Interesting!

[edit] yes, that's probably their actual address if they're not behind a firewall. You're not, and I'm connecting to http://141.213.217.170:596/.. which matches the IP address you're posting comments with.

[fbartho.livejournal.com]

actually I have a level of indirection... I'm actually connected via wireless hub to .215 of the same ip, which then remote desktops into my desktop computer which is running wirehog... the wireless is of course firewalled and NATted and I can only assume that you are firewalled, becaues 138. etc is the ip address that I meant to pull out of of my comment above but I'm just now seeing didn't actually get pulled out... I meant to protect them in case it was their real IP but my change to my comment must have gotten lost... anyways... with the link you showed me it seems like you are firewalled yourself... and that ip must then point to one of wirehog's servers....

Hey!! I wonder if we can host our own webpages via the wirehog server we are running... and have fbartho.wirehog.com point to our own little servers... :O oooo pretty...

[ibneko.livejournal.com]

::blinks:: Hum. Actually, I'm not firewalled at all. Just NATted and behind a router. But in all honesty, I treat [ip address that darwin.servehttp.com points to] as my real IP, since I'm pretty much NATted so all incoming traffic goes my way.

Mmmm, I dunno... it's a posibilitiy. You'll probably have to modify the wirehog code, but most of the stuff should be there...

[fbartho.livejournal.com]

Natting equates to firewall essentially... usually when you have a router, it drops unsolicited packets... thats the definition of firewall albeit hardware... and thats what I was under too.. I was being redundant by saying firewalled... but that's what it is...

[ibneko.livejournal.com]

127.0.0.1 is globally recognized as localhost. :D and I know. And yes, it's not really a client.. it's a mix of a client/server.

[ibneko.livejournal.com]

O.o Huh. Find me on thefacebook first. We'll run an identity check from there. Given the questionable nature of the files transfered over wirehog, I'd rather not be the one to invite the first CIA/FBI/MPAA/RIAA agent. =^.-= Besides, as you noted, I don't know you. Although I really don't care if you tell the world or not.

Mmm. I'm assuming that e-mail's valid, so I'm going to screen your post, so e-mail bots can't pick it up, k?