Hi all, I have following issue. I have a network infrastructure (ec2 instances) in AWS and all of them are visible to each other. As for an example I have 3 Instances called:
PC_1 - can ping PC_2, PC_3
PC_2 - can ping PC_1, PC_3
PC_3 - can ping PC_1, PC_2
I am able to ping each one of them from each. When I have installed Twingate on PC_2 then it had influenced my network. With the ping requests it looked like that:
PC_1 - could ping PC_2, PC_3
PC_2 - could ping PC_1, but could not ping PC_3
PC_3 - could ping PC_1, PC_2
Is there any setting in the Twingate configuration that is blocking some IP addresses from pinging? As soon as I removed Twingate situation was back to normal.
Thanks in advance.
When you say you installed Twingate you mean a connector or the client?
If it were the connector then no there should be no change in what the machine could access because of the connector on the machine. The connector makes no changes to the DNS etc of the machine on which it is installed.
If it is the client then I could see perhaps that the user on PC_2 doesn’t have ping rights to PC_3? but these being AWS machines I am not sure why the client would be installed.
Clarify and let’s see what else might be the cause.
Hi Jason, thank you for your reply.
Indeed I was not specific enough, what I do is go to Download Twingate | Twingate and download the installer. Then I install TwingateWindowsInstaller.exe (Version 1.0.33+24402 | 0.146.1) and connect to the existing network. It is a client.
If it is the client then I could see perhaps that the user on PC_2 doesn’t have ping rights to PC_3
User on PC_2 does has rights as before installation I could ping PC_3 without any issues. Then what I did next was run
ping -t and in the next window started uninstalling Twingate Client and then suddenly ping started working again as before the installation.
but these being AWS machines I am not sure why the client would be installed.
Regarding this I am not exactly sure, but I believe it still should be fine for the Twingate Client?
The setup I have currently is that there is one Connector deployed on the AWS network and another Connector running on the Raspberry PI, in this case when I install Twingate Client on one of the EC2 instances (running windows) I am able to access things that are connected to the Raspberry Pi outside the AWS infrastructure. Only issue is with accessing other EC2 instances as described.
Thank you for help.
Just to follow up on Jason’s reply … When you connect to Twingate on PC_2, are the IP’s of PC_1 and PC_3 defined as Twingate resources, or are they just locally accessible machines that aren’t routing through Twingate?
They are just locally accessible machines that aren’t routing through Twingate. Which means when there is no Twingate Client installed on PC_2 there is still connection to PC_1 and PC_3 from PC_2.
And are you pinging via hostname or IP?
Theoretically, Twingate should have zero effect on you pinging local resources that aren’t defined as Twingate resources.
Can you tell me your Twingate tenant name so I can take a look at your config? ([tenant].twingate.com) And what’s the hostname/ips of the machines?
Thank you for your reply. When Twingate was not installed I could ping by both, hostname and IP.
I can share the details but I would like not to do it publicly. I had a look if it is possible to send direct message but I could not find this option. If you could share email with me it would be perfect.
Thanks for helping me!
You can email me at arthur (at) twingate.com