Muxomor
Member
- Messages
- 2
- Reaction score
- 0
- Points
- 1
Hello everyone! Please don't throw tomatoes at me, this is my first article. Perhaps it will be useful to newbies like me. I've recently joined a club that's currently undergoing training. I was faced with the question: which setup should I choose for this work? After sifting through a ton of forum threads, I came to the conclusion that there's currently no better setup than the legendary Raspberry Pi + iPhone combo. This combo is being trumpeted from practically every corner of the internet. For my part, I've decided to contribute to the forum as much as I can at this point.
I won't discuss anti-detection devices here, although I've seen hundreds of posts about how they're currently ineffective. I'm still considering this option and hope that this tool will become part of my arsenal, as I believe it's a more versatile weapon that's definitely worth having.
But today, we'll talk about something else. Having decided to start with a Raspberry Pi and iPhone to avoid blowing my budget, I was horrified to learn the prices of firmware for the Raspberry Pi. Every newbie comes to this craft from a difficult life, and they don't always have the extra money for such an expensive setup.
While talking with a new friend and classmate, I learned from him that you can use a laptop for distributing Wi-Fi instead of a Raspberry Pi. However, those who do this most often use paid software for this purpose, called Double SSH Tunnel Manager. It costs about $100 per month (I can't say for sure, but that's what I heard). By chance, I had an old iPhone 11 and an ASUS laptop lying around in my closet. I decided to try to cobble together something with minimal investment in third-party software.
So, what's the problem and what is this article about? Just install Socks through some proxy server and share it via a mobile hotspot. But it's not that simple. With this approach, we connect to the proxy server directly from our IP. I don't think this is the best option from a security standpoint. After all, the proxy provider will then know our IP. But how then can we share Wi-Fi by creating a VPN + Socks5 chain on our PC without resorting to paid software? Below, I'll share my scheme, which works and doesn't require any additional investment.
What you'll need
Full connection diagram (briefly): iPhone → Laptop Wi-Fi → TUN adapter (v2rayN) → VLESS + SOCKS5 chain → Internet
Step-by-step setup:
1. Install and run v2rayN as administrator.
Download the latest version from GitHub. Unzip and run. It's that simple.
2. Add both servers.
3. Assemble our chain.
Click Add proxy chain.
In the window that opens, arrange our chain in order: first VLESS, then SOCKS5.
Name the group and click Confirm.
4. Don't forget about the DNS settings. I used the default ones. The output seems to be adequate (see the last screenshots). If you have any advice, I'd be happy to hear it.
You also need to set the MTU to 1500. By default, it's set to 9000 — this is "jumbo frames" for data center local networks, not the regular internet. Set it to 1500 — this is the standard for home Wi-Fi/Ethernet, so the traffic looks like it's coming from a typical American user and isn't fragmented. Stack: mixed (I've experimented with all the options, and it doesn't seem to make a difference, but any advice would be welcome).
5. Next, we test our chain for functionality, checking latency and download speed. If everything is OK, these parameters will be displayed, and you can enable TUN mode.
I also set "Clear system proxy" here. As I understand it, this ensures that all our traffic goes through our chain; by default, "Whitelists" were enabled.
At this point, we can go to BrowserLeaks and check our configuration for DNS and WebRTC leaks.
6. Share our connection from the laptop's mobile hotspot.
This is simple: go to our mobile hotspot and enable Wi-Fi sharing. It's worth clarifying that by default, you won't be able to share this connection due to Windows' default settings. To resolve this, we need to:
Done. You can grab your phone and connect to our "American" Wi-Fi.
A little tip: name your hotspot something similar to real routers in the US, like "Linksys_5G_774" or "SpectrumWiFi_Guest." Something different from the standard network name like "DESKTOP-XXXX-Network."
Here's what we get:
Everything would be fine, but this connection has its downsides.
1) High ping, I have about 220ms. Antifraud at top shops clearly won't let that through (I'm only speaking from my own guess).
2) Low download speed. Mine ranges from 0.9 MB/s to 1.5 MB/s. (But this is due to cheap server proxies; I haven't tested with residential ones yet, I'll do that when I get closer to the payload. For now, I'm putting together all the theory and trying to put everything in its place in my head so as not to waste my entire starting budget on tests.)
3) Distance: 15 Hops. For the US, this is a bit much (the packet passed through 15 nodes). Ideally, it should be 3-7. This is precisely what reveals that we are using a proxy chain (VLESS + SOCKS).
4) And the most important, in my opinion, is the TCP/IP Fingerprint mismatch. In our case, it's detected as Android (at least not Linux or Windows, and thankfully so). For top antifraud software, this is also a clear indicator that we're using tunneling rather than a direct connection.
I tried to fix this at the Windows level, following the AI's advice.
As Gemini assured me:
I tried this through the Windows registry. It didn't help. But it couldn't hurt, so here's how:
What's the solution? I saw this advice in one thread: You need to find a proxy provider that allows you to change this fingerprint. I think I'll do this soon to maximize my technical setup.
Conclusion:
I'm still learning, and this setup is the result of my experiments and communication with other newbies. Perhaps someone has ideas for how to overcome TCP/IP mismatch, or you know a service that sells residential proxies with the ability to change this parameter. I'd appreciate any advice (PM is fine). Also, if you have your own solutions for distributing internet through a laptop, please share them, let's discuss.
Happy mining! As I delve deeper into the topic, I'll share more interesting solutions and developments. If this article was helpful, you know what to do. I'll know my work wasn't in vain.
I won't discuss anti-detection devices here, although I've seen hundreds of posts about how they're currently ineffective. I'm still considering this option and hope that this tool will become part of my arsenal, as I believe it's a more versatile weapon that's definitely worth having.
But today, we'll talk about something else. Having decided to start with a Raspberry Pi and iPhone to avoid blowing my budget, I was horrified to learn the prices of firmware for the Raspberry Pi. Every newbie comes to this craft from a difficult life, and they don't always have the extra money for such an expensive setup.
While talking with a new friend and classmate, I learned from him that you can use a laptop for distributing Wi-Fi instead of a Raspberry Pi. However, those who do this most often use paid software for this purpose, called Double SSH Tunnel Manager. It costs about $100 per month (I can't say for sure, but that's what I heard). By chance, I had an old iPhone 11 and an ASUS laptop lying around in my closet. I decided to try to cobble together something with minimal investment in third-party software.
So, what's the problem and what is this article about? Just install Socks through some proxy server and share it via a mobile hotspot. But it's not that simple. With this approach, we connect to the proxy server directly from our IP. I don't think this is the best option from a security standpoint. After all, the proxy provider will then know our IP. But how then can we share Wi-Fi by creating a VPN + Socks5 chain on our PC without resorting to paid software? Below, I'll share my scheme, which works and doesn't require any additional investment.
What you'll need
- A laptop with Windows (any will do).
- Ethernet cable
- Subscription or your own VLESS server (European server, for bypassing blocking (relevant for residents of the Russian Federation) and hiding the IP of the proxy provider).
- A SOCKS5 residential proxy is our exit IP address. For testing, I used a cheap server proxy just to make sure everything worked.
- v2rayN program (free, open source).
Full connection diagram (briefly): iPhone → Laptop Wi-Fi → TUN adapter (v2rayN) → VLESS + SOCKS5 chain → Internet
Step-by-step setup:
1. Install and run v2rayN as administrator.
Download the latest version from GitHub. Unzip and run. It's that simple.
2. Add both servers.
- Import VLESS and check that it works.
- Import SOCKS5 and check that it works.
3. Assemble our chain.
Click Add proxy chain.
In the window that opens, arrange our chain in order: first VLESS, then SOCKS5.
Name the group and click Confirm.
4. Don't forget about the DNS settings. I used the default ones. The output seems to be adequate (see the last screenshots). If you have any advice, I'd be happy to hear it.
You also need to set the MTU to 1500. By default, it's set to 9000 — this is "jumbo frames" for data center local networks, not the regular internet. Set it to 1500 — this is the standard for home Wi-Fi/Ethernet, so the traffic looks like it's coming from a typical American user and isn't fragmented. Stack: mixed (I've experimented with all the options, and it doesn't seem to make a difference, but any advice would be welcome).
5. Next, we test our chain for functionality, checking latency and download speed. If everything is OK, these parameters will be displayed, and you can enable TUN mode.
I also set "Clear system proxy" here. As I understand it, this ensures that all our traffic goes through our chain; by default, "Whitelists" were enabled.
At this point, we can go to BrowserLeaks and check our configuration for DNS and WebRTC leaks.
6. Share our connection from the laptop's mobile hotspot.
This is simple: go to our mobile hotspot and enable Wi-Fi sharing. It's worth clarifying that by default, you won't be able to share this connection due to Windows' default settings. To resolve this, we need to:
- Open network adapters settings.
- Find the singbox_tun adapter there and go to properties
- In the Access tab, check the box "Allow other network users to connect through this computer's Internet connection."
- In the list below, select "Local Area Connection* 12" (this is our Wi-Fi adapter, responsible for distributing the Internet).
Done. You can grab your phone and connect to our "American" Wi-Fi.
A little tip: name your hotspot something similar to real routers in the US, like "Linksys_5G_774" or "SpectrumWiFi_Guest." Something different from the standard network name like "DESKTOP-XXXX-Network."
Here's what we get:
Everything would be fine, but this connection has its downsides.
1) High ping, I have about 220ms. Antifraud at top shops clearly won't let that through (I'm only speaking from my own guess).
2) Low download speed. Mine ranges from 0.9 MB/s to 1.5 MB/s. (But this is due to cheap server proxies; I haven't tested with residential ones yet, I'll do that when I get closer to the payload. For now, I'm putting together all the theory and trying to put everything in its place in my head so as not to waste my entire starting budget on tests.)
3) Distance: 15 Hops. For the US, this is a bit much (the packet passed through 15 nodes). Ideally, it should be 3-7. This is precisely what reveals that we are using a proxy chain (VLESS + SOCKS).
4) And the most important, in my opinion, is the TCP/IP Fingerprint mismatch. In our case, it's detected as Android (at least not Linux or Windows, and thankfully so). For top antifraud software, this is also a clear indicator that we're using tunneling rather than a direct connection.
I tried to fix this at the Windows level, following the AI's advice.
As Gemini assured me:
I tried this through the Windows registry. It didn't help. But it couldn't hurt, so here's how:
What's the solution? I saw this advice in one thread: You need to find a proxy provider that allows you to change this fingerprint. I think I'll do this soon to maximize my technical setup.
Conclusion:
I'm still learning, and this setup is the result of my experiments and communication with other newbies. Perhaps someone has ideas for how to overcome TCP/IP mismatch, or you know a service that sells residential proxies with the ability to change this parameter. I'd appreciate any advice (PM is fine). Also, if you have your own solutions for distributing internet through a laptop, please share them, let's discuss.
Happy mining! As I delve deeper into the topic, I'll share more interesting solutions and developments. If this article was helpful, you know what to do. I'll know my work wasn't in vain.
