Alexander Dalloz ad+lists@uni-x.org wrote: Am Mi, den 15.02.2006 schrieb spart cus um 1:36:

has anyone come across a good and nice tutorial on openvpn ? havent seen any of it so far. i want to setup a low cost vpn network.

tia

What are you missing?

http://openvpn.net/howto.html

Alexander

http://lists.centos.org/mailman/listinfo/centos Im on the part of building the dh, already finished that. im looking where my key files are stored. then im stuck where to go now

--------------------------------- Yahoo! Mail Use Photomail to share photos without annoying attachments.

Another neat link is http://www.samag.com/documents/s=9766/sam0506a/ 0506a.htm

Michael

On Feb 15, 2006, at 9:28 AM, Jeffrey Tadlock wrote:

spart cus wrote:

...

hi guy, has anyone come across a good and nice tutorial on openvpn ? havent seen any of it so far. i want to setup a low cost vpn network.

The openvpn site is pretty helpful from my experience, but here are a few links to something someone in my LUG put together:

http://www.skippy.net/trac/wiki/OpenVPN http://www.skippy.net/trac/wiki/OpenVPN_Howto http://www.skippy.net/trac/wiki/OpenVPN_Certificate_HOWTO

/jt _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

hello,

I don't want to be rude but problem solving it's much easier if you read the docus. and if you want to administrate a VPN server than you should know the basics of linux and package management/compiling from source.

bye, Ago

hi!

2 Mach Speed K8M8MS motherboards eth0 ---use the onboard LAN port eth1 ---pci nic card using crossover to another box

eth0....that is just a regular lan...the whole domain...internet etc

eth1...just a private lan between 2 servers.

for about a year I have been running this on 32 bit boards w/no problems

but w/these 64 bit boards, they just don't want to hear about it

when I hit the nic card, there is no response, when the nic card tries to hit, it give a "Wrong data bite #30" error

whew!!! never ran into this before

thx

John Rose

rado wrote:

kk, I am guilty of easily just booting up in Kde's gui, start/system settings/users and groups but then also I'd rather do it from the bash console.

after googling around a good bit I am still not exactly sure of the proper way to do this.

I want to add a user to another group w/out removing the groups the user already belongs to.

in man usermod: -G group,[...] A list of supplementary groups which the user is also a member of. Each group is separated from the next by a comma, with no intervening whitespace. The groups are subject to the same restrictions as the group given with the -g option. If the user is currently a member of a group which is not listed, the user will be removed from the group. This behaviour can be changed via -a option, which appends user to the current supplementary group list.

ok...I kinda get this but unclear of the exact format and I am super fearful of ripping up my userbase.

Here is what I think it should be:

# usermod <user> -a -G <group>

where the user's name is say..."pete" and I want him to be added to the group "tech":

# usermod pete -a -G tech

Say pete is already in groups ummm, sales,admin, and help. After administering the above command, would pete still be in sales, admin,help, and now tech? I am interested in the simplest, correct way to do this.

thx,

John Rose

---

CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

The command should be # usermod -G <group1,group2...> <username> When doing it this way you need to specify ALL the groups the user belongs to as this does not append to the current list. So to get a list of groups a user may be associated with type # groups <username> Then take the output to be used with usermod command. Or you can just edit the /etc/groups file by hand

Zeb

On Sat, 2006-02-18 at 18:59 -0600, rado wrote:

...

...

I want to add a user to another group w/out removing the groups the user already belongs to.

in man usermod: -G group,[...] A list of supplementary groups which the user is also a member of. Each group is separated from the next by a comma, with no intervening whitespace. The groups are subject to the same restrictions as the group given with the -g option. If the user is currently a member of a group which is not listed, the user will be removed from the group. This behaviour can be changed via -a option, which appends user to the current supplementary group list.

ok...I kinda get this but unclear of the exact format and I am super fearful of ripping up my userbase.

Here is what I think it should be:

# usermod <user> -a -G <group>

where the user's name is say..."pete" and I want him to be added to the group "tech":

# usermod pete -a -G tech

Say pete is already in groups ummm, sales,admin, and help. After administering the above command, would pete still be in sales, admin,help, and now tech? I am interested in the simplest, correct way to do this.

thx,

John Rose

---

CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

The command should be # usermod -G <group1,group2...> <username> When doing it this way you need to specify ALL the groups the user belongs to as this does not append to the current list. So to get a list of groups a user may be associated with type # groups <username> Then take the output to be used with usermod command. Or you can just edit the /etc/groups file by hand

Zeb

ok, thx, Zeb! sure works for me

incidently tho, all I had read up on it, I never did really see or thought to just edit /etc/group but then only in the current (4.2) man useradd did I see mention of the "-a" command for append. Must be some pretty recent new addition I guess.

John

On Mon, 2006-02-20 at 13:12 -0600, rado wrote:

for some reason, crontab is not picking up a job here listed. I, for one see nothing wrong w/it as I have been running approx the same basic crontab for well over a year now. I have just put this box on line about a week ago tho soooo...here's the crontab: SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=root HOME=/

# run-parts 01 * * * * root run-parts /etc/cron.hourly 02 4 * * * root run-parts /etc/cron.daily 22 4 * * 0 root run-parts /etc/cron.weekly 42 4 1 * * root run-parts /etc/cron.monthly 05 * * * * /usr/bin/freshclam # 11 0,4,8,12,16,20 * * * root /usr/bu-snap/bu-snap.sh > /dev/null 2>&1

I have another box running bu-snap.sh in the same kinda crontab setup. Only diff. is that box is a 64bit and this 32...both 4.2 sys.

In the other box...bu-snap is logging in var/log/messages as it's supposed to the time it starts and the time it finishes...and the results show working fine. In this latest installed system...I just can't get it to run under this crontab. should run at hr:11 every 4 hrs.

thx

John Rose

make sure crond is running and set to start on bootup.

service crond status

and

chkconfig --list crond

On 20/02/06, rado rado@rivers-bend.com wrote:

if there is any kind of problem, where it cannot complete it's job(bu- snap.sh) it does msg me. ...no msgs from it. oh ya...crond is running and /var/log/messages and cron are plum full or crond input. bu-snap.sh writes to ../log/messages when it starts and when it finishes... but in this box, says nothing and, of course, it doesn't even run as I can tell. this sucker has me stumped... and also...lots of other stuff in the logs of chrond running root stuff so it's not a problem of not running root stuff.

Is /usr/bu-snap/bu-snap.sh executable by root? i.e. is it owned by root and executable by its owner or owned by some other user but executable by other, if you see what I mean? So, either...

-rwxr--r-- 1 root root 0 Feb 20 20:45 bu-snap.sh or -rwxr--r-x 1 wmcdonald wmcdonald 0 Feb 20 20:45 bu-snap.sh

I also notice, from the format, this is /etc/crontab rather than a user crontab, yes? If that's the case then perhaps the freshclam command before bu-snap.sh is causing the problem. The freshclam job you've listed doesn't have a user to run as specified.

42 4 1 * * root run-parts /etc/cron.monthly 05 * * * * /usr/bin/freshclam

Shouldn't that be...

42 4 1 * * root run-parts /etc/cron.monthly 05 * * * * root /usr/bin/freshclam

So, it could well be that crond's choking before getting to bu-snap.sh.

I like to include the following header in user crontabs just as a reminder of the formatting (for other users, obviously :)) ...

# minute (0-59), # | hour (0-23), # | | day of the month (1-31), # | | | month of the year (1-12 or Jan-Dec), # | | | | day of the week (0-6, 0=Sunday, or Sun-Sat). # | | | | | commands

For /etc/crontab you could have something similar...

# minute (0-59), # | hour (0-23), # | | day of the month (1-31), # | | | month of the year (1-12 or Jan-Dec), # | | | | day of the week (0-6, 0=Sunday, or Sun-Sat). # | | | | | user to run as # | | | | | | commands

Hi y'all I can't tell you which msg thread it was in but after an install and the system hangs...one of the responses was that the boot partition might be too large...

Although most of the installs (raid 1) I don't have that problems but I have before. I usually make my boot partition 200mb.

my question: What size do y'all recomend for the boot partition, 100mb?

thx

John Rose

On Thu, 2006-02-16 at 11:22 -0600, rado wrote:

Hi y'all I can't tell you which msg thread it was in but after an install and the system hangs...one of the responses was that the boot partition might be too large...

No, it was that it's location puts things above 1024 cyls (largeness *can* cause).

Although most of the installs (raid 1) I don't have that problems but I have before. I usually make my boot partition 200mb.

Generally 100mb is enough. @00 is ok too.

my question: What size do y'all recomend for the boot partition, 100mb?

The important thing is that the partition shoud begin and end below 1024 cyls. Grub/lilo, etc. have to use BIOS calls.

sfdisk -l /dev/xxx will let you see the mappings.

thx

John Rose

---

CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

rado spake the following on 2/16/2006 9:22 AM:

Hi y'all I can't tell you which msg thread it was in but after an install and the system hangs...one of the responses was that the boot partition might be too large...

Although most of the installs (raid 1) I don't have that problems but I have before. I usually make my boot partition 200mb.

my question: What size do y'all recomend for the boot partition, 100mb?

thx

John Rose

I have never filled 100 mb, but I usually only keep the current and one older kernel on a machine.

On Thu, 2006-02-16 at 11:22, rado wrote:

Hi y'all I can't tell you which msg thread it was in but after an install and the system hangs...one of the responses was that the boot partition might be too large...

Although most of the installs (raid 1) I don't have that problems but I have before. I usually make my boot partition 200mb.

my question: What size do y'all recomend for the boot partition, 100mb?

100mb should be plenty, but it's not the size that matters. The important thing is that it fits in the first 1024 cylinders of the disk, since that may be all that bios can access and the kernel and initrd must be loaded by bios calls.

On Thu, 2006-02-16 at 13:03 -0500, Chris Mauritz wrote:

Les Mikesell wrote:

...

On Thu, 2006-02-16 at 11:22, rado wrote:

...

Hi y'all I can't tell you which msg thread it was in but after an install and the system hangs...one of the responses was that the boot partition might be too large...

Although most of the installs (raid 1) I don't have that problems but I have before. I usually make my boot partition 200mb.

my question: What size do y'all recomend for the boot partition, 100mb?

100mb should be plenty, but it's not the size that matters.

Any admin that tells you size doesn't matter must just have a small disk....

<ducking>

---- and probably lacking someone to fsck it too!

</ducking>

Craig

2006/2/16, Aleksandar Milivojevic alex@milivojevic.org:

Quoting rado rado@rivers-bend.com:

...

What size do y'all recomend for the boot partition, 100mb?

If /boot partition starts on the first cylinder, and if your drive reports 255 heads and 63 sectors per track, this will give you BIOS addressable range of aprox 8Gb (a little bit less):

255 heads * 63 cylinders * 512 bytes * 1024 cylinders

Anything above it, and your BIOS can't access it.

Is this a problem related to the age of BIOS in question, or is it a plainly never-to-be-solved problem?

-- Eduardo Grosclaude Universidad Nacional del Comahue Neuquen, Argentina