Discuss

discuss@lists.centos.org

2 participants
34758 discussions

Upgrade 4.1 --> 4.2 Question
by Thom van der Boon 03 Nov '05

03 Nov '05

Hi, I am in the proces of upgrading my CentOS 4.1 servers to 4.2. I've burnt CentOS 4.2 CD's from the ISO images (these images work because I already installed a new server with it), but I am unable to upgrade the existing servers to 4.2 using the CD's.... Does anybody have a clue, why this is not working... or is the online update option the only one... Thom

3 2

firewall dilemma
by JC 03 Nov '05

03 Nov '05

Hi everyone, I have this problem that I'm not sure what's the best solution for it. I need your input & help... I have an internal network behind a hardware firewall. All traffics go thru. the firewall. One of the firewall's rules is that it doesn't allow internal network accesses internal resources that travels outside then come back. In the other words, it drops all packets originate from inside the network that travels outside and then come back to access internal resources. For example: I have web server (used internal ip 10.1.1.10) behind the firewall, internal network can access this web server with http://10.1.1.10, but they can't access http://www.mydomain.com. Assume that I have static IP (xxx.xxx.xxx.xxx) maps to 10.1.1.10 and dns record www.mydomain.com points to xxx.xxx.xxx.xxx What I want is to allow users inside the network be able to access http://www.mydomain.com instead of http://10.1.1.10 Here is my question: should I change the rule of the firewall? If so, is there a security risk? Is there any other solution for this? By the way, I don't have an internal DNS, I use my ISP DNS service. Thank you so much for your help, JC

9 13

CentOS-announce Digest, Vol 9, Issue 2
by centos-announce-request＠centos.org 03 Nov '05

03 Nov '05

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2005:807 Moderate CentOS 4 ia64 curl - security update (Pasi Pirhonen) 2. CESA-2005:812 Important CentOS 4 ia64 wget - security update (Pasi Pirhonen) 3. CESA-2005:830 Moderate CentOS 4 ia64 openssl096b - security update (Pasi Pirhonen) 4. CESA-2005:807 Moderate CentOS 4 axp curl - security update (Pasi Pirhonen) 5. CESA-2005:830 Moderate CentOS 4 axp wget - security update (Pasi Pirhonen) 6. CESA-2005:807 Moderate CentOS 3 ia64 - security update (Pasi Pirhonen) 7. CESA-2005:812 Important CentOS 3 ia64 wget - security update (Pasi Pirhonen) 8. CESA-2005:830 Moderate CentOS 3 ia64 openssl096b - security update (Pasi Pirhonen) 9. CESA-2005:830 Moderate CentOS 4 axp openssl096b - security update (Pasi Pirhonen) 10. CESA-2005:807 Moderate CentOS 3 s390(x) curl - security update (Pasi Pirhonen) 11. CESA-2005:812 Important CentOS 3 s390(x) wget - security update (Pasi Pirhonen) 12. CESA-2005:807 Moderate CentOS 4 s390(x) curl - security update (Pasi Pirhonen) 13. CESA-2005:812 Important CentOS 4 s390(x) wget - security update (Pasi Pirhonen) 14. CESA-2005:807 Moderate CentOS 4 x86_64 curl - security update (Johnny Hughes) 15. CESA-2005:807 Moderate CentOS 4 i386 curl - security update (Johnny Hughes) 16. CESA-2005:807 Moderate CentOS 3 i386 curl - security update (Tru Huynh) 17. CESA-2005:812 Important CentOS 4 i386 wget - security update (Johnny Hughes) 18. CESA-2005:812 Important CentOS 4 x86_64 wget - security update (Johnny Hughes) 19. CESA-2005:807 Moderate CentOS 3 x86_64 curl - security update (Tru Huynh) 20. CESA-2005:812 Important CentOS 3 i386 wget - security update (Tru Huynh) 21. CESA-2005:830 Moderate CentOS 4 i386 openssl096b - security update (Johnny Hughes) 22. CESA-2005:830 Moderate CentOS 4 x86_64 openssl096b - security update (Johnny Hughes) 23. CESA-2005:812 Important CentOS 3 x86_64 wget - security update (Tru Huynh) 24. CESA-2005:830 Moderate CentOS 3 i386 openssl096b - security update (Tru Huynh) 25. CESA-2005:830 Moderate CentOS 3 x86_64 openssl096b - security update (Tru Huynh) 26. CESA-2005:830 Moderate CentOS 3 s390 openssl096b - security update (Pasi Pirhonen) 27. CESA-2005:830 Moderate CentOS 4 s390 openssl096b - security update (Pasi Pirhonen) 28. CESA-2005:812-00: Important CentOS 2 i386 wget security update (John Newbigin) 29. CESA-2005:829-00: Important CentOS 2 i386 openssl security update (John Newbigin) ---------------------------------------------------------------------- Message: 1 Date: Wed, 2 Nov 2005 19:06:54 +0200 From: Pasi Pirhonen <upi(a)papat.org> Subject: [CentOS-announce] CESA-2005:807 Moderate CentOS 4 ia64 curl - security update To: centos-announce(a)centos.org Message-ID: <20051102170653.GA9786(a)core.upi.iki.fi> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2005:807 https://rhn.redhat.com/errata/RHSA-2005-807.html The following updated files have been uploaded and are currently syncing to the mirrors: files: updates/ia64/RPMS/curl-7.12.1-6.rhel4.ia64.rpm updates/ia64/RPMS/curl-devel-7.12.1-6.rhel4.ia64.rpm -- Pasi Pirhonen - upi(a)iki.fi - http://iki.fi/upi/

1 0

