Software :: Run Firestarter Firewall But Keep Getting The Message ETH0 Is Not Ready?
Jul 26, 2011
I am trying to run Firestarter firewall but keep getting the message ETH0 is not ready. This problem has been highlighted by others but is there a simple way of sorting this out, answers in other forums are wide and varied. but it's not clear if they have been successful.
My network name is eth2 it was changed by some reason and now i got these errors... i installed, reinstalled, re re installed, tried to run the asistant but no luck :/
Code:
* Stopping the Firestarter firewall... eth0: error fetching interface information: Device not found eth0: error fetching interface information: Device not found eth0: error fetching interface information: Device not found
All I want to do is share my internet connection that comes through the eth0 cable to my wlan0 wiki card. Firestarter seems the convenient tool for doing this. BUT it keeps telling me wlan0 not ready. The card is connected correctly and network-manager does see incoming signals.
how to configure my firestarter firewall. I have a website which requires the port 1935 to be open. I figured out how to open the port using firestarter. Is there anyway to make the port open only to this website, and not to every other website for security reasons of course.
I updated my system with system updates and when i restarted.I couldn't access the internet from my desktop. i got on laptop internet worked just fine..i disabled firestarter and mozilla connected to the internet just fine. I turned firestarter on. and i couldn't reach anything.. What do I have to do to get firestarter to allow me to connect to the internet via firefox
I am trying to set up a computer to act as a firewall/gateway on my network, and am using the Firestarter program to do this. Everything appears to be set up correctly, and I followed the instructions on their website completely, and I get an error message when I try to start the firewall. It says that eth0 (my internal NIC) isn't ready, and to make sure it's active.
I gave a presentation on the Firestarter Firewall interface at my local LUG meeting tonight (another member followed with a presentation on iptables).You can download a copy of the handout from this link.
My installation has stopped detecting my wired network. Another computer connects fine with the same cable to the same access point. As far as I can tell it is simply behaving as if there was no network available from that cable but obviously there is. It was working a couple of hours ago, and I didn't install or uninstall anything, just shut down and booted up again.
LAN is enabled in the BIOS ifconfig does display eth0 ifup eth0 returns "Ignoring unknown interface eth0=eth0" in the output from dmesg:
"ADDRCONF(NETDEV_UP): eth0: link is not ready"
network appears in lshw and is not listed as disabled
Have homebrewed machine, was running Fedora 8. Installed Fedora 10.Firestarter firewall manager keeps crashing after about 5 minutes. Restarts, runs for a while, then crashes.Thought it might be an IPTABLES turf war with the native Fedora 10 gui firewall manager, so disabled that at System > Admin > Firewall. Also disabled SElinux. Still have problems.Firestarter firewall seems to work OK, just the gui Firestarter monitor/manager.If anyone has ideas as to cause, I'll take a clue.I could use Firestarter to generate the IPTABLES by ..manually editing the /etc/firestarter/inbound|outbound/allow-.. files and then../etc/init.d/firestarter restartBut I find the events log useful to look at. Anyone know where the events log file is kept in the file system?
I have a HP Elitebook 6930 with Intel 5300 wireless card and today I update it from Fedora11 to Fedora 12 and now I cannot connect with my home wireless network. Previously with F11 I connected without problems but now the wireless connection presents a "Device not ready" message. I tried to switch on/off the wireless card but without results. I had to set intel_iommu=off as kernel parameter to complete the boot. Is something related to it?
I just installed Debian onto a PowerPC G4 Tower with two hard drives. I left OS X on one of the drives and reformatted and installed Debian on the other, using the installer from the 60Mb ISO from the Debian website.
The installation had no issues and it starts yaboot and Debian no problem.
After about 2 minutes of the booting up process, it starts to output this, every five seconds:
While this happens, other things still continue load and it outputs occasional messages and even gets to "Debian Login:" where if you type really quickly and hit enter, it takes it and prompts for "Password:" right after the next round of the above messages.
I have not been able to completely log in yet.
I can start up into the shell as root with "Linux single" with no problems.
I think this might have something to do with the second Mac OS Formatted Hard drive. I have considered unplugging that drive and testing it that way, but I am looking for a solution to turn off whatever script is running that every five seconds and failing, regardless of what it is trying to do.
I installed Firestarter firewall on debian Squeeze.Now i note there is a gui available in System->Administration which apparently does not need to be running all the time - its not set up to start on boot.When I boot I notice the boot message has a line saying "Starting Firestarter firewall .... failed"When I am logged in and type "/etc/init.d/firestarter status" as the Firestarter FAQs say, I get"Firestarter is running... ... (warning)"I can run the gui manually and still same message.
I tryed to setup a second IP address with yast on a openSUSE 11.2 on eth0 as eth0:2nd but with a different firewall zone. But SUSE firewall just see eth0.
I want to define with services are available on with IP address. Also with custom rules I can't specify a destination IP.
So now can I do this with yast? Or have I todo this manually without SUSE firewall?
I get connected to the internet via a router. The router dials to my provider and is connected to my computers via LAN and WLAN (mostly WLAN, see below). A few days ago I installed Suse11.2 to an old laptop (connected both ways: ethernet with wire and wireless ethernet).
The access to the online repositories worked only after I added the LAN-Adapter (Eth0) to the Demilitarised Zone of the firewall (I did also with the WLAN Adapter).
1. Is this normal?
2. Should I add the network devices now to an other zone?
I want to update my main laptop now from openSuse11.1 to 11.2 via new installation (from DVD) and make this installation right.
Or should I install only the data on the DVD and update after the installation via Yast? (My main laptop has also an loose contact at the ethernet adapter.)
Greetings pistazienfresser
Now I am using (on my main laptop = Samsung X20) openSuse 11.1 and Gnome 2.24.1 (mostly, 1 account is using KDE) and Kernel Linux 2.6.27.45-01.1-pae. "/home" is on an separated partition (as part of an extended partition). I have also 2 NTFS partitions for Windows XP (System and Data), and a FAT, a root (/) and a swarp partition. My router is a AVM fritzbox 7270 (firewall should be included).
I installed firestarter and then at a later date uninstalled/purged it, both actions via synaptic. I have a very verbose boot, I like to see what's going on, and noticed after the uninstall/purge that I was getting an error zooming up the screen containing firestarter in it. After many restarts I found that a file was left in /etc/network/if-up.d/50firestarter and this file was simply a script trying to restart firestarter. At this point I've commented out the calling line and followed the commented line with exit 0. This removes the error but there's still a link calling the file so, is this a bug or am I missing something? It appears the uninstall/purge wasn't entirely complete.
I am in the process of settign up a home server under FC14. The installation recognized both NICs, one as Intel Gigabit and the other as a Realtek Semiconductor as it should be. But when trying to start eth0 (Realtek) I get the following error message:
[root@theraugafamily network-scripts]# ifup eth0 Active connection state: activating Active connection path: /org/freedesktop/NetworkManager/ActiveConnection/1 ** (process:2296): WARNING **: _nm_object_get_property: Error getting 'State' for /org/freedesktop/NetworkManager/ActiveConnection/1: (19) Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist
state: unknown Error: Connection activation failed. Some more ifo the this NIC as it is of special type.It is a Viking PCI ADSL2+ Modem Card. I am quoting form the description "Being a gully integrated card, no external plug packs are required and cabling is simplified to just an ADSL line connection. The need to purchase an extra ethernet card is also eliminated, as yjis features is build into the card. The onboard Ethernet controller (RTL8139) makes the modem appear to the OS as a standard network card. Thus the Viking can be used with almost any modern O/S without the need for special drivers. This includes Windows, Linux, Solaris, xBSD, etc.." setting ACPI=off in GRUB.conf does not fix the issue
I need to set up my centOS computer as a firewall in my home network. Ive got 2 interfaces, eth0 and eth1. I want to allow and forward all traffic on eth0 and block all traffic on eth1 except ssh, ping(icmp) and DNS. How do I do this? Ive tried some editing in /etc/sysconfig/iptables but no luck.
5.10 Breezy configured as machine controller. Works great eth0 is a fixed IP to communicate with controller comms board. Not easy at all to alter - the comms board is hard coded to listen on eth0 for commands.
I can use eth1 as the default gateway and ping google.com, etc. But when I now attempt to communicate with the controller with netcat, e.g.
Code: echo !HH | nc 192.168.1.6 80
I obviously never get an answer since the request is passed via eth1. Using the -g option with netcat doesn't work either. I had a look at iptables but it doesn't seem to be able to do what I want. How I can still use eth0 as my communication port to the controller whilst eth1 is the default gateway?
I have two servers on a vlan at my datacentre/colocation and previously both servers had public IPs on their eth0 interfaces. The servers are HP ProLiant DL360s - one is a G4 and one is a G5 The newer G5 is now the LAMP server and the G4 has been retired and I want to repurpose it as an iSCSI target using openfiler freenas or similar.
My G5 has public/static IPs lashed to the eth0 physical interface and the eth1 is not configured to do anything yet. The G4 will have both interfaces available - perhaps one for ssh access from one of my static public IPs and the other to be a private IP on the local vlan. Here is what I am trying to get my head around...
The G5 eth0 - Public IP - full LAMP services on two or three virtual interfaces eth1 - Private IP 192.168.0.1 The G4 eth0 - Public IP for ssh eth1 - Private IP 192.168.0.2
Because my traffic between eth1 on these boxes is via private IPs on the local private vlan it doesn't add to my quota for bandwidth. How do I go about configuring the routing and gateways and other aspects of this so that I can run a private IP space network between the eth1s and still serve the outside world from the eth0s...
I am afraid that if I assign the private IPs to the eth1 interfaces the routing may either not work or interfere with the access to the production internet facing interfaces (eth0s).
If I uncheck and recheck "Enable Networking" in the Network Manager Applet 0.7.996 I would expect the wired network to disconnect (which it does) and reconnect (which it does NOT). So I tried sudo ifdown eth0 and got
Quote:
Ignoring unknown interface eth0=eth0.
ifconfig tells me
Quote:
eth0 Link encap:Ethernet HWaddr 00:25:64:e8:18:2c inet addr:192.168.0.112 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::225:64ff:fee8:182c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
[code]....
so I am at a loss. How do I stop and restart the network interface short of rebooting the machine?
I got two IP's in my dedicated server. Both are external IP's. I would like to make connections using 2nd IP address under eth0:0 interface. For example: when using "lynx whatismyip.com" should display my 2nd IP. How to do this using iptables ?
On my machine (Desktop PC) I have 2 network card : wireless (rt61 802.11) and a wired card (BCM44). When I install debian 5.
The wired card is detected and logical name eth0 is assigned, while wireless is not assigned I install firmeware* software to configure the card. It is done in some way ( I used mnetwork from mepis, it works fine).
Now the problem: eth0 disapears, and no eth0 inteface found? ifconfig gives just wlan0.
Question: Why there is no eth0, it was before configuration of wlan0 ?
How to active again eth0, or ho to create the logical eth0?
I'm running a dual boot Ubuntu 10.04/Backtrack 4 (Ubuntu 8.10) system. I can get internet in the BT4 side but not in the Lucid side. In Lucid I can ping my router, and the network manager says I'm good to go, but I can't get to any web sites. It all started when I tried to put my laptop on another network by mimicking the settings of a computer I had just unplugged from the network. MAC address and all.
ifconfig eth0:
Code:
eth0 Link encap:Ethernet HWaddr 00:1f:16:ba:4c:8c inet addr:10.136.9.147 Bcast:10.136.9.159 Mask:255.255.255.240 inet6 addr: fe80::21f:16ff:feba:4c8c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
I suspect this is an initial configuration bug. All firewall logs seem to be going to all three files. That causes a lot of clutter in the log files, and makes it difficult to see whether there are any serious problems being logged.
I am learning to setup firewall in my home for that i have selected four system(sys1,sys2....sys4) for testing .I have configured sys2 to act as a firewall with two NIC. sys3 and sys4 are inside the firewall . sys1 is not connected to firewall for testing purpose.
the IP assignments are follows :
sys1 : ( fedora, not connected to firewall i am thinking, But i am not sure )
what happened is that sys1(not connected to firewall) can ssh to sys4(connected,inside firewall),since the rules are written not to ssh form sys1 to sys4..
then I came to know whatever the request I give, It directly goes as sys1 --> sys4. Not as sys1-----> sys2(firewall)---> sys4 .and the firewall is not filtering and processing anything for both inbound and outbound (i think it's my mistake some where). the requests are directly going inside without firewall.