ClearFoundation

Hello. I am new installation used VMware ClearOS 5.2. however network setup error

1. Select manual configuration:
IP Address 192.168.1.101 / 255.255.255.0
Gateway 192.168.1.1
Name Server 8.8.8.8
2. Next setup IP Address: 192.168.1.101 / 255.255.255.0 -> ok
3. Network Error: There was an error configuring your network interface
I can't do next setup. How to configure Clear OS. Please help

OK, so I still have this problem. Is anyone else getting this issue from a fresh install of 5.2?

Thanks for any help.

Hi,

I'm came from IpCop distro to ClearOS Enterprise solution because I needed 2 WAN.

On IpCop, I had:

GREEN (lan)
ORANGE (some server - block all traffic from/to red interface except certain ip/ports allowed)
RED (wan)


Now on ClearOS i need:

LAN (lan)
DMZ (some server - block all traffic from/to red interface except certain ip/ports allowed)
WAN 1
WAN 2


How can i configure DMZ to access ip/ports allowed on internet?


Thanks
Alex

actually we have 3 interfaces.first one is the external that connects to the ISP, second one is for our internal network and the third one is for backup of the first interface.
from the second interface we have created 4 different virtual interfaces.
now we all want to do is set the DHCP on and lease the ip from the pool based on mac,for this we already have captured macs of all machines.
help us reagarding the different subnets with different gateway which dhcp should broadcast while leasing ip to the client.

Hope this is not classed as thred hijacking

But I was woundering other than larger memory allocation for programs (might be wrong here), what are the advantages over the PAE kernel?

I tried searching for any certs containing "localhost.localdomain" on my system, but came up empty.

Webconfig reports that both the CA and system certs are signed for my domain, as opposed to localhost.localdomain.

Where would I want to place a cert in order for Zarafa to pick it up for Exchange purposes?

Hi,

I will be patient and do the re-boot early tomorrow morning from the console.



David

looking at the list on my system:

[root@cc ~]# find / -print | egrep "rpmnew$|rpmsave$"
/etc/samba/smb.conf.rpmnew
/etc/rbs/rbs.conf.rpmnew
/etc/ssl/openssl.cnf.rpmnew
/etc/sudoers.rpmnew
/etc/suvad.conf.rpmnew
/etc/squid/squid.conf.rpmnew
/etc/system/webconfig.rpmnew
/etc/ntp.conf.rpmnew
/etc/ppp/options.ldap.rpmnew
/etc/ldap.conf.rpmnew

There are not many - so following the advice from your link I will have a look and see if i can deal with each as appropriate.

David

Let me try to summarize my conclusions.

1. There is a new Flexshare causing problems.

2. The new Flexshare module does not cater for a situation that was possible in the former version, i.e. equal names for shares and user groups. The new module cannot be started if this situation is present but it does not issue any error message, it just stops functioning.

3. In the situation above Flexshare will also shut down the Samba module, again without issuing any message at all. The user can see that Samba is not working, although it was originally started correctly, but he can have no clue that the real cause is with Flexshare.

4. There is a prolem with Flexshare interpreting the ldap.conf file in /etc/proftpd, probably because capitals are used. The same conf file has been used before by the system booter, without a problem. So, FTP is correctly started during the boot process but is subsequently shut down by the new Flexshare moduile, again without issuing any message at all. Like in the Samba-situation, the user sees that something is wrong with FTP, but can have no clue about the real reason, being a problem in Flexshare.

I may be entirely wrong with my conclusions but I thought it would be most helpful if I stated my findings in the clearest possible terms.
In the meantime I have upgraded to 5.2 and conclude that the problems also exist in 5.2.
That being said, I think 5.2 is another great achievement by ClearCenter. We should all try helping to improve it even further.

Hi all,

when I did the yum upgrade last night I noticed three warning messages:

Installing: app-webconfig ##################### [119/336]
warning: /etc/system/webconfig created as /etc/system/webconfig.rpmnew

Updating : app-remote-backup ##################### [140/336]
warning: /etc/rbs/rbs.conf created as /etc/rbs/rbs.conf.rpmnew

Updating : app-ssl ##################### [144/336]
warning: /etc/ssl/openssl.cnf created as /etc/ssl/openssl.cnf.rpmnew

These warning messages did not stop the upgrade from completing successfully.

Why would the warning occur? (were the files mentioned in use at the time, and therefore locked?)

Do I need to take any action (such as restarting the system, or running the upgrade process again)?

apologies for my inexperience (Linux upgrades are not something I am familiar with).

David

Hi,

My system also displayed the 5.1 image until i cleared my browser's cache - and therefore forced a reload from the box - the 5.2 image came up straight away.

(I am using Mozilla SeaMonkey).

David

Hi Randall,

Clear OS is not designed for a system with that many users, but the software is all based on enterprise class code - so should have no problems performing network tasks such as proxy server / firewall etc for that number of users provided your hardware is up to the job. On a high specification hardware box i wouldn't see a problem. My system supports 150, so bit of a step up by *10.

I think that the community would be very interested to hear your results / experience should you install Clear - although with that number of users there may be other systems which better support your needs.

David

i won't ping to other clients even though it appear on ip->setting
then i try the new driver then all mess up
i reinstall back old driver after the new driver can't detect the lan card

here what happen

eth1: RealTek RTL8139 at 0xf8a32800, 00:30:84:9e:d2:02, IRQ 177
eth1: Identified 8139 chip type 'RTL-8139C'
eth2: RealTek RTL8139 at 0xf8a34c00, 00:80:48:49:98:a2, IRQ 58
eth2: Identified 8139 chip type 'RTL-8100B/8139D'
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
eth0: IPv6 duplicate address detected!
eth1: no IPv6 routers present
eth0: Promiscuous mode enabled.
device eth0 entered promiscuous mode
type=1700 audit(1280385123.662:3): dev=eth0 prom=256 old_prom=0 auid=4294967295 ses=4294967295
device eth0 left promiscuous mode
type=1700 audit(1280385123.665:4): dev=eth0 prom=0 old_prom=256 auid=4294967295 ses=4294967295
eth0: Promiscuous mode enabled.
device eth0 entered promiscuous mode
type=1700 audit(1280385123.672:5): dev=eth0 prom=256 old_prom=0 auid=4294967295 ses=4294967295
eth1: Promiscuous mode enabled.
device eth1 entered promiscuous mode
type=1700 audit(1280385126.192:6): dev=eth1 prom=256 old_prom=0 auid=4294967295 ses=4294967295
device eth1 left promiscuous mode
type=1700 audit(1280385126.195:7): dev=eth1 prom=0 old_prom=256 auid=4294967295 ses=4294967295
eth1: Promiscuous mode enabled.
device eth1 entered promiscuous mode
type=1700 audit(1280385126.199:8): dev=eth1 prom=256 old_prom=0 auid=4294967295 ses=4294967295

since in kudzu Atl2 detected as eth0 i change it on modprobe.conf

alias scsi_hostadapter ata_piix
options snd-intel8x0 index=0
remove snd-intel8x0 { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-intel8x0
alias eth0 atl2
alias eth1 8139too
alias eth2 8139too
alias snd-card-0 snd-hda-intel
options snd-card-0 index=0
options snd-hda-intel index=0
remove snd-hda-intel { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-hda-intel

Hi all,

I performed an upgrade of our box last night via yum. The upgrade went without problem, and yum stated that it completed successfully.

There was no prompt for a restart.

I logged in this morning and the system displays 5.2, so looking good.

In the hardware report the system is listed as having kernel version 2.6.18-164.6.1.v5 (SMP).

In the yum log I noticed the kernel being upgraded (kernel.i686 0:2.6.18-194.8.1.v5).

Excuse my Linux inexperience - but do I need to perform a restart of the system for some of the changes to take effect?

David

hello communitiy,
we have got clearos installed in our office as a gateway.currently we have 4 subnets and have been using the gateway services of clearos by configuring the ip address for the other system statically, but we do want to run a dhcp server which automatically leases the ip looking at the mac and also broadcast the desired gateway among different 4 subnets gateway.

on looking through the webconsole DHCP server settings only allowed to add the ip pool range and the DNS but does not seems to include any provision for netmask.

we are confused about how to meet our requirements.any help will be greatly be appreciated..

present network architecture:
192.168.0.0/27
192.168.0.32/27
and so on....


thanks in advance

Hello!
I install latest ClearOS 5.2 and set domain for my network. And now I can change passwords for user only from webconfig. When user try change password from windows XP (or windows 7) interface they get 'you don't have rights for change password'
and in log I see error

system userpasswd: password change failed for avp: Parameter is invalid - Username

I try from console
/usr/sbin/userpasswd avp
...
and get same error

Can anybody help my with this problem?

Thank you!
Alexander