problem setting inet6 route
Hi
I rented a server from Hetzner where I installed OpenBSD 5.1. Hetzner also
provides IPv6 but somehow with a strange setup. I got something like the
following from them:
Gateway Address: 2001:db8:1:1110::1/64
Subnet I can use: 2001:db8:1:/64
If I now assign for example 2001:db8:1::1/64 to the interface on my
server it doesn't let me set the default gateway becaus it's not in the
same subnet:
openbsd# ifconfig rl0 inet6 2001:db8:1::/64
openbsd# route add -inet6 default 2001:db8:1:1110::1
route: writing to routing socket: Network is unreachable
add net default: gateway 2001:db8:1:1110::1: Network is unreachable
For Linux they give these instructions:
linux# ip route add 2001:db8:1:1110::1 dev eth0
linux# ip route add default via 2001:db8:1:1110::1
I tried:
openbsd# route add -inet6 -iface 2001:db8:1:1110::1 2001:db8:1:::1
openbsd# route add -inet6 default 2001:db8:1:1110::1
But now it's not possible to ping6 2001:db8:1:1110::1 or any other IPv6
address.
In pf.conf I have the following rules and pflog shows no blocked
icmp6 traffic:
block in log
pass out log quick
block log quick from sshguard
pass log inet proto icmp icmp-type { echoreq, unreach }
pass log inet6 proto icmp6
pass in log on egress proto {tcp udp} to any port domain
pass in log on egress proto tcp to any port ssh
How can I make this work?
Remi
Re: vpn access for Macos, windows clients
Thank you for this first reply. So, the only way is to use OpenBSD-current with npppd, and there's no other way to do it ? Simon A. - Original Message - From: Johan Beisser Sent: 08/31/12 02:22 AM To: Simon ALFRED Subject: Re: vpn access for Macos, windows clients On Thu, Aug 30, 2012 at 12:05 PM, Simon ALFRED simonalf...@mail.com wrote: Hi everyone, I have a firewall at work running OpenBSD 5.1-RELEASE I need to make a vpn access for outside clients, they use MacOs 10.6 and Windows XP/7. I can't add thrid software on theses clients. So i need a VPN Server on the OpenBSD Gateway that can works natively with MacOS and Windows clients. I've had very good success with npppd's L2TP VPN on OpenBSD snapshots. Due to it not being linked, it's not built by default. With OpenBSD 5.1, I found an odd keepalive failure that prevented my tunnel from staying active for more than 10 minutes. I do have odd issues with my old-as-dirt soekris crashing, but I blame memory exhaustion more than running beta versions of OpenBSD. A couple other oddities you'll encounter deal with routing (if you don't want to route *all* traffic to the VPN), and the lack of any real documentation outside of the code itself, and no alternative ways to authentica! te other than RADIUS and a flat file. Do a quick search of the archives for NPPPD and check out a brief article on undeadly giving some overview. Then read the code: http://www.openbsd.org/cgi-bin/cvsweb/src/usr.sbin/npppd/ I know TheGreenBow works great with isakmpd, but here we can't add software on clients. Is it possible to make a pptp server ? npppd does support PPTP as well. I'd suggest using L2TP instead, though. Any idea ?
Re: problem setting inet6 route
On 2012-08-31, Remi Locherer remi.loche...@relo.ch wrote: I rented a server from Hetzner where I installed OpenBSD 5.1. Hetzner also provides IPv6 but somehow with a strange setup. I got something like the following from them: Gateway Address: 2001:db8:1:1110::1/64 Subnet I can use: 2001:db8:1:/64 If I now assign for example 2001:db8:1::1/64 to the interface on my server it doesn't let me set the default gateway becaus it's not in the same subnet: openbsd# ifconfig rl0 inet6 2001:db8:1::/64 openbsd# route add -inet6 default 2001:db8:1:1110::1 route: writing to routing socket: Network is unreachable add net default: gateway 2001:db8:1:1110::1: Network is unreachable For Linux they give these instructions: linux# ip route add 2001:db8:1:1110::1 dev eth0 linux# ip route add default via 2001:db8:1:1110::1 I tried: openbsd# route add -inet6 -iface 2001:db8:1:1110::1 2001:db8:1:::1 openbsd# route add -inet6 default 2001:db8:1:1110::1 But now it's not possible to ping6 2001:db8:1:1110::1 or any other IPv6 address. No idea if it will work, but you could try something like this route add -inet6 -mpath default -ifp rl0 2001:db8:1:1110::1
Re: hostname.if: preventing IPV4 assignment
On 2012-08-30, Scott 8f27e...@gmail.com wrote: vis-a-vis /etc/hostname.if, where the 'if' is em1 and is a real interface that is aggregating several VLANs (as em1 is connected to a Cisco L2 switch). Since the each of the VLAN interface has its own, and topology relevant, IPV4 address, we don't want or need em1 itself to have an IP. Our /etc/hostname.em1 is as follows, START -inet mtu 1518 -inet6 group inside up END - the default is to have no IPv4 address, no need to do anything there, so just try -inet6 mtu 1518 group inside up (but note, you don't need to set mtu manually if this is just standard 802.1q vlans, only if you're doing something special like svlan(4) q-in-q tag stacking). when I have an interface just hosting vlans I usually just have 'up' in hostname.if, no IPv4 address is assigned. -inet is invalid syntax. 'em1' is CORRECTLY absent an IPV6 address (NOINET6); however, it always -- and UNDESIRABLY -- comes up with an IPV4 address in the 8.n.n.n/8 range. (Side note: No idea why it gets an IPV4 8/8 as that isn't in our topology anywhere and it becomes problematic at times to the routing table.) if you want to track down why this happens, you might like to add 'echo running: $cmd' before the 'eval $cmd' line in /etc/netstart and look at the output.
Re: Smtpd disposable addresses
On 2012-08-31, ml+helloke...@extensibl.com ml+helloke...@extensibl.com wrote: On Thu, Aug 30, 2012 at 10:32:57PM +0100, Kevin Chadwick wrote: You specify a character usually defaulting to - as a seperator and then acceptable addresses bob bob- pete- for a domain like bobszz.net so bobszz.net can receive mail to b...@bobszz.net bob-canitrust...@bobszz.net bob-groupedascompanyc...@bobszz.net bob-anyth...@bobszz.net pete-anyth...@bobszz.net Hi Kevin, I think you can use '+' character instead (bob+canitrust...@bobszz.net, bob+groupedascompanyc...@bobszz.net), can't you? Depends on the MTA, and if smtpd supports this it's not obvious in the config file. Also + doesn't work with many web-forms that validate the address syntax... :/
Re: wol for nfe
On 08/30/12 10:41, Stefan Sperling wrote: On Wed, Aug 29, 2012 at 07:53:54AM -0700, russell wrote: finally even though it did not work out for me. ( my nics were nfe(4) which has no WOL bits in OBSD, I blame nvidia, those secretive assholes.) Yes, but they cannot hide their secrets forever ;) The nfe driver already knows the which register to poke, and in fact it currently attempts to enable WOL by default. However, it always shuts down the receive engine when the interface goes down which prevents wol from working. The diff below disables wol by default and makes it configurable. Works for me with: nfe0 at pci0 dev 5 function 0 NVIDIA nForce3 LAN rev 0xa2: apic 1 int 9, address 00:11:d8:90:b3:56 rlphy0 at nfe0 phy 1: IP101 10/100 PHY, rev. 4 Can you please test if this works for you, too? snip diff Very cool, like Christmas came early this year. Sorry for the wait, caught me with my metaphorical trousers down much to my shame I did not have a build environment set up. I can now confirm the patch does work.(I tested with -current) before: nfe0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 hwfeatures=37CSUM_IPv4,CSUM_TCPv4,CSUM_UDPv4,VLAN_MTU,VLAN_HWTAGGING lladdr 00:e0:81:77:e8:78 priority: 0 groups: netboot egress media: Ethernet autoselect (1000baseT full-duplex) status: active inet 192.168.16.11 netmask 0xff00 broadcast 192.168.16.255 after: nfe0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 hwfeatures=8037CSUM_IPv4,CSUM_TCPv4,CSUM_UDPv4,VLAN_MTU,VLAN_HWTAGGING,WOL lladdr 00:e0:81:77:e8:78 priority: 0 groups: netboot egress media: Ethernet autoselect (1000baseT full-duplex) status: active inet 192.168.16.11 netmask 0xff00 broadcast 192.168.16.255 I can set and disable the WOL flag with wol and -wol When set, i can turn off machine and turn it back on with arp -W This is great, Thank you very much.
Re: Smtpd disposable addresses
On Fri, 31 Aug 2012 13:30:05 +1200 ml+helloke...@extensibl.com wrote: You specify a character usually defaulting to - as a seperator and then acceptable addresses bob bob- pete- for a domain like bobszz.net so bobszz.net can receive mail to b...@bobszz.net bob-canitrust...@bobszz.net bob-groupedascompanyc...@bobszz.net bob-anyth...@bobszz.net pete-anyth...@bobszz.net Hi Kevin, I think you can use '+' character instead (bob+canitrust...@bobszz.net, bob+groupedascompanyc...@bobszz.net), can't you? Regards, Alex Yeah, thanks Yahoo mails take a while to hit the list so I sent another straight to Giles to save him Googling, he responded with this. ___ With OpenSMTPD, gilles+foo...@openbsd.org will automagically strip foobar and if you're setup to deliver to maildir it will even create a directory foobar in your Maildir ___
Re: Ports security updates in 5.1 or 5.2
On Thu, Aug 30, 2012 at 10:21:35AM +0200, Sébastien Marie wrote: On Wed, Aug 29, 2012 at 09:34:22PM +0200, Patrick Lamaiziere wrote: Le Wed, 29 Aug 2012 09:59:46 +0200, Sebastien Marie semarie-open...@latrappe.fr a écrit : Hello, I currently follow STABLE branch for openbsd (and so, for ports too), which is OPENBSD_5_1. But, I saw that the last security updates for ports go to OPENBSD_5_2 and not to OPENBSD_5_1. Any examples ? The probleme may not be present in 5.1. databases/postgresql version 9.1.4 (in OPENBSD_5_1) is vulnerable to CVE-2012-3488 and CVE-2012-3489 CVE-2012-3488 : insecure use of xslt (xslt is in contrib, so need activation) CVE-2012-3489 : insecure use of libxml2 (XXE possible) OPENBSD_5_2 has upgraded from 9.1.4 to 9.1.5 I have an update for this and I will commit it asap (lack of time..) -- Pierre-Emmanuel André pea at raveland.org GPG key: 0x7AE329DC
Re: setting WOL for Realtek 8168
On Thu, Aug 30, 2012 at 07:58:07PM -0500, Ed Ahlsen-Girard wrote: I'm all good now, actually - apparently wol has to be reset by rc.local each startup. Yes, or alternatively add the 'wol' keyword to '/etc/hostname.re0'. The option doesn't stick across reboots.
Líderes dentro y Fuera de la Oficina, Germán Silva! 2790425
2790425 [IMAGE] Foro Empresarial 3era Edición Liderazgo Vanguardia Empresarial 5 Expositores acompañándolo y brindado las estrategias y herramientas necesarias para superar con Éxito los Nuevos Retos. Presentación Exclusiva: 28 de Septiembre Ciudad de México. Líder del deporte Nacional German Silva / Dr. Guillermo Carmona / Sergio Villalobos / Mónica Herrero / Lev. Castelán presentes. Líder no es mandar, es saber servir y dirigir a los demás con propósito. Solicite MAYORES informes o inscríbase ahora! Por favor responda este e-mail escribiendo los datos siguientes: Empresa: Nombre: Teléfono: Email: Número de Interesados: En breve recibirá temario, reseña de expositor y tarifas. Si lo prefiere comuníquese a los teléfonos donde con gusto uno de nuestros ejecutivos le atenderá. Teléfonos: (0133) 8851-2365, (0133) 8851-2741 con más de 10 líneas. Pms Capacitación Efectiva de México es una empresa Registrada ante la STPS Trabajamos con expertos en la materia para poder brindar herramientas tácticas, vanguardistas y de fácil aplicación. Síguenos en Twitter@pmscapacitacion o bien en Facebook PMS de México Tip del día! Planea: Evita los problemas de vivir al momento y crear estrategias de último momento. Planea tus objetivos, elige un rumbo y mantente. Anticipa posibles causales de emergencia y diseña planes de contingencia previos que permitan conocer rutas a seguir. Esto ayudará a crear metas en su compañía, compartirlas con su equipo y anticipar obstáculos. Copyright (C) 2011, PMS Capacitación Efectiva de México S.C. Derechos Reservados. E-Mail MARKETING SERVICE POWERED BY MEDIAMKTOOLS. Este Mensaje ha sido enviado a misc@openbsd.org como usuario de Pms de México o bien un usuario le refirió para recibir este boletín. Como usuario de Pms de México, en este acto autoriza de manera expresa que Pms de México le puede contactar vía correo electrónico u otros medios. ALTO, si en esta ocasión la información recibida no fue de su interés pero desea recibir información personalizada en relación a otros temas favor de indicarlo. Si usted ha recibido este mensaje por error, haga caso omiso de el y de antemano una sincera disculpa por la molestia, reporte su cuenta respondiendo este correo con el subject BAJAFORO3 Unsubscribe to this mailing list, reply a blank message with the subject UNSUBSCRIBE BAJAFORO3 Tenga en cuenta que la gestión de nuestras bases de datos es de suma importancia para nosotros y no es intención de la empresa la inconformidad del receptor, nuestra intención es promover herramientas de utilidad para el [demime 1.01d removed an attachment of type image/jpeg which had a name of image001.jpg]
Re: Smtpd disposable addresses
On 31/08/2012, at 9:30, ml+helloke...@extensibl.com wrote: I think you can use '+' character instead (bob+canitrust...@bobszz.net, bob+groupedascompanyc...@bobszz.net), can't you? Tried it lately? Every other website incorrectly reinvents is this a valid email address logic. It's just a trivial regex, amirite? :-/ Gmail supports +foo syntax, but the number of times I've actually successfully used an address like that is vanishingly small - is a much better separator IMHO John
Re: problem setting inet6 route
(I rearranged your email: provider info at the top, your actions at the bottom.) Le 2012-08-31 03:19, Remi Locherer a écrit : I rented a server from Hetzner where I installed OpenBSD 5.1. Hetzner also provides IPv6 but somehow with a strange setup. I got something like the following from them: Gateway Address: 2001:db8:1:1110::1/64 Subnet I can use: 2001:db8:1:/64 For Linux they give these instructions: linux# ip route add 2001:db8:1:1110::1 dev eth0 linux# ip route add default via 2001:db8:1:1110::1 I would understand this to mean: a---[You]---b---[Them]---Internet a = 2001:db8:1:::/64 b = 2001:db8:1:1110::/64 You on a = 2001:db8:1:::whatever You on b = 2001:db8:1:1110::whatever except 1 Them on b = 2001:db8:1:1110::1 If you don't need a, don't configure it. If I now assign for example 2001:db8:1::1/64 to the interface on my server it doesn't let me set the default gateway becaus it's not in the same subnet: openbsd# ifconfig rl0 inet6 2001:db8:1::/64 openbsd# route add -inet6 default 2001:db8:1:1110::1 route: writing to routing socket: Network is unreachable add net default: gateway 2001:db8:1:1110::1: Network is unreachable I tried: openbsd# route add -inet6 -iface 2001:db8:1:1110::1 2001:db8:1:::1 openbsd# route add -inet6 default 2001:db8:1:1110::1 But now it's not possible to ping6 2001:db8:1:1110::1 or any other IPv6 address. Yeah that's all wrong. Assuming that rl0 is on network b, try: ifconfig rl0 inet6 2001:db8:1:1110::2 route add -inet6 default 2001:db8:1:1110::1 Simon
（9月21日深圳）科技项目专项资金申报暨企业知识产权管理战略会议通知
22:02:48 [demime 1.01d removed an attachment of type application/octet-stream which had a name of =?utf-8?B?56eR5oqA6K6h5YiS6aG555uu44CB5LiT6aG557uP6LS5566h55CG77yIOeaciDIx5pel5rex5ZyzKS5kb2M=?=]
Cost of malloc options
A couple of weeks ago, I ran a bunch of make builds (ncpu=4 amd64) with different malloc() options enabled. I don't want to spawn a discussion, but for anybody who's curious, and for the archives, here are the results: 36m17.68s real47m33.50s user26m49.97s system F 39m34.31s real48m22.50s user35m57.48s system G 38m20.87s real48m40.61s user31m36.31s system J 42m56.74s real64m19.61s user25m51.23s system FG 40m59.86s real49m11.18s user39m12.52s system FGJ 49m0.12s real 68m17.34s user39m34.63s system S 55m14.16s real61m29.02s user71m24.59s system -- Christian naddy Weisgerber na...@mips.inka.de
Re: Cost of malloc options
On Fri, Aug 31, 2012 at 02:08:39PM +, Christian Weisgerber wrote: A couple of weeks ago, I ran a bunch of make builds (ncpu=4 amd64) with different malloc() options enabled. I don't want to spawn a discussion, but for anybody who's curious, and for the archives, here are the results: 36m17.68s real47m33.50s user26m49.97s system F 39m34.31s real48m22.50s user35m57.48s system G 38m20.87s real48m40.61s user31m36.31s system J 42m56.74s real64m19.61s user25m51.23s system FG40m59.86s real49m11.18s user39m12.52s system FGJ 49m0.12s real 68m17.34s user39m34.63s system S 55m14.16s real61m29.02s user71m24.59s system I kind of wonder about similar data for full bulk builds. Of course, I know a part of the answer: bulk with S will be shorter than expected thanks to the fallout in large shit such as mono...
Re: problem setting inet6 route
On Fri, Aug 31, 2012 at 09:22:06AM +, Stuart Henderson wrote: On 2012-08-31, Remi Locherer remi.loche...@relo.ch wrote: I rented a server from Hetzner where I installed OpenBSD 5.1. Hetzner also provides IPv6 but somehow with a strange setup. I got something like the following from them: Gateway Address: 2001:db8:1:1110::1/64 Subnet I can use: 2001:db8:1:/64 If I now assign for example 2001:db8:1::1/64 to the interface on my server it doesn't let me set the default gateway becaus it's not in the same subnet: openbsd# ifconfig rl0 inet6 2001:db8:1::/64 openbsd# route add -inet6 default 2001:db8:1:1110::1 route: writing to routing socket: Network is unreachable add net default: gateway 2001:db8:1:1110::1: Network is unreachable For Linux they give these instructions: linux# ip route add 2001:db8:1:1110::1 dev eth0 linux# ip route add default via 2001:db8:1:1110::1 I tried: openbsd# route add -inet6 -iface 2001:db8:1:1110::1 2001:db8:1:::1 openbsd# route add -inet6 default 2001:db8:1:1110::1 But now it's not possible to ping6 2001:db8:1:1110::1 or any other IPv6 address. No idea if it will work, but you could try something like this route add -inet6 -mpath default -ifp rl0 2001:db8:1:1110::1 Bad adivece. Hetzner gave the wrong gateway or the wrong network. It is funny that the Linux example they give is using proper network numbers. In short, the gateway MUST be part of a connected route (network configured on the interface) because ND or ARP for INET is needed to figure out the MAC address to talk to that host on the L2 network. The only excpetion are point to point interfaces but those have a destination IP on the interface and don't need a L2 address resolution protocol. -- :wq Claudio
Re: smtpd queue encryotion
Kurt Mosiejczuk k...@se.rit.edu wrote: Blowfish is older, not standardized, and hasn't received the attention from the cryptographic community that AES has. Blowfish isn't standardized? Not being chosen as a standard doesn't mean that everyone is using an incompatible version of something. And I meant the former, not the latter. And AES-128 (and only that flavor of AES, so far) has a crack making decrypting it significantly quicker. News to me. Reference? (You are probably confusing this with the related-key attacks on AES-192 and AES-256.) Speedwise, Blowfish and AES are similar, My understanding is that actually, blowfish is significantly slower. Go and run openssl speed aes-128-cbc bf-cbc on a number of machines and architectures. There is quite a bit of variation. -- Christian naddy Weisgerber na...@mips.inka.de
Re: problem setting inet6 route
On Fri, Aug 31, 2012 at 09:22:06AM +, Stuart Henderson wrote: On 2012-08-31, Remi Locherer remi.loche...@relo.ch wrote: I rented a server from Hetzner where I installed OpenBSD 5.1. Hetzner also provides IPv6 but somehow with a strange setup. I got something like the following from them: Gateway Address: 2001:db8:1:1110::1/64 Subnet I can use: 2001:db8:1:/64 If I now assign for example 2001:db8:1::1/64 to the interface on my server it doesn't let me set the default gateway becaus it's not in the same subnet: openbsd# ifconfig rl0 inet6 2001:db8:1::/64 openbsd# route add -inet6 default 2001:db8:1:1110::1 route: writing to routing socket: Network is unreachable add net default: gateway 2001:db8:1:1110::1: Network is unreachable For Linux they give these instructions: linux# ip route add 2001:db8:1:1110::1 dev eth0 linux# ip route add default via 2001:db8:1:1110::1 I tried: openbsd# route add -inet6 -iface 2001:db8:1:1110::1 2001:db8:1:::1 openbsd# route add -inet6 default 2001:db8:1:1110::1 But now it's not possible to ping6 2001:db8:1:1110::1 or any other IPv6 address. No idea if it will work, but you could try something like this route add -inet6 -mpath default -ifp rl0 2001:db8:1:1110::1 Unfortunately this does not work. With this the link local address is used: openbsd# sysctl net.inet6.ip6.multipath=1 net.inet6.ip6.multipath: 0 - 1 openbsd# route add -inet6 -mpath default -ifp rl0 2001:db8:1:1110::1 add net default: gateway 2001:db8:1:1110::1 openbsd# ping6 2001:db8:1:1110::1 PING6(56=40+8+8 bytes) 2001:db8:1:::78 -- 2001:db8:1:1110::1 ping6: sendmsg: No route to host ping6: wrote 2001:db8:1:1110::1 16 chars, ret=-1 ^C --- 2001:db8:1:1110::1 ping6 statistics --- 1 packets transmitted, 0 packets received, 100.0% packet loss openbsd# route -n get -inet6 2001:db8:1:1110::1 route to: 2001:db8:1:1110::1 destination: :: mask: default gateway: 2001:db8:1:1110::1 interface: rl0 if address: fe80::2e0:4cff:fec2:697c%rl0 priority: 8 (static) flags: UP,GATEWAY,DONE,STATIC use mtuexpire 24 0 0 root@typhoon#
Tecnicas Super Efectivas de Cobranza
Técnicas Súper Efectivas de Cobranza Salón Virtual ONLINE este 04 de Septiembre de 2012. ¡Descubra el modo rápido, fácil y legal de recuperar su dinero de cuentas atrasadas! Usted conocerá docenas de secretos que las empresas más efectivas usan para que los deudores paguen rápido, convierta el teléfono en su instrumento más poderoso de recuperación de cartera, cómo manejar cada excusa, cómo tratar con gente enojada y abusiva. Entre los puntos a tratar se incluyen: - Cómo manejar excusas, mentiras y quejas de los deudores - Calme a clientes furiosos e irracionales con técnicas que trabajan como un encanto - Mantenga su organización fuera de problemas, sabiendo exactamente cuáles son sus derechos y límites legales - Haga que ingrese más dinero con sus cartas de cobranza - Mantenga el control de la conversación telefónica cuando los deudores tratan de conducirlo por otro lado - Sepa exactamente cuándo y cómo usted debería considerar la demanda judicial en cuentas atrasadas. Lo más importante: Usted podrá cursar este Seminario ONLINE en Vivo desde la comodidad de su casa u oficina con todas las ventajas que le ofrece un curso presencial de manera remota, ¡y en tiempo real! Adquiera la información completa y sin compromiso, solo responda este correo con asunto -Deseo Folleto Tecnicas o Comuníquese al (507) 279-1083 / 279-0258 / 279-0887 - y a la brevedad lo recibirá! ESTE CORREO NO PUEDE SER CONSIDERADO INTRUSIVO YA QUE CUMPLE CON LAS POLÍTICAS ANTISPAM INTERNACIONALES Y LOCALES: Responda este correo con el Asunto borrar y automáticamente quedará fuera de nuestras listas. Este correo ha sido enviado a: misc@openbsd.org
Re: Cost of malloc options
On Fri, Aug 31, 2012 at 04:27:05PM +0200, Marc Espie wrote: On Fri, Aug 31, 2012 at 02:08:39PM +, Christian Weisgerber wrote: A couple of weeks ago, I ran a bunch of make builds (ncpu=4 amd64) with different malloc() options enabled. I don't want to spawn a discussion, but for anybody who's curious, and for the archives, here are the results: 36m17.68s real47m33.50s user26m49.97s system F 39m34.31s real48m22.50s user35m57.48s system G 38m20.87s real48m40.61s user31m36.31s system J 42m56.74s real64m19.61s user25m51.23s system FG 40m59.86s real49m11.18s user39m12.52s system FGJ 49m0.12s real 68m17.34s user39m34.63s system S 55m14.16s real61m29.02s user71m24.59s system I kind of wonder about similar data for full bulk builds. Of course, I know a part of the answer: bulk with S will be shorter than expected thanks to the fallout in large shit such as mono... See? S saves time! BTW, if you are wondering why S is slower than FGJ: S is FGJ plus a page size cache of zero. That means than any unused page is unmapped immediately. In normal operation, malloc maintains a set of pages for later re-use. -Otto
Re: problem setting inet6 route
On Fri, Aug 31, 2012 at 04:27:50PM +0200, Claudio Jeker wrote: On Fri, Aug 31, 2012 at 09:22:06AM +, Stuart Henderson wrote: On 2012-08-31, Remi Locherer remi.loche...@relo.ch wrote: I rented a server from Hetzner where I installed OpenBSD 5.1. Hetzner also provides IPv6 but somehow with a strange setup. I got something like the following from them: Gateway Address: 2001:db8:1:1110::1/64 Subnet I can use: 2001:db8:1:/64 If I now assign for example 2001:db8:1::1/64 to the interface on my server it doesn't let me set the default gateway becaus it's not in the same subnet: openbsd# ifconfig rl0 inet6 2001:db8:1::/64 openbsd# route add -inet6 default 2001:db8:1:1110::1 route: writing to routing socket: Network is unreachable add net default: gateway 2001:db8:1:1110::1: Network is unreachable For Linux they give these instructions: linux# ip route add 2001:db8:1:1110::1 dev eth0 linux# ip route add default via 2001:db8:1:1110::1 I tried: openbsd# route add -inet6 -iface 2001:db8:1:1110::1 2001:db8:1:::1 openbsd# route add -inet6 default 2001:db8:1:1110::1 But now it's not possible to ping6 2001:db8:1:1110::1 or any other IPv6 address. No idea if it will work, but you could try something like this route add -inet6 -mpath default -ifp rl0 2001:db8:1:1110::1 Bad adivece. Hetzner gave the wrong gateway or the wrong network. It is funny that the Linux example they give is using proper network numbers. They're realy giving customers a gateway address that is not part of the clients subnet. http://wiki.hetzner.de/index.php/Zusaetzliche_IP-Adressen#Root-Server (german website) In short, the gateway MUST be part of a connected route (network configured on the interface) because ND or ARP for INET is needed to figure out the MAC address to talk to that host on the L2 network. I found instructions for FreeBSD. There it is recommended to add static configuration for ndp. Since FreeBSD 8.3 they use /etc/rc.d/static_ndp for that. But I don't like it because I wouldn't reach my server when the routers mac changes. http://blog.vx.sk/archives/33-FreeBSD-Netzwerkkonfiguration-auf-Servern-von-Hetzner.html (german website) The only excpetion are point to point interfaces but those have a destination IP on the interface and don't need a L2 address resolution protocol. -- :wq Claudio
Re: Cost of malloc options
Marc Espie: 36m17.68s real S 55m14.16s real I kind of wonder about similar data for full bulk builds. That was my starting point, actually. I did a full bulk build with S and was startled by the slowdown. I forgot the exact numbers, but the relative difference was in the vicinity of the figures above. Of course, I know a part of the answer: bulk with S will be shorter than expected thanks to the fallout in large shit such as mono... Mono was the most significant breakage and that's fairly negligible overall. But I did end up with a tail end where libreoffice was the only port that was still building. Remind me to try this again during a slow part of the release cycle. -- Christian naddy Weisgerber na...@mips.inka.de
Re: problem setting inet6 route
On Fri, Aug 31, 2012 at 09:47:39AM -0400, Simon Perreault wrote: (I rearranged your email: provider info at the top, your actions at the bottom.) Le 2012-08-31 03:19, Remi Locherer a ?crit : I rented a server from Hetzner where I installed OpenBSD 5.1. Hetzner also provides IPv6 but somehow with a strange setup. I got something like the following from them: Gateway Address: 2001:db8:1:1110::1/64 Subnet I can use: 2001:db8:1:/64 For Linux they give these instructions: linux# ip route add 2001:db8:1:1110::1 dev eth0 linux# ip route add default via 2001:db8:1:1110::1 I would understand this to mean: a---[You]---b---[Them]---Internet Right except there is no network a. On [You] there is only one interface (rl0). a = 2001:db8:1:::/64 b = 2001:db8:1:1110::/64 You on a = 2001:db8:1:::whatever You on b = 2001:db8:1:1110::whatever except 1 Them on b = 2001:db8:1:1110::1 If you don't need a, don't configure it. If I now assign for example 2001:db8:1::1/64 to the interface on my server it doesn't let me set the default gateway becaus it's not in the same subnet: openbsd# ifconfig rl0 inet6 2001:db8:1::/64 openbsd# route add -inet6 default 2001:db8:1:1110::1 route: writing to routing socket: Network is unreachable add net default: gateway 2001:db8:1:1110::1: Network is unreachable I tried: openbsd# route add -inet6 -iface 2001:db8:1:1110::1 2001:db8:1:::1 openbsd# route add -inet6 default 2001:db8:1:1110::1 But now it's not possible to ping6 2001:db8:1:1110::1 or any other IPv6 address. Yeah that's all wrong. Assuming that rl0 is on network b, try: ifconfig rl0 inet6 2001:db8:1:1110::2 route add -inet6 default 2001:db8:1:1110::1 This works. But I have to figure out (ask Hetzner) if I'm the only customer they use 2001:db8:1:1110::/64 (I think so). Also over their web interface they only offer me to create DNS entries for 2001:db8:1:::/64.
Re: problem setting inet6 route
Le 2012-08-31 10:52, Remi Locherer a écrit : Gateway Address: 2001:db8:1:1110::1/64 Subnet I can use: 2001:db8:1:/64 For Linux they give these instructions: linux# ip route add 2001:db8:1:1110::1 dev eth0 linux# ip route add default via 2001:db8:1:1110::1 I would understand this to mean: a---[You]---b---[Them]---Internet Right except there is no network a. On [You] there is only one interface (rl0). So? It allows you to create such a network a. That's the point. You don't need a physical interface. There are many kinds of network interfaces that you can create yourself (loopback, tunnels, etc.). Have some imagination. a = 2001:db8:1:::/64 b = 2001:db8:1:1110::/64 You on a = 2001:db8:1:::whatever You on b = 2001:db8:1:1110::whatever except 1 Them on b = 2001:db8:1:1110::1 If you don't need a, don't configure it. If I now assign for example 2001:db8:1::1/64 to the interface on my server it doesn't let me set the default gateway becaus it's not in the same subnet: openbsd# ifconfig rl0 inet6 2001:db8:1::/64 openbsd# route add -inet6 default 2001:db8:1:1110::1 route: writing to routing socket: Network is unreachable add net default: gateway 2001:db8:1:1110::1: Network is unreachable I tried: openbsd# route add -inet6 -iface 2001:db8:1:1110::1 2001:db8:1:::1 openbsd# route add -inet6 default 2001:db8:1:1110::1 But now it's not possible to ping6 2001:db8:1:1110::1 or any other IPv6 address. Yeah that's all wrong. Assuming that rl0 is on network b, try: ifconfig rl0 inet6 2001:db8:1:1110::2 route add -inet6 default 2001:db8:1:1110::1 This works. But I have to figure out (ask Hetzner) if I'm the only customer they use 2001:db8:1:1110::/64 (I think so). If not it would mean there are multiple customers on network b. That would be somewhat unusual. Also over their web interface they only offer me to create DNS entries for 2001:db8:1:::/64. This make total sense. Just assign yourself an address from that prefix, e.g. on the loopback interface. Simon
Re: Ports security updates in 5.1 or 5.2
On Thu, Aug 30, 2012 at 06:52:15PM +, Stuart Henderson wrote: On 2012-08-30, Sébastien Marie semarie-open...@latrappe.fr wrote: I not used all pervious ports, and some are used in safe usage (like using postgresql ports, but not for server). It just a question to known what follow, in order to keep updated... really, in order to keep updated, following -current is a good policy. sure, updates in -current are more fresh ! but the investissement may be important, as it is required to upgrade the system before add or upgrade ports... I think I will consider installing -current on an external disk, in order to see and learn upgrade process (via snapshots) before definitively switch to -current on my laptop. Thanks Stuart. -- Sebastien Marie
Re: smtpd queue encryotion
Christian Weisgerber wrote: Kurt Mosiejczuk k...@se.rit.edu wrote: And AES-128 (and only that flavor of AES, so far) has a crack making decrypting it significantly quicker. News to me. Reference? (You are probably confusing this with the related-key attacks on AES-192 and AES-256.) That may be what happened. I remember thinking I'd throw in the reference when I was making my initial email, but decided not to. Now when I look for it, I'm mainly seeing those related-key attacks and the reduced-round attacks (that seem to effect all 3). I will humbly plead that my brain was addled from prepping for the return of students next week. Speedwise, Blowfish and AES are similar, My understanding is that actually, blowfish is significantly slower. Go and run openssl speed aes-128-cbc bf-cbc on a number of machines and architectures. There is quite a bit of variation. I did mention that it was in particular the key setup that was slow. Running the test like you suggested I am seeing variation. I think I may crawl back into my hole again. --Kurt
Re: vpn access for Macos, windows clients
On Aug 30, 2012, at 22:28, Simon ALFRED simonalf...@mail.com wrote: Thank you for this first reply. So, the only way is to use OpenBSD-current with npppd, and there's no other way to do it ? I can't say there's no other way to do it. PPTP is an option, via PoPToP. I just found that npppd worked better for me, and that it was much improved by the snapshot.
OpenBGPD 'enforce neighbor-as no' 'announce self' weirdness
Hi,
I don't know if this is a real bug, but at least it may be brought to
attention
that announce self without proper filtering may lead to some unexpected
behaviour.
When configured with enforce neighbor-as no (as for connection to an IXP
route server), OpenBGPD seems to accept UPDATE with empty AS_PATH and,
without
proper filtering, announce them back prepended with AS self to every
neighbor even if announce self as been set on the neighbor definition.
The following 3 BGP routers configuration was used for testing:
- rsix: 10.0.0.1/24 - AS65000, running exabgp 2.0.2
announcing 199.185.136.0/23 with empty AS_PATH
- ourself: 10.0.0.2/24 - AS65200, running stock OpenBGPD with OpenBSD 5.1
announcing 192.0.2.0/24 originating from AS65200
- transit: 10.0.0.3/24 - AS65300, running stock OpenBGPD with OpenBSD 5.1
announcing 0.0.0.0/0 originating from AS65300
the following OpenBGPD/exabgp configuration was used:
# rsix exabgp.conf
neighbor 10.0.0.2 {
description evil or goofy RS;
router-id 10.0.0.1;
local-address 10.0.0.1;
local-as 65000;
peer-as 65200;
static {
route 199.185.136.0/23 {
next-hop 10.0.0.1;
as-path [ ];
}
}
}
###
# ourself bgpd.conf
AS 65200
router-id 10.0.0.2
network 192.0.2.0/24
neighbor 10.0.0.1 {
descr IXP RS
announce self
remote-as 65000
enforce neighbor-as no
}
neighbor 10.0.0.3 {
descr transit provider
announce self
remote-as 65300
}
###
# transit bgpd.conf
AS 65300
router-id 10.0.0.3
network 0.0.0.0/0
neighbor 10.0.0.2 {
descr customer
announce self
remote-as 65200
}
###
After starting everything here are the bgpctl show rib outputs:
Seen by ourself:
flags destination gateway lpref med aspath origin
*0.0.0.0/010.0.0.3 100 0 65300 i
AI* 192.0.2.0/24 0.0.0.0100 0 i
*199.185.136.0/23 10.0.0.1 100 0 i
- 0.0.0.0/8 through our transit
- announce 192.0.2.0/24 as it's our network
- 199.185.136.0/23 with an empty AS_PATH injected via IXP RS (exabgp)
and seen by transit provider:
flags destination gateway lpref med aspath origin
AI* 0.0.0.0/00.0.0.0100 0 i
*192.0.2.0/24 10.0.0.2 100 0 65200 i
*199.185.136.0/23 10.0.0.1 100 0 65200 i
- announce default route to customer
- received AS65200 announce of 192.0.2.0/24, OK
- 199.185.136.0/23 looks like being originated by AS65200, despite using the
announce self statement, NOK
Here is also a patch attempt that fix this and drop sessions on empty
AS_PATH UPDATE from EBGP peers (I'm not a BGP expert and my C is a bit
rusty, so do not hesitate to drop this ;))
--- rde.c.orig 2012-08-22 18:12:48.0 +0200
+++ rde.c 2012-08-22 18:12:48.0 +0200
@@ -972,6 +972,17 @@
}
}
+ /* check for empty AS path with ebgp peers */
+ if (asp-flags F_ATTR_ASPATH
+ asp-aspath-ascnt == 0
+ peer-conf.ebgp ) {
+ log_peer_warnx(peer-conf, bad path,
+ path empty but not an IBGP peer);
+ rde_update_err(peer, ERR_UPDATE, ERR_UPD_ASPATH,
+ NULL, 0);
+ goto done;
+ }
+
rde_reflector(peer, asp);
}
--
Rémi Laurent
Phone: +352 26 10 30 61
General Support: supp...@conostix.com
GPG FP: 27F4 6810 2B0E 1AA0 CDAE 7C7B 3DC9 085A 0FA0 0601
[demime 1.01d removed an attachment of type application/pgp-signature which had
a name of signature.asc]
Re: problem setting inet6 route
Penned by Claudio Jeker on 20120831 9:27.50, we have: | On Fri, Aug 31, 2012 at 09:22:06AM +, Stuart Henderson wrote: | On 2012-08-31, Remi Locherer remi.loche...@relo.ch wrote: | I rented a server from Hetzner where I installed OpenBSD 5.1. Hetzner also | provides IPv6 but somehow with a strange setup. I got something like the | following from them: | | Gateway Address: 2001:db8:1:1110::1/64 | Subnet I can use: 2001:db8:1:/64 | | If I now assign for example 2001:db8:1::1/64 to the interface on my | server it doesn't let me set the default gateway becaus it's not in the | same subnet: | | openbsd# ifconfig rl0 inet6 2001:db8:1::/64 | openbsd# route add -inet6 default 2001:db8:1:1110::1 | route: writing to routing socket: Network is unreachable | add net default: gateway 2001:db8:1:1110::1: Network is unreachable | | For Linux they give these instructions: | linux# ip route add 2001:db8:1:1110::1 dev eth0 | linux# ip route add default via 2001:db8:1:1110::1 | | I tried: | openbsd# route add -inet6 -iface 2001:db8:1:1110::1 2001:db8:1:::1 | openbsd# route add -inet6 default 2001:db8:1:1110::1 | | But now it's not possible to ping6 2001:db8:1:1110::1 or any other IPv6 | address. | | No idea if it will work, but you could try something like this | | route add -inet6 -mpath default -ifp rl0 2001:db8:1:1110::1 | | | Bad adivece. Hetzner gave the wrong gateway or the wrong network. It is | funny that the Linux example they give is using proper network numbers. | | In short, the gateway MUST be part of a connected route (network | configured on the interface) because ND or ARP for INET is needed to | figure out the MAC address to talk to that host on the L2 network. | | The only excpetion are point to point interfaces but those have a | destination IP on the interface and don't need a L2 address resolution | protocol. | -- | :wq Claudio I hate exceptions. 1and1.com, I'm looking at you. This abomination has survived too many years: hostname.if: !route add -llinfo -iface -net 10.255.0.0/16 10.255.255.1 -ifp nfe0 inet 1.2.3.4 255.255.255.255 inet 1.2.4.3 255.255.255.255 ... mygate: 10.255.255.1 This forces the subnet to be on the interface so one can reach a router without having any IP's on the local system corresponding to the remote router IP. Thanks, -- Todd Fries .. t...@fries.net _ | \ 1.636.410.0632 (voice) | Free Daemon Consulting, LLC \ 1.405.227.9094 (voice) | http://FreeDaemonConsulting.com \ 1.866.792.3418 (FAX) | 2525 NW Expy #525, Oklahoma City, OK 73112 \ sip:freedae...@ekiga.net | ..in support of free software solutions. \ sip:4052279...@ekiga.net \\ 37E7 D3EB 74D0 8D66 A68D B866 0326 204E 3F42 004A http://todd.fries.net/pgp.txt
Re: vpn access for Macos, windows clients
I will try poptop, npppd. Thank you. Simon A. - Original Message - From: Johan Beisser Sent: 08/31/12 07:55 PM To: Simon ALFRED Subject: Re: vpn access for Macos, windows clients On Aug 30, 2012, at 22:28, Simon ALFRED simonalf...@mail.com wrote: Thank you for this first reply. So, the only way is to use OpenBSD-current with npppd, and there's no other way to do it ? I can't say there's no other way to do it. PPTP is an option, via PoPToP. I just found that npppd worked better for me, and that it was much improved by the snapshot.
Re: OpenBGPD 'enforce neighbor-as no' 'announce self' weirdness
On Fri, Aug 31, 2012 at 05:43:10PM +0200, Rémi Laurent wrote: Hi, I don't know if this is a real bug, but at least it may be brought to attention that announce self without proper filtering may lead to some unexpected behaviour. When configured with enforce neighbor-as no (as for connection to an IXP route server), OpenBGPD seems to accept UPDATE with empty AS_PATH and, without proper filtering, announce them back prepended with AS self to every neighbor even if announce self as been set on the neighbor definition. This is somewhat expected. announce self is nothing more then an implicit filter to only allow emtpy-as path out. It needs to be questioned if there should be not a implicit input filter that filters out empty AS pathes from ebgp hosts. It would also be possible to extend the announce self filter a bit to make sure the prefix originated via an ibgp session or was self generated. In the end you need to concede that a route server leaking empty AS paths to the wild is the bigger issue than OpenBGPD redistributing the info onwards. -- :wq Claudio
Re: problem setting inet6 route
* Remi Locherer (remi.loche...@relo.ch) wrote: Hi I rented a server from Hetzner where I installed OpenBSD 5.1. Hetzner also provides IPv6 but somehow with a strange setup. I got something like the following from them: Gateway Address: 2001:db8:1:1110::1/64 Subnet I can use: 2001:db8:1:/64 You could begin with actually getting real IPv6 addresses. 2001:DB8::/32 is a reserved prefix for use in documentation. http://tools.ietf.org/html/rfc3849 Cheers, /Joakim
Re: Dell Latitude E6420 issues - not working...
Works fine here. You just need to set the drive to AHCI in the BIOS OpenBSD 5.2-current (GENERIC.MP) #4: Thu Aug 30 18:12:48 MDT 2012 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 3fconfig_unit,memory_size,fixed_disk,invalid_time real mem = 8464576512 (8072MB) avail mem = 8216829952 (7836MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xf1d30 (106 entries) bios0: vendor Dell Inc. version A06 date 07/11/2011 bios0: Dell Inc. Latitude E6420 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC TCPA SSDT MCFG HPET BOOT SSDT SSDT DMAR SLIC acpi0: wakeup devices UAR1(S3) HDEF(S4) GLAN(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) RP07(S4) PXSX(S4) RP08(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEG2(S4) PEG3(S4) PXSX(S4) RP03(S4) EHC2(S1) EHCI(S1) LID_(S3) PBTN(S3) 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) Core(TM) i5-2520M CPU @ 2.50GHz, 2494.71 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,A ES,XSAVE,AVX,NXE,LONG,LAHF cpu0: 256KB 64b/line 8-way L2 cache cpu0: apic clock running at 99MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2494.34 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,A ES,XSAVE,AVX,NXE,LONG,LAHF cpu1: 256KB 64b/line 8-way L2 cache cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2494.34 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,A ES,XSAVE,AVX,NXE,LONG,LAHF cpu2: 256KB 64b/line 8-way L2 cache cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2494.34 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,A ES,XSAVE,AVX,NXE,LONG,LAHF cpu3: 256KB 64b/line 8-way L2 cache ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P1) acpiprt2 at acpi0: bus 1 (RP01) acpiprt3 at acpi0: bus 2 (RP02) acpiprt4 at acpi0: bus 9 (RP04) acpiprt5 at acpi0: bus -1 (RP05) acpiprt6 at acpi0: bus 10 (RP06) acpiprt7 at acpi0: bus -1 (RP07) acpiprt8 at acpi0: bus -1 (RP08) acpiprt9 at acpi0: bus -1 (PEG0) acpiprt10 at acpi0: bus -1 (PEG1) acpiprt11 at acpi0: bus -1 (PEG2) acpiprt12 at acpi0: bus -1 (PEG3) acpiprt13 at acpi0: bus 3 (RP03) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpicpu2 at acpi0: C3, C2, C1, PSS acpicpu3 at acpi0: C3, C2, C1, PSS acpitz0 at acpi0: critical temperature is 107 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: PBTN acpibtn2 at acpi0: SBTN acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT0 model DELL 9KN4418 serial 711 type LION oem SMP acpibat1 at acpi0: BAT1 not present acpibat2 at acpi0: BAT2 not present acpivideo0 at acpi0: VID_ acpivout0 at acpivideo0: LCD_ cpu0: Enhanced SpeedStep 2494 MHz: speeds: 2501, 2500, 2200, 2000, 1800, 1600, 1400, 1200, 1000, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel Core 2G Host rev 0x09 vga1 at pci0 dev 2 function 0 Intel HD Graphics 3000 rev 0x09 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 0xd000, size 0x1000 inteldrm0 at vga1: apic 2 int 16 drm0 at inteldrm0 Intel 6 Series MEI rev 0x04 at pci0 dev 22 function 0 not configured em0 at pci0 dev 25 function 0 Intel 82579LM rev 0x04: msi, address 5c:26:0a:7d:33:b6 ehci0 at pci0 dev 26 function 0 Intel 6 Series USB rev 0x04: apic 2 int 16 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 Intel 6 Series HD Audio rev 0x04: msi azalia0: codecs: IDT/0x76e7, Intel/0x2805, using IDT/0x76e7 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 6 Series PCIE rev 0xb4: msi pci1 at ppb0 bus 1 ppb1 at pci0 dev 28 function 1 Intel 6 Series PCIE rev 0xb4: msi pci2 at ppb1 bus 2 iwn0 at pci2 dev 0 function 0 Intel Centrino Advanced-N 6205 rev 0x34: msi, MIMO 2T2R,
Re: boot panic with qemu, -current guest on a Linux host
somehow, your computer thinks C3_CPUID_HAS_RNG is valid, which would mean you
are running the via_nano_setup routine, which means your cpu model is VIA Nano
processor, which is all just wrong. wtf?
LEVAI Daniel [l...@ecentrum.hu] wrote:
Hi!
I'm just curious if this is something that could get fixed (or maybe
danced around):
@linux $ qemu-kvm -enable-kvm -cpu host -smp 2 -m 512 \
-hda openbsd-current.img \
-net nic,model=e1000,macaddr=52:54:00:12:34:56 \
-net tap,ifname=tap0,script=no,downscript=no -curses
iPXE v1.0.0-591-g7aee315
iPXE (http://ipxe.org) 00:03.0 C900 PCI2.10 PnP PMM+1FFC82A0+1FF882A0 C900
Booting from Hard Disk...
Using drive 0, partition 3.
Loading...
probing: pc0 com0 apm pci mem[637K 510M a20=on]
disk: hd0+
OpenBSD/i386 BOOT 3.18
boot
booting hd0a:/bsd: 8354720+1102340 [52+376992+363706]=0x9b9ca8
entry point at 0x200120
[ using 741124 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
Copyright (c) 1995-2012 OpenBSD. All rights reserved. http://www.OpenBSD.org
OpenBSD 5.2-current (GENERIC.MP) #6: Mon Aug 27 20:40:45 MDT 2012
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: AMD Phenom(tm) II X4 B50 Processor (AuthenticAMD 686-class, 512KB L2
cac
he) 3.11 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF
LUSH,MMX,FXSR,SSE,SSE2,NXE,MMXX,FFXSR,3DNOW2,3DNOW,SSE3,CX16,POPCNT,LAHF,CMPLEG,
SVM,AMCR8,ABM,SSE4A,MASSE,3DNOWP
real mem = 536395776 (511MB)
avail mem = 516698112 (492MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 06/23/99, BIOS32 rev. 0 @ 0xff046,
SMBIOS
rev. 2.4 @ 0xfd900 (11 entries)
bios0: vendor Bochs version Bochs date 01/01/2007
bios0: Bochs Bochs
acpi0 at bios0: rev 0
acpi0: sleep states S3 S4 S5
acpi0: tables DSDT FACP SSDT APIC HPET
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
acpihpet0 at acpi0: 1 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
mpbios0 at bios0: Intel MP Specification 1.4
cpu0 at mainbus0: apid 0 (boot processor)
kernel: protection fault trap, code=0
Stopped at viac3_rnd+0x9f: rdmsr
viac3_rnd(d0b025a0,d09e3268,d08f384b,3,4) at viac3_rnd+0x9f
amd64_errata(d0b025a0,d0b025a0,d0f8,d078eb77,d0b025a0) at
amd64_errata+0xb9
cpu_init(d0b025a0,0,2000,0,d0bbbc04) at cpu_init+0x19
cpu_attach(d164bfc0,d155e400,d0bbbc4c,d03ee29b,d078de30) at cpu_attach+0x297
config_attach(d164bfc0,d09d45c0,d0bbbc4c,d078cb20,800,0,0,d08f3129,0,1,d09f21c0
,100f42,78bfbff) at config_attach+0x1bb
mpbios_cpu(f51a5a9c,d16737c0,2,1,2) at mpbios_cpu+0x85
mpbios_scan(d16737c0,d16737c0,d0bbbd60,d03ee29b,0) at mpbios_scan+0x2dc
config_attach(d164bf80,d09d45a0,d0bbbd60,d0789d30,b) at config_attach+0x1bb
biosattach(d164bfc0,d164bf80,d0bbbe58,d03ee29b,0) at biosattach+0x517
config_attach(d164bfc0,d09d4560,d0bbbe58,d05afb60,3000) at
config_attach+0x
1bb
ddb{0}
The host has an AMD Phenom(tm) II X4 B50 Processor.
The guest OpenBSD tries to boot a -current bsd.mp. This works with other
cpu types specified (like kvm32, or qemu32...), I just wanted to try out
if the guest would be faster with the 'phenom' or 'host' cpu type.
Has anyone experimented with this kind of or similar setup?
Daniel
--
L?VAI D?niel
PGP key ID = 0x83B63A8F
Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
--
Keep them laughing half the time, scared of you the other half. And always keep
them guessing. -- Clair George
Re: setting WOL for Realtek 8168
On 08/31/12 05:38, Stefan Sperling wrote: On Thu, Aug 30, 2012 at 07:58:07PM -0500, Ed Ahlsen-Girard wrote: I'm all good now, actually - apparently wol has to be reset by rc.local each startup. Yes, or alternatively add the 'wol' keyword to '/etc/hostname.re0'. The option doesn't stick across reboots. Derp. Yes the netstart scripts would be a better place to put it. I was thinking in linux and how you have to find somewhere to hide that infernal ehttool command.
My first macppc install not going well.
Hi. I got an iBook G4 and I'm having issues. I'm going for an MBR scheme using the whole disk but I'm not sure fdisk is working according to the installation instructions but I might have a borked disk ... Here's what I see: Available disks are: wd0. Which one is the root disk? (or 'done') [wd0] Enter Use DUIDs rather than device names in fstab? [yes] n Use HFS or MBR partition table? [HFS] MBR Here I get read failed repeated 8 times, 3 not HFS, a print out of the HFS style partitions. The read failed are obviously cause for concern but I don't know if that's from trying to read some previous Apple stuff, something in-correct that's correctable by proceeding with a write, something that's stopping the rest of the install or whatever. Are you *sure* you want an MBR partition table on wd0? [no] y Disk: wd0 geometry: 116280/16/63 [117210240 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- *0: 06 0 0 2 -2 0 33 [ 1:2048 ] DOS 32MB 1: 00 0 0 0 -0 00 [ 0: 0 ] unused 2: 00 0 0 0 -0 00 [ 0: 0 ] unused 3: A6 4 1 2 - 116279 15 63 [ 4096: 117206144 ] OpenBSD Use (W)hole disk, use the (O)penBSD area, or (E)dit the MBR? [OpenBSD] w I guess the reason for the DOS and OpenBSD partitions is that I've been through this a few times. I've tried using the whole disk or the OpenBSD area with as far as I can see the same result except using the whole disk re-creates the DOS partition. Creating a 1MB DOS partition and an OpenBSD partition for the rest of wd0...done. /dev/rwd0i: 116720008 sectors in 15490001 FAT32 clusters (4096 bytes/cluster) bps=512 spc=8 res=32 nft=2 mid=0xf8 spt=63 hds=16 hid=262208 bsec=116948016 bspf=113985 rdcl=2 infs=1 bkbs=2 The auto-allocated layout for wd0 is: #size offset fstype [fsize bsize cpg] a: 128.0M 64 4.2BSD 2048 163841 # / c: 57231.6M 0 unused i: 57103.5M 262208 HFS Use (A)uto layout, (E)dit auto layout, or create (C)ustom layout? [a] c Here I've tried A and C but I only seem to be able to use 128MB of disk space. For instance using A ... /dev/rwd0a: 128.0MB in 262144 sectors of 512 bytes 4 cylinder groups of 32.00MB, 2048 blocks, 4096 inodes each /dev/wd0a on /mnt type ffs (rw, asynchronous, local) I've tried deleting i and adding b and so on but the a is using the entire 128MB ... If I delete a which as far as I can tell is not what I should be doing, I can add 128MB at most ... There's not enough room to install bsd and etc so I've tried installing bsd.rd only but when I try ... boot hd:,ofwboot /bsd.rd ... at the OF prompt I get: Warning: sector size mismatch! can't OPEN: hd:,ofwboot Cant open device or file Any advice appreciated. Best wishes.
Weird problem - sound suddenly stops playing
I'm running 5.1/amd64 on a ThinkPad 410. sndiod is started in /etc/rc.conf with the default 'sndiod_flags=' entry. I have working audio from mpd, mplayer, and assorted other applications. Everything just works. The problem is, at some point, sound simply cuts out. I can run audioctl and see the play.samples value continue to increase, but there's no more sound coming out of the speakers. play.errors remains at 0. There aren't any errors being logged anywhere that I can find. Killing and restarting sndiod doesn't bring back sound, nor does trying to play sounds directly with aucat after killing sndiod. However, rebooting restores sound, but it always eventually dies again. Can anyone offer any further troubleshooting advice? I'm including a dmesg and mixerctl -v output below... OpenBSD 5.1 (GENERIC.MP) #207: Sun Feb 12 09:42:14 MST 2012 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4078419968 (3889MB) avail mem = 3955687424 (3772MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xe0010 (78 entries) bios0: vendor LENOVO version 6IET81WW (1.41 ) date 02/09/2012 bios0: LENOVO 2537JU5 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) UART(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) i5 CPU M 520 @ 2.40GHz, 2394.47 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 133MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz, 2394.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) i5 CPU M 520 @ 2.40GHz, 2394.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) i5 CPU M 520 @ 2.40GHz, 2394.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 2 (EXP1) acpiprt3 at acpi0: bus 3 (EXP2) acpiprt4 at acpi0: bus -1 (EXP3) acpiprt5 at acpi0: bus 5 (EXP4) acpiprt6 at acpi0: bus 13 (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: SLPB acpibat0 at acpi0: BAT0 model 42T4911 serial 50006 type LION oem LGC acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 cpu0: Enhanced SpeedStep 2394 MHz: speeds: 2400, 2399, 2266, 2133, 1999, 1866, 1733, 1599, 1466, 1333, 1199 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel Core Host rev 0x02 vga1 at pci0 dev 2 function 0 Intel Mobile HD graphics 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 0xd000, size 0x1000 inteldrm0 at vga1: apic 1 int 16 drm0 at inteldrm0 Intel 3400 MEI rev 0x06 at pci0 dev 22 function 0 not configured em0 at pci0 dev 25 function 0 Intel 82577LM rev 0x06: msi, address f0:de:f1:5a:45:49 ehci0 at pci0 dev 26 function 0 Intel 3400 USB rev 0x06: apic 1 int 23 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 Intel 3400 HD Audio rev 0x06: msi azalia0: codecs: Conexant/0x5069, Intel/0x2804, using Conexant/0x5069 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 3400 PCIE rev 0x06: msi pci1 at ppb0 bus 2 ppb1 at pci0 dev 28 function 1 Intel 3400 PCIE rev 0x06: msi pci2 at ppb1 bus 3
Re: Ports security updates in 5.1 or 5.2
On Fri, Aug 31, 2012 at 6:06 PM, Sébastien Marie semarie-open...@latrappe.fr wrote: On Thu, Aug 30, 2012 at 06:52:15PM +, Stuart Henderson wrote: On 2012-08-30, Sébastien Marie semarie-open...@latrappe.fr wrote: I not used all pervious ports, and some are used in safe usage (like using postgresql ports, but not for server). It just a question to known what follow, in order to keep updated... really, in order to keep updated, following -current is a good policy. sure, updates in -current are more fresh ! but the investissement may be important, as it is required to upgrade the system before add or upgrade ports... I think I will consider installing -current on an external disk, in order to see and learn upgrade process (via snapshots) before definitively switch to -current on my laptop. You will find it very quick and easy: boot bsd.rd and choose (U)pgrade reboot sysmerge -s $ -x $ maybe reboot check current.html for possible manual steps pkg_add -ui It's possible to have modest machine to be completely updated in about 10 minutes completely binary way. Thanks Stuart. -- Sebastien Marie
Re: Weird problem - sound suddenly stops playing
On Sat, Sep 1, 2012 at 7:11 AM, Joe Gidi j...@entropicblur.com wrote: I'm running 5.1/amd64 on a ThinkPad 410. sndiod is started in /etc/rc.conf with the default 'sndiod_flags=' entry. I have working audio from mpd, mplayer, and assorted other applications. Everything just works. Did you try to run with sndiod -d if there will be something more in console? The problem is, at some point, sound simply cuts out. I can run audioctl and see the play.samples value continue to increase, but there's no more sound coming out of the speakers. play.errors remains at 0. There aren't any errors being logged anywhere that I can find. Killing and restarting sndiod doesn't bring back sound, nor does trying to play sounds directly with aucat after killing sndiod. However, rebooting restores sound, but it always eventually dies again. Can anyone offer any further troubleshooting advice? I'm including a dmesg and mixerctl -v output below... OpenBSD 5.1 (GENERIC.MP) #207: Sun Feb 12 09:42:14 MST 2012 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4078419968 (3889MB) avail mem = 3955687424 (3772MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xe0010 (78 entries) bios0: vendor LENOVO version 6IET81WW (1.41 ) date 02/09/2012 bios0: LENOVO 2537JU5 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) UART(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) i5 CPU M 520 @ 2.40GHz, 2394.47 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 133MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz, 2394.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) i5 CPU M 520 @ 2.40GHz, 2394.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) i5 CPU M 520 @ 2.40GHz, 2394.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 2 (EXP1) acpiprt3 at acpi0: bus 3 (EXP2) acpiprt4 at acpi0: bus -1 (EXP3) acpiprt5 at acpi0: bus 5 (EXP4) acpiprt6 at acpi0: bus 13 (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: SLPB acpibat0 at acpi0: BAT0 model 42T4911 serial 50006 type LION oem LGC acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 cpu0: Enhanced SpeedStep 2394 MHz: speeds: 2400, 2399, 2266, 2133, 1999, 1866, 1733, 1599, 1466, 1333, 1199 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel Core Host rev 0x02 vga1 at pci0 dev 2 function 0 Intel Mobile HD graphics 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 0xd000, size 0x1000 inteldrm0 at vga1: apic 1 int 16 drm0 at inteldrm0 Intel 3400 MEI rev 0x06 at pci0 dev 22 function 0 not configured em0 at pci0 dev 25 function 0 Intel 82577LM rev 0x06: msi, address f0:de:f1:5a:45:49 ehci0 at pci0 dev 26 function 0 Intel 3400 USB rev 0x06: apic 1 int 23 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 Intel 3400 HD Audio rev 0x06:
