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 need some help here, I'm trying to open Active UNIX domain sockets. Trying to run an icecast server off of it. I got the tcp "Active internet connections" open, just having a bit of trouble with the "Active UNIX domain sockets. Please help.
I'm trying to open Active UNIX domain sockets. Trying to run an icecast server off of it. I got the tcp "Active internet connections" open, just having a bit of trouble with the "Active UNIX domain sockets.
You don't "open" sockets or "bind" to a port: apps do that for you. You just need to run the app.
I don't know if Icecast(2) needs UNIX sockets, if it does make sure you use the right netstat flags. For instance if you use "netstat -pant" the "t" will prohibit displaying UDP and UNIX sockets in use. If you want to see all sockets regardless of protocol try "-pna" and for all listening sockets regardless of protocol use "-pnl".
If it's not that but about say opening up the firewall try asking more specific and detailed questions.
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
I do not believe iptables even has the capability to filter UNIX domain sockets. If it does, it's most certainly disabled by default since these sockets can only be bound to locally. If you believe you are having connectivity problems with some software, unless there is specifically an error mentioning UNIX domain sockets, it's not a problem with them. It's much more likely that you are having problems accessing a tcp/ip service through NAT, or something along those lines.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.