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.
I setup an IRCD server the other day. I am running the process using my user account. I can connect just fine with an IRC client locally (localhost:6667), but not from another computer..
I imagine there is a firewall stopping this from working, but I can't figure out how or where. I am running Susa 9.1. Through YaST, I disabled the Suse firewall. All my other services can be reached (SSH, HTTP, FTP, etc.), but not IRCD. I sudo'd "iptables --list", and all I got was the following:
This sounds like an NAT problem. Do you have a router that the computer running the ircd server connects through? If so, you will have to go to that router's config page and forward port 6667 for the internal IP of the machine running the ircd server.
If you need help with that second step, let me know
This sounds like an NAT problem. Do you have a router that the computer running the ircd server connects through? If so, you will have to go to that router's config page and forward port 6667 for the internal IP of the machine running the ircd server.
If you need help with that second step, let me know
I should have clarified the situation a little more - this Linux server is not running out of my home, but is a Virtual server at 1and1.com.
Ah! Well, the same thing may apply if the virtual machine uses bridged networking instead of getting it's own address from the DHCP server (and even then, maybe!)
Also, some VPS providers will intentionally block port ranges like 6660-6669 precisely because they don't want people running ircd servers and things like that. IRC servers are notoriously common and easy targets for DDOS attacks, which means very high server load for your provider. This may be intentional.
Your best bet is to contact 1and1.com technicians and ask them
a) If you're allowed to just run an ircd server
b) If they need to forward the appropriate port range for you
Your configurations inside the box seem to already be fine, judging by your post.
Ah! Well, the same thing may apply if the virtual machine uses bridged networking instead of getting it's own address from the DHCP server (and even then, maybe!)
Also, some VPS providers will intentionally block port ranges like 6660-6669 precisely because they don't want people running ircd servers and things like that. IRC servers are notoriously common and easy targets for DDOS attacks, which means very high server load for your provider. This may be intentional.
Your best bet is to contact 1and1.com technicians and ask them
a) If you're allowed to just run an ircd server
b) If they need to forward the appropriate port range for you
Your configurations inside the box seem to already be fine, judging by your post.
Thanks, that put me in the right direction. 1and1 has seperate firewall software that I have to access through their website.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.