LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   Iodine dns tunneling not work (https://www.linuxquestions.org/questions/linux-networking-3/iodine-dns-tunneling-not-work-4175732240/)

Mr linuxy 12-28-2023 03:51 PM

Iodine dns tunneling not work
 
i test iodine dns tunneling on my server but i have problem ، i've run command both on my server and client side same as their github document , i can successfully connect to my server from client but i can not ping or ssh to my interval ip that i set as dns0 in my server from clinent side ( for example 10.0.0.1 or any ip that i set for my iodined server ) the connection has been successful but i can not ping or ssh

Any one can help me with this ?


I test many times and i check my firewall for open 53 port udp/tcp and my network card but i have problem , the connection between server and client are successful but i can not ping

slac-in-the-box 12-28-2023 05:51 PM

hello mr. linuxy, and welcome to lq... I had never heard of iodine, and thank you for bringing it to my attention, however, I don't know anything about it... I do know a little bit about linux networking, and can comment that though dns works standard on port 53, ping is not even udp or tcp, but rather it is its own protocol: internet control messaging protocol, and needs as well to be allowed in a firewall to operate--so with a standard linux iptables firewall, you would allow it with a command like

Code:

iptables -A icmp_packets -p ICMP -s 0/0 --icmp-type 8 -j ACCEPT
you could change the 0/0 to the netmask of ip addresses you want to allow pinging from... likewise ssh is normally operating on tcp port 22, however, in many distributions of linux, the port sshd listens on is configured to a non-standard port in the file /etc/ssh/sshd_config. Also, in the same file, sometimes user/password type of ssh login is disabled, in favor of certificate login using ssl key pairs... but regardless of whether its certificate login, user/password login, or both, the port defined for sshd to listen on, must also be enabled in the firewall, basically the same way that port 53 is enabled.

hope you find your solution...

JJJCR 01-11-2024 02:24 AM

Quote:

I test many times and i check my firewall for open 53 port udp/tcp and my network card but i have problem , the connection between server and client are successful but i can not ping
Is ping or ICMP protocol allowed in your firewall?

Or see this one:

Quote:

The client's tunnel interface will get an IP close to the server's (in this case 192.168.99.2 or .3 etc.) and a suitable MTU. Enter the same password as on the server either as commandline option or after the client has started. Using the -f option will keep the iodine client running in the foreground.

Resulting commandline in this example situation, adding -r forces DNS tunneling even if raw UDP tunneling would be possible:

./iodine -f -P secretpassword t1.mydomain.com

From either side, you should now be able to ping the IP address on the other end of the tunnel. In this case, ping 192.168.99.1 from the iodine client, and 192.168.99.2 from the iodine server.
From this link: https://github.com/yarrick/iodine


All times are GMT -5. The time now is 08:16 PM.