Re: [CentOS] www.centos.org - Contact Us Form
by Karanbir Singh 03 Nov '05

03 Nov '05

Kai Schaetzl wrote: > Karanbir Singh wrote on Wed, 02 Nov 2005 13:39:02 +0000: > > >>And why did you think it was worth sending your reply to the entire >>mailing list ? > > > sorry, your mail got filed in that folder and when I replied the > mailing-list was set as the recipient without me noticing it. It was > obviously a bad idea to file anything coming from centos.org in that > folder :-( > No Worries :) hope that problem you were testing got fixed... -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

1 1

RE: [CentOS] Has anyone successfully used centos 4 as an iscsi CLIENT/w CHAP?
by Drew Weaver 03 Nov '05

03 Nov '05

Well, Im using an Adaptec Snap 4500 and I've had nothing but problems with it, initially I thought it was an issue with CHAP authentication so I completely disabled authentication and the kernel is still reporting in dmesg and /var/log/messages that it cannot authenticate with the target /boggle... On a side note, I know the iscsi slice works because I can connect to it just fine on Windows XP pro. So go figure :-) ;-) -Drew -----Original Message----- From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On Behalf Of Robin Mordasiewicz Sent: Wednesday, November 02, 2005 4:43 PM To: CentOS mailing list Subject: Re: [CentOS] Has anyone successfully used centos 4 as an iscsi CLIENT/w CHAP? On Wed, 2 Nov 2005, Drew Weaver wrote: > I am having a very hard time getting iscsi to work with > CentOS 4, if I put the same exact settings into the Microsoft ISCSI > initiator it works great, however I continually get authentication > errors from the kernel driver for iscsi when I try it on my *nix > machine. I am curious as to how this works. We are expecting a IPSAN device to arrive and Iam hoping iSCSI under CentOS will work _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos

2 1

JRE for x86_64
by Sam Drinkard 03 Nov '05

03 Nov '05

Does anyone know if the folks at Sun have put out a jre version to work with the x86_64 version of CentOS? If not, is there even any possibility of it occuring? Thanks.. Sam -- Snowman

7 11

Re: [CentOS] VPN via PPTP and MPPE
by Les Mikesell 02 Nov '05

02 Nov '05

On Tue, 2005-11-01 at 22:53, James B. Byrne wrote: > On 1 Nov 2005 at 11:25, Joe Pruett wrote: > > > on the windows box deep in the network properties for the vpn you'll > > find the 'use default gateway on this interface' or something very much > > like that. uncheck that and then regular internet traffic will not go > > over the vpn. > > Thank you. I found a fairly well written faq on what can go wrong > with vpn, which of course I cannot find at the moment. The basic > problem with my setup as originally given is that VPNs cannot connect > over IPs belonging to the same netblock as the physical NICs. So > the client end has to have an IP address assigned by the pptpd that > is on a different netblock from that assigned to its NIC. > > I changed the client side IP address asignment and I can now get a > VPN link to the PPTPD host, but I cannot get a route off that box. > Once I get past that problem then I will post a summary of whaI did. > This is evidently a routing issue, as you have pointed out, but one > that is probably a by product of some configuration error I have made > to the pptpd options. Does the rest of the world have a route back to the server for that new IP address? That is, you may be using the VPN address as your source and the server side as your default gateway so the packets go out, but you need routes back for the return packets. -- Les Mikesell lesmikesell(a)gmail.com

1 0

Has anyone successfully used centos 4 as an iscsi CLIENT /w CHAP?
by Drew Weaver 02 Nov '05

02 Nov '05

I am having a very hard time getting iscsi to work with CentOS 4, if I put the same exact settings into the Microsoft ISCSI initiator it works great, however I continually get authentication errors from the kernel driver for iscsi when I try it on my *nix machine. Any advice? Thanks, -Drew

2 1

Best mkfs.ext2 performance options on RAID5 in CentOS 4.2
by Sean Staats 02 Nov '05

02 Nov '05

I can't seem to get the read and write performance better than approximately 40MB/s on an ext2 file system. IMO, this is horrible performance for a 6-drive, hardware RAID 5 array. Please have a look at what I'm doing and let me know if anybody has any suggestions on how to improve the performance... System specs: ----------------- 2 x 2.8GHz Xeons 6GB RAM 1 3ware 9500S-12 2 x 6-drive, RAID 5 arrays with a stripe size of 256KB. Each array is 2.3TB after formatting. ioscheduler set to use the deadline scheduler. mkfs.ext2 options used: ------------------------ mkfs.ext2 -b 4096 -L /d01 -m 1 -O sparse_super,dir_index -R stride=64 -T largefile /dev/sda1 I'm using a stride size of 64 since the ext2 block size is 4KB and the array stripe size is 256KB (256/4 = 64). Output of using bonnie++: --------------------------- $ /usr/local/bonnie++/sbin/bonnie++ -d /d01/test -r 6144 -m anchor_ext2_4k_64s Version 1.03 ------Sequential Output------ --Sequential Input- --Random- -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP anchor_ext2_4k_ 12G 41654 96 41937 11 30537 8 40676 88 233015 27 426.6 1 ------Sequential Create------ --------Random Create-------- -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 16 3369 83 +++++ +++ +++++ +++ 4142 100 +++++ +++ 11728 100 Cheers! Sean

5 10

Has anyone successfully used centos 4 as an iscsi TARGET
by Scott Heisler 02 Nov '05

02 Nov '05

I'd love to create an ISCSI Target with Centos 4 but have not seen any good docs on how to accomplish this. Anyone know of any good docs on how to make Centos 4.1 a good ISCSI Target? Thanks Scott

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss