Begin forwarded message:
Date: Mon, 19 Nov 2001 18:32:01 +0000
From: Geoff
Geoff
The same errors remain at the end. The last few lines of the make follow:-
<snip>
/usr/i486-suse-linux/bin/ld: cannot find -lesd collect2: ld returned 1 exit status make[3]: *** [firestarter] Error 1
Have you installed the package esound? libesd appears to be missing, and that lib is installed by esound. Geoff _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
I am still having problems with the Firestarter firewall. When setting it up and selecting the modem as the internet connection, only eth0 is offered as a choice. I know that is wrong. The message in the window suggests that ppp0 should be used as the modem identification. That doesn't work. I see from Yast/modem that it is identified as /dev/ttyS1 modem0. I have tried both of these and they don't work either. It would seem that the program is not seeing the modem at all. There are many messages being produced in the terminal window as follows. I really do not understand there meaning, except it cannot find ppp0 Regards, David Terminal messages linux:~ # firestarter Gdk-WARNING **: locale not supported by Xlib, locale set to C NETFILTER detected Using /lib/modules/2.4.4-4GB/kernel/net/ipv4/netfilter/ip_tables.o insmod: a module named ip_tables already exists GnomeUI-WARNING **: Could not open help topics file NULL NETFILTER detected Using /lib/modules/2.4.4-4GB/kernel/net/ipv4/netfilter/ip_tables.o insmod: a module named ip_tables already exists ppp0: error fetching interface information: Device not found ppp0: error fetching interface information: Device not found iptables v1.2.1a: invalid mask `' specified Try `iptables -h' or 'iptables --help' for more information. iptables v1.2.1a: invalid mask `' specified SNIP These lines continue for 50 or more lines. Try `iptables -h' or 'iptables --help' for more information. iptables v1.2.1a: invalid mask `' specified Try `iptables -h' or 'iptables --help' for more information. Firewall script restarted Gtk-WARNING **: invalid cast from (NULL) pointer to `GtkContainer' Gtk-CRITICAL **: file gtkcontainer.c: line 726 (gtk_container_remove): assertion `container != NULL' failed. Gtk-WARNING **: invalid cast from (NULL) pointer to `GtkBox' Gtk-CRITICAL **: file gtkbox.c: line 366 (gtk_box_pack_end): assertion `box != NULL' failed. NETFILTER detected Using /lib/modules/2.4.4-4GB/kernel/net/ipv4/netfilter/ip_tables.o insmod: a module named ip_tables already exists SNIP again many lines like this NETFILTER detected Using /lib/modules/2.4.4-4GB/kernel/net/ipv4/netfilter/ip_tables.o insmod: a module named ip_tables already exists Gtk-WARNING **: invalid cast from (NULL) pointer to `GtkContainer' Gtk-CRITICAL **: file gtkcontainer.c: line 726 (gtk_container_remove): assertion `container != NULL' failed. Gtk-WARNING **: invalid cast from (NULL) pointer to `GtkBox' Gtk-CRITICAL **: file gtkbox.c: line 366 (gtk_box_pack_end): assertion `box != NULL' failed. Gtk-WARNING **: invalid cast from (NULL) pointer to `GtkContainer' Gtk-CRITICAL **: file gtkcontainer.c: line 726 (gtk_container_remove): assertion `container != NULL' failed. Gtk-WARNING **: invalid cast from (NULL) pointer to `GtkBox' Gtk-CRITICAL **: file gtkbox.c: line 366 (gtk_box_pack_end): assertion `box != NULL' failed. Gtk-WARNING **: invalid cast from (NULL) pointer to `GtkContainer' Gtk-CRITICAL **: file gtkcontainer.c: line 726 (gtk_container_remove): assertion `container != NULL' failed. Gtk-WARNING **: invalid cast from (NULL) pointer to `GtkBox' Gtk-CRITICAL **: file gtkbox.c: line 366 (gtk_box_pack_end): assertion `box != NULL' failed. Gtk-WARNING **: invalid cast from (NULL) pointer to `GtkContainer' Gtk-CRITICAL **: file gtkcontainer.c: line 726 (gtk_container_remove): assertion `container != NULL' failed. Gtk-WARNING **: invalid cast from (NULL) pointer to `GtkBox' Gtk-CRITICAL **: file gtkbox.c: line 366 (gtk_box_pack_end): assertion `box != NULL' failed. Gtk-WARNING **: invalid cast from (NULL) pointer to `GtkContaine
I am still having problems with the Firestarter firewall. When setting it up and selecting the modem as the internet connection, only eth0 is offered as a choice. I know that is wrong. The message in the window suggests that ppp0 should be used as the modem identification. That doesn't work. I see from Yast/modem that it is identified as /dev/ttyS1 modem0. I have
On Tue, 20 Nov 2001 13:52:16 +0000
David
both of these and they don't work either. It would seem that the program is not seeing the modem at all. There are many messages being produced in the terminal window as follows. I really do not understand there meaning, except it cannot find ppp0
<snipped error messages> I am afraid that I may not be able to be much help on thid occasion, because I do not know Firestarter and my knowledge of firewalls is limited. One thing that does occur, however, is to ask whether you are online when you do this configuration exercise. I ask because (unlike eth0), ppp0 does not exist until a connection is made. If as, root, you run "ifconfig", you will see details of the available interfaces - ppp0 will not be in the list until you log on to your ISP. Secondly, I do not know if you are running the gnome desktop, or just using the libraries so that you can use Firestarter. If it is the former then I think that may account for some of the errors. If you are not online, see if going online helps and report back to us. I am sure that others on the list can be more help here. Geoff _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Thanks Geoff Never occurred to me that it would only be visible when connected. Setting it up on line sorts that out and most of the error messages. Also found that I hadn't configured to correctly. I am running KDE but it is said to be ok so long as the Gnome libraries are installed. It is meant to start on dial up, but doesn't. The alternative is to put it into the start up, there are only instructions for RH. Where do I go in Suse. On connection I think I am using kinternet, little plug in bottom right hand corner. Can it be configured not to disconnect after a couple of minutes. Is there an equivalent to the Windows modem lights in the sys tray. I find it useful to know what is going on. Now I have to work out how to get the Win box to connect through. Regards, David On Tue, 20 Nov 2001 14:42:27 +0000, Geoff wrote:
I am afraid that I may not be able to be much help on thid occasion, because I do not know Firestarter and my knowledge of firewalls is limited.
One thing that does occur, however, is to ask whether you are online when you do this configuration exercise. I ask because (unlike eth0), ppp0 does not exist until a connection is made. If as, root, you run "ifconfig", you will see details of the available interfaces - ppp0 will not be in the list until you log on to your ISP.
Secondly, I do not know if you are running the gnome desktop, or just using the libraries so that you can use Firestarter. If it is the former then I think that may account for some of the errors.
If you are not online, see if going online helps and report back to us.
I am sure that others on the list can be more help here.
Geoff
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
On Wed, 21 Nov 2001 01:35:44 +0000
David
I am running KDE but it is said to be ok so long as the Gnome libraries are installed.
It looks like you have spotted and corrected the typo in my last post, where I said "former" but meant "latter". It is correct that if you have the libraries gnome apps will generally run under kde and vice-versa. I have noticed, however, that occasionally you will see (generally harmless), error messages thrown up because the application is expecting to find its full enviromnent, and doesn't.
It is meant to start on dial up, but doesn't. The alternative is to put it into the start up, there are only instructions for RH. Where do I go in Suse.
I think you need to be careful here. To begin with, are you sure that your configuration survives the destruction of the particular instance of ppp0 that is running during the online session when you configured it? You will, I expect, have a dynamically configured IP address, which changes from session to session, and which Firestarter may extract for its own use when ppp0 is up and which it cannot extract again until you reconfigure. That is *not* necessarily the case, but if it *is* then there is no point to trying to start Firestarter automatically until that issue is sorted. Secondly, if it is meant to start on dial-up, then I would have thought that the right approach would be to modify something like /etc/ppp/ip-up rather than have it run at boot-time. Take a look at that script - it contains some commented-out options for starting stuff that one might use as a model. I have never done this though - if anyone reading this knows better please post accordingly. Third, there are several ways of having things start at boot-time. The easiest is to put them in the /sbin/init.d/boot.local script, which SuSE has kindly provided for your convenience. At least I assume that you have this, please do bear in mind in reading anything I write that I am using 7.0 and your 7.2 may differ. There may be a problem with the boot.local approach, however, because I do not think that the network will be available at the time when it runs and that *may* screw up Firestarter's initialisation - I am just guessing here. If the boot.local approach does not work, there are slightly deeper alternatives, but we need to bear in mind that any errors we make in modifying your boot structures could leave the box unbootable. That can usually be fixed via the SuSE rescue system, but we obviously do not want to get into that if we can avoid it. May I suggest that you (a) make sure that your configuration survives going on and off line a few times. (b) Post the RH instructions so that we can see if they modify easily for SuSE. We can then take it from there.
On connection I think I am using kinternet, little plug in bottom right hand corner. Can it be configured not to disconnect after a couple of minutes.
Is there an equivalent to the Windows modem lights in the sys tray. I find it useful to know what is going on.
Back when I was playing with KDE I used Kppp, which had the lights you need. I never tried kinternet. There are many mini-apps that show the lights (asmodem is one ), http://www.tigr.net/afterstep/list.pl) I suggest, however, that you try Kppp first unless that has gone from the current KDE.
Now I have to work out how to get the Win box to connect through.
That may involve sending an evelope stuffed with fivers to Mr Gates ;-)
Regards,
Geoff _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Thanks Geoff Continues below On Wed, 21 Nov 2001 08:45:06 +0000, Geoff wrote:
It looks like you have spotted and corrected the typo in my last post, where I said "former" but meant "latter". It is correct that if you have the libraries gnome apps will generally run under kde and vice-versa. I have noticed, however, that occasionally you will see (generally harmless), error messages thrown up because the application is expecting to find its full enviromnent, and doesn't.
I didn't notice the typo. I have a bad habit of reading what I expect to see and not reading what is there - usually end in trouble - worked this time though :)
I think you need to be careful here. To begin with, are you sure that your configuration survives the destruction of the particular instance of ppp0 that is running during the online session when you configured it? You will, I expect, have a dynamically configured IP address, which changes from session to session, and which Firestarter may extract for its own use when ppp0 is up and which it cannot extract again until you reconfigure. That is *not * necessarily the case, but if it *is* then there is no point to trying to start Firestarter automatically until that issue is sorted.
Haven't had much time tonight, but from quick testing it doesn't seem to mind if it is started first. Let you know how it goes.
Secondly, if it is meant to start on dial-up, then I would have thought that the right approach would be to modify something like /etc/ppp/ip-up rather than have it run at boot-time. Take a look at that script - it contains some commented-out options for starting stuff that one might use as a model. I have never done this though - if anyone reading this knows better please post accordingly.
Third, there are several ways of having things start at boot-time. The easiest is to put them in the /sbin/init.d/boot.local script, which SuSE has kindly provided for your convenience. At least I assume that you have this, please do bear in mind in reading anything I write that I am using 7.0 and your 7.2 may differ. There may be a problem with the boot.local approach, however, because I do not think that the network will be available at the time when it runs and that *may* screw up Firestarter's initialisation - I am just guessing here.
If the boot.local approach does not work, there are slightly deeper alternatives, but we need to bear in mind that any errors we make in modifying your boot structures could leave the box unbootable. That can usually be fixed via the SuSE rescue system, but we obviously do not want to get into that if we can avoid it.
May I suggest that you (a) make sure that your configuration survives going on and off line a few times. (b) Post the RH instructions so that we can see if they modify easily for SuSE. We can then take it from there.
Noted I'll check out the rest tomorrow if I have time.
Back when I was playing with KDE I used Kppp, which had the lights you need. I never tried kinternet. There are many mini-apps that show the lights (asmodem is one ), http://www.tigr.net/afterstep/list.pl) I suggest, however, that you try Kppp first unless that has gone from the current KDE.
That may involve sending an evelope stuffed with fivers to Mr Gates ;-)
Yes I sent him a quick note, but he said he was too busy installing RH on all those machines - and my oh my a pig has just flown past the window :) Regards, David
Still having problems here. Is there any particular syntax in adding commands to these files? I have just added firestarter and that does not work although it does from an x terminal. If I add the path as well it does not work. This is in ip-up. Also tried boot.local - no good. But that is loading before the X system is up, and firestarter will not run from level 3. Is there a file that can me modified when the x system loads. Regards, David
I think you need to be careful here. To begin with, are you sure that your configuration survives the destruction of the particular instance of ppp0 that is running during the online session when you configured it? You will, I expect, have a dynamically configured IP address, which changes from session to session, and which Firestarter may extract for its own use when ppp0 is up and which it cannot extract again until you reconfigure. That is *not * necessarily the case, but if it *is* then there is no point to trying to start Firestarter automatically until that issue is sorted.
Secondly, if it is meant to start on dial-up, then I would have thought that the right approach would be to modify something like /etc/ppp/ip-up rather than have it run at boot-time. Take a look at that script - it contains some commented-out options for starting stuff that one might use as a model. I have never done this though - if anyone reading this knows better please post accordingly.
Third, there are several ways of having things start at boot-time. The easiest is to put them in the /sbin/init.d/boot.local script, which SuSE has kindly provided for your convenience. At least I assume that you have this, please do bear in mind in reading anything I write that I am using 7.0 and your 7.2 may differ. There may be a problem with the boot.local approach, however, because I do not think that the network will be available at the time when it runs and that *may* screw up Firestarter's initialisation - I am just guessing here.
If the boot.local approach does not work, there are slightly deeper alternatives, but we need to bear in mind that any errors we make in modifying your boot structures could leave the box unbootable. That can usually be fixed via the SuSE rescue system, but we obviously do not want to get into that if we can avoid it.
May I suggest that you (a) make sure that your configuration survives going on and off line a few times. (b) Post the RH instructions so that we can see if they modify easily for SuSE. We can then take it from there.
On connection I think I am using kinternet, little plug in bottom right hand corner. Can it be configured not to disconnect after a couple of minutes.
Is there an equivalent to the Windows modem lights in the sys tray. I find it useful to know what is going on.
Back when I was playing with KDE I used Kppp, which had the lights you need. I never tried kinternet. There are many mini-apps that show the lights (asmodem is one ), http://www.tigr.net/afterstep/list.pl) I suggest, however, that you try Kppp first unless that has gone from the current KDE.
Now I have to work out how to get the Win box to connect through.
That may involve sending an evelope stuffed with fivers to Mr Gates ;-)
Regards,
Geoff
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Hi: Just wondering if you have gotten firestarter to work to your satisfaction? I am interested in using it but it seems to be quite a task. Thanks for comments. David wrote
Still having problems here.
Is there any particular syntax in adding commands to these files? I have just added firestarter and that does not work although it does from an x terminal. If I add the path as well it does not work. This is in ip-up.
Also tried boot.local - no good. But that is loading before the X system is up, and firestarter will not run from level 3. Is there a file that can me modified when the x system loads.
Regards,
David
-- _____________________ Christopher R. Carlen crobc@earthlink.net Suse 7.3 Linux 2.4.10
On Sat, 08 Dec 2001 09:17:56 -0800
Chris Carlen
Hi:
Just wondering if you have gotten firestarter to work to your satisfaction? I am interested in using it but it seems to be quite a task.
Thanks for comments.
Naaaaaaaa David will tell you that for anyone with six or eight weeks to spare and the determination of a charging rhino on speed, its a pushover ;-). Actually I don't think that he found setting it up much of a problem - autoloading was a little harder, but even that seems to be possible now. David is the user though, and I am sure he will respond to your post. Regards, Geoff _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Hi Chris I have got Firestarter to work manually, but still have to work out how to allow my Win box to connect via it. Though I haven't done much with that side until I get the Linux side working correctly. To get it working manually is not much of a task, providing you have the correct Gnome files installed. It may work better for you, Geoff didn't have much trouble getting it going, my system seems a bit more awkward. If you need any help I can try and help, but I am no expert On Sat, 08 Dec 2001 09:17:56 -0800, Chris Carlen wrote:
Hi:
Just wondering if you have gotten firestarter to work to your satisfaction? I am interested in using it but it seems to be quite a task.
Thanks for comments.
David wrote
Still having problems here.
Is there any particular syntax in adding commands to these files? I have just added firestarter and that does not work although it does from an x terminal. If I add the path as well it does not work. This is in ip-up.
Also tried boot.local - no good. But that is loading before the X system is up, and firestarter will not run from level 3. Is there a file that can me modified when the x system loads.
Regards,
David
-- _____________________ Christopher R. Carlen crobc@earthlink.net Suse 7.3 Linux 2.4.10
Regards, David
participants (3)
-
Chris Carlen
-
David
-
Geoff