I believe this was fixed by patch 21 in firestarter version 1.0.3-9.
Are you able to test/confirm, please?
Regards,
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Exactly.
a) fix the configuration file replacing both (null) strings with eth0
and eth1
b) /etc/init.d/firestarter start works
c) aptitude reinstall firestarter - breaks firewall leaving host open,
no rules in iptables.
When I get a chance to work on the console, (rather then remotely), I
will sta
Anthony Mutiso wrote:
On doing a reinstall again, the two variables where null and firestart
wound not start an my iptables rule set was empty.
To confirm, after having a fixed configuration, with the GUI not
running, you did:
apt-get install --reinstall firestarter
and the configuration br
I can confirm this problem.
On an aptitude safe-upgrade this morning, firestarter broke with the
same error leaving my host unprotected. I had to create manual iptable
rules to protect the host.
I attempted a re-install of firestarter and again, firestarter failed to
start and all iptable rules wh
The Internet is configured via DHCP:
# /sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 00:**:**:**:**:**
inet addr:1**.1**.**.*** Bcast:1**.1**.**.*** Mask:255.255.254.0
inet6 addr: f***::**c:c***:***1:/** Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500
Package: firestarter
Version: 1.0.3-8
Severity: critical
After upgrade to version 1.0.3-8, firestarter does not start:
# /etc/init.d/firestarter start
Starting the Firestarter firewall...(null): error fetching interface
information: Device not found
(null): error fetching interface information: D
6 matches
Mail list logo
