This one was a royal pain to solve.
It was a hardware problem.
Taking out the tulip card and plugging in an eepro100 in a different slot
fixed the problem.
Having my laptop with me this time was a big help. I set up the laptop with
the same network configuration worked fine. I noticed that
joy_ping wrote:
hi,
i would say get off of this bastile-crap and use pure iptables-scripts.
dont know if bastille uses iptables, but you learn more, and it is really
no magic to set up your firewall by hand. it is easy to configure, you
can set special rules for special ports, and you
This is an odd problem. The on-site docs seem to be less than useful. (Too
much time spent with remedial firewall instruction and too little telling
where the damn config scripts live.)
Note: This is at a friend's house that is about 45 miles away. Not easy to
get to, so some details may be
The configuration for it is in:
/etc/Bastille
There is a utility to set it up. I dont remember the name, look in /sbin I
think it is there. There is also a graphic utility. As for turning it on or
off, there is a script in /etc/rc.d/init.d just for that.
I suggest you try turning it off, try
Its name is:
bastille-firewall
Technically, this is what is in it:
#!/bin/sh
#
# bastille-firewall Load/unload ipchains rulesets
#
# do not rename this file unless you edit /sbin/bastille-firewall-reset
#
# chkconfig: 2345 5 98
# description: A firewall/packet-filter script for
hi,
i would say get off of this bastile-crap and use pure iptables-scripts.
dont know if bastille uses iptables, but you learn more, and it is really
no magic to set up your firewall by hand. it is easy to configure, you
can set special rules for special ports, and you know what you do, and
some
