Solved ! RE: [suse-security] SuSe Firewall 2 - FW_HTB_TUNE_DEV ???
Hi,
Oh I see you are using SuSEfirewall2 from SuSE 8.1
No, I have Suse 8.2, but I have done updates via Yast Online Update, maybe that goes wrong ?? I have seen more references to Suse 8.1 during upgrading. I will try to find-out what's going wrong with that.... Update after some tests: I have investigated data with "Ethereal", the online-update of Suse 8.2 gets it's updates from pub/suse/i386/update/8.1/.... So the update program was getting the wrong updates (8.1 instead of 8.2) all the time. This is probably also the answer of other minor problems with updating. Now the next thing is to find an updated version of "YOU" (yast online update), and I have to do this manually as the update-program can never find this..... (Probably I am not the only one with this problem ;)
I recomend you to download SuSEfirewall2-3.1.95.noarch.rpm from: ftp.suse.com/pub/suse/i386/update/8.2/rpm/noarch/SuSEfirewall2-3.1- 95.noarch.rpm
[Cees Tool] I have done this, and indeed now the "FW-HTB*" references are in the Susefirewall2 script and it seems to work now ! Thanks all, for the information. Problem (almost) solved. Now I have to see if there is a solution for the wrong directory in yast online update.... Regards, Cees
Hi,
I have investigated data with "Ethereal", the online-update of Suse 8.2 gets it's updates from pub/suse/i386/update/8.1/.... So the update program was getting the wrong updates (8.1 instead of 8.2) all the time. This is probably also the answer of other minor problems with updating.
This last problem was also solved now. A directory existed : /var/lib/YaST2/you/mnt/i386/update/8.1 The normal directory : /var/lib/YaST2/you/mnt/i386/update/8.2 was also there. It seems that after deleting the 8.1 directory, Yast Online Update did not try to get it's updates from the 8.1 directory anymore. But why the 8.1 directory was there, I still don't know. Version 8.1 has never been installed.... Thanks again for all feedback, Regards, Cees
On Tue, Oct 07, 2003 at 06:23:29PM +0200, Cees Tool wrote:
Update after some tests: I have investigated data with "Ethereal", the online-update of Suse 8.2 gets it's updates from pub/suse/i386/update/8.1/....
this is weird. I don't know exactly where where you have to look for the wrong setting... Was this 8.2 an updated 8.1 or did it change its identity by accident?
So the update program was getting the wrong updates (8.1 instead of 8.2) all the time. This is probably also the answer of other minor problems with updating.
Now the next thing is to find an updated version of "YOU" (yast online update), and I have to do this manually as the update-program can never find this..... (Probably I am not the only one with this problem ;)
I never heard of a problem like that, but i also never do updates, i always do fresh installs, just keeping my $HOME and /usr/local, which are on different partitions/drives/machines. you could give fou4s http://fou4s.gaugusch.at a try, it works fine for me on many installations. goot luck :-) Stefan -- Stefan Seyfried Senior Consultant community4you GmbH, Chemnitz, Germany. http://www.community4you.de http://www.open-eis.com
From: Stefan Seyfried [mailto:seife@community4you.de]
Update after some tests: I have investigated data with "Ethereal", the online-update of Suse 8.2 gets it's updates from pub/suse/i386/update/8.1/....
this is weird. I don't know exactly where where you have to look for
Hi Stefan, the
wrong setting... Was this 8.2 an updated 8.1 or did it change its identity by accident?
No this was a fresh install of 8.2
I never heard of a problem like that, but i also never do updates, i always do fresh installs, just keeping my $HOME and /usr/local, which are on different partitions/drives/machines.
I have investigated more, because today I had the same problem again !!! The configuration was changed, by the automatic update script which you can select by "YOU". When you select the auto-update facility from "YOU" there will be an entry "/etc/cron.d/yast2-online-update" The contents of this is : 23 20 * * * root online_update (I programmed it at 20:23 hours) "/usr/bin/online_update" is getting the updates automatically, but unfortunately it is an old version : linux:/ # online_update -c Product: SuSE-Linux Version: 8.1 Architecture: i386 Language: de Directory: directory.3 If you try to use it in 'dry mode' with verbose output, you see : linux:/etc/cron.d # online_update -d -V Types of patches to be installed: security recommended URL: ftp://ftp.quicknet.nl//pub/Linux/ftp.suse.com Path: ./i386/update/8.1/patches As you can see, it gets the updates from the 8.1 version again. I think it can be solved to change the cron-job to : 23 20 * * * root online_update -v 8.2 When trying this manually and verbose : linux:/ # online_update -v 8.2 -d -V Types of patches to be installed: security recommended URL: ftp://ftp.quicknet.nl//pub/Linux/ftp.suse.com Path: ./i386/update/8.2/patches Could you try with "online-update -c" if your version is also 8.1 ? If so, this must be a bug .... Regards, Cees
Hi Cees, I've got a fresh install of 8.2 too, but online_update -c displays everything correct. (Never used online_update, fou4s runs much smarter for me...) What does a cat /etc/SuSE-release display? Cheers, Ralf 'CoKo' Koch
"/usr/bin/online_update" is getting the updates automatically, but unfortunately it is an old version :
linux:/ # online_update -c Product: SuSE-Linux Version: 8.1 Architecture: i386 Language: de Directory: directory.3
Hi Ralf,
I've got a fresh install of 8.2 too, but online_update -c displays everything correct. (Never used online_update, fou4s runs much smarter for me...)
What does a cat /etc/SuSE-release display?
linux:~ # cat /etc/SuSE-release SuSE Linux 8.2 (i586) VERSION = 8.2 So that's not the problem. Anyway it works now with the -v 8.2 option, but I will use fou4s in the future probably. It looks very nice (didn't know it before) Regards, Cees
On Wed, Oct 08, 2003 at 11:44:08PM +0200, Cees Tool wrote:
"/usr/bin/online_update" is getting the updates automatically, but unfortunately it is an old version :
linux:/ # online_update -c Product: SuSE-Linux Version: 8.1 Architecture: i386 Language: de Directory: directory.3
| mixi:~ # cat /etc/SuSE-release
| SuSE Linux 8.2 (i586)
| VERSION = 8.2
| mixi:~ # online_update -c
| Product: SuSE Linux
| Version: 8.2
| Architecture: i386
| Language: de
| Directory: directory.3
| mixi:~ # rpm -qi `rpm -qf /usr/bin/online_update`
| Name : yast2-packagemanager Relocations: (not relocateable)
| Version : 2.7.36 Vendor: SuSE Linux AG, Nuernberg, Germany
| Release : 0 Build Date: Tue Mar 18 19:08:48 2003
| Install date: Sat Apr 26 18:23:35 2003 Build Host: E120.suse.de
| Group : System/YaST Source RPM: yast2-packagemanager-2.7.36-0.src.rpm
| Size : 2786434 License: YaST License
| Packager : http://www.suse.de/feedback
| Summary : YaST2 - Package manager
| Description :
| YaST2 - Package manager
|
| Authors:
| --------
| Michael Andres
Could you try with "online-update -c" if your version is also 8.1 ? If so, this must be a bug ....
no, mine is 8.2 At some point, something went terribly wrong on your machine. Regards, Stefan -- Stefan Seyfried Senior Consultant community4you GmbH, Chemnitz, Germany. http://www.community4you.de http://www.open-eis.com
I have investigated data with "Ethereal", the online-update of Suse 8.2 gets it's updates from pub/suse/i386/update/8.1/....
this is weird. I don't know exactly where where you have to look for the wrong setting... Was this 8.2 an updated 8.1 or did it change its identity by accident?
So the update program was getting the wrong updates (8.1 instead of 8.2) all the time. This is probably also the answer of other minor problems with updating.
Yes I have seen this too on all 3 8.1 machines I updated to 8.2 (all the other 8.2 were fresh installs). I was under the impression that SuSE updates actually worked. There was absolutely no way to convince yast update that this was not an 8.1 machine (/etc/SuSE-release contained 8.2), it insisted on loading updates for 8.1. I poked around in /var/lib/YaST2, and sure enough there was a file containing 8.1 in either its name, its content, or both. Deleting that solved the trouble, and immediately YOU offered the 8.2 updates instead of the 8.1 updates. The file seems no longer used by 8.2 yast, and I can't remember exactly what it was called. Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
participants (4)
-
Cees Tool -
Ralf Koch -
Stefan Seyfried -
Volker Kuhlmann