On Fri, 2004-05-21 at 00:13, Lanman wrote: > Lyvim Xaphir wrote: > > > My problem was corrected when I updated to the latest slew of updates > > and also replaced the secure kernel with the latest version. have not > > seen that problem since then. > > Lyvim; How ya doin' Buddy? I found another way to fix the problem. Can > you say Bastille? Killed Shorewall, copied over my Bastille files, ran > the command and voila! No more shorewall data on my console, and the > firewall is running fine (actually runs a bit faster)!
Hello, Immortal One. ;) Good to see that you are still your old indefatigable and irrepressible self. <grin> I may go the Bastille route. But I had an immense success story getting shorewall to run an internal Neverwinter Nights server not too long ago, and now I'm sort of loath to give it up just yet. I think my problem is just a matter of editing the right config files in shorewall, maybe the zone conf file isn't set up right, or something like that...I figure between the Shorewall mailing lists and the great documentation on Tom Estep's site, it's a matter of time before I lick it. > > >>Also, is there a "Bind" Guru here somewhere? I can't get "rndc" to > >>behave itself. It keeps giving me an error that states - > >> > >> "rndc: connect failed: connection refused" > >> > >>Even though Bind seems to start up without errors, and even though port > >>53 is open on my firewall for DNS authentication, port scans keep > >>stating that the port is closed. > > > You're running shorewall on the firewall, correct? ;) I've been > > encountering the same problems with both qmail and bind. > > > > LX > > RNDC problem is still happening though. Because of that, my DNS server > still appears closed in a firewall scan. I checked at Bind's website, > and they say that it's usually due to silly things like the server's > hostname ( mine's good ), or the fact that there's no rndc-key located > in named.conf or rndc.conf ( which is there in both files on this > machine), so I'm not sure what to do. The DNS port is open on the > firewall, but the service is not fully starting. The funny thing is that > my email server (postfix) runs like a charm, and so does everything else. > > So right now, it's more of an annoyance than anything, but I'd like to > solve it. Still open to suggestions. > > Lanman Don't have any yet, but I can tell you this; when the email server problem gets resolved, the DNS problem will quickly follow, and when it does I'll send you the results. The difference between the NWN server and the firewall problem is that while the NWN server ports were being directed to another box on the internal net, the ports for DNS/Email on the firewall are not; because of it needing to be a fully qualified domain name with respect to Qmail. Qmail is picky about stuff like that. Keep it straight up buddy.. :) LX
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
