What's new

G·TM GTM NoLoad Situation with Modem + PC

Emperorization

Honorary Poster
Joined
Aug 6, 2017
Posts
772
Reaction
253
Points
233
Using GTM no load using your modem + PC(or Mobile) gets confusing because the indications (e.g. 302 Found status code, magic IP, etc.) that the no load trick may work contradict the established prerequisites needed for the trick.

THE SITUATION

Here are the things you will encounter when trying to perform the no load trick with your modem:

Hunting the MagicIP

SUCCESS!                      FAILED TO HUNT: KEEP HUNTING!

internetExplorer_ipHunt_success.png
internetExplorer_ipHunt_failed.png

The first thing you need to secure in order to browse the Internet without load or data, is that your device is using the MagicIP--the IP address that has a vulnerability that the VPN will exploit to perform the trick.

To hunt the MagicIP without using any software applications, you only need an outdated version of a browser (preferably Internet Explorer) and visit the link You do not have permission to view the full content of this post. Log in or register now..

If the resulting webpage looks like what's shown in the first picture then CONGRATULATIONS! you have successfully hunted the all so elusive MagicIP. Otherwise, you have to reboot the modem and repeat the hunting process until you have successfully hunted the IP.​

On the VPNs

Now, it's time to connect to a VPN. We will use the OpenVPN and NetMod desktop applications.

Here are the side-by-side comparison of the results when trying to connect when you are on the MagicIP and when you are not on the MagicIP:

MagicIP

NetMod log: MagicIP
netMod_HostCheck_MagicIP.png
OpenVPN log: MagicIP

Veterans of the No Load trick and config makers will advise you to keep retrying to connect to the VPN when it refuses to connect even though you are already in the MagicIP.

Spoiler contents are visible only to Established Members.

But then we are faced with a problem--that is, the screenshot on the left. Supposedly, the screenshots below should appear when connecting to OpenVPN whilst on the MagicIP, yet, this eyesore of an error shows up. As per the thread title, this only happens when using a modem.

Not on the MagicIP

NetMod log: Not MagicIP
netMod_HostCheck_NotMagicIP.png
OpenVPN log: Not MagiciP

The confusing bit starts here: when you connect without hunting the MagicIP, it should give you a different error such as a 302 Moved Temporarily error. So why does it show a 302 Found error?! IDFK!

THE ALTERNATIVE

This now leads us to the question: Can modems still be used to enjoy the no load trick? The answer is YES! Using the Shadowsocks desktop application, you can still connect. This is what I only use, though I can't vouch for its reliability and stability. Go to You do not have permission to view the full content of this post. Log in or register now. to get a config.

TL;DR

You do not have permission to view the full content of this post. Log in or register now.
 

Attachments

Last edited:
So no way na talaga using hc or ovpn pag modem gamit ts??

Naka ilang try na din ako using ovpn or hc pero napaka hirap ikonek kahit goods na ip ko. Pero dati pumapalo pa ko sa hc pero ngayon napaka hirap na talaga pakonekin.
 
So no way na talaga using hc or ovpn pag modem gamit ts??

Naka ilang try na din ako using ovpn or hc pero napaka hirap ikonek kahit goods na ip ko. Pero dati pumapalo pa ko sa hc pero ngayon napaka hirap na talaga pakonekin.
There's a way. The blocking way. Connected agad but less than 24 hours lang tatagal sim card mo.
 
The confusing bit starts here: when you connect without hunting the MagicIP, it should give you a different error such as a 302 Moved Temporarily error. So why does it show a 302 Found error?!
I think it's because of the HTTP protocol version that you're using in your payload set up. ganyan kasi ang response pag HTTP/1.1 protocol ang gamit kahit wala sa MagicIP. subukan mong palitan, magiging 302 Moved Temporarily response nyan pag wala ka sa MagicIP.
 
Last edited:
I think it's because of the HTTP protocol version that you're using in your payload set up. ganyan kasi ang response pag HTTP/1.1 protocol ang gamit kahit wala sa MagicIP. subukan mong palitan, magiging 302 Moved Temporarily response nyan pag wala ka sa MagicIP.
True. But more importantly, why doesn't it work the same way 'pag nasa MagicIP?
 
Back
Top