We live in a student dormitory where the internet is tightly controlled and restricted. The only protocol that works is “443 tcp”. Can you help me if I can run other protocols? Is this problem with the ports and what should I do?
“443 TCP” isn’t exactly a protocol. It’s an indicator of the type of traffic and where it’s going, which in this case would be port 443 TCP packets. Something like a protocol would be OpenVPN, which has support for running on port 443 with TCP.
That sounds about right with a campus and security… sometimes your only option is TCP… are you able to port forward? Just curious
Most popular VPNs will have an option to run on port 443.
You can also try wireguard with fake tcp or what ever it call, wstunnel is a example. Or xray proxy with reality protocol. They both should work.
I mean… What are you trying to get around? If your only issue is hitting other ports then simply host your own openVPN server on AWS, GCP or Azure (hundreds of tutorials all over the internet, it shouldn’t take more than thirty minutes).
It might work for udp too (for gaming and such)… Try it.
“443 TCP” isn’t exactly a protocol.
Really? I mean it literally stands for Transport Control Protocol.
How much more unambiguous could that be?
we can not reach the modem interface
these protocols are not working for us just connecting icon rotates
Not disagreeing with you at all, just clarifying: TCP is the L4 protocol, 443 is the destination port. When you see tcp-443 or any variant of it, it is generally understood that it’s referring to http(s) (if the person communicating it is knowledgeable, that is), despite any L7 proto being technically capable of transport over that port. The same applies to literally every other L7 proto; tcp-22=SSH, tcp-3389=RDP, tcp-445=ntlm, etc.
In fact, reading over the person’ response it’s even more frustrating because OpenVPN, or any VPN for that matter, is a service, not a protocol. Highly recommend they read up on the OSI layers before spouting nonsense.
@OP: tcp-443 grants you access to the vast majority of the visible internet. For most people this is fine. Yes, a VPN provider will help you bypass your campus restrictions but at the same time you could run into issues if they are sinkholing popular backend VPN/Cloud Provider ASNs. Difficulty rating for someone non-technical: 3/10.
This is based on the assumption that you are not hosting services of your own. If that is the case, renting a server elsewhere and setting up Apache Guacamole over TLS would be your best, least traceable (by your institution), most reliable option. Difficulty rating for someone non-technical: 11/10.
With that said, I suggest you review your institution’s responsible use policy prior to implementing your own solution. If you are found to be in violation, there could be consequences beyond your control.
Don’t forget that even with a solution in-hand, you are using Campus services. When you are connecting your devices to the Campus network, you are likely authenticating when you do so - there is a trace of your logon. It is not out of the realm of possibility that the school’s firewall is acting as a MiTM, decrypting all traffic to ensure the safety of its network. If that is the case, you can forget about anonymity.
Source: If you think you know better than me you are probably right.
TCP is a protocol but in the terms of this subreddit about vpns where the term “protocol” is often used referring to vpns. It wouldn’t make much sense if I was talking about the McDonald’s burger cooking protocol at a fire station emergency protocol meeting
You sure? Wireguard with websocket does not work? Not wireguard by itself. And for xray, you can use a different server config, what protocol with reality are you using for xray?
Thanks for your reply!