Discuss January 2011

discuss@lists.centos.org

276 participants
289 discussions

centos 5.5: iptables: module recent
by Helmut Drodofsky 29 Jan '11

29 Jan '11

Hello, I have well performing iptables in centos 5.2 and 5.3 : -A INPUT -m state --state NEW -m recent --update --seconds 60 --hitcount 1000 -p tcp --dport 25 -j LOG --log-prefix "FW DROP IP Flood: " Centos 5.5, updated today: Without -hitcount : iptables accept the line Including -hitcount : iptables brings an error message: Applying iptables firewall rules: iptables-restore: line 47 failed [FAILED] The Line Number is always the number of the COMMIT statement. Not the line number of the statement with the recent module. So I think, iptables is missing something, What? When I add the line interactive, the result is [root@host sysconfig]# iptables -A INPUT -m state --state NEW -m recent --update --seconds 60 --hitcount 1000 -p tcp --dport 25 -j LOG --log-prefix "FW DROP IP Flood: " iptables: Unknown error 18446744073709551615 The man page describes the parameter: [!] --seconds seconds This option must be used in conjunction with one of --rcheck or --update. When used, this will narrow the match to only happen when the address is in the list and was seen within the last given number of seconds. [!] --hitcount hits This option must be used in conjunction with one of --rcheck or --update. When used, this will narrow the match to only happen when the address is in the list and packets had been received greater than or equal to the given value. This option may be used along with --seconds to create an even nar- rower match requiring a certain number of hits within a specific time frame. Without -hitcount the rule is worthless. Suggestions? Many Thanks Helmut

3 4

Cold install kernel .config file
by Tom G Murphy 29 Jan '11

29 Jan '11

