Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Fedora, CentOS, and would like to get back to Gentoo
Posts: 332
Rep:
No-ip DNS Updater + iptables rules.
I opened port 8245 for both inbound/outbound and tcp/udp traffic, but the noip2 updater continues to fail:
Sep 22 16:49:18 noip2[9326]: Can't gethostbyname for dynupdate.no-ip.com
Sep 22 16:49:18 noip2[9326]: Can't get our visible IP address from ip1.dynupdate.no-ip.com
My iptables rules to allow traffic on port 8245 (on eth0 internet interface) follow:
iptables -t filter -A INPUT -i eth0 -p tcp -m state --state NEW --dport 8245 -j ACCEPT
iptables -t filter -A INPUT -i eth0 -p udp --dport 8245 -j ACCEPT
iptables -t filter -A OUTPUT -o eth0 -p tcp -m state --state NEW --dport 8245 -j ACCEPT
iptables -t filter -A OUTPUT -o eth0 -p udp --dport 8245 -j ACCEPT
I asked no-ip support whether I had to allow ping requests on that interface and port, but they didn't mention anything about it in the response. They did confirm that the default port for the dns updater is 8245.
Sep 22 16:49:18 noip2[9326]: Can't gethostbyname for dynupdate.no-ip.com
Sep 22 16:49:18 noip2[9326]: Can't get our visible IP address from ip1.dynupdate.no-ip.com
The first line sas that the hostname can't be resolved to an ip. do a
dig dynupdate.no-ip.com
or
host dynupdate.no-ip.com
Seems like an DNS issue.
Quote:
Originally Posted by Sum1
My iptables rules to allow traffic on port 8245 (on eth0 internet interface) follow:
Dunno what the ports are good for but is this the machine connected to the WWW you have this iptables rules? If not you would need to set up some forwarding rules.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.