HIn here
BThank you.
B
BI have setup split tunnels to make sure that
10.1.1.1 IP is proxied through WARP.
CJust adding the Private Networks in Tunnels isn't enough to do anything on it's own.
You have to have the machines bound to those IPs, and the services bound as well. In your case, it might be configuring a loopback adapter to bind to that Private IP, and then configuring the server (if it's not bound to all IPs already) to bind to that IP as well
You have to have the machines bound to those IPs, and the services bound as well. In your case, it might be configuring a loopback adapter to bind to that Private IP, and then configuring the server (if it's not bound to all IPs already) to bind to that IP as well
C(That is, assuming that your local network isn't already on 10.0.0.0)
BHow do I do that?
BYes, I have limited WARP to not proxy
10.0.1.0/24 and 10.0.2.0/24.CThe idea of Private Networking is that you would already have had a Private Network on 10.0.0.0/24 for example, like you probably have your home network on 192.168.0.0/24, and tunnels would just be the glue to proxy connections over it.
Without that, you'll need to manually bind those IPs on the machine you want to reach. Way back in the day on windows I used Microsoft's Loopback Adapter. The exact way of binding your machine to those IPs is going to depend on your os
Without that, you'll need to manually bind those IPs on the machine you want to reach. Way back in the day on windows I used Microsoft's Loopback Adapter. The exact way of binding your machine to those IPs is going to depend on your os
BNo, my main network subnet is
10.0.1.0, and my secondary network subnet is 10.0.2.0.BThe server is in the main network on Static Local IP
10.0.1.2.CYou have that already configured on those servers? Like if you go on that server and do
ping 10.0.1.2, you get a response?Byes.
BI'm connected via SSH right now.
COk that's a good start then, it's just that some applications don't work?
You mentioned "10.0.3.1" does not work, but it doesn't seem that is part of your configs in the screenshot above
You mentioned "10.0.3.1" does not work, but it doesn't seem that is part of your configs in the screenshot above
BThat was the original IP, now it's
10.1.1.1.CAnd you can access it locally, like doing
curl http://10.1.1.1, but just not through the tunnel?BIP Organisation:
10.{ip-location}.{network-number}.{device-specific}BI can't access it through or outside the tunnel.
CIf you can't access it locally, the tunnel isn't going to work either. It sounds like that specific service/web server might not be bound to that IP
B10.1.0.0 subnet is for WARP Private Networks.CWhen I say "locally", I mean on the same machine or local network as that machine, not entirely external of course
BWell, the Tunnel that is running on the server has the CIDR on Private Networks tab.
BLocally as in LAN Connection.
CAll Private Networking is doing is "expanding your lan". If it doesn't work on LAN, then it's not going to work over the tunel, gotta fix that first
BSo... I bind
10.1.1.1 on local network, or bind 10.0.1.2 to the WARP network?CThere is no such thing as the "WARP Network". Adding Networks to the Private Network tab is just basically saying "Come through me, and I'll proxy traffic meant for this cidr, and send them on their way"
BHuh.. So it's only a relay portal from WARP Team Users to the Local Network.
CGoing back to, if you can't curl it from the tunnel machine, then private networking can't reach it either.
If it's on the same machine as the tunnel host, bind it locally as loopback.
If it's on a different machine, then you'll need to assign it a static ip that you can use, or otherwise make it reachable
If it's on the same machine as the tunnel host, bind it locally as loopback.
If it's on a different machine, then you'll need to assign it a static ip that you can use, or otherwise make it reachable
CYea, it's a way to access your "Private Network". It can be a bit confusing when you're not using the real IPs of the devices, so for a more clean example, think of your home network:
If you have a home network running on 192.168.0.0/24, with a Pi on 192.168.1.253, router on 192.168.1.1, Intel Nuc/Server on 192.168.1.252, you add the 192.168.0.0/24 CIDR to a tunnel on the Pi, and you can start reaching all of those services as if it's a VPN
If you have a home network running on 192.168.0.0/24, with a Pi on 192.168.1.253, router on 192.168.1.1, Intel Nuc/Server on 192.168.1.252, you add the 192.168.0.0/24 CIDR to a tunnel on the Pi, and you can start reaching all of those services as if it's a VPN
BOh.. My.. Gosh...
BI removed my home router from the filter, then I SSHed in after adding the local IP in the network, not it works!
BOne more question though...
BI get issues when browsing Twitter or using Luna Client.
BI think it's something to do with the SSL...
BI added the Certificates to my mac and trusted them, so most websites work, but some don't.
CHmm, you don't need TLS Decryption on for Private Networking unless you want some of its features
BWhat features does it give?
CGateway can inspect your exact traffic even with ECH and filter on it/log it/etc
BI don't want that, but I still want twitter and some broken websites to work.
CIf you don't need/want the capabilities of gateway then you can just disable it, unless I misunderstood you.
Not really sure about the exact cause of that issue though, sorry. I did use WARP for a while, but I used it with "Include IPs" rather then Exclude, and without TLS Decryption, so only traffic bound for Private Networking was set over WARP
Not really sure about the exact cause of that issue though, sorry. I did use WARP for a while, but I used it with "Include IPs" rather then Exclude, and without TLS Decryption, so only traffic bound for Private Networking was set over WARP
BOk, if I make it Include IPs instead, can I use other VPN Services?
CNot sure about that one, maybe? WARP works a bit differently then a normal VPN, at least on Windows
BSame here, it breaks...
BAnyway, Thank you soooo much! this helped me a lot!!!