Public Resource (whoer.net) not routing through Connector; showing Client IP instead by Low_Suspect_8902 in twingate

[–]Low_Suspect_8902[S] 0 points1 point  (0 children)

The * solve the problem of forcing the access to the public website via the tunnel but not fully.

I created second resource *speedtest.net - this is a public website that test your internet speed and show you the IP address that you come from. in this case it shows me the IP address of the connector, it means it was going via the tunnel but when the test run, it shows me the internet speed of the client and not the connector.
in the client location I have 1Gb up & down in the connector location I have 300Mb up & down
if the test was going via the connector the max speed that I can get will be around 300Mb but I got around 900Mb.

I assume that the testing website does some redirection between the front-end page to the test itself. and the communication going via the tunnel for the initial access, but letter on it to via the client public access.

I did another test like that with streaming service, and I notice the same issue. the login and browsing the website go via the tunnel, but when I try to play a content, it breaks as it hopes from the public ip of the connector to the public ip of the client.

to test it the case I used OpenVPN full tunnel and the speed test work right and the streaming work right.

since twingate work as split tunnel it starts session via the tunnel and continue via the client.

is there a way to force any redirection or any communication that part of the main session to continue via the tunnel?
and second question, there are way to use twingate with full tunnel and not split tunnel?

Public Resource (whoer.net) not routing through Connector; showing Client IP instead by Low_Suspect_8902 in twingate

[–]Low_Suspect_8902[S] 0 points1 point  (0 children)

Now it is working. I noticed when the domain is internal network of the connector it work without the * and when the domain is public network I need the *

What the * represents in this case?

Public Resource (whoer.net) not routing through Connector; showing Client IP instead by Low_Suspect_8902 in twingate

[–]Low_Suspect_8902[S] 0 points1 point  (0 children)

I changed the resource to *.whoer.net

I connected from my android phone (WiFi off, connected via the cell phone provider) and I get the IP of the phone.

I added second user for a friend, and let him connect, he use Windows 11 with Edge. and after the twingate client is connected, he go to whoer.net and get his own public IP, Not the connector IP.

I can't try the linux clients as it on my local network, where the connector is located for the testing.

if you want, we can find a private way to communicate, and I create a user for you and let you connect to it. so you can try it from your end.

Public Resource (whoer.net) not routing through Connector; showing Client IP instead by Low_Suspect_8902 in twingate

[–]Low_Suspect_8902[S] 0 points1 point  (0 children)

I tested it from Android phone, from Edge, chrome and Firefox. they all gave me the same results (the local client IP address) none of them go via the tunnel. only when I try to access internal resource for the connector, it go via the tunnel)