ClearFoundation

Hi Tim,

Wow ... thanks!
I will be looking forward to the connlimit "how to" and to the new kernel updates.
It looks like someone should be paying you for all the work that you do.

The link you send me (linux.die.net/man/8/iptables) is huge, so I hope that I won't have to dig to deep to get a basic understanding of ip tables.

I wonder what the Internet speed of Krod was before he implemented your kernel, because without a reference, it doesn't mean that much.

Anyway ... keep up the good work ...

Greetings,

John

Just been testing this further and found that adding 'nomodeset' to the kernel boot line has helped with some Intel graphics card related issues (freezing after about 10mins without a monitor attached). May help with your Nvidia card issues too John?

Also I don't think i mentioned it elsewhere yet, but all your hard drives will now be known as /dev/sdxX not /dev/hdxX, thats a global change by newer kernels

So this is newer than timb6_kernel?

A quick question, do you think its a problem that we cant use oinkmaster to update the intrusion detection system with the clearos kernel, i really do like the os the system is sweet but most of the other systems do not disable the free updates.

Hi Krod,

Yes
kernel-2.6.31.12-174.2.22.timb1.i686.rpm
is newer than
kernel-2.6.31.5-127.timb6.i686.rpm

download.clearfoundation.com/community/timb80/kernel/

Oinkmaster is not related to kernel support at all, in fact you can still use oinkmaster to update your intrusion detection rules but it will remove all the snortsam 'autoblock' entries. I did try this a long time ago on ClarkConnect, and was successful but manually adding all the fwsam alerts was too painful. I did write a script to automate the process but i've not put any work into it for a long time - mainly becuase I came to the conclusion that ClarkConnect do a good job of importing all the important ones anyway. In newer versions of snort /snortsam you *should* be able to manage these by using sid-block.map which is essentially a list of SID's that are meant to autoblock

FYI I do add the following rules (which are downloaded on a regular schedule) from emergingthreats.org to block suspect IP's
www.emergingthreats.net/index.php/rules-mainmenu-38.html
www.emergingthreats.net/rules/emerging-compromised-BLOCK.rules
www.emergingthreats.net/rules/emerging-dshield-BLOCK.rules
Then add them to /etc/snort.conf under the include section
(Using the -BLOCK rules also includes the automatic block via snortsam)

Thanks for your answers...it clears things up for me.

I really love the os im just trying to figure out how things work under the hood.

I am glad to hear that ClearOS does not block the free updates...it sounds like thay offer some free, along with, some custome signatures for the paid services and thats ok with me as long as the ids sigs, the free sigs get updated and not leave us open to new attacks.

And i did install the new kernel-2.6.31.12-174.2.22.timb1.i686.rpm, no problems here. I did not run the yum to install X simply because i am running it as a headless server. I do plug the monitor in just to make sure it does not through out errors on boot.

I also updated php with out any problems here.

I did notice that the intrusion detection rules were upated because i could no longer reach gmail.com, i had to add an exception to the rules then all was good again.

Hi Tim,

This is the result of installing your latest kernel:
When changing the following in the kernel boot line (/etc/grub.conf), it crashed during boot:

Currently /etc/grub.conf looks like this:

What is the last line doing ... ?!?

It took about 20 minutes to boot after I changed "/ nomodeset" to "/1", but still with the same problem of having nothing on my screen.
Also when rebooting, just before the reboot, the font becomes very small and the last few lines are suddenly visible.
I love using your bleeding edge kernel, but will you please try to solve this issue, when you have time ... ?!?

Please advise,

John

Hi John, thanks for taking the time to test this out

You appear to have picked up a relabelling partition issue I saw when I was testing earlier kernels. The root partition is relabelled to /1 instead of / and the the boot partition is relabelled to /boot/1. It has no consequence other than messing up your grub config. The later kernels don't have this problem

When I said add 'nomodeset' to the kernel boot line, I didn't mean modify the other section too...so in your case it should have been (note the LABEL=/1)


Also you shouldn't have that extra line spare kernel line at the bottom, so can be deleted

To revet the labelling issue back to defaults, I need a little more info, can you provide the output of


I will do some more research on why display goes blank on NV04 cards at the udev stage...