You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I'm running Termux 0.118.1 on Android 14. I also use Ivanti Secure Access Client 22.7.5.15 to connect to our enterprise VPN.
While in Termux, I can connect to any enterprise service without a glitch. All service see Termux on Android as a part of the VPN. But when I log in into a Linux distro, let's say, for instance, pd login ubuntu, connections fail.
Whereas, while in Termux, remote servers see the Android device as, for instance, 192.168.244.54. But if I connect from the proot-distro, packets reach remote servers as sent from a commercial IP, not allowed to access them. For instance, a while ago, I've got assigned IP 92.58.175.182.
Does this make sense for anybody? Could I be skipping some step in configuration?
Thanks for any insight!
The text was updated successfully, but these errors were encountered:
Hi! I'm running Termux 0.118.1 on Android 14. I also use Ivanti Secure Access Client 22.7.5.15 to connect to our enterprise VPN.
While in Termux, I can connect to any enterprise service without a glitch. All service see Termux on Android as a part of the VPN. But when I log in into a Linux distro, let's say, for instance,
pd login ubuntu
, connections fail.Whereas, while in Termux, remote servers see the Android device as, for instance,
192.168.244.54
. But if I connect from theproot-distro
, packets reach remote servers as sent from a commercial IP, not allowed to access them. For instance, a while ago, I've got assigned IP92.58.175.182
.Does this make sense for anybody? Could I be skipping some step in configuration?
Thanks for any insight!
The text was updated successfully, but these errors were encountered: