Date: Mon, 9 Jan 2017 18:09:19 +0100 From: Polytropon <freebsd@edvax.de> To: swjatoslaw gerus <milstar2@eml.cc> Cc: Boris Samorodov <bsam@passap.ru>, freebsd-questions@freebsd.org Subject: Re: Edison tactic - keymap="de", wlans_iwn0="wlan0", ifconfig_wlan0="WPA & WPA2 Enterprise " ...privacy on Message-ID: <20170109180919.f4726ed4.freebsd@edvax.de> In-Reply-To: <1483953900.3528029.841566129.683EDB76@webmail.messagingengine.com> References: <1483886536.3077593.840915257.60D1F4BB@webmail.messagingengine.com> <20170108165630.540acb46.freebsd@edvax.de> <941e4b56-0d6b-ee11-bf87-0a3b96ccd80a@passap.ru> <20170108190338.682794e7.freebsd@edvax.de> <1483953900.3528029.841566129.683EDB76@webmail.messagingengine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Allow me to summarize your many "unthreaded" messages. Honestly: Please learn to use your mailing program (or web interface) properly. It isn't that hard. Show some respect for the participants of this mailing list. On Mon, 09 Jan 2017 10:25:00 +0100, swjatoslaw gerus wrote: > Re: Edison tactic - > 1. >=20 > keymap=3D"de" > wlans_iwn0=3D"wlan0" > ifconfig_wlan0=3D"WPA & WPA2 Enterprise "=20 > ...privacy on =20 I assume you did use the _correct_ setting for infoncif_wlan0, and what you presented is just a paraphrasing placeholder. :-) > In University linux notation was tunneled TLS=20 > and PAP , if entry was allcorrect ,but without PAP > - not worked=20 That is a somewhat strange description. > ---------------------- > 2.Only mobile application=20 >=20 > Need some equal indicator of wlan network as Hewlett Paccard =20 > Linux 16.04=20 I have no idea what "Hewlett Paccard Linux 16.04" is. The version number looks like Ubuntu is meant. > watch -n1 iwconfig=20 >=20 > Can see segnal level in sec ... -54 dbm -84 dbm in 5-10 metr=20 > by -84 dbm network crashed , ...browser ...parsing due worst network > connectivity .. >=20 > Tested mutiple days -suspect date/measurement are relevant > ------------- I still suspect it's a firmware issue with the specific wireless network card that you have... > a.not found equal "watch" by FreeBSD=20 Have you even tried "man watch"? > b.found S =3D -76 ,N=3D -95 by myssid=20 > Anna Ipod S-61=20 You're starting to explore the fun of wireless diagnostics. :-) On Mon, 09 Jan 2017 10:33:53 +0100, swjatoslaw gerus wrote: > University Hamburg Notation >=20 > Authehtication WPA2 > Encryption AES > EAP Type -EAP-TTLS > Outer identity -anonymous@uni-hamburg.de =20 > Authentication method PAP > User ID myid@uni-hamburg.de > passwd mypassd Okay, _that_ looks like understandable access information. You already have the relevant settings for access control in /etc/wpa_supplicant.conf (hopefully _correct_, as I said, spaces matter). So basically you need to activate the correct _mode_ for the wireless network interface. On Mon, 09 Jan 2017 11:17:37 +0100, swjatoslaw gerus wrote: > -space checked ,all was correct by sony Excellent. > work by linux 16.04 64 bit=20 That is _Ubuntu_, right? > myssid > WPA & WPA 2 Enterprise=20 > Tunneled TLS=20 > anonymous@uni-hamburg.de # > # that is outer identity equal by 20 000 + students=20 > PAP > myid@uni-hamburg.de=20 > mypasswd=20 > Deutsche telecom RA Zertifikate -avoid=20 > Ipv4 -automaticaly=20 Good, so you'll get an address via DHCP. Why don't they just write "DHCP"? On Mon, 09 Jan 2017 11:24:40 +0100, swjatoslaw gerus wrote: > Re: Edison tactic - Uni Hamburg force all linux advicers out s 4.0ct > 2016 ,worked as is ... I have no idea what this means... sorry... > If ask ,answer would - " ... We are not support freebsd ,it is your > risk ,all linux advisers forced out &" You don't need OS-specific support, just the correct information that the wireless network expects you to implement so you will be able to connect to that network. Even though this information is reflected in different files and formats across the many versions of Linux, as well as on FreeBSD or Solaris, it's more or less the same "idea" behind it. > https://www.rrz.uni-hamburg.de/services/netz/downloads.html The relevant information is stated here: https://www.rrz.uni-hamburg.de/services/netz/daten/manual/wlan-uhh-en.pdf You also got your individual user information (name and password), so _after_ you got your network _hardware_ to work properly, you're good to start. > If you are using an operating system we do not offe > r a preconfigured software or profile for please > configure the 802.1X access manually by applying th > e following parameters: > Authentication: > WPA2 > Encryption: > AES > EAP type: > EAP-TTLS > Outer identity: > anonymous@uni-hamburg.de > Certificate: > "Deutsche Telekom Root CA 2"=20 > Authentication method: PAP > User id / password: > Your UHH user id and password > Domain: > uni-hamburg.de > author ssid is eduroam -that is standart=20 Good you know that. Now you can configure /etc/rc.conf according to that information. On Mon, 09 Jan 2017 11:26:02 +0100, swjatoslaw gerus wrote: > Re: Edison tactic - PS. Use "man iwn" for more info. ...would check=20 If you do so, you'll find out that your wireless network card needs to load a specific firmware. On Mon, 09 Jan 2017 11:56:55 +0100, swjatoslaw gerus wrote: > Re: Edison tactic - checked man iwn ,where is loader.conf file ? See "man loader.conf", the path is /boot/loader.conf. > if file not exist ,which of another methode suited ? Just create it, for example with an editor (because you need to put some information there anyway): # ee /boot/loader.conf add line: if_iwn_load=3D"YES" iwn5000fw_load=3D"YES" Esc Enter Enter -> save & exit Of course you need to know _which_ firmware you must load. The brand and model of your network card will tell you. There are several firmwares to choose from: iwn1000fw_load=3D"YES" iwn100fw_load=3D"YES" iwn105fw_load=3D"YES" iwn135fw_load=3D"YES" iwn2000fw_load=3D"YES" iwn2030fw_load=3D"YES" iwn4965fw_load=3D"YES" iwn5000fw_load=3D"YES" iwn5150fw_load=3D"YES" <=3D=3D=3D I assume this one. iwn6000fw_load=3D"YES" iwn6000g2afw_load=3D"YES" iwn6000g2bfw_load=3D"YES" iwn6050fw_load=3D"YES" Use only _the one_ that applies to your actual hardware. Again, I'm not sure if you need to do this (I don't own that kind of hardware), or if you've just misconfigured something in a different place (WLAN connection configuration, not WLAN hardware configuration). As soon as this aspect is working, your WLAN connection should be working (given that the authentication information is valid). > If rememmber correctly by installer default was Intel 5010 5010 ,it > is not listed by man iwn It should be covered by the 5000 family. And as you said you already have an entry for iwn0 in "ifconfig -a" output, it looks like the iwn driver supports your card (or it wouldn't have been loaded). > processor is p8600 2*2.4 ghz=20 This has nothing to do with networking. > how define wireless card (receiver-transmitter) and software by > freebsd on sony ? The card is already supported, it's probably just missing the firmware. There is nothing you need to "define". > Which command ist it ?=20 All the required commands have been presented and explained several times. There is no "one command". The information, depending on the aspect of the wireless connection, has to be entered to the appropriate files, which you should have done by now. I assume only minor configuration tweaks are needed. If you want to find out which hardware the wireless card is, use the following command: # pciconf -lv | less or just # pciconf -lv and use the Scroll Lock key to scroll up if there are more lines than your display will show. You will then see all the relevant hardware in your computer. Look for the one that looks like a wireless network adapter. Here is an example, look for something similar: wpi0@pci0:3:0:0: class=3D0x028000 card=3D0x10118086 chip=3D0x42278086 rev=3D0x02 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'PRO/Wireless 3945ABG [Golan] Network Connection' class =3D network Note the "vendor" and "device" information. You'll quickly find it when you look for "network". On Mon, 09 Jan 2017 12:35:16 +0100, swjatoslaw gerus wrote: > linux eduroam UniversityLeibnitz wpa* ... suspect can be relevant > for Freebsd Hamburg=20 >=20 >=20 > https://www.lrz.de/services/netz/mobil/802_1x/802_1x-linux/ They suggest the wpa_supplicant.conf method as well, followed by obtaining an IP via DHCP. wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf=20 dhcpcd -n wlan0 oder dhclient wlan0 On FreeBSD, this works similar, as I already wrote. There is also an example for wpa_supplicant.conf (my translation of the german comments) to connect using PEAP/MSCHAPV2: network=3D{ ssid=3D"eduroam" key_mgmt=3DWPA-EAP eap=3DPEAP ca_cert=3D"/etc/ssl/certs/Deutsche_Telekom_Root_CA_2.pem" # must match Radius-Real / Radius-Server phase2=3D"auth=3DMSCHAPV2" identity=3D"kennung@eduroam.mwn.de" # replace eduroam.mwn.de by matching Radius-Realm ersetzen domain_suffix_match=3D"radius.lrz.de" # this option is only available to newer versions # of wpa_supplicant; must match Radius-Realm / Radius-Server=20 subject_match=3D"radius.lrz.de"=20 # only for older versions, is weaker than domain_suffix_match, # must match Radius-Realm / Radius-Server anonymous_identity=3D"anonymous@mwn.de" # or anonymous@heimat-uni-realm password=3D"XXXX" # alternatively create hash: # https://wlan.lrz.de/cgi-bin/nt-password-hash.py=20 # password=3Dhash:XXXX } But that's for Bavaria, not Hamburg, so don't copy 1:1. :-) To connect via TTLS+PAP, they suggest: network=3D{ ssid=3D"eduroam" key_mgmt=3DWPA-EAP eap=3DTTLS identity=3D"kennung@eduroam.mwn.de" # eduroam.mwn.de ggf. durch das passende Radius-Realm ersetzen domain_suffix_match=3D"radius.lrz.de" # die Option ist nur bei neueren wpa_supplicant-Versionen # verf=FCgbar, muss zum Radius-Realm bzw. Radius-Server passen=20 subject_match=3D"radius.lrz.de" # f=FCr =E4ltere Versionen, ist schw=E4cher als domain_suffix_match, # muss zum Radius-Realm bzw. Radius-Server passen anonymous_identity=3D"anonymous@mwn.de" # bzw. anonymous@heimat-uni-realm password=3D"XXXX" #(wird f=FCr PAP im Klartext ben=F6tigt) ca_cert=3D"/etc/ssl/certs/Deutsche_Telekom_Root_CA_2.pem" # muss zum Radius-Real bzw. Radius-Server passen phase2=3D"auth=3DPAP" } I don't need to translate all this, you can see the obvious difference (last line). On Mon, 09 Jan 2017 12:37:48 +0100, swjatoslaw gerus wrote: > Re: linux eduroam University Hamburg -sorry only graphics =20 >=20 > http://wpad.wlan.uni-hamburg.de/wlan-linux-kurz.pdf I get only timeouts here... On Mon, 09 Jan 2017 14:37:49 +0100, swjatoslaw gerus wrote: >=20 >=20 > Dear Sir Did Author understand your suggest correctly > - Please, do not use top post. And use inline quoting.=20 Yes. > 1.pciconf -vlc|grep -A5 iwn > Intel Wi-Fi link 5100 Okay, the model 5100 might be covered by the 5150 firmware, at least it's worth a try. > 2. man iwn=20 >=20 > ... > device iwn5000fw > device iwn5150fw > ... > device iwn6150fw >=20 > 5100 not listed .Attempt install freebsd false ? No. You already seem to have the card recognized and the driver attached, so check that firmware thing. Additionally, when I look at https://www.freebsd.org/cgi/man.cgi?query=3Diwn&apropos=3D0&sektion=3D4&man= path=3DFreeBSD+11.0-RELEASE&arch=3Ddefault&format=3Dhtml I read the following DESCRIPTION The iwn driver provides support for: [...] Intel Centrino Wireless-N 5100 [...] I assume that shows the device is supported. It's just a question now _if_ it needs additional firmware, and if yes, _which_ additional firmware must be provided. > 3. man loader.conf=20 > the file /boot/loader.rc must contain folloving two lines=20 >=20 > include /boot/loader.4th > start Do you see the difference between "loader.con" and "loader.rc"? You need to concentrate. The relevant configuration goes into loader.conf. The file loader.rc has been created by the installer. See the "FILES" section at the bottom of the manual: FILES /boot/defaults/loader.conf default settings -- do not change this fil= e. /boot/loader.4th defines the commands used by loader to read and process loader.conf. /boot/loader.conf user defined settings. /boot/loader.conf.local machine-specific settings for sites with a common loader.conf. /boot/loader.rc contains the instructions to automatically process loader.conf. You need to create /boot/loader.conf. > 4. more loader.rc NB: "more" is "less". :-) On FreeBSD, "less" is the pager people typically use. > include /boot/loader.4th > try_include /boot/loader.rc.local=20 > initialize=20 > check-passwd > include /boot/beastie.4th > beastie-start=20 A correct content - but the wrong file. Check: # less /boot/loader.conf If it isn't there, create and populate it as instructed. Again: I do not own a laptop with Intel Wireless WiFi Link 5100, so I cannot tell you if the 5150 firmware might work with that piece. But you can quickly try it. I still think you have some problem in your WLAN configuration. Compare with the examples again. Concentrate on the details. --=20 Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170109180919.f4726ed4.freebsd>