Timeline for AT&T VPN blocks incomming tcp connections
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 4, 2022 at 15:15 | history | edited | PiTheNumber | CC BY-SA 4.0 |
deleted 6242 characters in body; edited tags
|
| Aug 4, 2022 at 15:09 | comment | added | Spiff | For maximum security, some VPN clients can do "full tunnel" mode, where ALL traffic to or from the VPN client machine MUST go via the VPN tunnel. Sometimes this is a setting you can control locally on the VPN client, but sometimes this is dictated by the VPN server (the VPN admin requires you to use a VPN client that allows him to force you to use full tunnel mode). | |
| Aug 4, 2022 at 12:21 | comment | added | PiTheNumber | @Robert Thanks for the feedback. Question is how does it work? And how can I hack it? It would help to see what ports are blocked. | |
| Aug 4, 2022 at 11:52 | history | edited | PiTheNumber | CC BY-SA 4.0 |
added routing table
|
| Aug 4, 2022 at 11:47 | comment | added | Robert | On most VPNS the admins of the VPN server (in your case the admins of "some network") can decide what traffic they allow or deny: they create a policy that the VPN client applies for being able to connect to the VPN server. On common policy is limit all connections to those that come through the VPN. If that is a problem you have to talk to the admins of the VPN server (admins of "some network"). | |
| Aug 4, 2022 at 11:09 | comment | added | Alex | Incoming TCP connections from where? Do you have a public IP or how do they come in? What do routing tables state? | |
| Aug 4, 2022 at 10:22 | comment | added | PiTheNumber | yes, I tried solving this with AT&T support. Got me nowhere. | |
| Aug 4, 2022 at 10:15 | history | asked | PiTheNumber | CC BY-SA 4.0 |