From owner-freebsd-questions@freebsd.org Thu Jan 5 20:31:20 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 01C76CA1A53 for ; Thu, 5 Jan 2017 20:31:20 +0000 (UTC) (envelope-from milstar2@eml.cc) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 B661B1EE4 for ; Thu, 5 Jan 2017 20:31:19 +0000 (UTC) (envelope-from milstar2@eml.cc) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D551B20F24; Thu, 5 Jan 2017 15:31:17 -0500 (EST) Received: from web5 ([10.202.2.215]) by compute1.internal (MEProxy); Thu, 05 Jan 2017 15:31:17 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=eml.cc; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=Lgn4UtYs+8vfNWmnrEm+V7Nn7M I=; b=bb6P5k3FVudzcP1ycBpk4le4VsIe7BvhoNWALet4JkPBUpWj39RpeBVoEY a/y7o1eVnEqVjIZLMAF4CMbSYVcZVxbSfZIBHPZpAI1dDwkSrJh7fdUXXPmfADSF NbaVN82oh1OSbKO+dCmhHm2FE+4E1I8Yb2IoKnGvtC6AU/zOo= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=smtpout; bh=Lg n4UtYs+8vfNWmnrEm+V7Nn7MI=; b=qSdG4d5ZtLPHNCxfWwHCbzhxLO+cj5b1+1 kGF8BCk8t5+2kI4/CBdcD09q8KoSKtsM5PxYwWZ7Q1fCOGQxz+fOnNsumgBC18YZ sP6wXssZkEqHut7tMX2kulDe3bWnnJmnLm3tiyWhulMiERPIV114K+dA4FfOBkmf jtfAG79AM= X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id B11386ABED; Thu, 5 Jan 2017 15:31:17 -0500 (EST) Message-Id: <1483648277.1462181.838634977.0F96BE41@webmail.messagingengine.com> From: swjatoslaw gerus To: Polytropon Cc: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-8d3535ca Date: Thu, 05 Jan 2017 21:31:17 +0100 References: <1483454858.4190708.835937993.300F2713@webmail.messagingengine.com> <20170103160657.GB43153@neutralgood.org> <20170103203023.b2396c95.freebsd@edvax.de> <861swjx6mv.fsf@WorkBox.homestead.org> <1483475176.874533.836320369.7B612577@webmail.messagingengine.com> <20170103214548.1d726a06.freebsd@edvax.de> <1483564140.1178887.837521761.7D1930C8@webmail.messagingengine.com> <20170105004510.44e54ddc.freebsd@edvax.de> <1483639288.1431717.838467905.64F6B28C@webmail.messagingengine.com> <20170105193234.37780fbb.freebsd@edvax.de> <1483644016.1447892.838558553.55CAAF02@webmail.messagingengine.com> <20170105204020.73eb19f1.freebsd@edvax.de> Subject: more etc/wpa* and rtc.conf-1 In-Reply-To: <20170105204020.73eb19f1.freebsd@edvax.de> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2017 20:31:20 -0000 power on msk0 -link state changed to down ----- login root ,passwd ... cd /etc ,more wpa* ssid =" author ssid -correctly" key_mgmt=WPA-EAP identity= " author correctly" password " correctly" priority = 5 network ={ priority=0 key_mgmt=NONE } -- swjatoslaw gerus milstar2@eml.cc On Thu, Jan 5, 2017, at 08:40 PM, Polytropon wrote: > On Thu, 05 Jan 2017 20:20:16 +0100, swjatoslaw gerus wrote: > > but your suggest possibly not correlated with local Hamburg University > > conditions > > It has been general advice working for every WLAN. The > one at Hamburg's university isn't very different. :-) > > > > > Linux 64 ,which can work with wlan asked > > So you have the proof that WLAN _per se_ works. If it works > on Linux, it will work on FreeBSD as soon as you did the > neccessary steps. > > > > > autorwlanid@uni-hamburg.de ( that is author specific ) > > passw (that is author specific) > > > > > ipv4 -automat > > That means DHCP. > > > > > that is for linux ,for windows and mac another instructions > > Of course. But Linux instructions won't work on FreeBSD because > Linux isn't FreeBSD. I've pointed you to the relevant instructions > for FreeBSD, including the sources from where I took them (and > where you could have read them on your own). > > Except putting your identification data for a non-public WLAN > into /etc/wps_supplicant.conf and configuring your WLAN interface > there is nothing else to do. > > > > > Can be ,that local wlan would not accept freebsd > > No, it's not common (and against the idea of openness, inter- > operability, and research in general) for a university to > implement a means that allows Linux, Mac OS X, iOS and > even "Windows" connect to a WLAN, but not FreeBSD. > > If WLAN _does not_ work even if you set up everything correctly, > with FreeBSD you have the option to find out _why_. In worst > case, ask those who maintain the actual WLAN access point(s) > and network, they'll be happy to clarify if they intendedly > "block" FreeBSD or if you just failed to configure your WLAN > settings properly. :-) > > > > > than ideja of author to use more stable as linux platform freebsd > > or solaris from start > > is false > > I have no idea how an educated person could develop such > a strange idea, sorry. > > And do you have instructions for setting up WLAN access > with Solaris? Maybe they'll "block" it, too... ;-) > > > > Summary: Set up your wireless network as instructed, add your > individual access credentials, and _try it_ before you make a > wild ass guess. :-) > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... -- http://www.fastmail.com - A no graphics, no pop-ups email service