DO NOT DEAL WITH THIS MEMBER
Jun 8, 2016 11:22 AM
(This post was last modified: Jun 8, 2016 11:23 AM by █BORNE█.)
I wrote this earlier so will be sharing it for everybody's use... all you need to do is send the client to a friend of yours and type 'start' in the server to capture their IP address, please post telling me what I could add/improve😎
Server
Pastebin Link
Client
Pastebin Link
-borne
DO NOT DEAL WITH THIS MEMBER
What's the reason for setting a socket timeout of 100 seconds? If this hasn't responded in over 4-5 seconds, you can safely assume that it's not going to and that something went wrong.
DO NOT DEAL WITH THIS MEMBER
Jun 8, 2016 11:34 AM
(This post was last modified: Jun 8, 2016 11:34 AM by █BORNE█.)
(Jun 8, 2016 11:31 AM)Mouse❤️ Wrote: What's the reason for setting a socket timeout of 100 seconds? If this hasn't responded in over 4-5 seconds, you can safely assume that it's not going to and that something went wrong.
Gives time for the friend to open the client instead of giving him 5 seconds to open it.
That's not how socket timeouts work at all... The server will listen forever until it receives a connection, regardless of timeout. The timeout is so that if you try to recv() from the client and it takes more than 5 seconds, THEN it times out. Also, this is really overcomplicated.
DO NOT DEAL WITH THIS MEMBER
(Jun 10, 2016 12:33 AM)Blackjack Wrote: That's not how socket timeouts work at all... The server will listen forever until it receives a connection, regardless of timeout. The timeout is so that if you try to recv() from the client and it takes more than 5 seconds, THEN it times out. Also, this is really overcomplicated.
I thought it was... and how is it overcomplicated?
Using raw sockets is not the way to go...
DO NOT DEAL WITH THIS MEMBER
(Jun 10, 2016 08:08 AM)Goodies Wrote: Using raw sockets is not the way to go...
What would you recommend
Jun 10, 2016 09:50 AM
(This post was last modified: Jun 10, 2016 10:33 AM by Goodies.)
(Jun 10, 2016 08:09 AM)█BORNE█ Wrote: What would you recommend
An actual server ;) I'm partial to Twisted, but anything should work, tbh. Flask, Django, etc.. they're all fine.
I'll whip something up real quick. Flask should be more than capable of handling this pretty easily with a few hundred connections, but I'm a Twisted kind of guy, so I'll be using that :P
Give me like half an hour.
Edit: taking a little longer than I thought.
DO NOT DEAL WITH THIS MEMBER
(Jun 10, 2016 09:50 AM)Goodies Wrote: An actual server ;) I'm partial to Twisted, but anything should work, tbh. Flask, Django, etc.. they're all fine.
I'll whip something up real quick. Flask should be more than capable of handling this pretty easily with a few hundred connections, but I'm a Twisted kind of guy, so I'll be using that :P
Give me like half an hour.
Okay Goodies send me it on skype
Jun 10, 2016 11:04 AM
(This post was last modified: Jun 10, 2016 11:04 AM by Goodies.)
I kind of changed it to a URL shortener + IP logger so... that's why it's taking so long.
DO NOT DEAL WITH THIS MEMBER
(Jun 10, 2016 11:04 AM)Goodies Wrote: I kind of changed it to a URL shortener + IP logger so... that's why it's taking so long.
It would take 30 seconds
DO NOT DEAL WITH THIS MEMBER
Only problem with this is unless the person has python installed the client will be useless for them, alot of people are starting to install it these days but it's still not that common.
DO NOT DEAL WITH THIS MEMBER
(Jun 10, 2016 11:14 AM)๖ۣۜCriminal Wrote: Only problem with this is unless the person has python installed the client will be useless for them, alot of people are starting to install it these days but it's still not that common.
Yeah I thought about that...
Jun 10, 2016 11:40 AM
(This post was last modified: Jun 10, 2016 11:43 AM by Goodies.)
Alright here it is. It's dirty but it works. There a ton of things I would change before putting it anywhere near a production environment....
Also I'm shit with web design so I just went with some plain ass HTML.
How to use:
1. run it.
2. Go to http://127.0.0.1:8080/new
3. enter a URL. Note that if you don't put an actual HTTP link in there, it will recursively call getChild and keep refreshing so don't do that.
4. send the link (example: http://127.0.0.1:8080/abcdefg123) to someone else (obviously this would need to be on your network)
5. When someone visits the link, go to http://127.0.0.1:8080/log/abcdefg123 to view the IP's.
DO NOT DEAL WITH THIS MEMBER
(Jun 10, 2016 11:40 AM)Goodies Wrote:
Alright here it is. It's dirty but it works. There a ton of things I would change before putting it anywhere near a production environment....
Also I'm shit with web design so I just went with some plain ass HTML.
How to use:
1. run it.
2. Go to http://127.0.0.1:8080/new
3. enter a URL. Note that if you don't put an actual HTTP link in there, it will recursively call getChild and keep refreshing so don't do that.
4. send the link (example: http://127.0.0.1:8080/abcdefg123) to someone else (obviously this would need to be on your network)
5. When someone visits the link, go to http://127.0.0.1:8080/log/abcdefg123 to view the IP's.
What the actual fuck... I obviously dont understand a word of that😧
|