It'd be nice if the guys at eGloo could rig something up for psiphon and other VPN tunneling apps in their Netify application and/or protocol filters. Maybe ClearOS could request that from them?
iptables -t filter -I FORWARD -d 192.168.1.165 -p udp --dport 5060 -j DROP
iptables -t filter -I FORWARD -s 126.96.36.199/28 -d 192.168.1.165 -p udp --dport 5060 -j ACCEPT
What is the difference? If mine work for SIP and PJSIP, why won't they work for RDP for the OP? These are in Custom Firewall only and I do not use a standard port forward under Network Port Forwarding.
You could swap the order of the two rules or maybe change the -I to a -A on the second rule. Seems to me the way you have the rules written, the first rule would be inserted at line 1, first. Then the second rule would be inserted at line 1, first. So since iptables works from rule 1 on down, the port accept rule would run first, then the drop rule. An append on the second rule would put it at the end of the table.
You would do better to use the dhcp server on your clearos box for your lan and disable the one on your Cisco router. Your cos firewall works in conjunction with dnsmasq (aka dhcp server) on your gateway. That's the beauty of using it as a gateway. I would try that first.
The following is just a suggestion in hope to point you in somewhat of a good direction. Testing the procedure adds the members to the group when doing an ldapsearch, but it doesn't show up in the Webconfig, so something is missing. Additionally, the group the user was added to shows up when using 'id test1' at shell.
With that said, perhaps start by creating an LDIF file (e.g. addmemberstogroup.ldif) where ldap operations could be performed to add multiple users to a group? You could somewhat mimic the snapshot.ldif file found in /var/clearos/openldap, but something way simpler to the effect of:
Then a script to modify your ldap group:
Note: Prior to and after the modification, you could see what the ldap directory looks like
You'll have to experiment, albeit gingerly, and see how well it works for you. Maybe one of the ClearOS gurus can add/takeway to/from this?
Thank you very much. It is all fine now again. It just installed app-kopano-basic and app-kopano-basic-core.
My subscription is also shown in the webconfig again (I do not have the community version). The reason for the "test-server" version was an update to kopano 8.5.8 posted by Ben if I remember correctly (link). It could not be done over the normal updates, because it needed some hands on and is still just available over the "test-server" version. The reason why I wanted the webconfig setup back is that I like the recursive backup method built in kopano, which is easier to access through the webconfig. I additionally backup the database and attachments on a daily base for disaster recovery.
Thank you again. You helped me a lot.
Try and do a yum install of app-kopano-basic and see what it wants to install. You can choose 'no' for the time being when yum prompts you to install. Based on your yum list of kopano, I would wager all yum will want to install is app-kopano-basic and app-kopano-basic-core. Any other dependencies are more than likely installed on your server, but you can verify that with and compare it to what yum wanted to install. You won't be able to select the repository since they're private due to kopano being a subscription from Clearcenter. I'm curios as to why your installed kopano apps are through a private testing repo, since it's a subscription service, unless maybe you're using ClearOS Community edition where some semblance of kopano comes free in the Community edition, and maybe you subscribed later through the Marketplace?
I'm pretty sure kopano basic is responsible for covering your subscription through Clearcenter, which will require you enter a license in the Webconfig once the package is installed. You can get that license number through your Clearcenter portal. I'm assuming you went through that at one time.
I might backup all kopano folders if I were you, prior to doing the yum install.
then copy all relevant folders to a dependable source.
Are you trying from the shell prompt or from the Marketplace? Have you tried using yum from the shell prompt, i.e. 'yum install app-web-proxy' (minus the quotes)? Yum will show you if it's already installed or not when you try.
'yum deplist app-web-proxy' will show you what dependencies are need to use the web proxy.