From owner-freebsd-net@FreeBSD.ORG  Tue Dec  2 01:32:57 2014
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id D0601DB1
 for <freebsd-net@freebsd.org>; Tue,  2 Dec 2014 01:32:57 +0000 (UTC)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com
 [66.111.4.27])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id A15DA907
 for <freebsd-net@freebsd.org>; Tue,  2 Dec 2014 01:32:57 +0000 (UTC)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42])
 by mailout.nyi.internal (Postfix) with ESMTP id C871C20C58
 for <freebsd-net@freebsd.org>; Mon,  1 Dec 2014 20:26:01 -0500 (EST)
Received: from web3 ([10.202.2.213])
 by compute2.internal (MEProxy); Mon, 01 Dec 2014 20:26:01 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=message-id:x-sasl-enc:from:to
 :mime-version:content-transfer-encoding:content-type:in-reply-to
 :references:subject:date; s=smtpout; bh=dS15zMPDzy3xHLXYmI/44z7s
 fnQ=; b=JGJu7Khhwcf5JssxHz1Ehq8pcs0aSPObrQqEcR1KbS4eR2kCvEt3EtGA
 k2A94fgCjTqaE9YKc/nceHSMkKo9cdoo3jGwvRct6RmcHa948eZ1ZJogFQ5df8YB
 mQs1MSq4m7/1olfi4w81vsdMshsE9tkjBur+D8LXephltEP+yXQ=
Received: by web3.nyi.internal (Postfix, from userid 99)
 id A81BA11C169; Mon,  1 Dec 2014 20:26:01 -0500 (EST)
Message-Id: <1417483561.1888990.197595249.00741CC9@webmail.messagingengine.com>
X-Sasl-Enc: 9E6QXzuatO6waLq/uuwWnpaxFOa2MJgXyOSiP56MWUKS 1417483561
From: Mark Felder <feld@FreeBSD.org>
To: freebsd-net@freebsd.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-53201334
In-Reply-To: <20141130170029.GB1056@albert.catwhisker.org>
References: <20141130010215.GP1228@albert.catwhisker.org>
 <547B081C.3000300@sunet.se>
 <20141130170029.GB1056@albert.catwhisker.org>
Subject: Re: How do I use net-mgmt/unifi{2,3,4} for Ubiquity UAP-PRO?
Date: Mon, 01 Dec 2014 19:26:01 -0600
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 01:32:57 -0000

Hi David,

The port installs an rc script so you can automate launching the
service. I've seen on some systems that it takes a very long time (15
minutes!) for the web interface to become accessible because java is
stuck in some weird "gettimeofday()" loop. I haven't seen it with recent
openjdk/unifi releases, though.

Keep in mind that anything Ubiquiti claims to be stable is actually
beta, beta is alpha, and alpha is likely to eat your children. I'd
recommend sticking with Unifi 3.x for the time being.


Good luck!