Re: add a daemon user
On Tuesday 29 Jan 2013 21:52:46 Alexander Hall wrote: > On 01/29/13 18:23, Tim Hoddy wrote: > > On Tuesday 29 Jan 2013 21:06:11 Wesley M.A. wrote: > >> To add a "daemon user" like for example _nginx : > >> > >> useradd -L daemon -d /var/empty -s /sbin/nologin -g =uid _nginx > >> > >> Is this enough ? > > > > Is there a '-L' option? > > The man page states so. Shouldn't it be? It should. I did a 'man useradd' from a shell on a Linux m/c. Apologies.
Re: add a daemon user
On 2013-01-29, Wesley M.A. wrote: > Le 2013-01-29 21:40, jca+o...@wxcvbn.org a écrit : >> "Wesley M.A." writes: >> >>> Hi, >> >> Hi >> >>> To add a "daemon user" like for example _nginx : >>> >>> useradd -L daemon -d /var/empty -s /sbin/nologin -g =uid _nginx >>> >>> Is this enough ? >> >> [...] >> >> Depends. Your _nginx user will likely serve files, you don't want to >> put >> them in /var/empty, which is where other daemons chroot. Do you want >> to >> chroot? Why not use the www user? Why not use the devel nginx >> package, >> if you need a more recent version? > > I want to make work mailserv (ie mailserv.github.com) on OpenBSD-5.2 > When i install it, _nginx was not created. > It is why my question. > > Thank you. > > -- > Wesley > > OpenBSD now normally runs nginx as the "www" user.
Re: hi OpenBSD
On Wed, Jan 30, 2013 at 2:45 AM, Jérémie Courrèges-Anglas < jca+o...@wxcvbn.org> wrote: > Robert Kopp wrote: > > almost cannot believe it..what do you think [url snipped] > > > > Robert > > Url shorteners are bad > > And you should feel bad :) -- Aaron Mason - Programmer, open source addict I've taken my software vows - for beta or for worse
Re: add a daemon user
On 01/29/13 18:23, Tim Hoddy wrote: On Tuesday 29 Jan 2013 21:06:11 Wesley M.A. wrote: To add a "daemon user" like for example _nginx : useradd -L daemon -d /var/empty -s /sbin/nologin -g =uid _nginx Is this enough ? Is there a '-L' option? The man page states so. Shouldn't it be?
Re: vnd and softraid panic
On Wed, Jan 23, 2013 at 02:33:16AM +1100, Joel Sing wrote: > On Thu, 3 Jan 2013, Eivind Evensen wrote: > > On Mon, Dec 31, 2012 at 07:21:08PM +1100, Joel Sing wrote: > > > On Mon, 31 Dec 2012, Eivind Evensen wrote: > > > > Hello. > > > > > > > > Trying to play around a bit with softraid using vnd reliably results > > > > in a panic when assembling the raid volume. I think the first time I > > > > tried this was around 4.9 so it's not something new. > > > > ... > > > > FWIW this should now be rectified in -current. I tried a snapshot downloaded on 21.th (OpenBSD 5.2-current (GENERIC) #17: Fri Jan 18 19:42:57 MST 2013) which produced the same results. I waited a few days in case the snapshot was too old and built from sources from yesterday, still giving the same results. I don't need such a setup so it's not a big deal, but here's output and dmesg in case it may be helpful: root:skoeske> dd if=/dev/zero of=disk1 bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 2.875 secs (36462177 bytes/sec) root:skoeske> r disk1=disk2 dd if=/dev/zero of=disk2 bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 3.219 secs (32567739 bytes/sec) root:skoeske> r disk2=disk3 dd if=/dev/zero of=disk3 bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 3.569 secs (29378164 bytes/sec) root:skoeske> vnconfig vnd0 disk1 root:skoeske> vnconfig vnd1 disk2 root:skoeske> vnconfig vnd2 disk3 root:skoeske> fdisk -iy vnd0 Warning CHS values out of bounds only saving LBA values Writing MBR at offset 0. root:skoeske> fdisk -iy vnd1 Warning CHS values out of bounds only saving LBA values Writing MBR at offset 0. root:skoeske> fdisk -iy vnd2 Warning CHS values out of bounds only saving LBA values Writing MBR at offset 0. root:skoeske> printf "a\n\n\n\nRAID\nw\nq\n\n" | disklabel -E vnd0 Label editor (enter '?' for help at any prompt) > partition: [a] offset: [128] size: [204672] FS type: [4.2BSD] > > No label > changes. root:skoeske> printf "a\n\n\n\nRAID\nw\nq\n\n" | disklabel -E vnd1 Label editor (enter '?' for help at any prompt) > partition: [a] offset: [128] size: [204672] FS type: [4.2BSD] > > No label > changes. root:skoeske> printf "a\n\n\n\nRAID\nw\nq\n\n" | disklabel -E vnd2 Label editor (enter '?' for help at any prompt) > partition: [a] offset: [128] size: [204672] FS type: [4.2BSD] > > No label > changes. root:skoeske> bioctl -c 1 -l /dev/vnd0a,/dev/vnd1a,/dev/vnd2a softraid0 sd0 at scsibus1 targ 1 lun 0: SCSI2 0/direct fixed sd0: 99MB, 512 bytes/sector, 204144 sectors softraid0: SR RAID 1 volume attached as sd0 panic: softraid0: sr_wu_init got active wu Stopped at Debugger+0x4: popl%ebp RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! ddb> trace Debugger(d08fcddc,f2087de8,d08d0da4,f2087de8,d0a7e540) at Debugger+0x4 panic(d08d0da4,d0f8c014,f2087dfc,d036ccf3,d0fedab8) at panic+0x5d sr_wu_init(d1055000,d0fedab8,f2087e3c,d1055a30,d1057f00) at sr_wu_init+0x73 sr_wu_put(d1055000,d0fedab8,f2087e3c,f2087e3c,d02030dd) at sr_wu_put+0x2f scsi_io_put(d1055a30,d0fedab8,8000,d0fedab8,d0fedab8) at scsi_io_put+0x19 scsi_xs_put(f2027000,f2027000,f2087e8c,d041de18,d1055000) at scsi_xs_put+0x37 sr_raid1_intr(d1065000,f1fabdc4,f17dc000,200,52000) at sr_raid1_intr+0x107 vndstrategy(d1065000,0,0,50,d1065000) at vndstrategy+0x70 spec_strategy(f2087f48,0,f2087f6c,d03f2c28,d1053d90) at spec_strategy+0x3d VOP_STRATEGY(d1065000,0,0,0,d0fedaf8) at VOP_STRATEGY+0x2c sr_startwu_callback(d1055000,d0fedab8,d02008bf,d1053d80,d03f2c50) at sr_startwu _callback+0x39 workq_thread(d1053d80) at workq_thread+0x36 Bad frame pointer: 0xd0bc8ed8 ddb> ps PID PPID PGRPUID S FLAGS WAIT COMMAND *23369 0 0 0 70x100200srdis 19292 1571 6315 1000 30x80 ttyin less 1571 6315 6315 1000 30x88 pause sh 6315 30722 6315 1000 30x80 wait man 30722 11048 30722 1000 30x88 pause ksh 11048 2130 2130 1000 30x80 selectsshd 2130 1703 2130 0 30x80 poll sshd 2513 1 2513 0 20x80ksh 20983 1 20983 0 30x80 ttyin getty 22576 1 22576 0 30x80 ttyin getty 19748 1 19748 0 30x80 ttyin getty 21880 1 21880 0 30x80 ttyin getty 5243 1 5243 0 30x80 ttyin getty 32690 1 32690 0 30x80 selectcron 24485 1 24485 99 30x80 poll sndiod 99 1 99 0 30x80 selectinetd 22458 15830 15830 95 30x80 kqreadsmtpd 17649 15830 15830 95 30x80 kqreadsmtpd 17949 15830 15830 95
Re: OpenBSD/iwn(4) support for WPA2/PEAP/MSCHAPv2?
From: Mark Kettenis Subject: Re: OpenBSD/iwn(4) support for WPA2/PEAP/MSCHAPv2? Date: Mon, 28 Jan 2013 21:27:23 + (UTC) > Erling Westenvik gmail.com> writes: > > > I need to connect my ThinkPad T500 running 5.2 current to the wifi > > network here at my university. E.g. the "eduroam" network which is > > available at most universities through, at least, Europe. After Googling > > around for a while I'm not sure whether OpenBSD yet has support for WPA2 > > and PEAP/MSCHAPv2. And if it does: if someone could provide me with a > > sample ifconfig? > > As of today it is actually possible to do this with OpenBSD: > > http://www.undeadly.org/cgi?action=article&sid=20130128142215 > Wow, thank you! -- posted from my school wireless
Re: add a daemon user
On Tuesday 29 Jan 2013 21:06:11 Wesley M.A. wrote: > To add a "daemon user" like for example _nginx : > > useradd -L daemon -d /var/empty -s /sbin/nologin -g =uid _nginx > > Is this enough ? Is there a '-L' option?
npppd with tun interface not work on i386?
Hello Misc!
I tried to start npppd with the default config with tun0 interface on
my Alix board:
I get the following error message:
# npppd -d
2013-01-29 19:54:38:NOTICE: Starting npppd pid=13464 version=5.0.0
2013-01-29 19:54:38:NOTICE: Load configuration
from='/etc/npppd/npppd.conf' successfully.
2013-01-29 19:54:38:ERR: tun0 delete ipaddress tun0 failed: Device not
configured
jan 21 amd64 snapshot vmware machine works:
# npppd -d
2013-01-29 19:59:21:NOTICE: Starting npppd pid=18398 version=5.0.0
2013-01-29 19:59:21:NOTICE: Load configuration
from='/etc/npppd/npppd.conf' successfully.
2013-01-29 19:59:21:INFO: tun0 Started ip4addr=10.0.0.1
2013-01-29 19:59:21:INFO: Listening /var/run/npppd_ctl (npppd_ctl)
2013-01-29 19:59:21:INFO: ipcp=IPCP pool
dyn_pool=[10.0.0.2/31,10.0.0.4/30,10.0.0.8/29,10.0.0.16/28,10.0.0.32/27,10.0.0.64/26,10.0.0.128/26,10.0.0.192/27,10.0.0.224/28,10.0.0.240/29,10.0.0.248/30,10.0.0.252/31,10.0.0.254/32]
pool=[10.0.0.2/31,10.0.0.4/30,10.0.0.8/29,10.0.0.16/28,10.0.0.32/27,10.0.0.64/26,10.0.0.128/26,10.0.0.192/27,10.0.0.224/28,10.0.0.240/29,10.0.0.248/30,10.0.0.252/31,10.0.0.254/32]
2013-01-29 19:59:21:INFO: Added 13 routes for new pool addresses
2013-01-29 19:59:21:INFO: Loading pool config successfully.
2013-01-29 19:59:21:INFO: l2tpd Listening 0.0.0.0:1701/udp (L2TP LNS)
[L2TP_ipv4]
2013-01-29 19:59:21:INFO: l2tpd Listening [::]:1701/udp (L2TP LNS) [L2TP_ipv6]
Config:
authentication LOCAL type local {
users-file "/etc/npppd/npppd-users"
}
tunnel L2TP_ipv4 protocol l2tp {
listen on 0.0.0.0
}
tunnel L2TP_ipv6 protocol l2tp {
listen on ::
}
ipcp IPCP {
pool-address 10.0.0.2-10.0.0.254
dns-servers 8.8.8.8
}
# use tun(4) interface. multiple ppp sessions concentrate one interface.
interface tun0 address 10.0.0.1 ipcp IPCP
bind tunnel from L2TP_ipv4 authenticated by LOCAL to tun0
bind tunnel from L2TP_ipv6 authenticated by LOCAL to tun0
Dmesg:
OpenBSD 5.2-current (GENERIC) #19: Mon Jan 21 17:55:18 MST 2013
t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD"
586-class) 499 MHz
cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW
real mem = 267976704 (255MB)
avail mem = 252608512 (240MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 11/05/08, BIOS32 rev. 0 @ 0xfd088
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: pcibios_get_intr_routing - function not supported
pcibios0: PCI IRQ Routing information unavailable.
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xe/0xa800
cpu0 at mainbus0: (uniprocessor)
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 1 function 0 "AMD Geode LX" rev 0x33
glxsb0 at pci0 dev 1 function 2 "AMD Geode LX Crypto" rev 0x00: RNG AES
vr0 at pci0 dev 9 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 10,
address 00:0d:b9:16:5e:e0
ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
0x004063, model 0x0034
vr1 at pci0 dev 10 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 11,
address 00:0d:b9:16:5e:e1
ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
0x004063, model 0x0034
vr2 at pci0 dev 11 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 15,
address 00:0d:b9:16:5e:e2
ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
0x004063, model 0x0034
athn0 at pci0 dev 12 function 0 "Atheros AR5416" rev 0x01: irq 9
athn0: MAC AR5416 rev 2, RF AR2133 (3T2R), ROM rev 5, address 00:21:27:cb:7a:36
glxpcib0 at pci0 dev 15 function 0 "AMD CS5536 ISA" rev 0x03: rev 3,
32-bit 3579545Hz timer, watchdog, gpio, i2c
gpio0 at glxpcib0: 32 pins
iic0 at glxpcib0
maxtmp0 at iic0 addr 0x4c: lm86
pciide0 at pci0 dev 15 function 2 "AMD CS5536 IDE" rev 0x01: DMA,
channel 0 wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 1-sector PIO, LBA, 3831MB, 7847280 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
pciide0: channel 1 ignored (disabled)
ohci0 at pci0 dev 15 function 4 "AMD CS5536 USB" rev 0x02: irq 12,
version 1.0, legacy support
ehci0 at pci0 dev 15 function 5 "AMD CS5536 USB" rev 0x02: irq 12
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "AMD EHCI root hub" rev 2.00/1.00 addr 1
isa0 at glxpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
usb1 at ohci0: USB revision 1.0
uhub1 at usb1 "AMD OHCI root hub" rev 1.00/1.00 addr 1
mtrr: K6-family MTRR support (2 registers)
nvram: invalid checksum
vscsi0 at root
scsibus0 at vscsi0: 256 targets
softraid0 at root
scsibus1 at softraid0: 256 targets
root on wd0a (86722b7d28b15b50.a) swap on wd0b dump on wd0b
clock: unknown CMOS layout
thx
csszep
Re: add a daemon user
Le 2013-01-29 21:40, jca+o...@wxcvbn.org a écrit : "Wesley M.A." writes: Hi, Hi To add a "daemon user" like for example _nginx : useradd -L daemon -d /var/empty -s /sbin/nologin -g =uid _nginx Is this enough ? [...] Depends. Your _nginx user will likely serve files, you don't want to put them in /var/empty, which is where other daemons chroot. Do you want to chroot? Why not use the www user? Why not use the devel nginx package, if you need a more recent version? I want to make work mailserv (ie mailserv.github.com) on OpenBSD-5.2 When i install it, _nginx was not created. It is why my question. Thank you. -- Wesley
Re: add a daemon user
"Wesley M.A." writes: > Hi, Hi > To add a "daemon user" like for example _nginx : > > useradd -L daemon -d /var/empty -s /sbin/nologin -g =uid _nginx > > Is this enough ? [...] Depends. Your _nginx user will likely serve files, you don't want to put them in /var/empty, which is where other daemons chroot. Do you want to chroot? Why not use the www user? Why not use the devel nginx package, if you need a more recent version? -- Jérémie Courrèges-Anglas GPG Key Fingerprint: 61DB D9A0 00A4 67CF 2A90 8961 6191 8FBF 06A1 1494
add a daemon user
Hi, To add a "daemon user" like for example _nginx : useradd -L daemon -d /var/empty -s /sbin/nologin -g =uid _nginx Is this enough ? Thank you very much. Cheers, Wesley
Re: firefox crashes
On Mon, 28 Jan 2013 21:32:59 +0100 Eric Huiban wrote: > On 01/28/13 13:43, Ed Ahlsen-Girard wrote: > > On Fri, 25 Jan 2013 01:55:35 +0100 > > Eric Huiban wrote: > > > >> On 01/23/13 01:43, Salil Wadnerkar wrote: > >>> Hi, > >>> > >>> On my amd64 machine, firefox crashes regularly after some time. > >>> > >>> [...] > >>> > >>> $ uname -a > >>> OpenBSD passport.my.domain 5.2 GENERIC.MP#17 amd64 > >>> > >>> I am on OpenBSD current and I have my system and packages updated > >>> just yesterday. > >>> > >>> Thanks > >>> Salil > >>> > >>> > >> > >> Your firefox does not crash by itself. It is wiped out by the > >> system when the process size reaches the maximum memory size you > >> allowed to be requested by your user. > >> > >> Already seen with 5.1, 5.2 and if what i'm remembering is correct > >> 5.0. (No change made on any binaries). Memory size can increase a > >> lot when using a lot of tabs at the same time, or after loading > >> pages overloaded with crappy scripts for advertisement display. > >> All this modulates the delay before firefox relaunch... > >> > >> Sorry for my poor english wording. Not my native language. > >> > > > > Perhaps this is related, perhaps not, but my firefox issue is that > > the system becomes unresponsive as more tabs/certain pages (ads, > > videos) are opened. Completely unresponsive: can't ssh in over the > > network (I'd try serial but I can't find my cable). dmesg below. > > Time to try Chrome? > > > > I observed the same behaviour. I have to wait a little bit for the > "application killing" by the system, or just have to press quietly > two times the "close" button on the window upper "bar" : then the > window manager proposes me to close the unresponsive application. > I waited overnight, and it made no difference. The system does not respond to either the mouse or the keyboard. -- Edward Ahlsen-Girard Ft Walton Beach, FL
Re: hi OpenBSD
Robert Kopp wrote: > almost cannot believe it..what do you think [url snipped] > > Robert Url shorteners are bad
Re: getting apps en masse
On Mon, Jan 28, 2013 at 12:33 AM, John Newton wrote: > Sirs: Especially Dewey and Jorge.I should have stated at the outset that I > must download from public computer not using openbsd so wget would > not work. I must work with the constraints of the mirror and my windows > system. BTW this is version 5.1 i am using. Maybe osdisc.com has app > repository for 5.1 but they don't say so explicitly on their site. To Jorge > especially: no, most of the apps are not on the install set. They take up > about 16 GB. Thanks to all > You can have some terminal fun (and in same time downloading in terminal) even in Windows like http://teusje.wordpress.com/2011/02/19/download-file-with-powershell/
Re: Emacs on OpenBSD for DEC VAX?
On Sat, Jan 26, 2013 at 4:58 PM, futzen wrote: > I have managed to install OpenBSD 5.2 on my DEC VaxStation 4000 Model 90 but > to my surprise have not found a binary for Emacs (any version) for the VAX > architecture. As best as I can tell I do not see it in the ports collection > either. > How about http://www.openbsd.org/cgi-bin/man.cgi?query=mg&apropos=0&sektion=0&manpath=OpenBSD+Current&arch=vax&format=html as "replacement"? > Has anybody succeeded in installing any version of Emacs (or for that matter > Zile) on the VAX architecture? Note that the VAX architecture distribution of > OpenBSD uses a modified version of GCC 2.9.5 as it's compiler. > > Thanks. > > Sincerely, > > Hany.
Re: openBSD 5.2 amd64 on lenovo x201s, part 2 apm support and overheating
2013/1/29 Andriy Samsonyuk : > Hi, > > is apm/apmd the only wat to change the fan speen? > > The fan speen never goes above: > hw.sensors.acpithinkpad0.fan0=4527 RPM > +- few RPMs > > if i set apmd -C or -A the laptop powers off after a while > without any warnings. > > with apm -L or -H its running, but getting hotter. > > Any suggestions/ideas? David Coppa already sent you a patch but probably I should clarify some things more. Many modern ThinkPad allow to either delegate management of fan speed to BIOS or to set it manually. OpenBSD point of view is that manual setting fans from userland is a BAD idea. So what's the patch mentioned does is taking management from BIOS to OS. BIOS does a good thing at managing fan speed until it gets too hot. But when overheating happens, there are two complimentary ways to handle the situation: a) raise the fan speed; b) lower CPU speed. (a) is what OpenBSD with the patch mentioned starts to do. The fan is put in so called "disengaged" mode, fan goes to 6000+ RPM and became spinning as if it's trying to make your laptop flying. This probably could damage the fan, but mine is still there for about two years. The same functionality exists in the Linux kernel but the code is (was? Didn't check for a year) disabled; I've actually picked up register addresses from there. (b) is what Windows does. Your videoplayer will start dropping frames but it'll be more or less quiet around. Probably some overheating logic could be added to apmd(8), but this daemon already wants too many options and thus probably needs refactoring. Or there could be some default scripts for sensorsd(8) written... -- WBR, Vadim Zhukov
Re: openBSD 5.2 amd64 on lenovo x201s, part 2 apm support and overheating
Thanx for your replys. Cleaning the fan and heat sink helped a bit, but not much (i cleaned it not so long ago). Running with the lower CPU freq. helps too. But neither of those solve the problem. Apparently the max fan speed is 7000 RPM and it would be nice if it could be used in the case of extremely high CPU load. i hope to try the patches soon, but it would be nice to have those features in the stable release Regards, Andriy [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: openBSD 5.2 amd64 on lenovo x201s, part 2 apm support and overheating
On Tue, Jan 29, 2013 at 12:07:10PM +0100, Stefan Sperling wrote: > [...] > Try sucking dust out of the heat vent with a hoover. > That helped me once with a thinkpad that kept shutting down itself > due to overheating. > [...] FWIW, I'd unplug the fan before doing that. The suction from the vaccum causes the fan to rotate, and in turn generate (a small amount of) power. That power is fed into the fan controller where the controller expects power to go _towards_ the fan instead of coming in, maybe damaging the controller. I don't know whether that's still an issue with modern Thinkpads but better safe than sorry. -- Gregor Best
Re: Could this be a faulty NIC?
Same thing. Argh. Nothing in the 5.2 or -current changelog to suggest
anything that would improve the situation. Might give it a go anyway.
On Tue, Jan 29, 2013 at 9:52 PM, Aaron Mason wrote:
> Ok, tried the Ralink card in a Toshiba Satellite M50, and still getting
> the same problem. I'll give the DCMA-81 a go, see where it goes. If it
> falls flat... maybe the Realtek NIC is a battle best not fought.
>
>
> On Mon, Jan 28, 2013 at 11:11 PM, Aaron Mason
> wrote:
>
>> Ok, I've replaced the Ralink card with a Wistron Neweb DCMA-81, an
>> Atheros-basec wireless NIC:
>>
>> ath0 at pci1 dev 6 function 0 "Atheros AR5413" rev 0x01: irq 11
>> ath0: AR5413 10.5 phy 6.1 rf 6.3, WOR0W, address c0:ff:ee:de:ca:f1
>>
>> I'm still having the same issue, however it now doesn't trigger an
>> interrupt storm. I have another system I can try; I'll give that a run
>> tomorrow evening.
>>
>>
>> On Thu, Jan 24, 2013 at 9:55 PM, Aaron Mason
>> wrote:
>>
>>> Ok, I fired up a connection both to the wireless and wired IPs, then ran
>>> du / continually. The interrupts on rl0 didn't register, but the
>>> interrupts on ral0 skyrocketed.
>>>
>>>
>>> On Thu, Jan 24, 2013 at 1:21 AM, Tomas Bodzar wrote:
>>>
On Wed, Jan 23, 2013 at 12:43 PM, Aaron Mason <
simplersolut...@gmail.com> wrote:
> HI all
>
> Got an old HP Compaq NX9040 laptop that I've repurposed as a wireless
> client router running OpenBSD 5.1. I've installed a Ralink RT2560
wireless
> card I salvaged from a broken D-Link print server. The wireless has
IP
> address 192.168.2.251, and the NIC has IP 172.16.1.254.
>
> My problem is if I connect to anything on the 172.16.1/24 network,
even the
> router's NIC address, it drops out after a few minutes. If I connect
to
> the wireless IP, it's rock solid.
>
> The onboard network card is a shitty Realtek 8139 card you find on
most
> laptops. Could it just be that the onboard NIC's gone to the dogs, or
> could there be more at play here? I don't see any errors appear in
dmesg
> when the dropout occurs.
>
Try to look with netstat -i, netstat -s for interface or protocol
errors. With vmstat -i or default screen of systat if there's not some
interrupt storm.
> Full dmesg:
>
> OpenBSD 5.1 (GENERIC) #160: Sun Feb 12 09:46:33 MST 2012
> dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Intel(R) Celeron(R) M processor 1400MHz ("GenuineIntel"
> 686-class) 1.40 GHz
> cpu0:
FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,TM,SBF
> real mem = 233238528 (222MB)
> avail mem = 219344896 (209MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 07/07/04, BIOS32 rev. 0 @
> 0xfd740, SMBIOS rev. 2.31 @ 0xdf010 (28 entries)
> bios0: vendor Hewlett-Packard version "BF.04M1" date 07/07/2004
> bios0: Hewlett-Packard
>
\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?
> apm0 at bios0: Power Management spec V1.2
> acpi at bios0 function 0x0 not configured
> pcibios0 at bios0: rev 2.1 @ 0xfd740/0x8c0
> pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf20/192 (10 entries)
> pcibios0: PCI Interrupt Router at 000:31:0 ("Intel 82371FB ISA" rev
0x00)
> pcibios0: PCI bus #3 is the last bus
> bios0: ROM list: 0xc/0xcc00! 0xcd000/0x1000 0xdf000/0x1000!
0xe/0x4000!
> cpu0 at mainbus0: (uniprocessor)
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> mem address conflict 0xdf0/0x400
> pchb0 at pci0 dev 0 function 0 "Intel 82855GM Host" rev 0x02
> "Intel 82855GM Memory" rev 0x02 at pci0 dev 0 function 1 not
configured
> "Intel 82855GM Config" rev 0x02 at pci0 dev 0 function 3 not
configured
> vga1 at pci0 dev 2 function 0 "Intel 82855GM Video" rev 0x02
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> intagp0 at vga1
> agp0 at intagp0: aperture at 0xe800, size 0x800
> inteldrm0 at vga1: irq 10
> drm0 at inteldrm0
> "Intel 82855GM Video" rev 0x02 at pci0 dev 2 function 1 not configured
> uhci0 at pci0 dev 29 function 0 "Intel 82801DB USB" rev 0x03: irq 10
> uhci1 at pci0 dev 29 function 1 "Intel 82801DB USB" rev 0x03: irq 11
> uhci2 at pci0 dev 29 function 2 "Intel 82801DB USB" rev 0x03: couldn't
> map interrupt
> ehci0 at pci0 dev 29 function 7 "Intel 82801DB USB" rev 0x03: irq 11
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
> ppb0 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0x83
> pci1 at ppb0 bus 1
> mem address conflict 0xdf01000/0x1000
> mem address confli
Re: openBSD 5.2 amd64 on lenovo x201s, part 2 apm support and overheating
On Tue, 29 Jan 2013, David Coppa wrote:
> On Tue, Jan 29, 2013 at 11:17 AM, Andriy Samsonyuk
> wrote:
> > Hi,
> >
> > is apm/apmd the only wat to change the fan speen?
> >
> > The fan speen never goes above:
> > hw.sensors.acpithinkpad0.fan0=4527 RPM
> > +- few RPMs
> >
> > if i set apmd -C or -A the laptop powers off after a while
> > without any warnings.
> >
> > with apm -L or -H its running, but getting hotter.
> >
> > Any suggestions/ideas?
>
> Try this patch by zhuk@:
>
> http://marc.info/?l=openbsd-tech&m=135645173413550
Attached to this mail, at your convenience...
Ciao,
David
Index: acpithinkpad.c
===
RCS file: /cvs/src/sys/dev/acpi/acpithinkpad.c,v
retrieving revision 1.28
diff -u -p -r1.28 acpithinkpad.c
--- acpithinkpad.c 6 Jun 2011 06:13:46 - 1.28
+++ acpithinkpad.c 25 Dec 2012 15:19:25 -
@@ -76,11 +76,25 @@
#defineTHINKPAD_POWER_CHANGED 0x6030
#defineTHINKPAD_SWITCH_WIRELESS0x7000
-#define THINKPAD_NSENSORS 9
-#define THINKPAD_NTEMPSENSORS 8
+#define THINKPAD_NSENSORS 10
+#define THINKPAD_NTEMPSENSORS 8
+
+#define THINKPAD_SENSOR_FANRPM (THINKPAD_NTEMPSENSORS + 0)
+#define THINKPAD_SENSOR_FANMODE(THINKPAD_NTEMPSENSORS + 1)
#define THINKPAD_ECOFFSET_FANLO0x84
#define THINKPAD_ECOFFSET_FANHI0x85
+#define THINKPAD_ECOFFSET_FANMODE 0x2f
+
+/* not used: #define THINKPAD_FANMODE_MIN 0x00 */
+#define THINKPAD_FANMODE_MAX 0x07
+#define THINKPAD_FANMODE_AUTO 0x80
+#define THINKPAD_FANMODE_DISENGAGED0x40
+#define THINKPAD_FANMODE_FORCEMAX (THINKPAD_FANMODE_MAX |
THINKPAD_FANMODE_DISENGAGED)
+
+/* critical temperature marks, in Celsius */
+#define THINKPAD_TEMP_OUCH_HMARK 80
+#define THINKPAD_TEMP_OUCH_LMARK 70
struct acpithinkpad_softc {
struct devicesc_dev;
@@ -90,7 +104,10 @@ struct acpithinkpad_softc {
struct aml_node *sc_devnode;
struct ksensor sc_sens[THINKPAD_NSENSORS];
+#define sc_sensfanmode sc_sens[THINKPAD_SENSOR_FANMODE]
struct ksensordevsc_sensdev;
+
+ u_int8_t sc_fanmodeinit;
};
extern void acpiec_read(struct acpiec_softc *, u_int8_t, int, u_int8_t *);
@@ -108,7 +125,7 @@ int thinkpad_volume_mute(struct acpithin
intthinkpad_brightness_up(struct acpithinkpad_softc *);
intthinkpad_brightness_down(struct acpithinkpad_softc *);
-voidthinkpad_sensor_attach(struct acpithinkpad_softc *sc);
+voidthinkpad_sensor_attach(struct acpithinkpad_softc *);
voidthinkpad_sensor_refresh(void *);
#if NAUDIO > 0 && NWSKBD > 0
@@ -165,8 +182,14 @@ thinkpad_sensor_attach(struct acpithinkp
}
/* Add fan probe */
- sc->sc_sens[i].type = SENSOR_FANRPM;
- sensor_attach(&sc->sc_sensdev, &sc->sc_sens[i]);
+ sc->sc_sens[THINKPAD_SENSOR_FANRPM].type = SENSOR_FANRPM;
+ sensor_attach(&sc->sc_sensdev, &sc->sc_sens[THINKPAD_SENSOR_FANRPM]);
+
+ /* Add fan mode indicator */
+ sc->sc_sens[THINKPAD_SENSOR_FANMODE].type = SENSOR_INTEGER;
+ sensor_attach(&sc->sc_sensdev, &sc->sc_sens[THINKPAD_SENSOR_FANMODE]);
+ acpiec_read(sc->sc_ec, THINKPAD_ECOFFSET_FANMODE, 1,
+ &sc->sc_fanmodeinit);
sensordev_install(&sc->sc_sensdev);
}
@@ -176,8 +199,10 @@ thinkpad_sensor_refresh(void *arg)
{
struct acpithinkpad_softc *sc = arg;
u_int8_t lo, hi, i;
- int64_t tmp;
+ int64_t tmp, maxtmp = -127;/* minimal correct value, see below */
+ int updatemode = 0;/* should we bother BIOS? */
char sname[5];
+ const char *desc;
/* Refresh sensor readings */
for (i=0; isc_acpi, sc->sc_ec->sc_devnode,
sname, 0, 0, &tmp);
sc->sc_sens[i].value = (tmp * 100) + 27315;
- if (tmp > 127 || tmp < -127)
+ if (tmp > 127 || tmp < -127) {
sc->sc_sens[i].flags = SENSOR_FINVALID;
+ sc->sc_sens[i].status = SENSOR_S_UNKNOWN;
+ }
+ if ((sc->sc_sens[i].flags & SENSOR_FINVALID) == SENSOR_FINVALID)
+ continue;
+ if (tmp > maxtmp)
+ maxtmp = tmp;
+ if (tmp > THINKPAD_TEMP_OUCH_HMARK)
+ sc->sc_sens[i].status = SENSOR_S_CRIT;
+ else if (tmp > THINKPAD_TEMP_OUCH_LMARK)
+ sc->sc_sens[i].status = SENSOR_S_WARN;
+ else
+ sc->sc_sens[i].status = SENSOR_S_OK;
}
/* Read fan RPM */
acpiec_read(sc->sc_ec, THINKPAD_ECOFFSET_FANLO, 1, &lo);
acpiec_read(sc->sc_ec, THINKPAD_ECOFFSET_FANHI, 1, &hi);
- sc->sc_sens[i].value = ((hi << 8L) + lo);
+ sc->sc_sens[THINKPAD_SENSOR_FANRPM].value = ((hi << 8L) + lo)
Re: openBSD 5.2 amd64 on lenovo x201s, part 2 apm support and overheating
On Tue, Jan 29, 2013 at 11:17:10AM +0100, Andriy Samsonyuk wrote: > Hi, > > is apm/apmd the only wat to change the fan speen? > > The fan speen never goes above: > hw.sensors.acpithinkpad0.fan0=4527 RPM > +- few RPMs > > if i set apmd -C or -A the laptop powers off after a while > without any warnings. > > with apm -L or -H its running, but getting hotter. > > Any suggestions/ideas? Try sucking dust out of the heat vent with a hoover. That helped me once with a thinkpad that kept shutting down itself due to overheating. If you really want fan control and would be willing to patch the kernel for it, see here for several patches to manually control the fan on thinkpads: http://marc.info/?t=12910412174&r=1&w=2 None of these were ever committed AFAIK. I don't know if they still apply to -current.
Re: openBSD 5.2 amd64 on lenovo x201s, part 2 apm support and overheating
On 01/29/13 21:17, Andriy Samsonyuk wrote: Hi, is apm/apmd the only wat to change the fan speen? The fan speen never goes above: hw.sensors.acpithinkpad0.fan0=4527 RPM +- few RPMs if i set apmd -C or -A the laptop powers off after a while without any warnings. with apm -L or -H its running, but getting hotter. Any suggestions/ideas? You can use "sysctl hw.setperf" to permanently set the cpu to run at a lower speed. On a laptop I used to have, sysctl hw.setperf=0 ran the cpu at 800mhz. This did not have much of a noticable effect on performance, unless I was trying to do some heavy compiling or such. Your bios settings may also have an option to change the fan speed.
Re: openBSD 5.2 amd64 on lenovo x201s, part 2 apm support and overheating
On Tue, Jan 29, 2013 at 11:17 AM, Andriy Samsonyuk wrote: > Hi, > > is apm/apmd the only wat to change the fan speen? > > The fan speen never goes above: > hw.sensors.acpithinkpad0.fan0=4527 RPM > +- few RPMs > > if i set apmd -C or -A the laptop powers off after a while > without any warnings. > > with apm -L or -H its running, but getting hotter. > > Any suggestions/ideas? Try this patch by zhuk@: http://marc.info/?l=openbsd-tech&m=135645173413550 Ciao, David
Re: Could this be a faulty NIC?
Ok, tried the Ralink card in a Toshiba Satellite M50, and still getting the
same problem. I'll give the DCMA-81 a go, see where it goes. If it falls
flat... maybe the Realtek NIC is a battle best not fought.
On Mon, Jan 28, 2013 at 11:11 PM, Aaron Mason wrote:
> Ok, I've replaced the Ralink card with a Wistron Neweb DCMA-81, an
> Atheros-basec wireless NIC:
>
> ath0 at pci1 dev 6 function 0 "Atheros AR5413" rev 0x01: irq 11
> ath0: AR5413 10.5 phy 6.1 rf 6.3, WOR0W, address c0:ff:ee:de:ca:f1
>
> I'm still having the same issue, however it now doesn't trigger an
> interrupt storm. I have another system I can try; I'll give that a run
> tomorrow evening.
>
>
> On Thu, Jan 24, 2013 at 9:55 PM, Aaron Mason wrote:
>
>> Ok, I fired up a connection both to the wireless and wired IPs, then ran
>> du / continually. The interrupts on rl0 didn't register, but the
>> interrupts on ral0 skyrocketed.
>>
>>
>> On Thu, Jan 24, 2013 at 1:21 AM, Tomas Bodzar wrote:
>>
>>> On Wed, Jan 23, 2013 at 12:43 PM, Aaron Mason
>>> wrote:
>>> > HI all
>>> >
>>> > Got an old HP Compaq NX9040 laptop that I've repurposed as a wireless
>>> > client router running OpenBSD 5.1. I've installed a Ralink RT2560
>>> wireless
>>> > card I salvaged from a broken D-Link print server. The wireless has IP
>>> > address 192.168.2.251, and the NIC has IP 172.16.1.254.
>>> >
>>> > My problem is if I connect to anything on the 172.16.1/24 network,
>>> even the
>>> > router's NIC address, it drops out after a few minutes. If I connect
>>> to
>>> > the wireless IP, it's rock solid.
>>> >
>>> > The onboard network card is a shitty Realtek 8139 card you find on most
>>> > laptops. Could it just be that the onboard NIC's gone to the dogs, or
>>> > could there be more at play here? I don't see any errors appear in
>>> dmesg
>>> > when the dropout occurs.
>>> >
>>>
>>> Try to look with netstat -i, netstat -s for interface or protocol
>>> errors. With vmstat -i or default screen of systat if there's not some
>>> interrupt storm.
>>>
>>> > Full dmesg:
>>> >
>>> > OpenBSD 5.1 (GENERIC) #160: Sun Feb 12 09:46:33 MST 2012
>>> > dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
>>> > cpu0: Intel(R) Celeron(R) M processor 1400MHz ("GenuineIntel"
>>> > 686-class) 1.40 GHz
>>> > cpu0:
>>> FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,TM,SBF
>>> > real mem = 233238528 (222MB)
>>> > avail mem = 219344896 (209MB)
>>> > mainbus0 at root
>>> > bios0 at mainbus0: AT/286+ BIOS, date 07/07/04, BIOS32 rev. 0 @
>>> > 0xfd740, SMBIOS rev. 2.31 @ 0xdf010 (28 entries)
>>> > bios0: vendor Hewlett-Packard version "BF.04M1" date 07/07/2004
>>> > bios0: Hewlett-Packard
>>> >
>>> \M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?
>>> > apm0 at bios0: Power Management spec V1.2
>>> > acpi at bios0 function 0x0 not configured
>>> > pcibios0 at bios0: rev 2.1 @ 0xfd740/0x8c0
>>> > pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf20/192 (10 entries)
>>> > pcibios0: PCI Interrupt Router at 000:31:0 ("Intel 82371FB ISA" rev
>>> 0x00)
>>> > pcibios0: PCI bus #3 is the last bus
>>> > bios0: ROM list: 0xc/0xcc00! 0xcd000/0x1000 0xdf000/0x1000!
>>> 0xe/0x4000!
>>> > cpu0 at mainbus0: (uniprocessor)
>>> > pci0 at mainbus0 bus 0: configuration mode 1 (bios)
>>> > mem address conflict 0xdf0/0x400
>>> > pchb0 at pci0 dev 0 function 0 "Intel 82855GM Host" rev 0x02
>>> > "Intel 82855GM Memory" rev 0x02 at pci0 dev 0 function 1 not configured
>>> > "Intel 82855GM Config" rev 0x02 at pci0 dev 0 function 3 not configured
>>> > vga1 at pci0 dev 2 function 0 "Intel 82855GM Video" rev 0x02
>>> > wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
>>> > wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
>>> > intagp0 at vga1
>>> > agp0 at intagp0: aperture at 0xe800, size 0x800
>>> > inteldrm0 at vga1: irq 10
>>> > drm0 at inteldrm0
>>> > "Intel 82855GM Video" rev 0x02 at pci0 dev 2 function 1 not configured
>>> > uhci0 at pci0 dev 29 function 0 "Intel 82801DB USB" rev 0x03: irq 10
>>> > uhci1 at pci0 dev 29 function 1 "Intel 82801DB USB" rev 0x03: irq 11
>>> > uhci2 at pci0 dev 29 function 2 "Intel 82801DB USB" rev 0x03: couldn't
>>> > map interrupt
>>> > ehci0 at pci0 dev 29 function 7 "Intel 82801DB USB" rev 0x03: irq 11
>>> > usb0 at ehci0: USB revision 2.0
>>> > uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
>>> > ppb0 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0x83
>>> > pci1 at ppb0 bus 1
>>> > mem address conflict 0xdf01000/0x1000
>>> > mem address conflict 0xdf02000/0x1000
>>> > rl0 at pci1 dev 0 function 0 "Realtek 8139" rev 0x10: irq 10, address
>>> > 00:c0:9f:57:68:77
>>> > rlphy0 at rl0 phy 0: RTL internal PHY
>>> > cbb0 at pci1 dev 1 function 0 "TI PCI1520 CardBus" rev 0x01: couldn't
>>> > map interrupt
>>> > cbb1 at pci1 dev 1 function 1 "TI PCI1520 CardBus" rev 0x01: couldn't
>>> > map interrupt
>>> >
Re: OpenBSD/iwn(4) support for WPA2/PEAP/MSCHAPv2?
Big thanks to Mark Kettenis. I tested it and it works.
openBSD 5.2 amd64 on lenovo x201s, part 2 apm support and overheating
Hi, is apm/apmd the only wat to change the fan speen? The fan speen never goes above: hw.sensors.acpithinkpad0.fan0=4527 RPM +- few RPMs if i set apmd -C or -A the laptop powers off after a while without any warnings. with apm -L or -H its running, but getting hotter. Any suggestions/ideas? Kind regards, Andriy sysctl hw.sensors hw.sensors.cpu0.temp0=68.00 degC hw.sensors.cpu1.temp0=68.00 degC hw.sensors.cpu2.temp0=68.00 degC hw.sensors.cpu3.temp0=68.00 degC hw.sensors.acpitz0.temp0=77.00 degC (zone temperature) hw.sensors.acpibat0.volt0=14.40 VDC (voltage) hw.sensors.acpibat0.volt1=16.62 VDC (current voltage) hw.sensors.acpibat0.current0=0.00 A (rate) hw.sensors.acpibat0.amphour0=2.02 Ah (last full capacity) hw.sensors.acpibat0.amphour1=0.10 Ah (warning capacity) hw.sensors.acpibat0.amphour2=0.01 Ah (low capacity) hw.sensors.acpibat0.amphour3=2.02 Ah (remaining capacity), OK hw.sensors.acpibat0.raw0=0 (battery full), OK hw.sensors.acpiac0.indicator0=On (power supply) hw.sensors.acpithinkpad0.temp0=77.00 degC hw.sensors.acpithinkpad0.temp1=77.00 degC hw.sensors.acpithinkpad0.temp2=77.00 degC hw.sensors.acpithinkpad0.temp3=77.00 degC hw.sensors.acpithinkpad0.temp4=77.00 degC hw.sensors.acpithinkpad0.temp5=77.00 degC hw.sensors.acpithinkpad0.temp6=77.00 degC hw.sensors.acpithinkpad0.temp7=77.00 degC hw.sensors.acpithinkpad0.fan0=4527 RPM hw.sensors.acpidock0.indicator0=Off (not docked) hw.sensors.itherm0.temp0=0.00 degC (Thermometer) hw.sensors.itherm0.temp1=74.04 degC (Core 1) hw.sensors.itherm0.temp4=77.00 degC (CPU/GPU Max temp) hw.sensors.itherm0.temp9=77.00 degC (GPU/Memory controller abs.) hw.sensors.itherm0.temp10=72.00 degC (PCH abs.) hw.sensors.itherm0.power0=6.00 W (CPU power consumption) hw.sensors.aps0.temp0=37.00 degC hw.sensors.aps0.temp1=37.00 degC hw.sensors.aps0.indicator0=On (Keyboard Active) hw.sensors.aps0.indicator1=Off (Mouse Active) hw.sensors.aps0.indicator2=On (Lid Open) hw.sensors.aps0.raw0=492 (X_ACCEL) hw.sensors.aps0.raw1=475 (Y_ACCEL) hw.sensors.aps0.raw2=492 (X_VAR) hw.sensors.aps0.raw3=475 (Y_VAR) OpenBSD 5.2 (GENERIC.MP) #368: Wed Aug 1 10:04:49 MDT 2012 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4078419968 (3889MB) avail mem = 3947483136 (3764MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xe0010 (78 entries) bios0: vendor LENOVO version "6QET64WW (1.34 )" date 02/24/2011 bios0: LENOVO 5397FEG acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET ASF! SLIC BOOT SSDT TCPA DMAR SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) EXP5(S4) EHC1(S3) EHC2(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7 CPU L 640 @ 2.13GHz, 2128.41 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,ES T,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF cpu0: 256KB 64b/line 8-way L2 cache cpu0: apic clock running at 132MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i7 CPU L 640 @ 2.13GHz, 2128.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,ES T,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF cpu1: 256KB 64b/line 8-way L2 cache cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i7 CPU L 640 @ 2.13GHz, 2128.00 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,ES T,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF cpu2: 256KB 64b/line 8-way L2 cache cpu3 at mainbus0: apid 5 (application processor) cpu3: Intel(R) Core(TM) i7 CPU L 640 @ 2.13GHz, 2128.00 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,ES T,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF cpu3: 256KB 64b/line 8-way L2 cache ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG_) acpiprt2 at acpi0: bus 13 (EXP1) acpiprt3 at acpi0: bus -1 (EXP2) acpiprt4 at acpi0: bus -1 (EXP3) acpiprt5 at acpi0: bus -1 (EXP4) acpiprt6 at acpi0: bus 2 (EXP5) acpicpu0 at acpi0: C3, C1, PSS acpicpu1 at acpi0: C3, C1, PSS acpicpu2 at acpi0: C3, C1, PSS acpicpu3 at acpi0: C3, C1, PSS acpipwrres0 at acpi0: PUBS acpitz0 at acpi0: critical temperature is 100 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLP
Re: bug / misunderstanding in how pf interacts with dhclient
On Tue, Jan 29, 2013 at 4:28 AM, Bohdan Tashchuk wrote: > --- On Mon, 1/28/13, Andres Perera wrote: > >> more than that, really, why should you or anybody care >> >> using bpf or not should be an implementation detail. no one should >> be making decisions as far as their pf config goes based upon >> whether dhclient uses bpf or not > > Thanks for your comments on the source code. I briefly looked thru > /usr/src/sbin/dhclient, but there were 6289 lines of *.c code there. > I'm not that familiar with networking code so there was too much > for me to easily comprehend. in the future, you can use systrace to find out what fd programs are really writing to. it has saved me enormous amounts of time when troubleshooting, e.g., cvs slowness. familiarizing myself with cvs's code base would've undoubtedly been more expensive > > I agree that bpf is simply an implementation technique; I don't really care > *how* dhclient does what it does. But I want to understand the required pf > rules for two reasons: > > 1) there have been people who have said (e.g. in the thread I quoted): > >"Using DHCP is not possible, pf block it, and i don't understand why" > > Missing pf rules are one reason why dhcp would fail. Many people search > for similar problems years later; I don't want them to be confused as I was. > > 2) This is the important one for me. I want to be a "good Internet citizen". > So I try to write my pf rules to be as restrictive as possible. I want to > keep machines behind my firewall from being "bad Internet citizens". > Right now my outgoing UDP below port 1024 is restricted to ports domain, > kerberos, and ntp. I will add dhcp to that list. > > I know I'm being a little quixotic (or perhaps pedantic) here. If there's > a misbehaving machine behind my firewall, I don't think that restricting > its UDP ports is going to make a whole lot of difference to the Internet > at large. But I'm trying to do what I can. > as it stands, i would wait for an "official" recommendation before jumping to conclusions. i'm only pointing out the problem. it could be that routing these unicast messages is useful, which is why they aren't being written directly to the interface's output buffer via bpf, or it could very well be that someone is devising a patch to write them through bpf regardless because the routing isn't required... that's a problem area i'm not familiar with, but i would expect $router_network == $dhcpd_network in common configurations... and even if not, having them potentially route through different interfaces makes no friggen sense
Re: bug / misunderstanding in how pf interacts with dhclient
--- On Mon, 1/28/13, Andres Perera wrote: > more than that, really, why should you or anybody care > > using bpf or not should be an implementation detail. no one should > be making decisions as far as their pf config goes based upon > whether dhclient uses bpf or not Thanks for your comments on the source code. I briefly looked thru /usr/src/sbin/dhclient, but there were 6289 lines of *.c code there. I'm not that familiar with networking code so there was too much for me to easily comprehend. I agree that bpf is simply an implementation technique; I don't really care *how* dhclient does what it does. But I want to understand the required pf rules for two reasons: 1) there have been people who have said (e.g. in the thread I quoted): "Using DHCP is not possible, pf block it, and i don't understand why" Missing pf rules are one reason why dhcp would fail. Many people search for similar problems years later; I don't want them to be confused as I was. 2) This is the important one for me. I want to be a "good Internet citizen". So I try to write my pf rules to be as restrictive as possible. I want to keep machines behind my firewall from being "bad Internet citizens". Right now my outgoing UDP below port 1024 is restricted to ports domain, kerberos, and ntp. I will add dhcp to that list. I know I'm being a little quixotic (or perhaps pedantic) here. If there's a misbehaving machine behind my firewall, I don't think that restricting its UDP ports is going to make a whole lot of difference to the Internet at large. But I'm trying to do what I can.
Re: Athn0 won't link with new router!!
On 01/29/13 09:49, Alexander Hall wrote: On 01/23/13 00:55, slhactivist wrote: Hi there misc! I'm having trouble connecting to my router. Any help would be appreciated. I can get athn0 to "link", but then it sends a dozen DHCPREQUESTs, and then sends DHCPDISCOVERs until it sleeps... I've never had this problem before. Last time I switch routers, I just changed nwid, and wpakey with ifconfig, then ran dhclient for athn0 and it worked. This time i've tried setting chan, bssid, nwid, nwkey, wpakey, and wpaakms. I've et these parameters with ifconfig, and also entered into my /etc/hostname.athn0 file I've also tried entering (into the /etc/hostname.athn0 file) "dhcp" and "dhcp NONE NONE NONE" before any parameters. Usually, the anth0 won't link, just sleeps. But sometimes I can get it to send some DHCPREQUESTs and DHCPDISCOVERs before sleeping... >_< Um...I haven't changed much. Just edited the /etc/pf.conf file (just delete all blank lines and comments to make it smaller :P) and did whatever afterboot said, oh and also right at the end of /etc/netstart I added "ifconfig athn0 lladdr random" to randomize my MAC on each boot. Don't do that. If you really want it, just put "lladdr random" first in the hostname.athn0 file. Ooooh... did you put it *last* in netstart? Meaning you change MAC address *after* starting dhclient and friends? Sounds like a really bad idea to me. Sometimes I try running /etc/netstart athn0 instead of dhclient athn0. Oh, and also I edited /etc/dhclient.conf a little, just to make it try longer before going to sleep, but doesn't help. Anyone have any ideas??? I'm totally stuck! (reading RFC 2131 right now...) Here's my /etc/hostname.athn0 file: -wol group egress chan 11 bssid ** nwid ** nwkey ** wpakey ** wpaakms pks dhcp NONE NONE NONE And here is ifconfig athn0: athn0 flag=8843 mtu 1500 lladdr: ** priority: 4 groups: wlan egress media: IEEE802.11 autoselect (DS1 mode 11g) Status: no network And when I scan (sudo ifconfig athn0 scan) I get something like this (forgot to write down so from memory): ieee80211: nwid ** chan 11 bssid ** 3dB 54MB privacy, short_preamble, short_slottime wpakey wpaprotos wpa1, wpa2 wpakms psk wpaciphers tkip, ccmp wpagroupcipher tkip inet ** prefixlen 64 scopeid 0x1 Um...when I looked at the router (It's a D-LINK connected to a Telus DSL box) there is a sticky note on it that says "Wireless: NO DHCP"...but everyone else is using wireless internet... Also , when I scan for networks, not only does the network name appear, but so does a DLINK and a TELUS network. MAIN PROBLEM: Athn0 won't link...1/10 times it will it seems, after I fiddle with it... I have a feeling this is a simple config file problem, but I'm just not used to editing conf files. Am I going about this the right way? (i.e. editing /etc/dhclient.conf, pf.conf, /etc/hostname.athn0, /etc/myname, and running /etc/netstart, ifconfig, and dhclient?) You should likely only need to edit hostname.athn0 well, myname could be nice too. /Alexander
Re: Athn0 won't link with new router!!
On 01/29/13 08:13, slhac tivist wrote: Thank you. Your suggestions have helped. I gave up on DHCP., and can consistently get a link, but I can't even ping the router...here's some info: cat /etc/hostname.athn0: inet 192.168.1.101 255.255.255.0 255.255.255.255 nwid "THENAME" nwkey "THEPASSWORD" Are you really using WEP? which results in the following: sudo ifconfig athn0: athn0: flags=8843 mtu 1500 lladdr * priority: 4 groups: wlan egress media: IEEE802.11 autoselect (DS5 mode 11g) status: *active* #
Re: Athn0 won't link with new router!!
On 01/23/13 00:55, slhactivist wrote: Hi there misc! I'm having trouble connecting to my router. Any help would be appreciated. I can get athn0 to "link", but then it sends a dozen DHCPREQUESTs, and then sends DHCPDISCOVERs until it sleeps... I've never had this problem before. Last time I switch routers, I just changed nwid, and wpakey with ifconfig, then ran dhclient for athn0 and it worked. This time i've tried setting chan, bssid, nwid, nwkey, wpakey, and wpaakms. I've et these parameters with ifconfig, and also entered into my /etc/hostname.athn0 file I've also tried entering (into the /etc/hostname.athn0 file) "dhcp" and "dhcp NONE NONE NONE" before any parameters. Usually, the anth0 won't link, just sleeps. But sometimes I can get it to send some DHCPREQUESTs and DHCPDISCOVERs before sleeping... >_< Um...I haven't changed much. Just edited the /etc/pf.conf file (just delete all blank lines and comments to make it smaller :P) and did whatever afterboot said, oh and also right at the end of /etc/netstart I added "ifconfig athn0 lladdr random" to randomize my MAC on each boot. Don't do that. If you really want it, just put "lladdr random" first in the hostname.athn0 file. Ooooh... did you put it *last* in netstart? Meaning you change MAC address *after* starting dhclient and friends? Sounds like a really bad idea to me. Sometimes I try running /etc/netstart athn0 instead of dhclient athn0. Oh, and also I edited /etc/dhclient.conf a little, just to make it try longer before going to sleep, but doesn't help. Anyone have any ideas??? I'm totally stuck! (reading RFC 2131 right now...) Here's my /etc/hostname.athn0 file: -wol group egress chan 11 bssid ** nwid ** nwkey ** wpakey ** wpaakms pks dhcp NONE NONE NONE And here is ifconfig athn0: athn0 flag=8843 mtu 1500 lladdr: ** priority: 4 groups: wlan egress media: IEEE802.11 autoselect (DS1 mode 11g) Status: no network And when I scan (sudo ifconfig athn0 scan) I get something like this (forgot to write down so from memory): ieee80211: nwid ** chan 11 bssid ** 3dB 54MB privacy, short_preamble, short_slottime wpakey wpaprotos wpa1, wpa2 wpakms psk wpaciphers tkip, ccmp wpagroupcipher tkip inet ** prefixlen 64 scopeid 0x1 Um...when I looked at the router (It's a D-LINK connected to a Telus DSL box) there is a sticky note on it that says "Wireless: NO DHCP"...but everyone else is using wireless internet... Also , when I scan for networks, not only does the network name appear, but so does a DLINK and a TELUS network. MAIN PROBLEM: Athn0 won't link...1/10 times it will it seems, after I fiddle with it... I have a feeling this is a simple config file problem, but I'm just not used to editing conf files. Am I going about this the right way? (i.e. editing /etc/dhclient.conf, pf.conf, /etc/hostname.athn0, /etc/myname, and running /etc/netstart, ifconfig, and dhclient?) You should likely only need to edit hostname.athn0 /Alexander
