How to forward UDP packets through an SSH tunnel - Quora

Technical Note: Traffic Types and TCP/UDP Ports used by UDP 53: NTP synchronization: UDP 123: Windows share: UDP 137-138: SNMP traps: UDP 162: Syslog; log forwarding Note : If a secure connection has been configured between a Fortigate and a FortiAnalyzer, Syslog traffic will be sent into an IPSec tunnel. Data will be exchanged over UDP 500/4500, Protocol IP/50. UDP 514: Log & report upload: TCP 21 VPN on port 53 = Bypass pretty much any wifi login page However, for the record, iodined is great for DNS tunnelling, and for those networks who were too lazy to block direct DNS queries on UDP 53 - just run openvpn on UDP 53. Job done. level 1 Openvpn Server Udp 53

Here is a nice tutorial for UDP on port 53: Performing UDP tunneling through an SSH connection For some reason I did not get message about updated thread. Thanks, I was able to do what I wanted to using udp-tunnel program but I am curious about the link you have posted.

DNS – 53 UDP Since default configurations for specific processes are well known, network admins can easily block certain ports to restrict a particular traffic. UDPTunnel 1.1 UDPTunnel is designed to tunnel RTP-style traffic, in which applications send and receive UDP packets to and from the same port (or pair of ports). It does not support request/response-style traffic, in which a client request is sent from a transient port X to a well-known port Y, and the server's response is returned from port Y to port X. RP614v4 tunnel using UDP 53 - NETGEAR Communities

When a VPN client, let's say 192.168.1.22 does a DNS query that query should go to 8.8.8.8:53 and then an UDP response packet should be sent back to 192.168.1.22 on a high UDP port. Any ideas? linux domain-name-system openvpn

Because protocol UDP port 53 was flagged as a virus (colored red) does not mean that a virus is using port 53, but that a Trojan or Virus has used this port in the past to communicate. UDP 53 – Disclaimer. We do our best to provide you with accurate information on PORT 53 and work hard to keep our database up to date. This is a free service Tunneling HTTPS and SSH traffic via port 53 | oilinki.com The line will drops all other outbound connections, except traffic to ports 80 (HTTP) and 53 (DNS). This basically means that SSH, ping, traceroute, IMAP and HTTPS does not work. SSH and HTTPS and IMAP connections are the most important to me so that I can access remote servers, get emails and use for example Google search or Facebook.