Re: The unknown in i386-unknown-openbsd5.4
On Fri, Jan 31, 2014 at 06:18:44PM -0500, Adam Jensen wrote: I see the string i386-unknown-openbsd5.4 in various places throughout my system. What does the unknown part of this string refer to and is there a canonical way to set it to something more meaningful? Thanks! Ah, but then the FSF will know who you are ! (well, basically, it's another example of over-engineering, and bad tools. You can't change it without breaking every gnu-configure script in existence and then some...)
Re: Does this usb wireless adapter works?
On Fri, Jan 31, 2014 at 6:06 PM, Alexander Pakhomov ker0...@yandex.ru wrote: No, it doesn't. It crashes kernel once a day and deadly hangs till reboot every 30 min. I've send a bug report, but nobody cares. I use RTL8192CU. It crashes kernel once a month. Sorry for this late response ... Oops ... then, what usb wireless adapter can I use for an OpenBSD hostap?? It seems that Alfa Networks adapters are not a good option ...
Re: Does this usb wireless adapter works?
I had this USB wireless NIC laying around (it's old). So far it seems to be working fine for me. But, I am just using it as a wireless client and not as an AP or anything. http://www.newegg.com/Product/Product.aspx?Item=N82E16833164015 On Feb 1, 2014, at 5:40 AM, C. L. Martinez carlopm...@gmail.com wrote: On Fri, Jan 31, 2014 at 6:06 PM, Alexander Pakhomov ker0...@yandex.ru wrote: No, it doesn't. It crashes kernel once a day and deadly hangs till reboot every 30 min. I've send a bug report, but nobody cares. I use RTL8192CU. It crashes kernel once a month. Sorry for this late response ... Oops ... then, what usb wireless adapter can I use for an OpenBSD hostap?? It seems that Alfa Networks adapters are not a good option ...
cheapest firewall?
Any suggestions for the cheapest possible firewall (that is new hardware not re-purposing some old stuff)? All I need is 2 ethernet interfaces and for it to run openbsd.
Re: cheapest firewall?
On 2014-02-01, Adam s...@my-balls.com wrote: Any suggestions for the cheapest possible firewall (that is new hardware not re-purposing some old stuff)? All I need is 2 ethernet interfaces and for it to run openbsd. alix 2d19 or 2d4. With a bit more work on OpenBSD/octeon, Edgerouter lite would be slightly cheaper, but the port isn't quite there yet (storage isn't supported yet).
Re: pf redirect through socks tunnel?
On 2014-01-31, Darren Tucker dtuc...@zip.com.au wrote:
On Fri, Jan 31, 2014 at 4:02 AM, Pieter Verberne
pieterverbe...@xs4all.nl wrote:
Hi there,
When I use a client, which is behind a pf firewall, I use this redirect
rule:
pass in on $ext_if proto {tcp, udp} from any to any port 12345 rdr-to
10.1.2.3
Now I have a client that is connected via a socks5 SSH tunnel to the pf
firewall. Can I still have a pf redirect to this client?
I wrote code to do this for PF some time back based on work by Luca
Barbieri for the same functionality on Linux:
https://bugzilla.mindrot.org/show_bug.cgi?id=1295
I suspect the patch will have bitrotted since then.
The other gotcha is that it needed to be run as root to open the PF
device to look up the NAT states. That could potentially be mitigated
by a setuid helper program, but from memory it needed write access for
the DIOCNATLOOK ioctl, so it'd still be potentially dangerous.
Rather than writing a helper running as root, you can change from using
nat redirects (rdr-to) to using divert sockets (divert-to), then the proxy
will receive unmodified packets and can just use getsockname(2) to retrieve
the original address which does not require privileges.
Same method will also work with FreeBSD ipfw.
Re: The unknown in i386-unknown-openbsd5.4
On Sat, 1 Feb 2014 00:52:31 + (UTC)
na...@mips.inka.de (Christian Weisgerber) wrote:
FreeBSD is more playful: It has ${ARCH}-portbld-freebsd
${OSREL} in its ports tree and ...
I wonder how the FreeBSD guys changed it without breaking every
gnu-configure script in existence.
It shows up in so many places, even my email headers:
X-Mailer:Sylpheed 3.2.0 (GTK+ 2.24.20; i386-unknown-openbsd5.4)
To the uninitiated masses, it might seem like the system was
sloppily configured or in some other way the admin was confused.
Re: OpenBSD 5.4 as guest under VMWare Server 2 install fails
Hello, Further to my earlier very basic erro description, I was able to colelct some more debug messages from when the Kernel panic occurs. Could you give me some pointers of how to possibly fix this or how to file a bug report. Thanks. Here is the trace output: cpu_init(d0b73880,0,30,d0a466a0,0) at cpu_init+0x51 cpu_attach(d15ce000,d14e1800,d0c3bbe4,d043f1ab,0) at cpu_attach+0x11c config_attacg(d15ce000,d0a466a0,d0c3bbe4,d08a7510,0) at config_attachg+0x1bb acpimadt_attach(d15cc200,d1655240,d0c3bc74,d043f1ab,d08972d0) at acpimadt_attach+0x1eb config_attach(d15ce040,d0a476e0,d0c3bc74,d0897f80,0) at config attach+0x1bb acpi_attach(d15ce040,d15cc200,d0c3bd74,d043f1ab,0) at acpi_attach+0x52d config_attach(d15ce040,d0a475c0,d0c3bd74,d07def50,2d) at config_attach+0x1bb biosttach)d15ce000,d15ce040,d0c3be54,d043f1ab,0) at biosattach+0x6b6 config_attach(d15ce000,d0c3be54,d0602b80,30c0) at config_attach+0x1bb mainbus_attachh(0,d15ce000,0,d0a44040,0) at mainbus_attach+0x4e config_attach(0,d0a44040,0,0,d0ab7a00) at config_attach+0x1bb config_rootfound(d0961f0c,0,0d042ff31,0) at config_rootfound+0x46 cpu_configure(d0b73880,1,1000,cff3f000,1) at cpu_configure+0x29 main(d02004f6,d02004fe,0,0,0) at main+0x3dd Here is the ps output: PID PPIDPGRPUID S FLAGS WAITCOMMAND * 0 -1 0 0 7 0x200 swapper -- nick * Nick H. wrote on Jan 26, 2014 [21:23, +0800] Date: Sun, 26 Jan 2014 21:23:03 +0800 (SGT) From: Nick H. nh.mailingl...@beo.im To: misc@openbsd.org Subject: OpenBSD 5.4 as guest under VMWare Server 2 install fails Hello, I tried installing OpenBSD 5.4 as a guest OS in a VMWare Server 2 (yes, old platform) and it fails early on during the install process. Since the VMWare console doesn't allow me to copypaste the output, I took two screenshots (as per attachment but not sure if this lost support attachments). Anyway, the final message on screen is: cpu0 at mainbus0: apid 0 (boot processor) fatal protection fault (4) in supervisor mode trap type 4 code 0 eip d04a4968 cs eflags 10202 cr2 0 cpl 0 panic: trap type 4, code=0, pc=d04a4968 I first noticed this behavior when I tried installing OpenBSD 5.3. I then tried to install OpenBSD 5.2, which worked like a charm. The dmesg of the running OpenBSD 5.2 under VMWare Server 2 follows at the end. I am wondering if you could give me pointers as to why the install fails. -- nick +++dmesg of OpenBSD 5.2 OpenBSD 5.2 (GENERIC) #278: Wed Aug 1 10:04:16 MDT 2012 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz (GenuineIntel 686-class) 2.31 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,NXE,LONG,SSE3,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,LAHF real mem = 536342528 (511MB) avail mem = 516718592 (492MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 07/29/08, BIOS32 rev. 0 @ 0xfd780, SMBIOS rev. 2.4 @ 0xe4010 (45 entries) bios0: vendor Phoenix Technologies LTD version 6.00 date 07/29/2008 bios0: VMware, Inc. VMware Virtual Platform acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP BOOT APIC MCFG SRAT acpi0: wakeup devices PCI0(S3) USB_(S1) P2P0(S3) S1F0(S3) S2F0(S3) S3F0(S3) S4F0(S3) S5F0(S3) S6F0(S3) S7F0(S3) S8F0(S3) S9F0(S3) Z00P(S3) Z00Q(S3) Z00R(S3) Z00S(S3) Z00T(S3) Z00U(S3) Z00V(S3) Z00W(S3) Z00X(S3) Z00Y(S3) Z00Z(S3) Z010(S3) Z011(S3) Z012(S3) Z013(S3) Z014(S3) Z015(S3) Z016(S3) Z017(S3) Z018(S3) Z019(S3) Z01A(S3) Z01B(S3) P2P1(S3) S1F0(S3) S2F0(S3) S3F0(S3) S4F0(S3) S5F0(S3) S6F0(S3) S7F0(S3) S8F0(S3) S9F0(S3) Z00P(S3) Z00Q(S3) Z00R(S3) Z00S(S3) Z00T(S3) Z00U(S3) Z00V(S3) Z00W(S3) Z00X(S3) Z00Y(S3) Z00Z(S3) Z010(S3) Z011(S3) Z012(S3) Z013(S3) Z014(S3) Z015(S3) Z016(S3) Z017(S3) Z018(S3) Z019(S3) Z01A(S3) Z01B(S3) P2P2(S3) S1F0(S3) S2F0(S3) S3F0(S3) S4F0(S3) S5F0(S3) S6F0(S3) S7F0(S3) S8F0(S3) S9F0(S3) Z00P(S3) Z00Q(S3) Z00R(S3) Z00S(S3) Z00T(S3) Z00U(S3) Z00V(S3) Z00W(S3) Z00X(S3) Z00Y(S3) Z00Z(S3) Z010(S3) Z011(S3) Z012(S3) Z013(S3) Z014(S3) Z015(S3) Z016(S3) Z017(S3) Z018(S3) Z019(S3) Z01A(S3) Z01B(S3) P2P3(S3) S1F0(S3) S2F0(S3) S3F0(S3) S4F0(S3) S5F0(S3) S6F0! (S3) S7F0(S3) S8F0(S3) S9F0(S3) Z00P(S3) Z00Q(S3) Z00R(S3) Z00S(S3) Z00T(S3) Z00U(S3) Z00V(S3) Z00W(S3) Z00X(S3) Z00Y(S3) Z00Z(S3) Z010(S3) Z011(S3) Z012(S3) Z013(S3) Z014(S3) Z015(S3) Z016(S3) Z017(S3) Z018(S3) Z019(S3) Z01A(S3) Z01B(S3) PE40(S3) S1F0(S3) PE50(S3) S1F0(S3) PE60(S3) S1F0(S3) PE70(S3) S1F0(S3) PE80(S3) S1F0(S3) PE90(S3) S1F0(S3) PEA0(S3) S1F0(S3) PEB0(S3) S1F0(S3) PEC0(S3) S1F0(S3) PED0(S3) S1F0(S3) PEE0(S3) S1F0(S3) PE41(S3) S1F0(S3) PE42(S3) S1F0(S3) PE43(S3) S1F0(S3) PE44(S3) S1F0(S3) PE45(S3) S1F0(S3) PE46(S3) S1F0(S3) PE47(S3) S1F0(S3) PE51(S3) S1F0(S3) PE52(S3) S1F0(S3) PE53(S3) S1F0(S3) PE54(S3) S1F0(S3) PE55(S3)
Re: The unknown in i386-unknown-openbsd5.4
On Sat, Feb 01, 2014 at 19:11, Adam Jensen wrote: It shows up in so many places, even my email headers: X-Mailer:Sylpheed 3.2.0 (GTK+ 2.24.20; i386-unknown-openbsd5.4) To the uninitiated masses, it might seem like the system was sloppily configured or in some other way the admin was confused. Well, that's true. If the admin cares about the value in X-Mailer, the admin should configure a better value.
Re: The unknown in i386-unknown-openbsd5.4
On Sat, 01 Feb 2014 22:06:47 -0500 Ted Unangst t...@tedunangst.com wrote: Well, that's true. If the admin cares about the value in X-Mailer, the admin should configure a better value. Patching the various occurrences of this string might be more cumbersome than changing the way it's generated and used throughout the system, but I get your gist.
Re: OpenBSD 5.4 as guest under VMWare Server 2 install fails
On Sat, Feb 1, 2014 at 6:49 PM, Nick H. nh.mailingl...@beo.im wrote: Further to my earlier very basic erro description, I was able to colelct some more debug messages from when the Kernel panic occurs. Could you give me some pointers of how to possibly fix this or how to file a bug report. Thanks. Here is the trace output: cpu_init(d0b73880,0,30,d0a466a0,0) at cpu_init+0x51 That corresponds to the lcr4() in this: if (ci-ci_feature_sefflags SEFF0EBX_SMEP) lcr4(rcr4() | CR4_SMEP); and indeed, that code was added in 5.3, support for the SMEP CPU extension. It appears that that ancient version of vmware had that bit set (incorrectly) in its cpuid emulation. Last I checked, vmware 2 had reached its end-of-support period *YEARS* ago. Wasting time on a broken and no longer supported emulator would be just that: a waste of time. Good luck. Philip guenther
Re: The unknown in i386-unknown-openbsd5.4
On Sat, Feb 01, 2014 at 07:11:25PM -0500, Adam Jensen wrote:
On Sat, 1 Feb 2014 00:52:31 + (UTC)
na...@mips.inka.de (Christian Weisgerber) wrote:
FreeBSD is more playful: It has ${ARCH}-portbld-freebsd
${OSREL} in its ports tree and ...
I wonder how the FreeBSD guys changed it without breaking every
gnu-configure script in existence.
You just need to create a few tens of thousands of patches to fix the
mess and send everything to upstream.
It shows up in so many places, even my email headers:
X-Mailer:Sylpheed 3.2.0 (GTK+ 2.24.20; i386-unknown-openbsd5.4)
To the uninitiated masses, it might seem like the system was
sloppily configured or in some other way the admin was confused.
--
Juan Francisco Cantero Hurtado http://juanfra.info
Re: The unknown in i386-unknown-openbsd5.4
On 01/02/14 11:18 PM, Adam Jensen wrote: On Sat, 01 Feb 2014 22:06:47 -0500 Ted Unangst t...@tedunangst.com wrote: Well, that's true. If the admin cares about the value in X-Mailer, the admin should configure a better value. Patching the various occurrences of this string might be more cumbersome than changing the way it's generated and used throughout the system, but I get your gist. The way it is generated can be changed very easily and contrary to the previous comment it doesn't break all autoconf scripts that use the triplet. But there is no purpose for doing so. OMG something I don't understand, must... fiddle... with. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: The unknown in i386-unknown-openbsd5.4
On Sun, 02 Feb 2014 00:23:18 -0500 Brad Smith b...@comstyle.com wrote: The way it is generated can be changed very easily and contrary to the previous comment it doesn't break all autoconf scripts Will you share your technique? that use the triplet. But there is no purpose for doing so. OMG something I don't understand, must... fiddle... with. There's an aesthetic nicety that comes from having everything well organized and thoughtfully labeled. But I agree with you that there is no immediate functional gain.
Re: No USB devices recognized (HP box, 5.4-stable)
On Mon, Dec 23, 2013 at 11:36:03PM -0700, howard eisenberger wrote: On Fri, Dec 20, 2013 at 06:21:03PM +, Neil Hughes wrote: I've got an HP dx5150MT minitower of 2006 vintage, and with OpenBSD 5.4 stable no USB devices are recognized whether they're attached before or after boot. No console message, nothing appended to dmesg. Same thing happens whether I use amd64 MP or SP kernel - I'm about to send dmesg reports but thought it worth querying here at the same time. On the same machine USB works fine with XP. A lost cause? ohci0 at pci0 dev 19 function 0 ATI SB400 USB rev 0x00: apic 2 int 18, version 1.0, legacy support ohci1 at pci0 dev 19 function 1 ATI SB400 USB rev 0x00: apic 2 int 18, version 1.0, legacy support ehci0 at pci0 dev 19 function 2 ATI SB400 USB2 rev 0x00: apic 2 int 18 With 5.4 on my dx5150, same onboard USB: APIC enabled in BIOS - nothing detected. APIC disabled in BIOS - USB pen drive detected, but not USB/IDE external laptop drive. AFAIK, onboard USB works fine with Linux. I just got back to this and, to be fair, with Debian Linux USB pen drive is detected, but not USB/IDE external laptop drive with APIC enabled or disabled in BIOS. The same external drive with the same USB/IDE adapter is detected and works with 5.4 on a couple of other machines with different USB chips. So, it looks like both Linux and OpenBSD have a problem with the ATI SB400 USB. I ended up disabling the onboard USB and adding a NEC USB PCI card, which seems to work fine with OpenBSD 5.4 Regards, Howard E.
