SlackwareThis Forum is for the discussion of Slackware Linux.
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 know this is a stupid question and maybe i did'nt search long enough but how do you open up a port rang in slackware 12 trying to get xchat to do dcc sends i can receive but cant send. router is configured what am i missing here thanks for any help
That depends. By router do you mean your linux box is the router, or you have a stand alone router as your gateway?
If the latter is the case, you'd need to work on the stand alone router. If your linux box is your network edge, you may not have the necessary connection tracking modules/loaded running. Of course, these may be deprecated since my network edge has been running 10.2 since it came out and I haven't bothered with it sans a new app here and there.
i have a stand alone netgear router the port forwarding matches between the router and xchat
I would suspect the reverse would be your issue. However, for IRC, you can build the following modules (or build them into the kernel):
ip_conntrack_irc
ip_conntrack_ftp
ip_conntrack
The following link seems to be relevant to your circumstances:
I would suspect the reverse would be your issue. However, for IRC, you can build the following modules (or build them into the kernel):
ip_conntrack_irc
ip_conntrack_ftp
ip_conntrack
The following link seems to be relevant to your circumstances:
if i understand what your saying is that i have to recompile the kernel because all i can find is .h files witch from what i have read need to be done that that way witch i havn't done before coudnt this be fixed by editing the linux firewall to open certain ports or am i missing somthing kinda new to linux so please excuse
It will FLUSH all the iptables rules, letting everything opened for external connections. So, make all the necessary settings in your stand alone router, after, use these commands in your linux box and then try it again with xchat.
If it worked, well, then you can focus your mind only into the iptables settings, since the router is passing the traffic.
Last edited by sparc86; 12-03-2007 at 06:49 PM.
Reason: correcting a grammatical mistake.
thanks for the iptable info tried it with fingers crossed with no success so its not linux keeping xchat from working has to be a goof on my end just have to figure out what do you happen to know where xchat keeps its config files and log files i dont see them in /usr/lib/xchat just the plugins sitting thier.time for more google searching thanks agine
update just changed ports range but what i think what it might have been was it was set to udp changed it to tcp/udp wow do i feel stupid thanks agine to all that responded
Last edited by blackbeard99; 12-03-2007 at 07:02 PM.
If you use Slackware, you can use the pppoe-start (firstly pppoe-setup) to establish a bridging direct connection (the router actually works as a bridge, therefore will be there no packet filtering by the router's side).
Do it and then test the xchat once again.
Don't forget to flush all the iptables rules before test it.
Once you find the xchat config sections, double check as to whether or not your problem is resolved via the same methods in the links provided. Since you can receive but not send, as is also the problem referenced in the links provided, you may be able to resolve the problem in the same manner, as is mentioned in the links provided.
In regards to a pppoe bridge or an iptables issue, sparc86, I would suspect this is not a global networking issue since blackbeard is able to receive transfers, implying a network connection and sucessful routing sans the listed problem, of course.
What I suspect is that his router isn't "DNATing" the connection to his internal host (linux box) and also there's an embedded firewall which is blocking incoming connections. That's why I think he should try a bridging connection, so there will be no router on the way, despite, his linux box will make a direct connection to his ISP, with no router on the way.
Quote:
Originally Posted by cronicded
Once you find the xchat config sections, double check as to whether or not your problem is resolved via the same methods in the links provided. Since you can receive but not send, as is also the problem referenced in the links provided, you may be able to resolve the problem in the same manner, as is mentioned in the links provided.
In regards to a pppoe bridge or an iptables issue, sparc86, I would suspect this is not a global networking issue since blackbeard is able to receive transfers, implying a network connection and sucessful routing sans the listed problem, of course.
If you use Slackware, you can use the pppoe-start (firstly pppoe-setup) to establish a bridging direct connection (the router actually works as a bridge, therefore will be there no packet filtering by the router's side).
Umm... I don't see how doing this could possibly do anything useful. Furthermore, routers are not bridges. It would also help if you actually read what was being said by the OP carefully, because he already figured out what he misconfigured in his router.
...and please refrain from posting wild guesses to the forum. Silence is more useful than misinformation.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.