From owner-freebsd-questions@freebsd.org Thu Jan 5 20:38:58 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 6279FCA1CE7 for ; Thu, 5 Jan 2017 20:38:58 +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 240521197 for ; Thu, 5 Jan 2017 20:38:58 +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 3363C21079 for ; Thu, 5 Jan 2017 15:38:57 -0500 (EST) Received: from web5 ([10.202.2.215]) by compute1.internal (MEProxy); Thu, 05 Jan 2017 15:38:57 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=eml.cc; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= mesmtp; bh=/kf+9yj5rCZt30dSMqnLLdx1JLo=; b=HpQ8bhDWRmA4VxRGHapgz 1F+e2+gBj0buIUDDPm3MtSuXJlUdFKkwdyKkTnl8gmQsiS1fM8M5ahMoFRdEc5O7 l0dpcCQB7bGjpO1u2AsIDWx5LMqWupY91/lFQWDhK+mJWokxnFmIujdkB4VXR8RI wufVz5qG5GXWPHOXsAP82c= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=smtpout; bh=/kf+9yj5rCZt30dSMqnLLdx1J Lo=; b=JNvT/nUanWq4A3hCzhkpJZOF6c8XGc0THlLCXc6N/VR3eO3uhZ19cJ1K+ kXa18niA4MRChzVA/OCR8GoVz036SE76jvmAChX8Sxe2eymjlO3B63kjz1/a1mHV UorooWODNzA329mcjmLLnkgUVV/P9V+1c6B3xdheTN4whfhzpM= X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 12A206ABED; Thu, 5 Jan 2017 15:38:57 -0500 (EST) Message-Id: <1483648737.1463635.838641785.19B6EF3A@webmail.messagingengine.com> From: swjatoslaw gerus To: 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 Subject: Fwd: more etc/wpa* and rtc.conf-2 Date: Thu, 05 Jan 2017 21:38:57 +0100 X-Forwarded-Message-Id: <1483648277.1462181.838634977.0F96BE41@webmail.messagingengine.com> 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:38:58 -0000 more etc/rtc.conf hostname="sony" keymap="german.iso.kbd" ifconfig_msk0="DHCP" ifconfig_msk0="inet 0.0.0.0 network 0.f000000" defaultrouter="" ifconfig_msk0_ipv6="inet6 accept_rtadv" create_args_wlan0="country US regdomain FCC" local_unbound_enable="YES" sshd_enable="YES" moused_enable=YES" dumpdev="AUTO" -- swjatoslaw gerus milstar2@eml.cc ----- Original message ----- From: swjatoslaw gerus To: Polytropon Cc: freebsd-questions@freebsd.org Subject: more etc/wpa* and rtc.conf-1 Date: Thu, 05 Jan 2017 21:31:17 +0100 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 -- http://www.fastmail.com - The way an email service should be