Convey uses a highly modified CentOS kernel to work with our attach coprocessor. Currently to setup a system for delivery we do a cold install using a "stock" CentOS cold install using kickstart. During that cold install we lay down our modified kernel and reboot the system with that kernel. After the reboot we are able to access the coprocessor management processor and down load updated firmware then reboot the system to have a completed install. My goal is to be able to boot a "modified" kernel on the cold install step so we can download the firmware updates and eliminate the second boot. I have tried using using the bzImage generated from the modified kernel build but that kernel fails to be able to load the kickstart file :-( I have done searches trying to find the .config file used to build the kernel booted during cold install but have had no luck. I am guessing I have either have too much or too little included in the kernel. I tried to make sure everything I thought was needed were not modules but included in the kernel. Does anyone have any suggestions? --- Tom Murphy Platform Support Convey Computer 1-866-338-1768 tmurphy(a)conveycomputer.com Support Site: http://conveysupport.com/ Support Ticket : http://rt.conveysupport.com/

5 6

Re: [CentOS] Static assignment of SCSI device names?
by Chuck Munro 29 Jan '11

29 Jan '11

> Les Mikesell kindly wrote: >> > >> > Identifying drives by their ID string (which includes the drive's serial >> > number) and assigning names in the rules works ok. BUT, what happens >> > when I have to swap out a failed drive? The serial number (and possibly >> > model number) changes, and the udev assignment should fail, probably >> > assigning an unexpected /dev/sd? name. RAID rebuild would choke until I >> > change the MD device assignment. > If you can figure things out for the initial md device creation, > subsequent assembly uses the uuid to match up the members and doesn't > care if the disks have been moved around either physically or by > detection order. And if you are hot-swapping drives and rebuilding > manually, you should be able to find the just-assigned name with 'dmesg'. > That's how I've been doing it with the two RAID-6 servers I have now, but in my advanced age I'm getting lazy. I did figure out how to tag the drive by path using the '-i' option to scsi_id and filtering by a "RESULT==<path> *" expression. However, something has gone very much astray, because now the rules don't do anything ... the system assigns names in the order scanned despite having added the udev rules before the default '50-udev.rules' is executed. I'm a bit mystified by this. Before I started messing around, filtering by drive id string did work, now it doesn't. Is there a small database somewhere I need to trash? Mike's suggestion is intriguing and makes me wonder if I can manually label a replacement drive with the same UUID as the failed one (assuming I keep records, of course). Since all drives in the array are partitioned exactly the same way, I can have one or two spares on the shelf pre-partitioned, ready to be given a UUID. I don't plan to hot swap. Still, I'd love to be able to use udev rules to assign names, if only to make life easier ... inquiring minds need to know why I suddenly can't get any rules to work. Maybe I need to re-install. I have just downloaded a trial version of RHEL-6 which I should try, to see if it handles this stuff more gracefully. It'll do for experimentation until CentOS-6 arrives. Chuck

1 0

internet connection tester script
by kellyremo 29 Jan '11

29 Jan '11

http://pastebin.com/raw.php?i=rykHdvBh bix.hu and www.yahoo.com are "pingable" test sites. 127.0.0.1 could not be pinged [firewall drops all icmp] i have a "oneliner" that echoes if theres "internet connection or no". $ ping -W 1 -c 2 bix.hu >& /dev/null && ping -W 1 -c 2 www.yahoo.com >& /dev/null && echo "internet connection ok" || echo "no internet connection" internet connection ok $ ping -W 1 -c 2 127.0.0.1 >& /dev/null && ping -W 1 -c 2 www.yahoo.com >& /dev/null && echo "internet connection ok" || echo "no internet connection" no internet connection $ ping -W 1 -c 2 127.0.0.1 >& /dev/null && ping -W 1 -c 2 127.0.0.1 >& /dev/null && echo "internet connection ok" || echo "no internet connection" no internet connection $ ping -W 1 -c 2 bix.hu >& /dev/null && ping -W 1 -c 2 127.0.0.1 >& /dev/null && echo "internet connection ok" || echo "no internet connection" no internet connection $ ping -W 1 -c 2 bix.hu >& /dev/null && ping -W 1 -c 2 www.yahoo.com >& /dev/null && echo "internet connection ok" || echo "no internet connection" internet connection ok $ Ok! But: if i want the "oneliner" to only go along when theres internet connection: $ while $TORF; do ping -W 1 -c 1 bix.hu >& /dev/null && ping -W 1 -c 1 www.yahoo.com >& /dev/null && TORF=false || TORF=true; done $ while $TORF; do ping -W 1 -c 1 127.0.0.1 >& /dev/null && ping -W 1 -c 1 www.yahoo.com >& /dev/null && TORF=false || TORF=true; done $ while $TORF; do ping -W 1 -c 1 127.0.0.1 >& /dev/null && ping -W 1 -c 1 127.0.0.1 >& /dev/null && TORF=false || TORF=true; done $ while $TORF; do ping -W 1 -c 1 bix.hu >& /dev/null && ping -W 1 -c 1 127.0.0.1 >& /dev/null && TORF=false || TORF=true; done $ while $TORF; do ping -W 1 -c 1 bix.hu >& /dev/null && ping -W 1 -c 1 www.yahoo.com >& /dev/null && TORF=false || TORF=true; done $ It just doesn't work. Goal: if theres no internet connection, then the oneliner must loop until there is internet connection. if theres internet connection the oneliner ends. what am i missing?

5 5

Recommendation for a Linux alternative to Centos - ATH9K disaster
by Always Learning 29 Jan '11

29 Jan '11

I persuaded a reluctant friend to buy a new computer. I enthusiastically extolled the joys and benefits of Centos and promised to install it on his new machine - dual booting with Micro$oft Windoze 7. His super-duper new laptop arrived. Acer, AMD 4 core, fast etc. but not as nice looking as my impressive HP DV5. The wireless refused to connect. After 8 hours on Saturday I could sometimes see hubs in the neighbourhood but could not connect to my own hub using WPA2. iwlist wlan0 scan produced technical details of local hubs - but still could not connect. NetworkManager sometimes froze. Spent many hours Googling for his wifi adaptor Altheros AR928K which uses a driver known as ATH9K. Many others have had a similar problem. Kernel 2.6.27 apparently includes this driver but Centos 5.5 is 2.6.18. On my Sony Vaio netbook I abandoned XP and installed Centos 5.5. No wifi (yet XP had) but luckily for me I eventually discovered the Altheros AR8132 needed ATL1E which, for Centos 5.5, means a kernel modification. Luckily it is on Elrepo as kmod-atl1e. A quick Yum and I was connected. Many thanks to Elrepo. The netbook comes to life with Centos. Its now a really usable machine. XP on a netbook was pure crap. However ATH9K for Centos 5.5 does not exist. This afternoon I had to tell my friend his brand new computer is incompatible with Centos and wifi. Please can anyone recommend a suitable Linux variant with a kernel >= 2.6.27 that is a bit like Centos ? Does anyone know if Centos 5.6 will be on 2.6.18 and whether it will have drivers like ATH9K ? Anyone any idea what kernel version Centos 6 will have ? Thank you. Best regards, Paul GB Centos on 2 VPS, 2 desktops, 1 laptop and 1 netbook. Going cheap : genuine Windoze 95 and 98 installation disks :-)

25 67

TrueCrypt WD External Drive
by Michael D. Berger 28 Jan '11

28 Jan '11

I have a WD Elements 2TB USB hard drive. I would like to encrypt the whole drive with TrueCrypt on my CentOS box. Could someone direct me to a tutorial on how to do this? Ideally, I would also like to access it with my WinXP box, but this part is optional. Thanks for your help. Mike.

3 3

problems with installl ing icecast
by mike cutie and maia 28 Jan '11

28 Jan '11

hi I run this to start the icecaste install and near the end I get this error c belowurned 1 exit status rpmbuild -bb /usr/src/redhat/SPECS/icecast.spec /usr/lib/libxml2.so -ldl -lz -lm /usr/lib/libxslt.so: undefined reference to `xmlX pathcontextSetCache' collect2: ld ret

2 1

Re: [CentOS] Ext4 on CentOS 5.5 x64
by Giuseppe Tanzilli - ServerPlan 28 Jan '11

28 Jan '11

Hi, it works just fine for me, but there is no quota support in the 5.5 ext4 release Giuseppe Il 28/01/2011 08:51, Sorin Srbu ha scritto: >> -----Original Message----- >> From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On >> Behalf Of compdoc >> Sent: Thursday, January 27, 2011 5:09 PM >> To: 'CentOS mailing list' >> Subject: Re: [CentOS] Ext4 on CentOS 5.5 x64 >> >>> For those of you that have been using the ext4 technology preview on >> CentOS 5.5, how has it panned out? Does it perform as expected? How do you > feel the >> stability, creation of the FS and the administration of it is? Ideas and >> comments welcome. >> >> >> I've recently been using ext4 because I have servers with large(ish) > storage >> volumes, and because I know that the next version of centos will support it >> better than 5.5. >> >> I only use it for storage, where I use rsync to copy terabytes of data to >> and from the servers. >> >> It works fine - it's been set and forget so far. Very fast read/write >> speeds. > Same story here. I'm building a new backup server from scratch (with no old > data on it), and while ext3 is nice and stable it's also pretty slow when we > start talking sevenish terabytes. > > My main concern is all the writing on the interweb regarding running an fsck > and a tune2fs after having formatted the filesystem to ext4; some say you > should while some say it isn't necessary. > Anyway, I get a bad block message when running fsck, and am not sure > whether this is a interface problem between the chair and the monitor or > something with the tech preview. > > > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos

1 0

SSH Automatic Log-on Failure - Centos 5.5
by Always Learning 28 Jan '11

28 Jan '11

Hallo, I wanted to avoid typing-in my password every occasion I remotely logged-on to a server. I created my SSH keys and copied the public part to the server and renamed it authorized_keys. My command line is: ssh root(a)xxxxxx.com -p 1234 The output shows the logging-on routine wants 3 types of authentication. Surely one successful authentication is sufficient ? OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to xxxxxx [123.123.123.123] port 1234. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/identity type -1 debug1: identity file /root/.ssh/id_rsa type 1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: loaded 3 keys debug1: Remote protocol version 2.0, remote software version OpenSSH_4.3 debug1: match: OpenSSH_4.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.3 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'xxxxxx' is known and matches the RSA host key. debug1: Found key in /root/.ssh/known_hosts:4 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,gssapi-with-mic,password debug1: Next authentication method: gssapi-with-mic debug1: Unspecified GSS failure. Minor code may provide more information Unknown code krb5 195 debug1: Unspecified GSS failure. Minor code may provide more information Unknown code krb5 195 debug1: Unspecified GSS failure. Minor code may provide more information Unknown code krb5 195 debug1: Next authentication method: publickey debug1: Trying private key: /root/.ssh/identity debug1: Offering public key: /root/.ssh/id_rsa debug1: Authentications that can continue: publickey,gssapi-with-mic,password debug1: Trying private key: /root/.ssh/id_dsa debug1: Next authentication method: password ------------------- files in client /root/.ssh are:- -rw------- 1 root root 1675 Jan 27 03:11 id_rsa -rw-r--r-- 1 root root 403 Jan 27 03:11 id_rsa.pub -rw-r--r-- 1 root root 2022 Jan 27 03:07 known_hosts --------------------------------------------- server /root/.ssh id_rsa.authorized_keys -rw-------- -------------------------------------------- The only active lines in /etc/ssh/ssh_config are Host * GSSAPIAuthentication yes SendEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES SendEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT SendEnv LC_IDENTIFICATION LC_ALL -------------------------------------------- After commenting-out GSSAPIAuthentication yes in /etc/ssh/ssh_config the remainder of a new debug report is:- ... debug1: Authentications that can continue: publickey,gssapi-with-mic,password debug1: Next authentication method: publickey debug1: Trying private key: /root/.ssh/identity debug1: Offering public key: /root/.ssh/id_rsa debug1: Authentications that can continue: publickey,gssapi-with-mic,password debug1: Trying private key: /root/.ssh/id_dsa debug1: Next authentication method: password All advice most gratefully received. -- With best regards, Paul. England, EU.

19 42

Re: [CentOS] Ext4 on CentOS 5.5 x64
by compdoc 28 Jan '11

28 Jan '11

>For those of you that have been using the ext4 technology preview on CentOS 5.5, how has it panned out? Does it perform as expected? How do you feel the stability, creation of the FS and the administration of it is? Ideas and comments welcome. I've recently been using ext4 because I have servers with large(ish) storage volumes, and because I know that the next version of centos will support it better than 5.5. I only use it for storage, where I use rsync to copy terabytes of data to and from the servers. It works fine - it's been set and forget so far. Very fast read/write speeds.

3 2

← Newer
1
2
3
4
5
6
7
...
29
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss January 2011