From owner-freebsd-questions@freebsd.org Thu Jan 5 19:40:33 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 94C92CA1B8C for ; Thu, 5 Jan 2017 19:40:33 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay13.qsc.de (mailrelay13.qsc.de [212.99.187.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 115B916F8 for ; Thu, 5 Jan 2017 19:40:31 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay13.qsc.de; Thu, 05 Jan 2017 20:42:04 +0100 Received: from r56.edvax.de (port-92-195-83-137.dynamic.qsc.de [92.195.83.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id C675C3CC3F; Thu, 5 Jan 2017 20:40:21 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v05JeKDZ001942; Thu, 5 Jan 2017 20:40:20 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Thu, 5 Jan 2017 20:40:20 +0100 From: Polytropon To: swjatoslaw gerus Cc: freebsd-questions@freebsd.org Subject: Re: Mr.Edison tactic ... performed to date -thank you for assistance Message-Id: <20170105204020.73eb19f1.freebsd@edvax.de> In-Reply-To: <1483644016.1447892.838558553.55CAAF02@webmail.messagingengine.com> 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> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay13.qsc.de with D669A683483 X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.2345 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 19:40:33 -0000 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, ...