From owner-freebsd-mobile@FreeBSD.ORG Wed Dec 18 13:19:29 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D24089F0 for ; Wed, 18 Dec 2013 13:19:29 +0000 (UTC) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8F6FB1E42 for ; Wed, 18 Dec 2013 13:19:29 +0000 (UTC) Received: from [89.204.155.191] (helo=tiny-r255948) by ms-10.1blu.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1VtGDR-0004dk-Tb for freebsd-mobile@freebsd.org; Wed, 18 Dec 2013 13:27:06 +0100 Received: from tiny-r255948 (localhost [127.0.0.1]) by tiny-r255948 (8.14.7/8.14.3) with ESMTP id rBICR3pd001643 for ; Wed, 18 Dec 2013 13:27:03 +0100 (CET) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by tiny-r255948 (8.14.7/8.14.3/Submit) id rBICR2E8001642 for freebsd-mobile@freebsd.org; Wed, 18 Dec 2013 13:27:02 +0100 (CET) (envelope-from guru@unixarea.de) X-Authentication-Warning: tiny-r255948: guru set sender to guru@unixarea.de using -f Date: Wed, 18 Dec 2013 13:27:02 +0100 From: Matthias Apitz To: freebsd-mobile@freebsd.org Subject: Wifi && connect from Android YourFreedom App (a bit OT) Message-ID: <20131218122702.GA1609@tiny-r255948> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 10.0-CURRENT r235646 (i386) User-Agent: Mutt/1.5.21 (2010-09-15) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 89.204.155.191 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Matthias Apitz List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Dec 2013 13:19:29 -0000 Hello, I returned last night from Havana, Cuba. They have now Wifi in the hotels and my FreeBSD netbook (10-CURRENT) connected fine, on start of WPA you get an IP addr by DHCP and the first page in a browser (FF 24.0) re-directed you to a page to enter the credentials (login, password for around 4 USD per hour); a lot of cubans were sitting around with their laptops and Android based tablets using the Wifi zone of the hotel; I talked to someone and he said he was using some App 'Your Freedom' (or something like that) and was not asked for credentials to connect to his Facebook account, etc. This surprised me a bit, how this could work technically, and that's why I wanted to ask it here: how this could bypass the credential page, because I could not route traffic through the assigned IP on the WLAN interface without passing the credential page... how this could work with this App? My interest is only technically or due to the surprise, I do not want to use such trick on FreeBSD and I do not have any Android device. Thanks matthias -- Sent from my FreeBSD netbook Matthias Apitz, , http://www.unixarea.de/ f: +49-170-4527211 UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 From owner-freebsd-mobile@FreeBSD.ORG Wed Dec 18 14:06:37 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 07FFC4F9 for ; Wed, 18 Dec 2013 14:06:37 +0000 (UTC) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BF12D1195 for ; Wed, 18 Dec 2013 14:06:36 +0000 (UTC) Received: from 0x20.net (0x20.net [217.69.76.212]) (Authenticated sender: lala) by mail.0x20.net (Postfix) with ESMTPA id 0BF7D6A6008 for ; Wed, 18 Dec 2013 15:06:34 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 18 Dec 2013 15:06:33 +0100 From: Lars Engels To: freebsd-mobile@freebsd.org Subject: Re: Wifi && connect from Android YourFreedom App (a bit OT) In-Reply-To: <20131218122702.GA1609@tiny-r255948> References: <20131218122702.GA1609@tiny-r255948> Message-ID: X-Sender: lars.engels@0x20.net User-Agent: Roundcube Webmail/0.7 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Dec 2013 14:06:37 -0000 Am 2013-12-18 13:27, schrieb Matthias Apitz: > Hello, > > I returned last night from Havana, Cuba. They have now Wifi in the > hotels and my FreeBSD netbook (10-CURRENT) connected fine, on start of > WPA you get an IP addr by DHCP and the first page in a browser (FF > 24.0) > re-directed you to a page to enter the credentials (login, password for > around 4 USD per hour); a lot of cubans were sitting around with their > laptops and Android based tablets using the Wifi zone of the hotel; > > I talked to someone and he said he was using some App 'Your Freedom' > (or something like that) and was not asked for credentials to connect > to his Facebook account, etc. This surprised me a bit, how this could > work technically, and that's why I wanted to ask it here: how this > could > bypass the credential page, because I could not route traffic through > the assigned IP on the WLAN interface without passing the credential > page... how this could work with this App? My interest is only > technically or due to the surprise, I do not want to use such trick on > FreeBSD and I do not have any Android device. It's possibly tunneled via port 53 (DNS)? From owner-freebsd-mobile@FreeBSD.ORG Thu Dec 19 13:44:40 2013 Return-Path: Delivered-To: mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 57B8B143; Thu, 19 Dec 2013 13:44:40 +0000 (UTC) Received: from fep28.mx.upcmail.net (fep28.mx.upcmail.net [62.179.121.48]) by mx1.freebsd.org (Postfix) with ESMTP id 7536311EB; Thu, 19 Dec 2013 13:44:39 +0000 (UTC) Received: from edge04.upcmail.net ([192.168.13.239]) by viefep28-int.chello.at (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP id <20131219134431.JJDI21494.viefep28-int.chello.at@edge04.upcmail.net>; Thu, 19 Dec 2013 14:44:31 +0100 Received: from mole.fafoe.narf.at ([80.109.55.137]) by edge04.upcmail.net with edge id 3RkX1n0092xdvHc03RkXjb; Thu, 19 Dec 2013 14:44:31 +0100 X-SourceIP: 80.109.55.137 Received: by mole.fafoe.narf.at (Postfix, from userid 1001) id AB3806D47B; Thu, 19 Dec 2013 14:44:30 +0100 (CET) Date: Thu, 19 Dec 2013 14:44:30 +0100 From: Stefan Farfeleder To: Adrian Chadd Subject: iwn debug messages Message-ID: <20131219134429.GA1515@mole.fafoe.narf.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.22 (2013-10-16) Cc: mobile@freebsd.org X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Dec 2013 13:44:40 -0000 Hi Adrian, as of late I see the following messages being printed by the kernel: "iwn0: iwn_check_rx_recovery: PLCP error threshold raw (278) comparison (27800) over limit (20400); retune!" (the values vary wildly) and: "iwn0: iwn_scan: called whilst scanning!" Is this something I should worry about? This is a . BR, Stefan From owner-freebsd-mobile@FreeBSD.ORG Thu Dec 19 15:18:49 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2372EBDA; Thu, 19 Dec 2013 15:18:49 +0000 (UTC) Received: from forward18.mail.yandex.net (forward18.mail.yandex.net [IPv6:2a02:6b8:0:1402::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A8B45198B; Thu, 19 Dec 2013 15:18:48 +0000 (UTC) Received: from web9g.yandex.ru (web9g.yandex.ru [95.108.252.109]) by forward18.mail.yandex.net (Yandex) with ESMTP id 593F91782484; Thu, 19 Dec 2013 19:18:34 +0400 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web9g.yandex.ru (Yandex) with ESMTP id E579F6603A0; Thu, 19 Dec 2013 19:18:33 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1387466314; bh=39RvsEnuqGoMhxWxuEWDL6xiufFfYdbmxEjAfBwV3/w=; h=From:To:Subject:Date; b=bpvLzA3pFjof91oFQ7yLbEOErmGHkFuvjI+atpmsBdLIRWMxhJiC4OQraaaLHF6cv wUmw2mtdk5Yf4YUy7S6zS0nwNfvXDCd2sK7SNZW/OZlArFaL3iI/ZNP9ug+55u5xU6 xuVo7bzlVMEkmIO89BulZhFn8woyfOJV4Q7kmUWw= Received: from net245.234.188-30.ertelecom.ru (net245.234.188-30.ertelecom.ru [188.234.245.30]) by web9g.yandex.ru with HTTP; Thu, 19 Dec 2013 19:18:33 +0400 From: =?koi8-r?B?59XM0cXXIOfP28E=?= To: freebsd-acpi@freebsd.org, freebsd-mobile@freebsd.org Subject: Reduced screen light after power disappearing. MIME-Version: 1.0 Message-Id: <81841387466313@web9g.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Thu, 19 Dec 2013 21:18:33 +0600 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Dec 2013 15:18:49 -0000 Good day! I have a laptop with FreeBSD 10-BETA4 AMD64. When the power is lost it automatically reduces screen brightness. But when the power comes back, the brightness does not return to a normal level. Fn + BrightUP key do not help. I have no other auto power saving set up except powerd_enable="yes" in /etc/rc.conf The only way to return brightness to a normal level now is to reboot. How I can fix that? Info from /var/log/messages when power lost/resumed: ========================================================================== Dec 11 12:27:20 MYBSD devd: Executing '/etc/rc.d/power_profile 0x00' Dec 11 12:27:20 MYBSD power_profile: changed to 'economy' Dec 11 12:27:23 MYBSD devd: Executing '/etc/rc.d/power_profile 0x01' Dec 11 12:27:23 MYBSD power_profile: changed to 'performance' my dmesg ========================================================================== Copyright (c) 1992-2013 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-BETA4 #0: Fri Dec 6 13:14:42 YEKT 2013 goshanecr@MYBSD:/usr/obj/usr/src/sys/MYBSD amd64 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 CPU: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz (2494.39-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x306a9 Family = 0x6 Model = 0x3a Stepping = 9 Features=0xbfebfbff Features2=0x7fbae3bf AMD Features=0x28100800 AMD Features2=0x1 Standard Extended Features=0x281 TSC: P-state invariant, performance statistics real memory = 4294967296 (4096 MB) avail memory = 4016545792 (3830 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 SMT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0 irqs 0-23 on motherboard Cuse4BSD v0.1.30 @ /dev/cuse kbd1 at kbdmux0 random: initialized acpi0: on motherboard acpi0: Power Button (fixed) cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 550 Event timer "HPET1" frequency 14318180 Hz quality 440 Event timer "HPET2" frequency 14318180 Hz quality 440 Event timer "HPET3" frequency 14318180 Hz quality 440 Event timer "HPET4" frequency 14318180 Hz quality 440 atrtc0: port 0x70-0x77 irq 8 on acpi0 atrtc0: Warning: Couldn't map I/O. Event timer "RTC" frequency 32768 Hz quality 0 attimer0: port 0x40-0x43,0x50-0x53 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xe000-0xe07f mem 0xf6000000-0xf6ffffff,0xe0000000-0xefffffff,0xf0000000-0xf1ffffff irq 16 at device 0.0 on pci1 pcib2: irq 16 at device 1.1 on pci0 pci2: on pcib2 vgapci1: port 0xf000-0xf03f mem 0xf7400000-0xf77fffff,0xd0000000-0xdfffffff irq 16 at device 2.0 on pci0 xhci0: mem 0xf7a00000-0xf7a0ffff irq 16 at device 20.0 on pci0 xhci0: 32 byte context size. xhci0: Port routing mask set to 0xffffffff usbus0 on xhci0 pci0: at device 22.0 (no driver attached) ehci0: mem 0xf7a17000-0xf7a173ff irq 16 at device 26.0 on pci0 usbus1: EHCI version 1.0 usbus1 on ehci0 hdac0: mem 0xf7a10000-0xf7a13fff irq 22 at device 27.0 on pci0 pcib3: irq 16 at device 28.0 on pci0 pci3: on pcib3 pcib4: irq 18 at device 28.2 on pci0 pci4: on pcib4 pci4: at device 0.0 (no driver attached) pcib5: irq 19 at device 28.3 on pci0 pci5: on pcib5 pci5: at device 0.0 (no driver attached) re0: port 0xc000-0xc0ff mem 0xf2104000-0xf2104fff,0xf2100000-0xf2103fff irq 19 at device 0.2 on pci5 re0: Using 1 MSI-X message re0: ASPM disabled re0: Chip rev. 0x48800000 re0: MAC rev. 0x00000000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet address: 00:90:f5:d0:a5:c4 ehci1: mem 0xf7a16000-0xf7a163ff irq 23 at device 29.0 on pci0 usbus2: EHCI version 1.0 usbus2 on ehci1 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xf110-0xf117,0xf100-0xf103,0xf0f0-0xf0f7,0xf0e0-0xf0e3,0xf0d0-0xf0df,0xf0c0-0xf0cf irq 19 at device 31.2 on pci0 ata2: at channel 0 on atapci0 ata3: at channel 1 on atapci0 pci0: at device 31.3 (no driver attached) atapci1: port 0xf0b0-0xf0b7,0xf0a0-0xf0a3,0xf090-0xf097,0xf080-0xf083,0xf070-0xf07f,0xf060-0xf06f irq 19 at device 31.5 on pci0 ata4: at channel 0 on atapci1 ata5: at channel 1 on atapci1 acpi_button0: on acpi0 acpi_button1: on acpi0 acpi_lid0: on acpi0 acpi_acad0: on acpi0 battery0: on acpi0 acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 orm0: at iomem 0xcf000-0xcffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 coretemp0: on cpu0 est0: on cpu0 p4tcc0: on cpu0 coretemp1: on cpu1 est1: on cpu1 p4tcc1: on cpu1 coretemp2: on cpu2 est2: on cpu2 p4tcc2: on cpu2 coretemp3: on cpu3 est3: on cpu3 p4tcc3: on cpu3 fuse-freebsd: version 0.4.4, FUSE ABI 7.8 Timecounters tick every 1.000 msec hdacc0: at cad 0 on hdac0 hdaa0: at nid 1 on hdacc0 pcm0: at nid 36,37 and 41 on hdaa0 pcm1: at nid 43 on hdaa0 hdacc1: at cad 3 on hdac0 hdaa1: at nid 1 on hdacc1 pcm2: at nid 6 on hdaa1 random: unblocking device. usbus0: 5.0Gbps Super Speed USB v3.0 usbus1: 480Mbps High Speed USB v2.0 usbus2: 480Mbps High Speed USB v2.0 ugen1.1: at usbus1 uhub0: on usbus1 ugen0.1: <0x8086> at usbus0 uhub1: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 ugen2.1: at usbus2 uhub2: on usbus2 uhub0: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered ada0 at ata2 bus 0 scbus0 target 0 lun 0 ada0: ATA-8 SATA 2.x device ada0: Serial Number TA95123VCA8GUX ada0: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes) ada0: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) ada0: quirks=0x1<4K> ada0: Previously was known as ad4 cd0 at ata2 bus 0 scbus0 target 1 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: Serial Number 667216404976 cd0: 150.000MB/s transfers (SATA 1.x, UDMA5, ATAPI 12bytes, PIO 8192bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #2 Launched! Timecounter "TSC-low" frequency 1247195270 Hz quality 1000 uhub1: 8 ports with 8 removable, self powered Root mount waiting for: usbus2 usbus1 usbus0 ugen2.2: at usbus2 uhub3: on usbus2 ugen1.2: at usbus1 uhub4: on usbus1 ugen0.2: at usbus0 uhub4: 6 ports with 6 removable, self powered uhub3: 6 ports with 6 removable, self powered Root mount waiting for: usbus2 usbus1 ugen1.3: at usbus1 ugen2.3: at usbus2 Trying to mount root from ufs:/dev/ada0s3a [rw]... ubt0: on usbus0 ums0: on usbus1 ums0: 3 buttons and [XYZ] coordinates ID=0 WARNING: attempt to domain_add(bluetooth) after domainfinalize() WARNING: attempt to domain_add(netgraph) after domainfinalize() agp0: on vgapci1 agp0: aperture size is 256M, detected 65532k stolen memory info: [drm] Initialized drm 1.1.0 20060810 drmn1: on vgapci1 info: [drm] MSI enabled 1 message(s) info: [drm] AGP at 0xd0000000 256MB iicbus0: on iicbb0 addr 0xff iic0: on iicbus0 iic1: on iicbus1 iicbus2: on iicbb1 addr 0xff iic2: on iicbus2 iic3: on iicbus3 iicbus4: on iicbb2 addr 0xff iic4: on iicbus4 iic5: on iicbus5 iicbus6: on iicbb3 addr 0xff iic6: on iicbus6 iic7: on iicbus7 iicbus8: on iicbb4 addr 0xff iic8: on iicbus8 iic9: on iicbus9 iicbus10: on iicbb5 addr 0xff iic10: on iicbus10 iic11: on iicbus11 iicbus12: on iicbb6 addr 0xff iic12: on iicbus12 iic13: on iicbus13 iicbus14: on iicbb7 addr 0xff iic14: on iicbus14 iic15: on iicbus15 info: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). info: [drm] Driver supports precise vblank timestamp query. drmn1: taking over the fictitious range 0xd0000000-0xe0000000 info: [drm] Initialized i915 1.6.0 20080730 pid 5765 (iconvcap), uid 0: exited on signal 11 (core dumped) error: [drm:pid818:intel_lvds_enable] *ERROR* timed out waiting for panel to power off Related topic on forum: [1] http://forums.freebsd.org/viewtopic.php?f=12&t=43758 From owner-freebsd-mobile@FreeBSD.ORG Thu Dec 19 17:03:18 2013 Return-Path: Delivered-To: mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 112FE7B7; Thu, 19 Dec 2013 17:03:18 +0000 (UTC) Received: from mail-qc0-x22f.google.com (mail-qc0-x22f.google.com [IPv6:2607:f8b0:400d:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B484A136C; Thu, 19 Dec 2013 17:03:17 +0000 (UTC) Received: by mail-qc0-f175.google.com with SMTP id e9so1146124qcy.6 for ; Thu, 19 Dec 2013 09:03:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=PeEn9ZrF4KSoi/Rk+U+H41mfVeXUjFiTsVcmGFi7A5k=; b=0h5ZKnHgvwvQ9ve7etqIHNG3xXSb5pTx4hEGv7xvwSy0jl6HMW6SeVckj17i408s7z Wl7ukxCM8FHt1KSN6c+I70maFsYElH7uIskiFHWtTPGHf9ksyu9qBDbuTLJro1fL/Z67 h5KWBra6Z+Vv7/Uuo1SrSjPZeLPvmz3pIXhamMdfZdUhr6lli98L9EbEHq9OUB6//x+d xbhTCwc6IoTPuziIta2J+AmX/o1yAfWrNuek6L2lJq9RcT0jNKUyTEaGbflpLCLv/i19 tGmzg9pM1Nj4xcEkjgpZr9eztD2mQZRMCWKUq2ejcIvxsDP7PdXHbjL7+vAYApqwiXlK 91xg== MIME-Version: 1.0 X-Received: by 10.224.16.204 with SMTP id p12mr5028906qaa.26.1387472596918; Thu, 19 Dec 2013 09:03:16 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.53.200 with HTTP; Thu, 19 Dec 2013 09:03:16 -0800 (PST) In-Reply-To: <20131219134429.GA1515@mole.fafoe.narf.at> References: <20131219134429.GA1515@mole.fafoe.narf.at> Date: Thu, 19 Dec 2013 09:03:16 -0800 X-Google-Sender-Auth: 9Y0P1-uLCJCQEZK0OMPlY8gkW-k Message-ID: Subject: Re: iwn debug messages From: Adrian Chadd To: Stefan Farfeleder Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-mobile@freebsd.org" X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Dec 2013 17:03:18 -0000 1) It's an indication that the air is busy. It's supposed to retune after that but I haven't yet finished that part. 2) Beause of how we do single channel scans, we seem to trigger the occasional bug where the firmware will sit on a passive channel (eg 13) for a couple of minutes at a time before moving on. Beforehand we would send another scan command even if the previous scan was not finished and this could cause the firmware to get upset. Now I track whether we're scanning on a channel and print out an error if we try to submit another scan. The real solution is to rewrite the net80211 scan stuff to be modular so iwn can implement its own multi-channel scanning but I just don't have the time at the moment. -a On 19 December 2013 05:44, Stefan Farfeleder wrote: > Hi Adrian, > > as of late I see the following messages being printed by the kernel: > > "iwn0: iwn_check_rx_recovery: PLCP error threshold raw (278) comparison (27800) over limit (20400); retune!" > (the values vary wildly) > > and: > > "iwn0: iwn_scan: called whilst scanning!" > > Is this something I should worry about? This is a . > > BR, > Stefan From owner-freebsd-mobile@FreeBSD.ORG Thu Dec 19 23:56:26 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CD586237 for ; Thu, 19 Dec 2013 23:56:26 +0000 (UTC) Received: from mail-qc0-x22f.google.com (mail-qc0-x22f.google.com [IPv6:2607:f8b0:400d:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 88AEC15B6 for ; Thu, 19 Dec 2013 23:56:26 +0000 (UTC) Received: by mail-qc0-f175.google.com with SMTP id e9so1610826qcy.20 for ; Thu, 19 Dec 2013 15:56:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=1n0MYV8ChZXl08PshktYRZzC3bVg/3yRV3Lf7bCUcxw=; b=OA/Faf5u/TERTuXs6wqHrjUY3nqEKPkbhmXQNh2+IlZ95WCq6Cod8TmpqKIVLFDytW Z0IjlWtKSlwIjRhq2Zmc0dDAkpsGi+//wNP1EOgS4s+xEwpQaBTqQ4uuH1pLJLNrF7Zp E/6lyHrl4nJste9ajYW93mCdbpUv4XjPySGxCknYbvKvWVXoUX28HkzXlm7DhBz/fiZh X8hLc1Gjd5moo/lngiZ2yFnpG7VvBdJica4MiIIfncsPw0chdjZXhXN1S+gb7/IavoLy anC24ua1jidu34tKHCcVQuRr6mtYes1809yIJATb4qP5BzfLvZRJ6DjiEo26k3tH0GBK GwLw== MIME-Version: 1.0 X-Received: by 10.229.53.68 with SMTP id l4mr8497634qcg.21.1387497385694; Thu, 19 Dec 2013 15:56:25 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.53.200 with HTTP; Thu, 19 Dec 2013 15:56:24 -0800 (PST) Received: by 10.224.53.200 with HTTP; Thu, 19 Dec 2013 15:56:24 -0800 (PST) In-Reply-To: <20131218122702.GA1609@tiny-r255948> References: <20131218122702.GA1609@tiny-r255948> Date: Thu, 19 Dec 2013 15:56:24 -0800 X-Google-Sender-Auth: gc4ujtlY-aj06sLKhEygC10f8mA Message-ID: Subject: Re: Wifi && connect from Android YourFreedom App (a bit OT) From: Adrian Chadd To: Matthias Apitz Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-mobile@freebsd.org X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Dec 2013 23:56:26 -0000 There are a few tunneling apps that bypass various forms of captive portals. But there are spyware and trust issues with them. adrian On Dec 18, 2013 7:19 AM, "Matthias Apitz" wrote: > > Hello, > > I returned last night from Havana, Cuba. They have now Wifi in the > hotels and my FreeBSD netbook (10-CURRENT) connected fine, on start of > WPA you get an IP addr by DHCP and the first page in a browser (FF 24.0) > re-directed you to a page to enter the credentials (login, password for > around 4 USD per hour); a lot of cubans were sitting around with their > laptops and Android based tablets using the Wifi zone of the hotel; > > I talked to someone and he said he was using some App 'Your Freedom' > (or something like that) and was not asked for credentials to connect > to his Facebook account, etc. This surprised me a bit, how this could > work technically, and that's why I wanted to ask it here: how this could > bypass the credential page, because I could not route traffic through > the assigned IP on the WLAN interface without passing the credential > page... how this could work with this App? My interest is only > technically or due to the surprise, I do not want to use such trick on > FreeBSD and I do not have any Android device. > > Thanks > > matthias > -- > Sent from my FreeBSD netbook > > Matthias Apitz, , http://www.unixarea.de/ f: > +49-170-4527211 > UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) > UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" > From owner-freebsd-mobile@FreeBSD.ORG Fri Dec 20 00:33:07 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 33962CA8 for ; Fri, 20 Dec 2013 00:33:07 +0000 (UTC) Received: from mail.ultra-secure.de (mail.ultra-secure.de [78.47.114.122]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 546C21863 for ; Fri, 20 Dec 2013 00:33:05 +0000 (UTC) Received: (qmail 62599 invoked by uid 89); 20 Dec 2013 00:23:22 -0000 Received: from unknown (HELO ?192.168.1.201?) (rainer@ultra-secure.de@217.71.83.52) by mail.ultra-secure.de with ESMTPA; 20 Dec 2013 00:23:22 -0000 Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: Wifi && connect from Android YourFreedom App (a bit OT) From: Rainer Duffner In-Reply-To: Date: Fri, 20 Dec 2013 01:23:18 +0100 Message-Id: References: <20131218122702.GA1609@tiny-r255948> To: Lars Engels X-Mailer: Apple Mail (2.1827) Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-mobile@freebsd.org X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Dec 2013 00:33:07 -0000 Am 18.12.2013 um 15:06 schrieb Lars Engels : > Am 2013-12-18 13:27, schrieb Matthias Apitz: >> Hello, >> I returned last night from Havana, Cuba. They have now Wifi in the >> hotels and my FreeBSD netbook (10-CURRENT) connected fine, on start = of >> WPA you get an IP addr by DHCP and the first page in a browser (FF = 24.0) >> re-directed you to a page to enter the credentials (login, password = for >> around 4 USD per hour); a lot of cubans were sitting around with = their >> laptops and Android based tablets using the Wifi zone of the hotel; >> I talked to someone and he said he was using some App 'Your Freedom' >> (or something like that) and was not asked for credentials to connect >> to his Facebook account, etc. This surprised me a bit, how this could >> work technically, and that's why I wanted to ask it here: how this = could >> bypass the credential page, because I could not route traffic through >> the assigned IP on the WLAN interface without passing the credential >> page... how this could work with this App? My interest is only >> technically or due to the surprise, I do not want to use such trick = on >> FreeBSD and I do not have any Android device. >=20 >=20 > It's possibly tunneled via port 53 (DNS)? Most likely, yes. Professional penetration testers have whole suite of programs that allow = them to tunnel all kinds of stuff front and back through firewalls that = allow random outgoing DNS traffic. I=92ve never tried them myself, but I imagine it=92s a bit slow. But fast enough to siphon data out... From owner-freebsd-mobile@FreeBSD.ORG Sat Dec 21 16:52:43 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 895C62DD; Sat, 21 Dec 2013 16:52:43 +0000 (UTC) Received: from mail.s1.d2ux.org (static.209.96.9.5.clients.your-server.de [5.9.96.209]) by mx1.freebsd.org (Postfix) with ESMTP id 41F1F11C9; Sat, 21 Dec 2013 16:52:42 +0000 (UTC) Received: from mail.s1.d2ux.org (mail [10.0.0.3]) by mail.s1.d2ux.org (Postfix) with ESMTP id 5175D84F25D2; Thu, 19 Dec 2013 16:46:17 +0100 (CET) Received: from mail.s1.d2ux.org ([10.0.0.3]) by mail.s1.d2ux.org (mail.s1.d2ux.org [10.0.0.3]) (amavisd-new, port 10024) with ESMTP id JaXPSvGoMxvd; Thu, 19 Dec 2013 16:46:15 +0100 (CET) Received: from www.s1.d2ux.org (unknown [10.0.0.4]) by mail.s1.d2ux.org (Postfix) with ESMTPS id 9405484F2589; Thu, 19 Dec 2013 16:46:15 +0100 (CET) Received: from 188.92.33.52 ([188.92.33.52]) by d2ux.org (Horde Framework) with HTTP; Thu, 19 Dec 2013 16:46:15 +0100 Date: Thu, 19 Dec 2013 16:46:15 +0100 Message-ID: <20131219164615.Horde.UYp_45CJTw6WSZ_EsSijVw1@d2ux.org> From: Matthias Petermann To: =?utf-8?b?0JPRg9C70Y/QtdCyIA==?= =?utf-8?b?0JPQvtGI0LA=?= Subject: Re: Reduced screen light after power disappearing. References: <81841387466313@web9g.yandex.ru> In-Reply-To: <81841387466313@web9g.yandex.ru> User-Agent: Internet Messaging Program (IMP) H5 (6.1.4) Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 8bit Cc: freebsd-acpi@freebsd.org, freebsd-mobile@freebsd.org X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Dec 2013 16:52:43 -0000 Hello, Zitat von Гуляев Гоша : > Good day! > > I have a laptop with FreeBSD 10-BETA4 AMD64. When the power is lost > it automatically reduces screen brightness. But when the power comes > back, the brightness does not return to a normal level. Fn + > BrightUP key do not help. I have no other auto power saving set up > except powerd_enable="yes" in /etc/rc.conf > > The only way to return brightness to a normal level now is to > reboot. How I can fix that? You could try to kldload acpi_video. # kldload acpi_video # sysctl -a | grep brightness should show up a key which you can use to set the brightness. # sysctl hw.acpi.video.lcd0.brightness=100 For some vendors (e.g. Lenovo) there are custom modules with their own brightness setting keys: # kldload acpi_ibm # sysctl -a | grep brightness If none of this are working, you might want to try out ports/sysutils/acpi_call and directly calling an ACPI method to increase or set the brightness. This was btw the only way it is working for my Lenovo X121e and E330. Kind regards, Matthias -- Matthias Petermann | www.petermann-it.de GnuPG: 0x5C3E6D75 | 5930 86EF 7965 2BBA 6572 C3D7 7B1D A3C3 5C3E 6D75