Topics created by JaredBusch

TP-Link switch is working excellent as well!

I like the idea of making wifi available to customers anywhere their other customers have access... but pay so someone else can have access? HELL NO!

Like you said dealing with double NAT would be bad enough... but having to pay.. ummm NO!

@nadnerB said:

Say what!? Stuff is being h4x0r3d easily because it's not maintained? Say it isn't so!

Won't anyone think of the children!!!!!

@thecreativeone91 said:

Well you have 21 days. but the BP is to uninstall Exchange from SBS, demote the SBS and then unjoin it from the domain before the 21 days are up.

There goes exchange.
image.jpg

@JaredBusch Correct. This has been the one downside for AD Connect if you have users that frequent the office. Traffic is forced across the Pertino interface. 430 will allow you to designate "zones" where devices use local routes instead.

@Carnival-Boy said:

But it's about doing your own cost-benefit analysis. It's too simplistic to say you should never run legacy applications.

Of course, there are always times that legacy applications need to be run. But there are limits too. ASP as a platform has been legacy for a decade and a half. That's a long time. It has a pending end date for when it may not be available any longer in any capacity. It presents platform level risk which may prove to not matter, but may prove to be extremely limiting in the future - that's the nature of risk, we don't know what will happen with hardware and software down the road. But it is technical debt building up in a platform that is nearly all of the way through its "trailing off support" timeframe.

It's fine to have legacy apps. But it is also important to identify when a legacy app is becoming too legacy. In the OP's case, ASP created support and hosting risk in addition to normal concerns. Those were probably types of risk that were not considered in the past. Any business running ASP is constrained if they decide that they want to go hosted, for example. They might not ever decide to do that, but there is technical debt potentially making that decision for them, as well.

Any ongoing support of an ASP legacy app means that investment is being put into the old system. Maybe that is trivial, maybe it is major. Technical debt is a hidden cost. Money goes into keeping the old system running instead of being implemented in a new system. The effort to support the old could offset the effort to replace it.

@JaredBusch
Yeah, when you name your server OS's with the same words - but in a different order, it makes searching quite difficult. SEO nightmare.

@scottalanmiller said:

@Dashrender said:

Plus update costs.

Those aren't required, though. It's a one time cost of the thing that you buy at the time.

Yeah I realized that shortly after I posted, but by then I was leaving my desk... lol

When it comes to projecting dates for technology, I usually see people say either "basically tomorrow" or "a billion years from now" and they're always wrong. People tend to forget technological change does have essentially a set pattern and keeps doubling in speed. People tend to over estimate that doubling or vastly underestimate it, and I think that's primarily a difference between optimists and people who have been disappointed with predictions in the past. If the prediction doesn't fall within what's likely possible in The Law of Accelerating Returns then it almost certainly won't happen.

Given the technology, I'd say mass production is likely in 5 years, but the problem is mass to them may not be mass to us. If they're creating even 10 million units a year, that's mass production, but it's likely to be fairly expensive to where it doesn't touch your daily life, therefore most people would say "ah, see, I told you, didn't' happen in 5 years," when it actually did. What you're really wanting is "when is it cheap enough for me to throw away" and that may indeed be 10 - 15 years, depending on many other factors and over all application.

@JaredBusch said:

No, you are missing the entire point. There is a reason that Elastix dropped FreePBX in 3.0. There is a reason the the PBXiaF team has spent the time and effort to come up with the Asterisk GUI distribution.

Both teams obviously hope that nothing changes as they are also continuing efforts with their products that use FreePBX.

FreePBX is a horrible interface. It is dated and sad. It works, mostly, but leaves a lot to be desired. Ever since FreePBX switched from being an interface to being a full on competitor to Elastix and PIAF they have had a huge incentive, really a need, to develop their own thing. If anything, my guess is that they hope that FreePBX does do something drastic and force them to either take over or abandon FreePBX, not that they fear that. I felt for years that they needed to do this, having nothing to do with source worries with FreePBX.

Simple business pressures would make them do what they are doing. Nothing more is needed.

Asterisk GUI is not there yet in usability. It functions, but the usability is just lacking yet.

I am leery of FreePBX due to the Sangoma buy out.

Elastix is only stable on an old as dirt system.

Just damnit.

Here is the UDP

Starting job... [2015-02-24 01:55:39] Stay on this page for results! Starting Nmap 6.00 ( http://nmap.org ) at 2015-02-24 03:55 EET Initiating UDP Scan at 03:55 Scanning 104.167.111.187 [9 ports] Discovered open port 123/udp on 104.167.111.187 Completed UDP Scan at 03:55, 0.23s elapsed (9 total ports) Nmap scan report for 104.167.111.187 Host is up (0.090s latency). PORT STATE SERVICE 53/udp open|filtered domain 69/udp closed tftp 111/udp open|filtered rpcbind 123/udp open ntp 161/udp open|filtered snmp 500/udp open|filtered isakmp 514/udp open|filtered syslog 4500/udp open|filtered nat-t-ike 5060/udp open|filtered sip Nmap done: 1 IP address (1 host up) scanned in 0.58 seconds Raw packets sent: 9 (604B) | Rcvd: 2 (132B) Job finished [2015-02-24 01:55:40]

So, @JaredBusch... what did you end up doing?

Just seen a nice post on the Elastix forums. Someone went through the trouble to manually compare a 2.4 install and list the updates needed.

http://forum.elastix.org/viewtopic.php?f=3&t=130440

I think I'll be testing this out.

I've never had good luck with Root Hints, always odd issues would pop up. But if you use forwarders don't use your ISPs either..

Here is a post, just now, that the free UEB can't back up Xen guests, which it could do if it was using the agents to do the backups.

http://community.spiceworks.com/topic/797407-setup-suggestions-freenas-r510-10x600gib-sas?page=4#entry-4319958

@JaredBusch said:

https://community.ubnt.com/t5/UniFi-Updates-Blog/UniFi-3-2-10-is-released/ba-p/1165532

I've upgraded my office and a client office today with no problems.

Good to hear, I did an update release not too long ago and the difference was night and day. I will look into doing this one now.

@Dashrender said:

Fuel Surcharge - REALLY.... we're splitting out the cost of fuel now?

I'm also surprised that it's cheaper for a child to fly than an adult - it's still only one person to a seat (I'm guessing infants in laps fly free). Yet the fuel surcharge is the same (you'd think if anything that is where the difference would be since most children weigh less and would require less fuel to move them than an adult..

Children weigh less and use less fuel. Not much, but some.

This is the HTTPS plugin.

wtf3