I'm on a university internet access line (fast!). But they blocked most p2p software (including DC++). I could use a proxy (hard to find a good one), but that means my transfers would go at the speed of the proxy (usually slow). I was wondering if there could be a way to use the proxy for connecting to hubs, chatting, etc. but then have my transfers go over a different port on this machine. So I could transfer over port 21, and use the proxy to setup the transfers. If anyone would be interested in helping, that would be great.
-chris
Changing the Proxy
Moderator: Moderators
-
GargoyleMT
- DC++ Contributor
- Posts: 3212
- Joined: 2003-01-08 02:46
- Location: .pa.us
-
TheNOP
- Posts: 275
- Joined: 2003-07-08 02:41
- Location: Quebec
barffy-man
keep in minds that if port 21 is open, it probably because there is a server in the network.
i don't think the admins will be glad if you start interfering with it, they will be suprise to see some DC people trying to connect to their FTP server..., stay in passive if you find a way to connect to hubs.
keep in minds that if port 21 is open, it probably because there is a server in the network.
i don't think the admins will be glad if you start interfering with it, they will be suprise to see some DC people trying to connect to their FTP server..., stay in passive if you find a way to connect to hubs.
-
GargoyleMT
- DC++ Contributor
- Posts: 3212
- Joined: 2003-01-08 02:46
- Location: .pa.us
TheNOP wrote:keep in minds that if port 21 is open, it probably because there is a server in the network.
i don't think the admins will be glad if you start interfering with it, they will be suprise to see some DC people trying to connect to their FTP server..., stay in passive if you find a way to connect to hubs.
What are you talkinga bout, TheNOP? The fact that they're allowing inbound connections to port 21 (and 22 presumably) and not throttling them... Unless they're NAT'ed and are portmapping 21 to the single FTP server on the network, there's no way using port 21 as your port in DC++ can affect another piece of software.
This is the second post from you that had me scratching my head, as it is factually incorrect.
-
TheNOP
- Posts: 275
- Joined: 2003-07-08 02:41
- Location: Quebec
GargoyleMT wrote:TheNOP wrote:keep in minds that if port 21 is open, it probably because there is a server in the network.
i don't think the admins will be glad if you start interfering with it, they will be suprise to see some DC people trying to connect to their FTP server..., stay in passive if you find a way to connect to hubs.
What are you talkinga bout, TheNOP? The fact that they're allowing inbound connections to port 21 (and 22 presumably) and not throttling them... Unless they're NAT'ed and are portmapping 21 to the single FTP server on the network, there's no way using port 21 as your port in DC++ can affect another piece of software.
This is the second post from you that had me scratching my head, as it is factually incorrect.
you are correct, there is something wrong in my post.
keep in minds that in NATed network, all incoming connection request are blocked unless forwarded, and normaly all outgoing request pass tru, unless filtered.
most of the users in an intranet network are on non routable IPs(NATed).
i made a mistake here --> how do you know they do not forward to their own servers ? (http, ftp, etc... access from same URL)
answere they do not, they have there own IP for their servers.and the gateway do not/should not have the same IP.
so in this intranet case my post was wrong. but still truth for an all NATed network.(that what i had in minds when writing previous post)
to be able to run a server on those intranet without forwarding stuff, you need to have a routable IP, university have a pool of routable IPs, but not for all users(you have to ask for such IPs and they usualy binds it to your network interface MAC).
-
TheNOP
- Posts: 275
- Joined: 2003-07-08 02:41
- Location: Quebec
i notice that i have not been precise on why i sayed to him to stay in passive.
if he is NATed, like i think he is, there is no ways incoming conection request can reach him.
this is a special case and was not my prime reason for my post--->if he use a port that is forwarded(open) to/for an other puter in the intranet then the other puter will try to reply, if the port is not forward it will be bloc anyway.
can't be possible in active mode if he have an non routable IP (NATed).
in passive you get a reverse connect to me from hub tru the proxy, and DC socket use an available port from 1024 to 65535. exactly like IE for example.
since the connection request is initiate from inside the connection will be made, transfer will start.
i have only talk about uploads needs until now.
download work like IE... socket use port 1024 to 65535 for transfer and are initiate from inside so no problem.
if he is NATed, like i think he is, there is no ways incoming conection request can reach him.
this is a special case and was not my prime reason for my post--->if he use a port that is forwarded(open) to/for an other puter in the intranet then the other puter will try to reply, if the port is not forward it will be bloc anyway.
I was wondering if there could be a way to use the proxy for connecting to hubs, chatting, etc. but then have my transfers go over a different port on this machine
can't be possible in active mode if he have an non routable IP (NATed).
in passive you get a reverse connect to me from hub tru the proxy, and DC socket use an available port from 1024 to 65535. exactly like IE for example.
since the connection request is initiate from inside the connection will be made, transfer will start.
i have only talk about uploads needs until now.
download work like IE... socket use port 1024 to 65535 for transfer and are initiate from inside so no problem.
-
GargoyleMT
- DC++ Contributor
- Posts: 3212
- Joined: 2003-01-08 02:46
- Location: .pa.us
-
TheNOP
- Posts: 275
- Joined: 2003-07-08 02:41
- Location: Quebec
perhaps just suggest they don't go into active mode and force a common port if they're on an RFC-1918 private network (192.168.* 10.*, you know the drill).
ok... yep
why do i always forget something... ?
download work like IE... socket use port 1024 to 65535 for transfer and are initiate from inside so no problem.
no problem..., unless filtered.
Who is online
Users browsing this forum: Google [Bot] and 0 guests