Re: Unbound in base, yes, what about ldns?
Thanks. 2014-03-20 1:44 GMT+02:00 Chris Smith obsd_m...@chrissmith.org: See the thread unbound dnssec revisited I started on 12/30/2013 for some hints. Looks like creating a new directory with the proper permissions is the best way to go. On Wed, Mar 19, 2014 at 7:01 PM, Àòàíàñ Âëàäèìèðîâ don.na...@gmail.com wrote: Hi, Sorry for Off-topic, but when you enable DNSSEC validation and fetch a root key with unbound-anchor(8) (needs root) the following error shows up in /var/log/messages: unbound: [0:0] error: could not open autotrust file for writing, /etc/root.key.29136-0: Permission denied May be this is because _unbound user has no rights to write to /var/unbound/etc/ after chroot. Am I correct? Any solutions? Best regards, Atanas
Re: PPTP after removing of userland ppp(8)
2014-03-20 1:15 GMT+02:00 Stefan Sperling s...@openbsd.org: ppp(8) used net/pptp as a pseudo-device via pipes to a pptp process. With pppd(8) I don't think there is support for using a pipe to a separate process as a device. Perhaps there is another way to make pptp work with pppd. I don't know. npppd supports PPTP but I believe it's currently server-side only. One possible path forward would be PPTP-client support in npppd. I don't know if there are any plans for this and I don't have any such plans myself. Yes, it's only server-side Even though I'm still listed as maintainer of net/pptp I haven't used it in a long time. If net/pptp goes away I won't miss it. From FAQ: PPTP The Point to Point Tunneling Protocol (PPTP) is a proprietary Microsoft protocol. A pptp client is available which interfaces with pppd(8)http://www.openbsd.org/cgi-bin/man.cgi?query=pppdsektion=8 and is capable of connecting to the PPTP-based Virtual Private Networks (VPN) used by some cable and xDSL providers. pptp itself must be installed from packages http://www.openbsd.org/faq/faq15.html#PkgMgmt or portshttp://www.openbsd.org/faq/faq15.html#Ports. Further instructions on setting up and using pptp are available in the man page which is installed with the pptp package. Is the following patch correct: --- faq6.html Mon Dec 2 09:06:04 2013 +++ faq6.html.new Thu Mar 20 10:35:38 2014 @@ -982,7 +982,7 @@ The Point to Point Tunneling Protocol (PPTP) is a proprietary Microsoft protocol. A pptp client is available which interfaces with -a href=http://www.openbsd.org/cgi-bin/man.cgi?query=pppdamp;sektion=8 pppd(8)/a +a href= http://www.openbsd.org/cgi-bin/man.cgi?query=pppamp;sektion=8amp;manpath=OpenBSD+5.4 ppp(8)/a and is capable of connecting to the PPTP-based Virtual Private Networks (VPN) used by some cable and xDSL providers. pptp itself must be installed from a href=faq15.html#PkgMgmtpackages/a
Re: npppd with two pppx interfaces causes kernel panic
On Thu, Mar 20, 2014 at 01:43:59PM +0900, YASUOKA Masahiko wrote: On Wed, 19 Mar 2014 21:05:35 -0700 Paul B. Henson hen...@acm.org wrote: On Thu, Mar 20, 2014 at 10:22:51AM +0900, YASUOKA Masahiko wrote: pppx will be fixed. Great :). This is a known bug then? It's new for me. I had not even try MAKEDEV pppx1 yet. The following diff prevents the panic here: Index: if_pppx.c === RCS file: /cvs/src/sys/net/if_pppx.c,v retrieving revision 1.26 diff -u -p -r1.26 if_pppx.c --- if_pppx.c 19 Oct 2013 14:46:30 - 1.26 +++ if_pppx.c 20 Mar 2014 10:21:04 - @@ -590,7 +590,8 @@ pppxclose(dev_t dev, int flags, int mode rw_enter_write(pppx_devs_lk); - pxd = pppx_dev_lookup(dev); + if ((pxd = pppx_dev_lookup(dev)) == NULL) + return (ENXIO); /* XXX */ while ((pxi = LIST_FIRST(pxd-pxd_pxis)))
Re: Trouble with connect to www.aeroflot.ru
On Wed, March 19, 2014 19:59, Mikkel C. Simonsen wrote: Marcus MERIGHI wrote: gimliandcomp...@gmail.com (Leonov Aleksey), 2014.03.19 (Wed) 16:18 (CET): On 19.03.2014 20:32, Marcus MERIGHI wrote: gimliandcomp...@gmail.com (Leonov Aleksey), 2014.03.19 (Wed) 15:07 (CET): I can`t connect to www.aeroflot.ru from lynx on openbsd 5.4. I can connect from gentoo, windows. Anybody can connect to wwe.aeroflot.ru from openbsd 5.4? OpenBSD 5.5-beta (GENERIC.MP) #284: Mon Feb 3 07:57:32 MST 2014 ftp -o aeroflot.html www.aeroflot.ru Trying 195.8.62.76... Connected to www.aeroflot.ru. 421 Service not available, remote server has closed connection. I try http, not ftp. http connect from openbsd to aeroflot.ru end Ooops on my side. I did not mean to test ftp but just use a different client (OpenBSD's ftp(1) handles http as well) and forgot the http://: ftp -o aeroflot.html http://www.aeroflot.ru Trying 195.8.62.75... Trying 195.8.62.76... ftp: connect: connection timed out It's not an OpenBSD/Lynx specific problem. I just tried connecting with SeaMonkey (on /2), and I get a time-out also. Works for me with ftp, mozilla and lynx under amd64 snapshot from february 24th . Best regards, Mikkel C. Simonsen
Re: Trouble with connect to www.aeroflot.ru
On Thu, March 20, 2014 17:03, Kirill Bychkov wrote: On Wed, March 19, 2014 19:59, Mikkel C. Simonsen wrote: Marcus MERIGHI wrote: gimliandcomp...@gmail.com (Leonov Aleksey), 2014.03.19 (Wed) 16:18 (CET): On 19.03.2014 20:32, Marcus MERIGHI wrote: gimliandcomp...@gmail.com (Leonov Aleksey), 2014.03.19 (Wed) 15:07 (CET): I can`t connect to www.aeroflot.ru from lynx on openbsd 5.4. I can connect from gentoo, windows. Anybody can connect to wwe.aeroflot.ru from openbsd 5.4? OpenBSD 5.5-beta (GENERIC.MP) #284: Mon Feb 3 07:57:32 MST 2014 ftp -o aeroflot.html www.aeroflot.ru Trying 195.8.62.76... Connected to www.aeroflot.ru. 421 Service not available, remote server has closed connection. I try http, not ftp. http connect from openbsd to aeroflot.ru end Ooops on my side. I did not mean to test ftp but just use a different client (OpenBSD's ftp(1) handles http as well) and forgot the http://: ftp -o aeroflot.html http://www.aeroflot.ru Trying 195.8.62.75... Trying 195.8.62.76... ftp: connect: connection timed out It's not an OpenBSD/Lynx specific problem. I just tried connecting with SeaMonkey (on /2), and I get a time-out also. Works for me with ftp, mozilla and lynx under amd64 snapshot from february 24th . Sorry, it works only via trasparent squid. Best regards, Mikkel C. Simonsen
Where is this device attached?
Hi, I am trying to use a USB device with a Loongson 5.3 stable box. The line from dmesg for the device is ugen0 at uhub1 port 3 HP Company HPx9G+ Device rev 1.10/1.00 addr 2 and the usbdevs -vd output is Controller /dev/usb0: addr 1: high speed, self powered, config 1, EHCI root hub(0x), AMD(0x1022), rev 1.00 uhub0 port 1 powered port 2 powered port 3 powered port 4 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, OHCI root hub(0x), AMD(0x1022), rev 1.00 uhub1 port 1 powered port 2 powered port 3 addr 2: full speed, power 50 mA, config 1, HPx9G+ Device(0x0121), HP Company(0x03f0), rev 1.00 ugen0 port 4 powered How do I correlate this info to a /dev filename so I can tell Kermit which line to open? Thanks, /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04
Re: Where is this device attached?
On Thu, Mar 20, 2014 at 2:31 PM, John Long codeb...@inbox.lv wrote: Hi, I am trying to use a USB device with a Loongson 5.3 stable box. The line from dmesg for the device is ugen0 at uhub1 port 3 HP Company HPx9G+ Device rev 1.10/1.00 addr 2 Is this a usb-to-serial thingie? If this is the case, then it's not properly recognized by the kernel. It should expose a ucom*, e.g.: ucom0 at uftdi0 portno 1
Re: Where is this device attached?
David- sorry, I meant to reply to the list, here it is again for public consumption with the topic threading borked, probably. On Thu, Mar 20, 2014 at 04:14:13PM +0100, David Coppa wrote: On Thu, Mar 20, 2014 at 2:31 PM, John Long codeb...@inbox.lv wrote: Hi, I am trying to use a USB device with a Loongson 5.3 stable box. The line from dmesg for the device is ugen0 at uhub1 port 3 HP Company HPx9G+ Device rev 1.10/1.00 addr 2 Is this a usb-to-serial thingie? I don't think so, but I don't know if it is a standard USB device either. It comes up as /dev/ttyUSB0 on that _other_ OS and will talk to Kermit but I can't get it working on OpenBSD yet. I would prefer to use it with the Loongson box if possible. If this is the case, then it's not properly recognized by the kernel. It should expose a ucom*, e.g.: ucom0 at uftdi0 portno 1 Any other ideas? Thanks, /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04
relayd crashing after header append added
Hi, I recently added a header append $REMOTE_ADDR to
X-Forwarded-For to my relayd.conf file and since adding that line the
relayd service has died a number of times.
I tried adding the no splice option and I think relayd stayed up for
longer but it died again last night. Relayd seesm to stay up for a
random about of time before stopping, from a few hours to a few days.
Does anyone know what might be causing this to happen and if there's a
workaround ?
Mar 19 19:14:15 NodeC relayd[23062]: hce exiting, pid 23062
Mar 19 19:14:15 NodeC relayd[12415]: pfe exiting, pid 12415
Mar 19 19:14:15 NodeC relayd[30965]: relay exiting, pid 30965
Mar 19 19:14:15 NodeC relayd[30994]: relay exiting, pid 30994
Mar 19 19:14:15 NodeC relayd[19179]: relay exiting, pid 19179
Mar 19 19:14:15 NodeC relayd[19774]: relay exiting, pid 19774
Mar 19 19:14:15 NodeC relayd[26432]: parent terminating, pid 26432
table web_hosts{ xxx.xxx.xxx.35, xxx.xxx.xxx.36 }
interval 60
timeout 8000
prefork 5
#log updates
protocol tcp_service { tcp { nodelay, socket buffer 65536 backlog 100 } }
http protocol http_service { tcp { nodelay, sack, socket buffer 65536,
no splice, backlog 1000 }
# header append $REMOTE_ADDR to X-Forwarded-For
return error
}
redirect http_Main {
listen on yyy.yyy.yyy.62 port 80 interface vlanXX
listen on yyy.yyy.yyy.63 port 80 interface vlanXX
match tag http_Main
forward to web_hosts port 82 check http / code 200
}
redirect https_Main {
listen on yyy.yyy.yyy.62 port 443 interface vlanXX
match tag https_Main
forward to web_hosts port 443 check tcp
}
redirect https_Only {
listen on yyy.yyy.yyy.63 port 443 interface vlanXX
match tag https_Only
forward to web_hosts port 445 check tcp
}
relay http_forwarder {
listen on 127.0.0.1 port 8080
protocol http_service
forward to web_hosts port 82 mode loadbalance check http / code 200
}
relay SSL_Generic {
listen on 127.0.0.1 port 8441
protocol tcp_service
forward to web_hosts port 443 mode loadbalance check tcp
}
relay SSL_Only {
listen on 127.0.0.1 port 8444
protocol tcp_service
forward to web_hosts port 445 mode loadbalance check tcp
}
# Out Bound Services #
relay some_mssql_forwarder {
listen on 127.0.0.1 port 8143
protocol tcp_service
forward to 10.240.8.185 port 1433
Thanks
Keith
Re: current/macppc on a Powerbook6,1
On 15/03/14(Sat) 16:22, Jan Stary wrote: On Mar 15 14:42:28, s...@openbsd.org wrote: On Sat, Mar 15, 2014 at 02:07:16PM +0100, Jan Stary wrote: This is an old 12 Powerbook G4 hw.model=7455 (Revision 0x303) with a freshly installed current/macppc. See full dmesg below. X doesn't work (NVIDIA GeForce4 440). I got the machine for peanuts so didn't bother checking http://marc.info/?l=openbsd-ppcm=136178209416987w=2 Trying `startx' without any configuration segfaults like this: I've got a battered 12 model which is suffering overheating issues. I'm not sure I'll ever be able to recover it. However, a little more than 2 weeks ago I had a -current snapshot running on it and X was working just fine (2D only) with the 'nv' driver. I just ran xdm, no xorg.conf since autodetection worked, and I had answered 'yes' to do you expect to run the X window system? during installation (in case this matters). Perhaps something changed in the meantime. But perhaps if you try an older snapshot, or 5.4 if necessary, you'll have a bit more luck with X? Yes. I just reinstalled with 5.4/macppc, and X works just fine (without xorg.conf) using the nv driver. See Xorg log below. There seem to be more differences in how this machone was supported by 5.4 and current; see both dmesgs below. Most notably, the cpu frequency is way different. cpu0 at mainbus0: 7455 (Revision 0x303): 866 MHz: 256KB L2 cache cpu0 at mainbus0: 7455 (Revision 0x303): 533 MHz: 256KB L2 cache The CPU in your machine supports different frequency, however there's no driver to control that in OpenBSD. I don't know what happened but it seems that know you're running at lower frequency. If somebody is interested into porting this frequency control via PMU, have a look at FreeBSD's pmufreq driver. Is that something that could happen, or is this a regression? Also, 5.4 recognizes appleagp, which current does not: appleagp0 at pchb0 agp0 at appleagp0: aperture at 0x0, size 0x1000 Is that why X works in 5.4? No, nvidia card never used this driver in macppc, and since we switch to KMS it doesn't work anymore with radeon neither, certainly some bug of mine. Could you send me the output of pcidump -v for 5.4 and -current, is there any difference?
Re: Where is this device attached?
On Thu, Mar 20, 2014 at 03:31:37PM +, John Long wrote:
David- sorry, I meant to reply to the list, here it is again for public
consumption with the topic threading borked, probably.
On Thu, Mar 20, 2014 at 04:14:13PM +0100, David Coppa wrote:
On Thu, Mar 20, 2014 at 2:31 PM, John Long codeb...@inbox.lv wrote:
Hi,
I am trying to use a USB device with a Loongson 5.3 stable box.
The line from dmesg for the device is
ugen0 at uhub1 port 3 HP Company HPx9G+ Device rev 1.10/1.00 addr 2
Is this a usb-to-serial thingie?
I don't think so, but I don't know if it is a standard USB device either.
It comes up as /dev/ttyUSB0 on that _other_ OS and will talk to Kermit but I
can't get it working on OpenBSD yet. I would prefer to use it with the
Loongson box if possible.
If this is the case, then it's not properly recognized by the kernel.
It should expose a ucom*, e.g.:
ucom0 at uftdi0 portno 1
Any other ideas?
It seems this needs a new driver, here is a quick test that modifies
an existing one that might work:
Index: moscom.c
===
RCS file: /cvs/src/sys/dev/usb/moscom.c,v
retrieving revision 1.19
diff -u -p -r1.19 moscom.c
--- moscom.c15 Nov 2013 08:25:30 - 1.19
+++ moscom.c20 Mar 2014 16:01:34 -
@@ -150,17 +150,17 @@ int moscom_cmd(struct moscom_softc *, in
struct ucom_methods moscom_methods = {
NULL,
- moscom_set,
- moscom_param,
NULL,
- moscom_open,
+ NULL,
+ NULL,
+ NULL,
NULL,
NULL,
NULL,
};
static const struct usb_devno moscom_devs[] = {
- { USB_VENDOR_MOSCHIP, USB_PRODUCT_MOSCHIP_MCS7703 }
+ { 0x03f0, 0x0121 }
};
int moscom_match(struct device *, void *, void *);
Re: relayd crashing after header append added
Keith(ke...@scott-land.net) on 2014.03.20 15:45:47 +: Does anyone know what might be causing this to happen and if there's a workaround ? possibly, but your report is lacking a dmesg.
Re: relayd crashing after header append added
Sorry forgot at include my dmesg... OpenBSD 5.4 (GENERIC.MP) #41: Tue Jul 30 15:30:02 MDT 2013 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4268331008 (4070MB) avail mem = 4146982912 (3954MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xbf79c000 (66 entries) bios0: vendor Dell Inc. version 1.11.0 date 09/18/2012 bios0: Dell Inc. PowerEdge R310 acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP APIC SPCR HPET DM__ MCFG WDAT SLIC ERST HEST BERT EINJ TCPA SSDT acpi0: wakeup devices PCI0(S5) USBA(S0) USBB(S0) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz, 2394.28 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,LONG,LAHF,PERF,ITSC cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 cpu0: apic clock running at 132MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz, 2393.99 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,LONG,LAHF,PERF,ITSC cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz, 2393.99 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,LONG,LAHF,PERF,ITSC cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz, 2393.99 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,LONG,LAHF,PERF,ITSC cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 0 pa 0xfec0, version 20, 24 pins acpihpet0 at acpi0: 14318179 Hz acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 4 (LYD0) acpiprt2 at acpi0: bus 5 (LYD2) acpiprt3 at acpi0: bus -1 (HVD0) acpiprt4 at acpi0: bus -1 (HVD2) acpiprt5 at acpi0: bus 3 (PEX0) acpiprt6 at acpi0: bus -1 (PEX2) acpiprt7 at acpi0: bus -1 (PEX3) acpiprt8 at acpi0: bus 2 (PEX4) acpiprt9 at acpi0: bus 1 (COMP) acpicpu0 at acpi0: C3, C1, PSS acpicpu1 at acpi0: C3, C1, PSS acpicpu2 at acpi0: C3, C1, PSS acpicpu3 at acpi0: C3, C1, PSS ipmi at mainbus0 not configured cpu0: Enhanced SpeedStep 2394 MHz: speeds: 2395, 2394, 2261, 2128, 1995, 1862, 1729, 1596, 1463, 1330, 1197 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel Core DMI rev 0x11 ppb0 at pci0 dev 3 function 0 Intel Core PCIE rev 0x11: msi pci1 at ppb0 bus 4 bnx0 at pci1 dev 0 function 0 Broadcom BCM5709 rev 0x20: apic 0 int 16 bnx1 at pci1 dev 0 function 1 Broadcom BCM5709 rev 0x20: apic 0 int 17 ppb1 at pci0 dev 5 function 0 Intel Core PCIE rev 0x11: msi pci2 at ppb1 bus 5 Intel Core Management rev 0x11 at pci0 dev 8 function 0 not configured Intel Core Scratch rev 0x11 at pci0 dev 8 function 1 not configured Intel Core Control rev 0x11 at pci0 dev 8 function 2 not configured Intel Core Misc rev 0x11 at pci0 dev 8 function 3 not configured Intel Core QPI Link rev 0x11 at pci0 dev 16 function 0 not configured Intel Core QPI Routing rev 0x11 at pci0 dev 16 function 1 not configured ehci0 at pci0 dev 26 function 0 Intel 3400 USB rev 0x05: apic 0 int 22 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb2 at pci0 dev 28 function 0 Intel 3400 PCIE rev 0x05 pci3 at ppb2 bus 3 ppb3 at pci0 dev 28 function 4 Intel 3400 PCIE rev 0x05 pci4 at ppb3 bus 2 bnx2 at pci4 dev 0 function 0 Broadcom BCM5716 rev 0x20: apic 0 int 16 bnx3 at pci4 dev 0 function 1 Broadcom BCM5716 rev 0x20: apic 0 int 17 ehci1 at pci0 dev 29 function 0 Intel 3400 USB rev 0x05: apic 0 int 22 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb4 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0xa5 pci5 at ppb4 bus 1 vga1 at pci5 dev 3 function 0 Matrox MGA G200eW rev 0x0a wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) pcib0 at pci0 dev 31 function 0 Intel 3420 LPC rev 0x05 pciide0 at pci0 dev 31 function 2 Intel 3400 SATA rev 0x05: DMA, channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide0: using apic 0 int 20 for native-PCI interrupt wd0 at pciide0 channel 0
Re: Where is this device attached?
On Fri, Mar 21, 2014 at 03:08:31AM +1100, Jonathan Gray wrote: Thanks. How do I build this? /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04
route add IP -link ???? -iface xx0
Hello, i cannot force the routing of an IP address to a particular MAC reading man route i expect to write route add DEST_IP -link DEST_MAC -iface TROUGH_THIS The real fun stuff is that i can add a weard mac destination my vr0 for example add 76:72:30:00:00:00 with route add DEST_IP -link -iface vr0 DEST_IP 76:72:30:00:00:00 UHLS 0 26 - 8 vr0 This is openBSD5.4 official release (i tryed to fix the MAC using arp -F -s without success) Am i miss-reading the man route ?? -- - () ascii ribbon campaign - against html e-mail /\
Re: Where is this device attached?
On 03/20/14 16:33, John Long wrote: On Fri, Mar 21, 2014 at 03:08:31AM +1100, Jonathan Gray wrote: Thanks. How do I build this? /jl http://www.openbsd.org/faq/faq5.html should answer most of your questions. hth Fred
Re: route add IP -link ???? -iface xx0
Hi, Le 20/03/2014 17:28, sven falempin a écrit : Hello, i cannot force the routing of an IP address to a particular MAC reading man route i expect to write route add DEST_IP -link DEST_MAC -iface TROUGH_THIS The real fun stuff is that i can add a weard mac destination my vr0 for example add 76:72:30:00:00:00 with route add DEST_IP -link -iface vr0 DEST_IP 76:72:30:00:00:00 UHLS 0 26 - 8 vr0 This is openBSD5.4 official release (i tryed to fix the MAC using arp -F -s without success) Am i miss-reading the man route ?? I've a machine doing this, with the following syntax : /sbin/route add A.B.C.D/32 -link -iface re0:0007b401 Hope this helps. Regards, Christophe.
Re: route add IP -link ???? -iface xx0
On Thu, Mar 20, 2014 at 1:19 PM, Christophe t...@stuxnet.org wrote: Hi, Le 20/03/2014 17:28, sven falempin a écrit : Hello, i cannot force the routing of an IP address to a particular MAC reading man route i expect to write route add DEST_IP -link DEST_MAC -iface TROUGH_THIS The real fun stuff is that i can add a weard mac destination my vr0 for example add 76:72:30:00:00:00 with route add DEST_IP -link -iface vr0 DEST_IP 76:72:30:00:00:00 UHLS 0 26 - 8 vr0 This is openBSD5.4 official release (i tryed to fix the MAC using arp -F -s without success) Am i miss-reading the man route ?? I've a machine doing this, with the following syntax : /sbin/route add A.B.C.D/32 -link -iface re0:0007b401 Hope this helps. Regards, Christophe. Thank you sir :) -- () ascii ribbon campaign - against html e-mail /\
Re: PPTP after removing of userland ppp(8)
On Thu, Mar 20, 2014 at 10:38:06AM +0200, Атанас Владимиров wrote: Is the following patch correct: A pptp client is available which interfaces with -a href=http://www.openbsd.org/cgi-bin/man.cgi?query=pppdamp;sektion=8 pppd(8)/a +a href= http://www.openbsd.org/cgi-bin/man.cgi?query=pppamp;sektion=8amp;manpath=OpenBSD+5.4 ppp(8)/a So people were confused about which PPP implementation can interface with net/pptp? I'm not surprised. I intend to remove the net/pptp port altogether unless someone can provide a working configuration using pppd(8). There are plans to add a PPTP client to npppd/pipex. So the lack of PPTP client support will hopefully be a temporary situation. And, as goes without saying, if possible, please consider using a different protocol. PPTP's weaknesses have been well understood for a long time now. Much better alternatives are available in the base system and the ports tree.
Re: Where is this device attached?
On Thu, Mar 20, 2014 at 04:45:12PM +, Fred wrote: On 03/20/14 16:33, John Long wrote: On Fri, Mar 21, 2014 at 03:08:31AM +1100, Jonathan Gray wrote: Thanks. How do I build this? /jl http://www.openbsd.org/faq/faq5.html should answer most of your questions. Nah, most of my questions have nothing to do with OpenBSD. The one you responded to could be clarified. My bad. Do I need to go through steps of rebuilding all of the kernel, userland, etc.? Since I don't know what has to happen to get this into the system. I figured Jonathan would know since he's the one who was nice enough to offer a test patch. hth Don't get too far ahead of yourself ;-) /jl -- ASCII ribbon campaign ( ) Powered by Lemote Fuloong against HTML e-mail X Loongson MIPS and OpenBSD and proprietary/ \http://www.mutt.org attachments / \ Code Blue or Go Home! Encrypted email preferred PGP Key 2048R/DA65BC04
Re: npppd with two pppx interfaces causes kernel panic
From: YASUOKA Masahiko Sent: Wednesday, March 19, 2014 9:44 PM Should I just keep an eye on the changelog for mention of pppx changes to tell when it's safe to try again? Sorry I cannot understand the point of this question. Sorry to be confusing; I switched to tun because of this bug, but I would prefer to use pppx once it has been fixed. The question was regarding how to know when the bug has been fixed. As I am unaware of any publicly accessible bug tracking system for openbsd, I was thinking of just watching the change log (http://www.openbsd.org/plus.html) for any mention of pppx. Thanks.
Re: npppd with two pppx interfaces causes kernel panic
From: Jonathan Gray Sent: Thursday, March 20, 2014 3:36 AM The following diff prevents the panic here: Interesting, given the XXX, it seems somebody was already a little suspicious of this section :). From a cursory glance, it seems pppx_dev_lookup is supposed to return data about a particular instance if it is in use, or NULL otherwise. So it seems for some reason pppxclose is being called for device that isn't open? While avoiding a panic is a plus :), it seems there is perhaps a logic error somewhere else resulting in an attempt to close a device that isn't open? Index: if_pppx.c == = RCS file: /cvs/src/sys/net/if_pppx.c,v retrieving revision 1.26 diff -u -p -r1.26 if_pppx.c --- if_pppx.c 19 Oct 2013 14:46:30 - 1.26 +++ if_pppx.c 20 Mar 2014 10:21:04 - @@ -590,7 +590,8 @@ pppxclose(dev_t dev, int flags, int mode rw_enter_write(pppx_devs_lk); - pxd = pppx_dev_lookup(dev); + if ((pxd = pppx_dev_lookup(dev)) == NULL) + return (ENXIO); /* XXX */ while ((pxi = LIST_FIRST(pxd-pxd_pxis)))
Re: PPTP after removing of userland ppp(8)
On 3/20/14, Stefan Sperling s...@openbsd.org wrote: [...] And, as goes without saying, if possible, please consider using a different protocol. PPTP's weaknesses have been well understood for a long time now. Much better alternatives are available in the base system and the ports tree. The statement much better alternatives are available suggests the user has a choice in picking these alternatives. This isn't the case some of the time. In my case, in the recent past, I was either to use PPTP or some other proprietary solution in order to connect to my employer's network. The proprietary solution would require lugging around a Windows or Mac laptop, which made PPTP the much better alternative, allowing work in my preferred environment. --patrick
Re: PPTP after removing of userland ppp(8)
On 3/20/14, Stefan Sperling s...@openbsd.org wrote: [...] And, as goes without saying, if possible, please consider using a different protocol. PPTP's weaknesses have been well understood for a long time now. Much better alternatives are available in the base system and the ports tree. The statement much better alternatives are available suggests the user has a choice in picking these alternatives. This isn't the case some of the time. In my case, in the recent past, I was either to use PPTP or some other proprietary solution in order to connect to my employer's network. The proprietary solution would require lugging around a Windows or Mac laptop, which made PPTP the much better alternative, allowing work in my preferred environment. You'd be safer using Windows than the code which was just deleted.
Questions about monitoring LAN traffic with openbsd/pf/pflog/pflow
I’m attempting to monitor traffic on my LAN, I have inserted a non-aggregating network tap between my firewall (not openbsd) and my enet switch. I wired the two monitor ports of the network tap to two ethernet interfaces (em2 and em3) on an openbsd machine (running 5.3 at present), em0 on this machine is the regular network port. I’m attempting to configure pf etc. in order to facilitate monitoring and analyzing the traffic on my lan. I started with just the em2 interface and associated tap output, which monitors traffic from my LAN to the firewall. AFAICT, the interfaces I use for this monitoring need to be “UP” and in “PROMISC” (promiscuous) mode, correct? So far, the only way I know I can do that is by adding the interface to a bridge. Is there another/better way? So, I have: ifconfig em2 up ifconfig bridge0 add em2 ifconfig bridge0 rule pass in on em2 tag tap_b ifconfig bridge0 up I’d like to configure pf as follows: Log all traffic on em2/bridge0 to (ideally a specific) pflog interface Also “log” flows on em2/bridge0 to (ideally a specific) pflow interface Leave em0 alone (in its default state), and don’t “duplicate” logging of packets received on this interface to pflog/pflow interfaces above. And after that, basically replicate the em2/bridge0 logging with similar logging for em3/bridge1, to distinct pflog/pflow interfaces. Here is my current pf.conf, it doesn’t do what I want above, but this is only thing I have gotten to work at all: set state-defaults pflow set skip on lo pass log on bridge0 block # block stateless traffic pass# establish keep-state block in on ! lo0 proto tcp to port 6000:6010 Is there a better way to log packets received on the bridge than by “pass” ing them? I tried to tag the packets coming in from em2 in the bridge config, but haven’t yet figured out how to use that tag to help me log. With the above, and with ifconfig pflow0 flowsrc 192.168.128.61 flowdst 192.168.128.61:1234 pflowproto 9 I’ve gotten some flow data to show up and I’ve used nfsen to look at it. I’d greatly appreciate any advice/pointers on how I can do what I describe above. I’ve spent many hours trying different things, reading man pages, and books (The Book of PF, Network Flow Analysis, etc) Don
Re: Questions about monitoring LAN traffic with openbsd/pf/pflog/pflow
Em 20-03-2014 17:12, Don Jackson escreveu: I’m attempting to monitor traffic on my LAN, I have inserted a non-aggregating network tap between my firewall (not openbsd) and my enet switch. I wired the two monitor ports of the network tap to two ethernet interfaces (em2 and em3) on an openbsd machine (running 5.3 at present), em0 on this machine is the regular network port. I’m attempting to configure pf etc. in order to facilitate monitoring and analyzing the traffic on my lan. I started with just the em2 interface and associated tap output, which monitors traffic from my LAN to the firewall. AFAICT, the interfaces I use for this monitoring need to be “UP” and in “PROMISC” (promiscuous) mode, correct? So far, the only way I know I can do that is by adding the interface to a bridge. Is there another/better way? You could implement some sort of daemon that puts the interfaces in promiscuous mode using the pcap library. Or running a tmux+tcpdump. A bridge can also work, but it introduces complexity, especially when filtering the packets. So, I have: ifconfig em2 up ifconfig bridge0 add em2 ifconfig bridge0 rule pass in on em2 tag tap_b ifconfig bridge0 up I’d like to configure pf as follows: Log all traffic on em2/bridge0 to (ideally a specific) pflog interface Also “log” flows on em2/bridge0 to (ideally a specific) pflow interface Leave em0 alone (in its default state), and don’t “duplicate” logging of packets received on this interface to pflog/pflow interfaces above. And after that, basically replicate the em2/bridge0 logging with similar logging for em3/bridge1, to distinct pflog/pflow interfaces. Here is my current pf.conf, it doesn’t do what I want above, but this is only thing I have gotten to work at all: set state-defaults pflow set skip on lo pass log on bridge0 block # block stateless traffic pass# establish keep-state block in on ! lo0 proto tcp to port 6000:6010 Is there a better way to log packets received on the bridge than by “pass” ing them? I tried to tag the packets coming in from em2 in the bridge config, but haven’t yet figured out how to use that tag to help me log. With the above, and with ifconfig pflow0 flowsrc 192.168.128.61 flowdst 192.168.128.61:1234 pflowproto 9 AFAIK, using anything beside proto 5 on pflow interfaces is broken, at least on OpenBSD 5.4. I know there were some recent work in this area that solves this issue. I’ve gotten some flow data to show up and I’ve used nfsen to look at it. I’d greatly appreciate any advice/pointers on how I can do what I describe above. I’ve spent many hours trying different things, reading man pages, and books (The Book of PF, Network Flow Analysis, etc) Don Instead of using the state-defaults, you should use more specific rules. pass on em0 pass on em2 (pflow) pass on em3 (pflow) and so on. I believe that this is it. Of course things would be much simpler if your OpenBSD machine was the router. And you could practically guarantee that you would see all the packets. Cheers, -- Giancarlo Razzolini GPG: 4096R/77B981BC
Re: Questions about monitoring LAN traffic with openbsd/pf/pflog/pflow
On Mar 20, 2014, at 2:14 PM, Giancarlo Razzolini grazzol...@gmail.com wrote: Em 20-03-2014 17:12, Don Jackson escreveu: I’m attempting to monitor traffic on my LAN, I have inserted a non-aggregating network tap between my firewall (not openbsd) and my enet switch. I wired the two monitor ports of the network tap to two ethernet interfaces (em2 and em3) on an openbsd machine (running 5.3 at present), em0 on this machine is the regular network port. I’m attempting to configure pf etc. in order to facilitate monitoring and analyzing the traffic on my lan. I started with just the em2 interface and associated tap output, which monitors traffic from my LAN to the firewall. AFAICT, the interfaces I use for this monitoring need to be “UP” and in “PROMISC” (promiscuous) mode, correct? So far, the only way I know I can do that is by adding the interface to a bridge. Is there another/better way? You could implement some sort of daemon that puts the interfaces in promiscuous mode using the pcap library. Or running a tmux+tcpdump. A bridge can also work, but it introduces complexity, especially when filtering the packets. Based on further experiments motivated by your suggestions, I have concluded that I’ve been using the wrong tool(s) for the job. Since I’m using the OpenBSD box to just read all packets on an interface, I shouldn’t be using pf/pflog/pflow at all, I should just focus on apps like tcpdump that open the interface directly, and read what they want. Some network monitoring packages (i.e. argus) seem to have their own tcpdump-like apps for reading network interfaces. If the box in question was the router/firewall, then obviously I could/should use pf/pflog/pflow to extract the info passing through/by that I would want to monitor. Thank you for kludging me in the right direction. Don
Re: PPTP after removing of userland ppp(8)
On 2014-03-20, patrick keshishian pkesh...@gmail.com wrote: On 3/20/14, Stefan Sperling s...@openbsd.org wrote: [...] And, as goes without saying, if possible, please consider using a different protocol. PPTP's weaknesses have been well understood for a long time now. Much better alternatives are available in the base system and the ports tree. The statement much better alternatives are available suggests the user has a choice in picking these alternatives. This isn't the case some of the time. In my case, in the recent past, I was either to use PPTP or some other proprietary solution in order to connect to my employer's network. The proprietary solution would require lugging around a Windows or Mac laptop, which made PPTP the much better alternative, allowing work in my preferred environment. Which particular proprietary solution? If by any chance it's Cisco anyconnect, see ports/net/openconnect...
Re: Unbound in base, yes, what about ldns?
On 2014-03-19, Chris Smith obsd_m...@chrissmith.org wrote: On Wed, Mar 19, 2014 at 6:12 PM, Kenneth Westerback kwesterb...@gmail.com wrote: The unbound in base has it's own cut down version of ldns. No need for the package. Can I just uninstall the package after the fact or do some files need to be replaced? Thanks, Chris You can uninstall the package if you don't need it, or you can keep it if you do need it (for example, for drill or the ldns-* tools).
Suspend and Hibernate Issues with 3/5 Snapshot and ThinkPad T42p
With OpenBSD 5.2, I had no issue doing suspend and hibernate: when I closed the lid, it suspended, when I hit Fn+F12 the BIOS took over, with it's own pretty text interface, and hibernated the system. iwi(4) also worked flawlessly with suspend/hibernate. Fast forward to upgrading to 5.5 with ACPI: setting machdep.lidsuspend=1 allows the system to suspend when I close the lid, but iwi(4) is broken upon resume (iwi0: could not load boot firmware) and Fn+F12 or ZZZ leaves me with a blank screen and an eternal flashing moon LED (swap is RAM + 1GB). If I disable ACPI in UKC, which is enabled by default, everything works as it did in 5.2 with the exception of hibernate which behaves as if ACPI was enabled. Any recommendations on how to fix? Thanks. dmesg with ACPI enabled (default): OpenBSD 5.5 (GENERIC) #276: Wed Mar 5 09:57:06 MST 2014 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) M processor 2.00GHz (GenuineIntel 686-class) 2 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE,EST,TM2,PERF real mem = 2146332672 (2046MB) avail mem = 2098974720 (2001MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 06/18/07, BIOS32 rev. 0 @ 0xfd750, SMBIOS rev. 2.33 @ 0xe0010 (61 entries) bios0: vendor IBM version 1RETDRWW (3.23 ) date 06/18/2007 bios0: IBM 2373C61 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT TCPA BOOT acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) PCI0(S3) PCI1(S4) DOCK(S4) USB0(S3) USB1(S3) AC9M(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (AGP_) acpiprt2 at acpi0: bus 2 (PCI1) acpicpu0 at acpi0: C3, C2, C1, PSS acpipwrres0 at acpi0: PUBS, resource for USB0, USB1, USB7 acpitz0 at acpi0: critical temperature is 93 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model IBM-08K8198 serial 153 type LION oem SANYO acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 acpidock0 at acpi0: DOCK not docked (0) bios0: ROM list: 0xc/0x1 0xd/0x1000 0xd1000/0x1000 0xdc000/0x4000! 0xe/0x1 cpu0 at mainbus0: (uniprocessor) mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: Enhanced SpeedStep 1999 MHz: speeds: 2000, 1800, 1600, 1400, 1200, 1000, 800, 600 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82855PM Host rev 0x03 intelagp0 at pchb0 agp0 at intelagp0: aperture at 0xd000, size 0x1000 ppb0 at pci0 dev 1 function 0 Intel 82855PM AGP rev 0x03 pci1 at ppb0 bus 1 radeondrm0 at pci1 dev 0 function 0 ATI Radeon Mobility M10 rev 0x80 drm0 at radeondrm0 radeondrm0: irq 11 uhci0 at pci0 dev 29 function 0 Intel 82801DB USB rev 0x01: irq 11 uhci1 at pci0 dev 29 function 1 Intel 82801DB USB rev 0x01: irq 11 uhci2 at pci0 dev 29 function 2 Intel 82801DB USB rev 0x01: irq 11 ehci0 at pci0 dev 29 function 7 Intel 82801DB USB rev 0x01: irq 11 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb1 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0x81 pci2 at ppb1 bus 2 2:0:0: mem address conflict 0xb000/0x1000 2:0:1: mem address conflict 0xb100/0x1000 cbb0 at pci2 dev 0 function 0 TI PCI4520 CardBus rev 0x01: irq 11 cbb1 at pci2 dev 0 function 1 TI PCI4520 CardBus rev 0x01: irq 11 em0 at pci2 dev 1 function 0 Intel 82540EP rev 0x03: irq 11, address 00:01:6c:eb:89:64 iwi0 at pci2 dev 2 function 0 Intel PRO/Wireless 2915ABG rev 0x05: irq 11, address 00:12:f0:5b:30:42 cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 3 device 0 cacheline 0x8, lattimer 0xb0 pcmcia0 at cardslot0 cardslot1 at cbb1 slot 1 flags 0 cardbus1 at cardslot1: bus 6 device 0 cacheline 0x8, lattimer 0xb0 pcmcia1 at cardslot1 ichpcib0 at pci0 dev 31 function 0 Intel 82801DBM LPC rev 0x01 pciide0 at pci0 dev 31 function 1 Intel 82801DBM IDE rev 0x01: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: FUJITSU MHV2080AH wd0: 16-sector PIO, LBA, 76319MB, 156301488 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: MATSHITA, UJDA765 DVD/CDRW, 1.02 ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 ichiic0 at pci0 dev 31 function 3 Intel 82801DB SMBus rev 0x01: irq 11 iic0 at ichiic0 spdmem0 at iic0 addr 0x50: 1GB DDR SDRAM non-parity PC2700CL2.5 spdmem1 at iic0 addr 0x51: 1GB DDR SDRAM non-parity PC2700CL2.5 auich0 at pci0 dev 31 function 5 Intel 82801DB AC97 rev 0x01: irq 11, ICH4 AC97 ac97: codec id 0x41445374 (Analog Devices AD1981B) ac97: codec features headphone, 20 bit DAC, No 3D Stereo audio0 at auich0 Intel 82801DB Modem rev 0x01 at pci0 dev 31 function 6 not configured usb1 at uhci0: USB revision 1.0 uhub1 at
Re: Suspend and Hibernate Issues with 3/5 Snapshot and ThinkPad T42p
5.2 to 5.5 is a big jump. Can you try 5.3 and/or 5.4 to narrow down when the problem began? Bisecting the tree would be the next step. :-) Ken On 20 March 2014 20:34, Daniel Melameth dan...@melameth.com wrote: With OpenBSD 5.2, I had no issue doing suspend and hibernate: when I closed the lid, it suspended, when I hit Fn+F12 the BIOS took over, with it's own pretty text interface, and hibernated the system. iwi(4) also worked flawlessly with suspend/hibernate. Fast forward to upgrading to 5.5 with ACPI: setting machdep.lidsuspend=1 allows the system to suspend when I close the lid, but iwi(4) is broken upon resume (iwi0: could not load boot firmware) and Fn+F12 or ZZZ leaves me with a blank screen and an eternal flashing moon LED (swap is RAM + 1GB). If I disable ACPI in UKC, which is enabled by default, everything works as it did in 5.2 with the exception of hibernate which behaves as if ACPI was enabled. Any recommendations on how to fix? Thanks. dmesg with ACPI enabled (default): OpenBSD 5.5 (GENERIC) #276: Wed Mar 5 09:57:06 MST 2014 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) M processor 2.00GHz (GenuineIntel 686-class) 2 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE,EST,TM2,PERF real mem = 2146332672 (2046MB) avail mem = 2098974720 (2001MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 06/18/07, BIOS32 rev. 0 @ 0xfd750, SMBIOS rev. 2.33 @ 0xe0010 (61 entries) bios0: vendor IBM version 1RETDRWW (3.23 ) date 06/18/2007 bios0: IBM 2373C61 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT TCPA BOOT acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) PCI0(S3) PCI1(S4) DOCK(S4) USB0(S3) USB1(S3) AC9M(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (AGP_) acpiprt2 at acpi0: bus 2 (PCI1) acpicpu0 at acpi0: C3, C2, C1, PSS acpipwrres0 at acpi0: PUBS, resource for USB0, USB1, USB7 acpitz0 at acpi0: critical temperature is 93 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model IBM-08K8198 serial 153 type LION oem SANYO acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 acpidock0 at acpi0: DOCK not docked (0) bios0: ROM list: 0xc/0x1 0xd/0x1000 0xd1000/0x1000 0xdc000/0x4000! 0xe/0x1 cpu0 at mainbus0: (uniprocessor) mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: Enhanced SpeedStep 1999 MHz: speeds: 2000, 1800, 1600, 1400, 1200, 1000, 800, 600 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82855PM Host rev 0x03 intelagp0 at pchb0 agp0 at intelagp0: aperture at 0xd000, size 0x1000 ppb0 at pci0 dev 1 function 0 Intel 82855PM AGP rev 0x03 pci1 at ppb0 bus 1 radeondrm0 at pci1 dev 0 function 0 ATI Radeon Mobility M10 rev 0x80 drm0 at radeondrm0 radeondrm0: irq 11 uhci0 at pci0 dev 29 function 0 Intel 82801DB USB rev 0x01: irq 11 uhci1 at pci0 dev 29 function 1 Intel 82801DB USB rev 0x01: irq 11 uhci2 at pci0 dev 29 function 2 Intel 82801DB USB rev 0x01: irq 11 ehci0 at pci0 dev 29 function 7 Intel 82801DB USB rev 0x01: irq 11 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb1 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0x81 pci2 at ppb1 bus 2 2:0:0: mem address conflict 0xb000/0x1000 2:0:1: mem address conflict 0xb100/0x1000 cbb0 at pci2 dev 0 function 0 TI PCI4520 CardBus rev 0x01: irq 11 cbb1 at pci2 dev 0 function 1 TI PCI4520 CardBus rev 0x01: irq 11 em0 at pci2 dev 1 function 0 Intel 82540EP rev 0x03: irq 11, address 00:01:6c:eb:89:64 iwi0 at pci2 dev 2 function 0 Intel PRO/Wireless 2915ABG rev 0x05: irq 11, address 00:12:f0:5b:30:42 cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 3 device 0 cacheline 0x8, lattimer 0xb0 pcmcia0 at cardslot0 cardslot1 at cbb1 slot 1 flags 0 cardbus1 at cardslot1: bus 6 device 0 cacheline 0x8, lattimer 0xb0 pcmcia1 at cardslot1 ichpcib0 at pci0 dev 31 function 0 Intel 82801DBM LPC rev 0x01 pciide0 at pci0 dev 31 function 1 Intel 82801DBM IDE rev 0x01: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: FUJITSU MHV2080AH wd0: 16-sector PIO, LBA, 76319MB, 156301488 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: MATSHITA, UJDA765 DVD/CDRW, 1.02 ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 ichiic0 at pci0 dev 31 function 3 Intel 82801DB SMBus rev 0x01: irq 11 iic0 at ichiic0 spdmem0 at iic0 addr 0x50: 1GB DDR SDRAM non-parity PC2700CL2.5 spdmem1 at iic0 addr 0x51: 1GB DDR SDRAM non-parity PC2700CL2.5
Re: Suspend and Hibernate Issues with 3/5 Snapshot and ThinkPad T42p
Hrm, I'll work on this and report back, but dissecting the tree and venturing down the ACPI and APM rabbit holes is likely beyond my ability. On Thu, Mar 20, 2014 at 6:39 PM, Kenneth Westerback kwesterb...@gmail.com wrote: 5.2 to 5.5 is a big jump. Can you try 5.3 and/or 5.4 to narrow down when the problem began? Bisecting the tree would be the next step. :-) Ken On 20 March 2014 20:34, Daniel Melameth dan...@melameth.com wrote: With OpenBSD 5.2, I had no issue doing suspend and hibernate: when I closed the lid, it suspended, when I hit Fn+F12 the BIOS took over, with it's own pretty text interface, and hibernated the system. iwi(4) also worked flawlessly with suspend/hibernate. Fast forward to upgrading to 5.5 with ACPI: setting machdep.lidsuspend=1 allows the system to suspend when I close the lid, but iwi(4) is broken upon resume (iwi0: could not load boot firmware) and Fn+F12 or ZZZ leaves me with a blank screen and an eternal flashing moon LED (swap is RAM + 1GB). If I disable ACPI in UKC, which is enabled by default, everything works as it did in 5.2 with the exception of hibernate which behaves as if ACPI was enabled. Any recommendations on how to fix? Thanks. dmesg with ACPI enabled (default): OpenBSD 5.5 (GENERIC) #276: Wed Mar 5 09:57:06 MST 2014 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) M processor 2.00GHz (GenuineIntel 686-class) 2 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE,EST,TM2,PERF real mem = 2146332672 (2046MB) avail mem = 2098974720 (2001MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 06/18/07, BIOS32 rev. 0 @ 0xfd750, SMBIOS rev. 2.33 @ 0xe0010 (61 entries) bios0: vendor IBM version 1RETDRWW (3.23 ) date 06/18/2007 bios0: IBM 2373C61 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT TCPA BOOT acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) PCI0(S3) PCI1(S4) DOCK(S4) USB0(S3) USB1(S3) AC9M(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (AGP_) acpiprt2 at acpi0: bus 2 (PCI1) acpicpu0 at acpi0: C3, C2, C1, PSS acpipwrres0 at acpi0: PUBS, resource for USB0, USB1, USB7 acpitz0 at acpi0: critical temperature is 93 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model IBM-08K8198 serial 153 type LION oem SANYO acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 acpidock0 at acpi0: DOCK not docked (0) bios0: ROM list: 0xc/0x1 0xd/0x1000 0xd1000/0x1000 0xdc000/0x4000! 0xe/0x1 cpu0 at mainbus0: (uniprocessor) mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: Enhanced SpeedStep 1999 MHz: speeds: 2000, 1800, 1600, 1400, 1200, 1000, 800, 600 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82855PM Host rev 0x03 intelagp0 at pchb0 agp0 at intelagp0: aperture at 0xd000, size 0x1000 ppb0 at pci0 dev 1 function 0 Intel 82855PM AGP rev 0x03 pci1 at ppb0 bus 1 radeondrm0 at pci1 dev 0 function 0 ATI Radeon Mobility M10 rev 0x80 drm0 at radeondrm0 radeondrm0: irq 11 uhci0 at pci0 dev 29 function 0 Intel 82801DB USB rev 0x01: irq 11 uhci1 at pci0 dev 29 function 1 Intel 82801DB USB rev 0x01: irq 11 uhci2 at pci0 dev 29 function 2 Intel 82801DB USB rev 0x01: irq 11 ehci0 at pci0 dev 29 function 7 Intel 82801DB USB rev 0x01: irq 11 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb1 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0x81 pci2 at ppb1 bus 2 2:0:0: mem address conflict 0xb000/0x1000 2:0:1: mem address conflict 0xb100/0x1000 cbb0 at pci2 dev 0 function 0 TI PCI4520 CardBus rev 0x01: irq 11 cbb1 at pci2 dev 0 function 1 TI PCI4520 CardBus rev 0x01: irq 11 em0 at pci2 dev 1 function 0 Intel 82540EP rev 0x03: irq 11, address 00:01:6c:eb:89:64 iwi0 at pci2 dev 2 function 0 Intel PRO/Wireless 2915ABG rev 0x05: irq 11, address 00:12:f0:5b:30:42 cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 3 device 0 cacheline 0x8, lattimer 0xb0 pcmcia0 at cardslot0 cardslot1 at cbb1 slot 1 flags 0 cardbus1 at cardslot1: bus 6 device 0 cacheline 0x8, lattimer 0xb0 pcmcia1 at cardslot1 ichpcib0 at pci0 dev 31 function 0 Intel 82801DBM LPC rev 0x01 pciide0 at pci0 dev 31 function 1 Intel 82801DBM IDE rev 0x01: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: FUJITSU MHV2080AH wd0: 16-sector PIO, LBA, 76319MB, 156301488 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: MATSHITA, UJDA765 DVD/CDRW, 1.02 ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4,
Re: PPTP after removing of userland ppp(8)
On 3/20/14, Stuart Henderson s...@spacehopper.org wrote: On 2014-03-20, patrick keshishian pkesh...@gmail.com wrote: On 3/20/14, Stefan Sperling s...@openbsd.org wrote: [...] And, as goes without saying, if possible, please consider using a different protocol. PPTP's weaknesses have been well understood for a long time now. Much better alternatives are available in the base system and the ports tree. The statement much better alternatives are available suggests the user has a choice in picking these alternatives. This isn't the case some of the time. In my case, in the recent past, I was either to use PPTP or some other proprietary solution in order to connect to my employer's network. The proprietary solution would require lugging around a Windows or Mac laptop, which made PPTP the much better alternative, allowing work in my preferred environment. Which particular proprietary solution? If by any chance it's Cisco anyconnect, see ports/net/openconnect... Don't recall. Maybe Juniper something? --patrick
[patch] little typo on current.html
Little typo on current.html. Index: current.html === RCS file: /cvs/www/faq/current.html,v retrieving revision 1.475 diff -u -p -r1.475 current.html --- current.html19 Mar 2014 20:10:29 - 1.475 +++ current.html21 Mar 2014 02:42:42 - @@ -762,7 +762,7 @@ which supports L2TP, PPTP and PPPoE (cur uucpd(8) has been removed. As a result, the old binaries and manual pages should be removed: pre -rm -f /usr/libxec/uucpd +rm -f /usr/libexec/uucpd rm -f /usr/share/man/man8/uucpd.8 /pre
Re: [patch] little typo on current.html
On Thu, Mar 20, 2014 at 11:46:01PM -0300, Daniel Bolgheroni wrote: Little typo on current.html. Fixed, thanks! Index: current.html === RCS file: /cvs/www/faq/current.html,v retrieving revision 1.475 diff -u -p -r1.475 current.html --- current.html 19 Mar 2014 20:10:29 - 1.475 +++ current.html 21 Mar 2014 02:42:42 - @@ -762,7 +762,7 @@ which supports L2TP, PPTP and PPPoE (cur uucpd(8) has been removed. As a result, the old binaries and manual pages should be removed: pre -rm -f /usr/libxec/uucpd +rm -f /usr/libexec/uucpd rm -f /usr/share/man/man8/uucpd.8 /pre
Re: Where is this device attached?
On Thu, Mar 20, 2014 at 04:33:01PM +, John Long wrote: On Fri, Mar 21, 2014 at 03:08:31AM +1100, Jonathan Gray wrote: Thanks. How do I build this? You need to build and install a new kernel. After checking out the src tree via cvs and saving the patch to a file. cd /usr/src/sys/dev/usb patch -p0 /path/to/file then build and install a kernel as described in http://www.openbsd.org/faq/faq5.html#BldKernel
