Fwd: more etc/wpa* and rtc.conf-2

[swjatoslaw gerus]

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 at eml.cc

----- Original message -----
From: swjatoslaw gerus <milstar2 at eml.cc>
To: Polytropon <freebsd at edvax.de>
Cc: freebsd-questions at 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 at 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 at 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