fixing the way you get to webmin Will help you setup the IPs of the cards.
On Thursday 12 July 2001 10:26, Chris Buxton wrote:
> As I noted before, I've already run Bastille. It seems to have mucked
> up a bunch of things, including breaking named. I have so far been
> able to fix named, but I haven't cataloged what else it broke, much
> less fixed any of it. Now I keep getting messages from the Bastille
> tmp directory protection script saying that it has been disabled and
> I need to log out and log back in again.
>
> I am not impressed with Bastille.
>
> So, for whatever reason (whether or not it was another victim of
> Bastille), webmin isn't working. Fixing webmin is not my first
> priority, unless it can be used to configure additional IP addresses
> on a network interface.
>
> Thanks for your thoughts, but I'm still looking for answers.
>
> Chris Buxton
>
> At 9:56 AM -0400 7/12/01, etharp wrote:
> >in a text console (ie.; [alt]+[ctrl]+ [F3] {or any Fkey 1 to 6} and
> >log in as root,
> >cd to /usr/sbin
> >Type "InteractiveBastille" (without the quotes, note
> > Capitalization...villy important in Unix) this should lead you to a way
> > to correct your firewall script. you need to have it allow connections
> > from 127.0.0.1
> >(localhost.localdomain) if that is where you are trying to connect to
> > webmine from.
> >
> >On Thursday 12 July 2001 01:32, Chris Buxton wrote:
> >> I seem to have disabled Webmin at some point, probably when I ran
> >> Bastille. It seems to have broken a large number of things, such as
> >> named. I did manage to fix that one, though, and got named properly
> >> chroot'd in the process.
