Ubuntu/Firestarter cluster-f*ck
noshellswill
My first post to a.o.l.d.
Running:
7vt600L / 2600+ / .75G / Ubuntu_5.1
dsl + linksys router / bellsouth
After a cross-country relocate to JAX, I nailed together my Ubuntu_box and
all seemed well. It punched right into the network automagically ... in
particular the firewall FireStarter came up without browser or system
issue. As expected. Then, because I'd just updated similar hardware
cross-town at bros' place I decided to allow an update to U_6.06(?) LT
Bad idea. Nothing, but trouble happens. First, the OS updater craps-out
half-way thru the install , whinning that the "network" had problems. I
don't believe it. Then, after a reboot UBUNTU informs me that the NEW
OS has been installed ! What ??
I expected trouble, and it happened the first time I checked FireStarter
against the SHIELDS-UP website probes ... pings were getting thru. I made
one (1) random? change to the FireStarter config and ... blotto ... I can
no longer reach the WWW with FireStarter engaged. Sure I removed? the
change ... with no effect.
Ofcourse I made further reasonable/random changes to various firewall
parameters ( even choosing 'default' ... whatever ... . I'm still shut out.
So heck I figure to remove and re-install FireStarter using the UBUNTU
pkg-manager. That removal fails. So does < apt-get remove > . SO ... I
have no working firewall, and I can't remove the "damaged?" proggie.
I'm hosed in usrland. What should I try??
nss
*****
Jeremy Boden
If you are using Firestarter, it must be because you need to make lots
of changes to your firewall. I don't use a firewall (as such) because
the defaults plus my router (with NAT) seems to take care of the
evildoers.
Uninstalling Firestarter can't be expected to undo any damage done.
Looks like you might need to reinstall (so as to overwrite /etc).
Why don't you load the Ubuntu CD as a live boot. I bet it gets through.
Unless you are deliberately running insecure servers you probably don't
need a firewall.
--
Jeremy Boden
noshellswill
JB:
Thanks for your comments.
No server here; just one usrland Ubuntu-box sharing the Linksys router
with my vintage ( & beloved ... ) WinME-P4.
Naturally I've ZoneAlarmed M$ since 2000; I vaguely understand the
router does it's own firewall thingy, but THAT is automagical, and not
part of my usrland.
Anyrate, when I decided to go mostly LINUX I switched over from RedHat to
UBUNTU_5.x ... the FireStarter proggie trivially installed and configured
with a pleasant dose of eye-candy. No sweat and no issues.
Now there ARE issues with U_6.06 + FS_1.0.3 ....
My CD contains U_5.1. I think I appreciate your 'trick' of a faux_install to tease over a
re_install of U_6.06 ( I've done similar things with a crashed WinME ) ,
but it seems pretty hairy. Granted, both Ubuntu pkg_installer and
<apt-get ...> have failed to nuke FireStarter --- I was hoping for a
kinder, gentler solution.
BTW ... on bootup, FireStarter still prompts me for a passwd, but ofcourse
neither 'me' nor 'r00t' works as no executable (appears to) exist.
nss
**********
Jeremy Boden
password) - but this can be altered...
The recommended way to use root is to type "sudo" followed by a command.
Do this from the user you set up during install and it will ask you for
a password, enter the user password (not the root password).
My suggestion of the "faux install" was simply to load a working Ubuntu
into RAM (it won't touch your hard disk unless you twist it's arm) -
this includes a web browser. It doesn't care whether you have a hard
disk - but you won't get firestarter so you should be able to access web
sites to prove that your network works.
If you can't do that then the fault lies outside your PC.
Why does firestarter ask you for a password?
Are you sure it's not Gnome or KDE etc that is asking you to signon?
--
Jeremy Boden