> I don't see the connection being a reseller service has to do with
> routing to specific proxies.
>
> Surely the routing is based on something entirely different - such as
> the users credit balance with services, or which packages they have
> routing to specific proxies.
>
> Surely the routing is based on something entirely different - such as
> the users credit balance with services, or which packages they have
> bought from you, which region(s) they are trying to access etc.
So the reason for my reseller service is bot and webscrape tools. These tools get banned on websites quickly if coming from the same IP (I know because I've been using them for a year). The reason for the reseller service is to add features on top of proxy services such as specific proxy rotation time.
> There is nothing in the PacketStream documentation or FAQ that indicates
> routing to specific proxies based on user/password details.
>
> Their on-sellers simply add/remove login accounts and payments to the
> routing to specific proxies based on user/password details.
>
> Their on-sellers simply add/remove login accounts and payments to the
> main system.
PacketStream does in fact route specific proxies based on the user password (I have an account with them).
It uses country and stick/random IPs categories.
E.g. this routes to a random country proxy AND constantly changes the IP:
mark251:fq4zEWC1B5A194C1:proxy.packetstream.io:
This routes to a United States proxy AND constantly changes the IP:
mark251:fq4zEWC1B5A194C1_country-UnitedStates:proxy.packetstream.io:32712
This routes to a United States proxy AND a sticky IP:
mark251:fq4zEWC1B5A194C1_country-UnitedStates_session-M9OtVn9p:proxy.packetstream.io:32712
Additionally, different session IDs are used to map to different sticky IP proxies:
mark251:fq4zEWC1B5A194C1_country-UnitedStates_session-Pux68O1z:proxy.packetstream.io:32712
mark251:fq4zEWC1B5A194C1_country-UnitedStates_session-SbbaynPQ:proxy.packetstream.io:32712
mark251:fq4zEWC1B5A194C1_country-UnitedStates_session-ybhX9gIf:proxy.packetstream.io:32712
mark251:fq4zEWC1B5A194C1_country-UnitedStates_session-dFgoeQMY:proxy.packetstream.io:32712
So there's definitely a reason to do this.
My question is how does PacketStream do this?
On Wednesday, September 23, 2020, 9:44:47 PM CDT, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote:
On 24/09/20 4:14 am, Ajb B wrote:
>
> Hey Anthony,
>
> I see you're point. It makes sense to have multiple usernames if I want
> a user to access multiple proxies. But I'm trying to create a "reseller"
> proxy service, so multiple usernames for a single user won't really make
> sense. I can just give users different passwords to access different
> proxies.
I don't see the connection being a reseller service has to do with
routing to specific proxies.
Surely the routing is based on something entirely different - such as
the users credit balance with services, or which packages they have
bought from you, which region(s) they are trying to access etc.
That type of info is traditionally managed via assigning users to
groups. In modern Squid it is more efficiently done with annotations and
"note" ACL as mentioned by Eliezer already.
>
> Also, I know PacketStream (https://packetstream.io/) does this and I'm
> pretty sure they use Squid.
There is nothing in the PacketStream documentation or FAQ that indicates
routing to specific proxies based on user/password details.
Their on-sellers simply add/remove login accounts and payments to the
main system.
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
>
> Hey Anthony,
>
> I see you're point. It makes sense to have multiple usernames if I want
> a user to access multiple proxies. But I'm trying to create a "reseller"
> proxy service, so multiple usernames for a single user won't really make
> sense. I can just give users different passwords to access different
> proxies.
I don't see the connection being a reseller service has to do with
routing to specific proxies.
Surely the routing is based on something entirely different - such as
the users credit balance with services, or which packages they have
bought from you, which region(s) they are trying to access etc.
That type of info is traditionally managed via assigning users to
groups. In modern Squid it is more efficiently done with annotations and
"note" ACL as mentioned by Eliezer already.
>
> Also, I know PacketStream (https://packetstream.io/) does this and I'm
> pretty sure they use Squid.
There is nothing in the PacketStream documentation or FAQ that indicates
routing to specific proxies based on user/password details.
Their on-sellers simply add/remove login accounts and payments to the
main system.
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
