Quote Originally Posted by Stephen
Quote Originally Posted by Cuddles
Firewall = GuardDog, and IRC is already allowed, are you also saying I should locate NAT and do the same Stephen?

Thanks,
Cuddles
Sorry poor choice of words I was thinking the ip_conntrack_irc module that needs to be loaded for the IRC not NAT there is also an ip_nat_irc as well that I believe has to be loaded when using the NAT. I used to use Guarddog and never had problems so have you checked to make sure that module gets loaded.
Ok, I am getting confused...

Check what? ip_conntrack_irc, or ip_nat_irc, or is this a referance to something in GuardDog?

Whatever I am suposed to check that is getting loaded, how do I do that? If I am installing something, what? You mention three things, and loading - GuardDog needs to load what? ip_conntrack_irc "module" is loaded how? ip_nat_irc is loaded how?

From your statement, here and previous, the assumption I am under is, xinetd is not needed, is it to be removed from running in SysV, and since inetd was loading in SysV, should I replace it back?

I'm learning here Stephen, I can do a few things, minor things, but this was all done because someone said I needed inetd for xchat, which I couldn't locate, so I found xinetd, which "appeared" to be a "x" of inetd, which someone said was needed - since installing it, I got these messages now. I am getting frustrated, and very confused at all of this. I just wanted xchat to work, now it does, but with all those boot/shutdown messages. Can I get something to work without something else going "funny", or wrong, or start spewing out messages that I don't know what to do about?

Can you explain what I need to do, in "smaller", easier "digestable" words, or sentences? Consider I never did this, don't know what to do, nor how to do it. If its something in GuardDog, I can locate it and select it to accept it, but other than that, I need a walk-through.

Thanks,
Cuddles