Blue mics are the way to go. Snowball, Yeti, whichever one you can afford, but go w/ Blue. They used to be all hand made in Latvia by artisans who used to work for Neumann (noi-man, say it right). The USB ones are Chinese made, but the designs are the tits. I have a snowball and 2x Yetis, all awesome.

FFS, no Samson, no Plantronics, no Logitech if you are actually seeking a real microphone. If budget rules, then I no longer give a f@ck what you use, and you obviously hate good sound (snowball mic is like $50).

edit: skip the Blue "ice" snowball... get the real one, $69.99 https://www.amazon.com/Blue-Snowball-Microphone-Textured-White/dp/B000EOPQ7E/ref=sr_1_3?ie=UTF8&qid=1488490633&sr=8-3&keywords=blue+snowball+mic

@stacksofplates said in CentOS 7 networking issues:

NetworkManager still creates the ifcfg files under network-scripts. So those configs will still be there, but should have NM_CONTROLLED=yes

Also, for some reason CentOS ships with both network and NetworkManager on at the same time. So that's most likely why you saw the DHCP for NetworkManager and the static file that you created. I always disable and mask network to keep people from turning it back on when they aren't paying attention.

So it looks like they took out the NM_CONTROLLED section. I must have been thinking of RHEL 6. But NM still creates the ifcfg files in the same directory.

@fuznutz04 said in Unable to create a parking lot in FreePBX 13:

Did you try disabling or uninstalling the call park module and then reinstalling the module?

Do that let me get something to save in the GUI, but parking still did not work.

Turns out the asterisk module was not even loaded.

4 different Google accounts have asked me to sign in again on my android device over the past week-end. Still get occasional blips.

@Breffni-Potter said in The SHA1 hash function is now completely unsafe:

If you burn 110K in cash.
And have a team of cyber security experts.

Today, yes. But in six months it'll be a script and $30K in compute power. In two years it'll be $500 of AWS time.

Nvm, answered my own question here.

@scottalanmiller said in Concern Around Hackers Using DHCP Pool:

@Dashrender said in Concern Around Hackers Using DHCP Pool:

In the case of the college, their dedicated IOT network was using DNS from their corporate network.

Then it wasn't dedicated 😉

No, clearly it wasn't dedicated.

Seems pretty clear that UBNT has gone public with this at this point.

@JaredBusch Awesome. Tks Jared. Tested and works beautifully!

@tim_g said in Installing Wordpress on CentOS 7 Minimal:

@jaredbusch said in Installing Wordpress on CentOS 7 Minimal:

setenforce permissive;

Setup SELinux permissions

semanage fcontext -a -t httpd_sys_content_t '/opt/yourdomain(/.*)?' restorecon -R /opt/yourdomain semanage fcontext -a -t httpd_sys_rw_content_t '/opt/yourdomain/wp-content(/.*)?' restorecon -R /opt/yourdomain/wp-content

I run my servers with SELinux running in Enforcing mode, not permissive.

So if it's in enforcing, WordPress will not run correctly. Example, you can't update, and the Add Plugins page gives a connection error (it's because httpd can't write correctly due to selinux enforcing).

Instead of running SELinux in permissive system-wide, you can keep it in Enforcing mode, and issue the following command:

semanage permissive -a httpd_t

The reason I use that one instead of by directory, is because I don't know how to do that... well I do, but I didn't have time yet to see what all directories need to be written to for updating and plugins pages and such to work correctly. I'll add that here some other time when I get a chance to look in to it more.

I only said that for install message you remove it back to enforcing

You can use the upgrade tool which is even easier if you are on a current version of owncloud. Even though the article doesn't say anything about updating from owncloud, the first article I posted does say you can use this method on current owncloud servers. You just switch the update channel and search for updates.

https://nextcloud.com/blog/get-up-to-date-with-the-new-nextcloud-updater/

I have a script I run that will remove them. Then I do the upgrade and add them back in via a script. I run a Ubuntu Server for the exact same reason you do. For a Unifi Controller

I just started getting this the other day after updating to 6.1/updating the access app on my machine. Very annoying. Who on earth thought this was something that was needed?

Now log into your new FreePBX system and it will show the Apply Config warning.

Do so.

0_1486444059378_upload-fea00064-3888-40ea-af94-ee5a8ca2979c

At this point you can go through the new system one piece at a time and make sure you are good.
Change a couple extensions to point to your new PBX and make sure they register and can call each other.
Once you are sure that the basics are working, disable the trunks on the old system, enable on the new system, and verify outside connectivity works.
Finally, you can change the rest of the extensions.

Little follow up to this as SC on CentOS was discussed in abother thread.. DB size is still small.

[root@bnasc ~]# ls -l /opt/screenconnect/App_Data/Session.db -rw-r--r--. 1 root root 46764032 Jan 26 12:30 /opt/screenconnect/App_Data/Session.db

@Kelly said in Ubiquiti now available retail:

Just so we're clear on terms, firewall vs UTM, the difference you all are noting is access rules vs packet inspection?

All firewalls do access rules and FAIAP packet inspection. Anything less and it is just a router.

The thing that points to there not being anything to worry about, while lacking the "unlimited" is a bit odd, is that those with limits say that there are limits. It doesn't say unlimited, but it does give a limit, either.

equivalent GUI settings.
0_1486133068408_upload-3e7834fd-c9c3-4a6d-a929-b3db2cc95e78