Re: OpenBSD 5.6/amd64 WLE200NX (Atheros AR9280) athn issues
On Mon, Nov 03, 2014 at 01:13:40AM +0100, Stefan Krüger wrote: Hi, I have a PC Engines APU board with a Compex WLE200NX miniPCI-e wifi card running in hostap mode (11g). root@apu:/var/log # dmesg | grep athn0 athn0 at pci4 dev 0 function 0 Atheros AR9281 rev 0x01: apic 2 int 19 athn0: AR9280 rev 2 (2T2R), ROM rev 22, address xx:xx:xx:xx:xx:xx root@apu:/var/log # ifconfig athn0 athn0: flags=28843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6 mtu 1500 lladdr xx:xx:xx:xx:xx:xx priority: 4 groups: wlan media: IEEE802.11 autoselect mode 11g hostap status: active ieee80211: nwid obsd chan 7 bssid xx:xx:xx:xx:xx:xx wpakey 0x... wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp powersave on (100ms sleep) inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255 It's rather unstable though: root@apu:/var/log # zgrep athn0: device messages* messages:Nov 3 01:08:40 apu /bsd: athn0: device timeout messages:Nov 2 00:41:22 apu /bsd: athn0: device timeout messages:Nov 2 02:20:06 apu /bsd: athn0: device timeout messages:Nov 2 03:11:03 apu /bsd: athn0: device timeout messages:Nov 2 19:56:36 apu /bsd: athn0: device timeout messages.0.gz:Oct 26 22:06:44 apu /bsd: athn0: device timeout messages.0.gz:Oct 27 02:17:05 apu /bsd: athn0: device timeout messages.0.gz:Oct 31 11:10:40 apu /bsd: athn0: device timeout messages.0.gz:Oct 31 20:48:43 apu /bsd: athn0: device timeout messages.0.gz:Nov 1 13:48:04 apu /bsd: athn0: device timeout messages.2.gz:Oct 14 18:26:52 apu /bsd: athn0: device timeout messages.3.gz:Oct 12 20:35:53 apu /bsd: athn0: device timeout I also see constant increasing error counters (even if there's no traffic visible via tcpdump): root@apu:/var/log # netstat -i -I athn0 5 athn0 in athn0 out total in total out packets errs packets errs colls packets errs packets errs colls 1190195 171127 2642652 4337 0 10759655 171127 8935403 4337 0 265 8 1096 0 0 2675 8 1845 0 0 12914 826 0 0 201114 1323 0 0 63015 1923 0 0 469615 3403 0 0 32214 894 0 0 231914 1738 0 0 58618 1244 0 0 365818 2956 0 0 40414 437 0 0 202114 1916 0 0 1540 13 0 0 54840 538 0 0 Anyone else seeing this? Any idea how I could fix this? Thanks. PS: OpenBSD 5.6 amd64, bsd is bsd.mp Can you check which error counters go up as per 'netstat -W athn0'? That could provide some more specific detail. I'm seeing some input errors on my AP too but they're just noise and don't cause any disruption: @@ -17,7 +17,7 @@ 0 input packets with elements too big 49 input packets with elements too small 0 input packets with invalid channel - 17542137 input packets with mismatched channel + 17544585 input packets with mismatched channel Some errors are harmless and even expected. 2.4Ghz radio is a shared medium many overlapping channels and usually has too many users unless you're living somewhere in the woods. If the AP recovers from timeouts without manual intervention and your usage of the AP is not significantly disrupted then I don't think this is worth spending any of your or anyone else's time on -- there are much worse problems in the wifi stack that need fixing. Perhaps changing the channel, asking your neighbours to switch their APs off, or coating walls to neighbouring houses or appartments with tinfoil will improve things a bit.
Re: still loosing connections
On Sun, Nov 02, 2014 at 08:41:44PM +0100, Stefan Wollny wrote: I think so. Your message is a million lines long, but I have no idea what the problem is. Hi Ted, thank you for taking your time to reply. Long story short: Sometimes (=not deliberately repeatable) when fetching a fresh snapshot and/or the sources afterwards and/or running 'pkg_add -ui' connections to the internet are lost, entirely. This happens with i386-current as well with amd64-current and with different providers. I have to bring down all interfaces and flush routes prior to 'sudo sh /etc/netstart' to get a connection - but even this does not always work - a restart is then required. My problem is: I have no clue where to look or how to investigate further into this issue. That is why I have described en d??tail what I am doing and added as much information as possible. Can you (or s.o. else) give me hint where to look? I feel kind of lost... Thank's a lot! Cheers, STEFAN BTW: By now I use OpenBSD 5.6-current (GENERIC.MP) #515: Sat Nov 1 20:55:07 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Hi Stefan, Did you say you used different providers? Did you try my udptunnel that I told you about in private mail? I can update the sources for you on my vps in amsterdam for you. If you've followed my problem it was with the FritzBox, still is because I couldn't restore my config on the FritzBox after downgrading, so I upgraded to 6.20 again. The udptunnel I wrote circumvents the bad networking associated with the fritzbox. Generally I think watching a netstat -s output for tcp is a good start. Look for retransmissions and hangups in the tcp section of that. A dmesg to the list would be helpful, as always add a description of what interfaces you use for default route. Also take a look at netstat -ni and look for hardware errors on the interface itself. There is input/output errors and collisions noted. So, netstat -s netstat-s.`date +%s` before your downloads and the same during and after, see if anything changes using diff helps too. Good luck! -peter
Re: still loosing connections
Hi Peter, thanks for your help. I was too busy with some private requirements over the weekend to test your tunnel. During the week I am not at home, living in a hotel. I guess you'll understand that I will not use my main laptop which needed daily (and has some confidential stuff...) but would like to use a spare machine running i386-current (instead amd64-current) to test your udptunnel first. I noticed the broken connections with 'KabelDeutschland' at home via em0 and with wpi0 via T-Mobile and via the hotel-WLAN (I guess DTAG). Only at home and at the hotel a Fritz!Box (different models) is involved, not if I use my mobile phone. I will take a look at 'man netstat' and proceed as you suggested. Best,STEFAN Gesendet: Montag, 03. November 2014 um 12:17 Uhr Von: Peter J. Philipp p...@centroid.eu An: Stefan Wollny stefan.wol...@web.de Cc: openbsd-misc misc@openbsd.org Betreff: Re: still loosing connectionsOn Sun, Nov 02, 2014 at 08:41:44PM +0100, Stefan Wollny wrote: I think so. Your message is a million lines long, but I have no idea what the problem is. Hi Ted, thank you for taking your time to reply. Long story short: Sometimes (=not deliberately repeatable) when fetching a fresh snapshot and/or the sources afterwards and/or running 'pkg_add -ui' connections to the internet are lost, entirely. This happens with i386-current as well with amd64-current and with different providers. I have to bring down all interfaces and flush routes prior to 'sudo sh /etc/netstart' to get a connection - but even this does not always work - a restart is then required. My problem is: I have no clue where to look or how to investigate further into this issue. That is why I have described en d??tail what I am doing and added as much information as possible. Can you (or s.o. else) give me hint where to look? I feel kind of lost... Thank's a lot! Cheers, STEFAN BTW: By now I use OpenBSD 5.6-current (GENERIC.MP) #515: Sat Nov 1 20:55:07 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Hi Stefan, Did you say you used different providers? Did you try my udptunnel that I told you about in private mail? I can update the sources for you on my vps in amsterdam for you. If you've followed my problem it was with the FritzBox, still is because I couldn't restore my config on the FritzBox after downgrading, so I upgraded to 6.20 again. The udptunnel I wrote circumvents the bad networking associated with the fritzbox. Generally I think watching a netstat -s output for tcp is a good start. Look for retransmissions and hangups in the tcp section of that. A dmesg to the list would be helpful, as always add a description of what interfaces you use for default route. Also take a look at netstat -ni and look for hardware errors on the interface itself. There is input/output errors and collisions noted. So, netstat -s netstat-s.`date +%s` before your downloads and the same during and after, see if anything changes using diff helps too. Good luck! -peter
Re: security - pass the hash style attacks?
Philip Guenther guent...@gmail.com writes: [apologies for the contentless previous message] On Sun, Nov 2, 2014 at 4:43 PM, Philip Guenther guent...@gmail.com wrote: On Sun, Nov 2, 2014 at 4:41 PM, Nex6|Bill n6gh...@yahoo.com wrote: ... what about kerberos? (windows K5 vs Unix K5?) There's a bunch of *really good* papers on Kerberos's design which discuss exactly these sorts of issues and how they are addressed or completely avoided. I remember finding the one cast as a dialog between two system programmers (one named Athena...) as a good intro on this stuff. Yup. First tutorial link on this page: http://web.mit.edu/kerberos/papers.html -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Re: audio in linux emulation, skype friends
On Fri, Oct 31, 2014 at 08:58:15AM +0100, Alexandre Ratchov wrote: On Fri, Oct 31, 2014 at 11:48:00AM +0530, Jay Patel wrote: Try https://jitsi.org/ or tox https://tox.im/ Hope this helps. thanks for the links. The question is more about audio support in linux emulation itself. Does anyone use it? does it even work? what about deleting it? I haven't used i386 for a year or so and i thought linux compat was still pretty much not usable anymore :-) but when i last used it, it was just for binary released linux games such as unreal tournament. so, i guess linux binaries that used sdl had sound. just for informational purposes, i would presume linux sdl binaries must have been using the ossaudio type layer as we have (had?) no alsa stuff. i don't use this anymore as my machines are amd64, cheers! -ryan -- Alexandre
IPv6 nonfunctional after upgrade from 5.5 to 5.6
Hello everyone. I am new to this list but I am in need of some help. I have been running OpenBSD since 4.6 as my firewall and gateway with much success (transitioned from FreeBSD) and it was working out great as a light weight and secure OS for my Internet router and gateway. One of the uses of this box is to route IPv6 for my local subnet out to the Internet. It used to use a free tunnel service that worked great. But I have since transitioned to the IPv6 that my ISP provides me directly. This was a bit painful at first but I got it working with the help of some 3rd party software not available in the ports collection called Dibbler. This software is not perfect, but with the help of a script I fleshed out myself i got it to do what I needed. The client portion of that DHCPv6 program reaches out to the DHCPv6 server on my ISP's network and obtains all the information I need. The only thing it is currently able to do on it's own is plumb up the primary IPv6 address it obtains from the ISP. But I still have to add the requisite default route information. Also I have to then manually plumb up the delegated IPv6 prefix assigned to my subnet (that I request) to my internal interface. I then use rtadvd to advertise that route and allow for SLAAC to work on my internal network to all IPv6 aware hosts. This used to work just fine until I upgraded my router to 5.6 from 5.5. After adding 'inet6 autoconf' to my hostname.if files, it appeared I got my IPv6 functionality back. However, while the box itself is back on IPv6 Internet, the subnet it acts as a router for can no longer get onto the Internet. After looking into it further it appears there is something wrong with the routing table. There is no route for the subnet of the address I manually add via ifconfig to the internal interface. I do not know how to do this, nor was this previously necessary. The ifconfig command I call to add the address specified the prefixlen 64 which *should* imply the address is part of a /64 subnet where all other addresses within that subnet should be reachable via the same interface the address is plumbed up on. When I do a route show or a netstat -nr I do not see such a route nor have I been successful in figuring out how to call the route add command to add such a route. Thanks in advance. SlyM Here is my ifconfig output: vr0: flags=208843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,AUTOCONF6 mtu 1500 lladdr 00:40:63:e6:42:a5 priority: 0 groups: egress media: Ethernet autoselect (100baseTX full-duplex) status: active inet 50.186.155.188 netmask 0xff00 broadcast 50.186.155.255 inet6 fe80::240:63ff:fee6:42a5%vr0 prefixlen 64 scopeid 0x1 inet6 2001:558:6030:44:35cc:9a5e:65f7:c139 prefixlen 64 em0: flags=208b43UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST,AUTOCONF6 mtu 1500 lladdr 00:1b:21:4e:d4:a2 priority: 0 media: Ethernet autoselect (1000baseT full-duplex,rxpause,txpause) status: active inet 192.168.82.1 netmask 0xff00 broadcast 192.168.82.255 inet6 fe80::21b:21ff:fe4e:d4a2%em0 prefixlen 64 scopeid 0x2 inet6 2601:7:5780:c99::1 prefixlen 64 Here is my route show output: Routing tables Internet: DestinationGatewayFlags Refs Use Mtu Prio Iface default50.186.155.1 UGS5 741497 - 8 vr0 50.186.155/24 link#1 UC 10 - 4 vr0 50.186.155.1 00:01:5c:6f:f6:46 UHLc 10 - 4 vr0 50.186.155.188 00:40:63:e6:42:a5 UHLl 00 - 1 lo0 127/8 127.0.0.1 UGRS 00 32768 8 lo0 127.0.0.1 127.0.0.1 UH 10 32768 4 lo0 192.168.82/24 link#2 UC 40 - 4 em0 192.168.82.1 00:1b:21:4e:d4:a2 HLl00 - 1 lo0 192.168.82.200 80:ee:73:64:13:0c UHLc 4 512052 - 4 em0 192.168.82.251 08:3e:8e:07:e5:64 UHLc 00 - 4 em0 192.168.82.253 00:15:c5:f5:0d:b4 UHLc 2 6854 - 4 em0 192.168.82.254 00:24:2b:df:8f:2b UHLc 0 3722 - 4 em0 224/4 127.0.0.1 URS00 32768 8 lo0 Internet6: DestinationGateway Flags Refs Use Mtu Prio Iface ::/104 ::1 UGRS 00 32768 8 lo0 ::/96 ::1 UGRS 00 32768 8 lo0 default2001:558:6030:44::1 UGS0 7716 - 8 vr0 ::1::1 UH140 32768 4 lo0 ::127.0.0.0/104::1 UGRS 00 32768
Re: uscom/ucom hardware question [was: OpenBSD 5.6 Released]
On Sat, Nov 01, 2014 at 10:32:52PM +0100, ropers wrote: o New uscom(4) driver for simple USB serial adapters. This reminds me of something I've been meaning to ask for some time: * Has anyone here used a USB-only laptop with a USB-to-serial adapter as a serial console? (You know, instead of hardware that has a native RS-232 port? Yes. * Does uscom(4) make this any easier/is it more compatible than ucom(4)? * If I buy a random USB-to-serial dongle, is it likely that it'll work with either uscom(4) or ucom(4)? If not, does anyone have any hardware recommendations, i.e. what do you use? I have got a cable labled ST-Lab USB-SERIAL-4 purchased from Dustin in Sweden, and it works well. I do not remember what device driver attaches to it and have not tried any other cables so I can not say even if it happens that some cable does not work due to e.g Windows-only drivers... Thanks for any input regards, ropers -- / Raimo Niskanen, Erlang/OTP, Ericsson AB
Re: audio in linux emulation, skype friends
On Mon, Nov 03, 2014 at 08:58:29AM -0800, Ryan Freeman wrote: On Fri, Oct 31, 2014 at 08:58:15AM +0100, Alexandre Ratchov wrote: On Fri, Oct 31, 2014 at 11:48:00AM +0530, Jay Patel wrote: Try https://jitsi.org/ or tox https://tox.im/ Hope this helps. thanks for the links. The question is more about audio support in linux emulation itself. Does anyone use it? does it even work? what about deleting it? I haven't used i386 for a year or so and i thought linux compat was still pretty much not usable anymore :-) but when i last used it, it was just for binary released linux games such as unreal tournament. Not sure to understand, did you manage to play with unreal tournament on OpenBSD, with working audio? so, i guess linux binaries that used sdl had sound. BTW, sdl (on linux) could be configured to use sndio, which would make sound work, as long as the linux binaries are dynamically linked against sdl. just for informational purposes, i would presume linux sdl binaries must have been using the ossaudio type layer as we have (had?) no alsa stuff. i don't use this anymore as my machines are amd64, cheers! so you won't object if ossaudio is removed for linux emulation, right? -- Alex
Re: security - pass the hash style attacks?
On Nov 3, 2014, at 4:28 AM, Jérémie Courrèges-Anglas j...@wxcvbn.org wrote: Philip Guenther guent...@gmail.com writes: [apologies for the contentless previous message] On Sun, Nov 2, 2014 at 4:43 PM, Philip Guenther guent...@gmail.com wrote: On Sun, Nov 2, 2014 at 4:41 PM, Nex6|Bill n6gh...@yahoo.com wrote: ... what about kerberos? (windows K5 vs Unix K5?) There's a bunch of *really good* papers on Kerberos's design which discuss exactly these sorts of issues and how they are addressed or completely avoided. I remember finding the one cast as a dialog between two system programmers (one named Athena...) as a good intro on this stuff. Yup. First tutorial link on this page: http://web.mit.edu/kerberos/papers.html -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE Here is a pretty good blackhat talk about this: though its windows specific the gist of it is Kerberos is just as broken as NTLM. since enforcement is client side . -Nex6 [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: IPv6 nonfunctional after upgrade from 5.5 to 5.6
Hi, can you show us the contents of your hostname.* and mygate files? What are the specific configuration steps? Reyk Am 03.11.2014 um 18:04 schrieb Sly Midnight slymidni...@yahoo.com: Hello everyone. I am new to this list but I am in need of some help. I have been running OpenBSD since 4.6 as my firewall and gateway with much success (transitioned from FreeBSD) and it was working out great as a light weight and secure OS for my Internet router and gateway. One of the uses of this box is to route IPv6 for my local subnet out to the Internet. It used to use a free tunnel service that worked great. But I have since transitioned to the IPv6 that my ISP provides me directly. This was a bit painful at first but I got it working with the help of some 3rd party software not available in the ports collection called Dibbler. This software is not perfect, but with the help of a script I fleshed out myself i got it to do what I needed. The client portion of that DHCPv6 program reaches out to the DHCPv6 server on my ISP's network and obtains all the information I need. The only thing it is currently able to do on it's own is plumb up the primary IPv6 address it obtains from the ISP. But I still have to add the requisite default route information. Also I have to then manually plumb up the delegated IPv6 prefix assigned to my subnet (that I request) to my internal interface. I then use rtadvd to advertise that route and allow for SLAAC to work on my internal network to all IPv6 aware hosts. This used to work just fine until I upgraded my router to 5.6 from 5.5. After adding 'inet6 autoconf' to my hostname.if files, it appeared I got my IPv6 functionality back. However, while the box itself is back on IPv6 Internet, the subnet it acts as a router for can no longer get onto the Internet. After looking into it further it appears there is something wrong with the routing table. There is no route for the subnet of the address I manually add via ifconfig to the internal interface. I do not know how to do this, nor was this previously necessary. The ifconfig command I call to add the address specified the prefixlen 64 which *should* imply the address is part of a /64 subnet where all other addresses within that subnet should be reachable via the same interface the address is plumbed up on. When I do a route show or a netstat -nr I do not see such a route nor have I been successful in figuring out how to call the route add command to add such a route. Thanks in advance. SlyM Here is my ifconfig output: vr0: flags=208843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,AUTOCONF6 mtu 1500 lladdr 00:40:63:e6:42:a5 priority: 0 groups: egress media: Ethernet autoselect (100baseTX full-duplex) status: active inet 50.186.155.188 netmask 0xff00 broadcast 50.186.155.255 inet6 fe80::240:63ff:fee6:42a5%vr0 prefixlen 64 scopeid 0x1 inet6 2001:558:6030:44:35cc:9a5e:65f7:c139 prefixlen 64 em0: flags=208b43UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST,AUTOCONF6 mtu 1500 lladdr 00:1b:21:4e:d4:a2 priority: 0 media: Ethernet autoselect (1000baseT full-duplex,rxpause,txpause) status: active inet 192.168.82.1 netmask 0xff00 broadcast 192.168.82.255 inet6 fe80::21b:21ff:fe4e:d4a2%em0 prefixlen 64 scopeid 0x2 inet6 2601:7:5780:c99::1 prefixlen 64 Here is my route show output: Routing tables Internet: DestinationGatewayFlags Refs Use Mtu Prio Iface default50.186.155.1 UGS5 741497 - 8 vr0 50.186.155/24 link#1 UC 10 - 4 vr0 50.186.155.1 00:01:5c:6f:f6:46 UHLc 10 - 4 vr0 50.186.155.188 00:40:63:e6:42:a5 UHLl 00 - 1 lo0 127/8 127.0.0.1 UGRS 00 32768 8 lo0 127.0.0.1 127.0.0.1 UH 10 32768 4 lo0 192.168.82/24 link#2 UC 40 - 4 em0 192.168.82.1 00:1b:21:4e:d4:a2 HLl00 - 1 lo0 192.168.82.200 80:ee:73:64:13:0c UHLc 4 512052 - 4 em0 192.168.82.251 08:3e:8e:07:e5:64 UHLc 00 - 4 em0 192.168.82.253 00:15:c5:f5:0d:b4 UHLc 2 6854 - 4 em0 192.168.82.254 00:24:2b:df:8f:2b UHLc 0 3722 - 4 em0 224/4 127.0.0.1 URS00 32768 8 lo0 Internet6: DestinationGateway Flags Refs Use Mtu Prio Iface ::/104 ::1 UGRS 00 32768 8 lo0 ::/96 ::1 UGRS 00 32768 8 lo0 default
Re: bridge + vlan broke after 5.5 5.6 upgrade
On 2014-11-02 13:51, Jorge Schrauwen wrote: Hey All, TL;DR: traffic leaving a bridge over a vlan does not get tagged but leaves untagged after upgrade. Is this by design? On 2014-11-02 13:51, Jorge Schrauwen wrote: Hey All, TL;DR: traffic leaving a bridge over a vlan does not get tagged but leaves untagged after upgrade. Is this by design? Looks exactly like my problem. Running 5.6 release. $ cat hostname.vr0 up description Outside $ cat hostname.vr1 inet 10.0.0.1 255.255.0.0 NONE $ cat hostname.vr2 up $ cat hostname.vlan4 vlandev vr0 description IPTV_vlan $ cat hostname.vlan6 vlandev vr0 description Internet_vlan $ cat hostname.bridge0 add vr1 add vr3 description LAN up $ $ cat hostname.bridge1 add vlan4 add vr2 up description IPTV $ cat hostname.pppoe0 inet 0.0.0.0 255.255.255.255 NONE \ pppoedev vlan6 authproto pap \ authname 'p...@xs4all.nl' authkey 'bar' up dest 0.0.0.1 !/sbin/route add default -ifp pppoe0 0.0.0.1 I see no vid (vlan id) here. I think there should be: $ sudo tcpdump ether host 50:7e:5d:b8:53:22 tcpdump: listening on vr0, link-type EN10MB 21:19:17.292926 0.0.0.0.bootpc 255.255.255.255.bootps: xid:0x2bd46c6c [|bootp] 21:19:21.007071 0.0.0.0.bootpc 255.255.255.255.bootps: xid:0x2bd46c6c [|bootp] http://pjhv.home.xs4all.nl/dmesg So now I can't watch TV :-) Need more information? Please ask. Gr, Pieter Verberne
Re: Mirror openbsd.cs.toronto.edu is NO LONGER broke
All supported and close-to-supported versions of OpenBSD have been reloaded (5.4, 5.5, 5.6 and -current snapshots), rsync is back on. Again ... my apologies for the inconvenience at a most inopportune time. Nick. On 11/01/14 09:06, Nick Holland wrote: Due to an administrative error (hint: I'm the administrator :-/ ), openbsd.cs.toronto.edu dumped its copy of most of the OpenBSD distribution files that it serves. It is currently refilling, but this will take a few days before it is where I want it to be. To minimize further downstream damage, rsync is disabled for now My apologies for the inconvenience this causes. THIS DOES NOT impact the replication of the CVS served by this mirror.
Re: bridge + vlan broke after 5.5 5.6 upgrade
On 2014-11-02 13:51, Jorge Schrauwen wrote: Hey All, TL;DR: traffic leaving a bridge over a vlan does not get tagged but leaves untagged after upgrade. Is this by design? Looks exactly like my problem. Running 5.6 release. (Sorry for the double quote). Of course... $ ifconfig lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 32768 priority: 0 groups: lo inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 inet 127.0.0.1 netmask 0xff00 vr0: flags=28b43UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST,NOINET6 mtu 1500 lladdr 00:00:24:cd:7d:f8 description: Outside priority: 0 media: Ethernet autoselect (100baseTX full-duplex) status: active vr1: flags=28b43UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST,NOINET6 mtu 1500 lladdr 00:00:24:cd:7d:f9 priority: 0 media: Ethernet autoselect (100baseTX full-duplex) status: active inet 10.0.0.1 netmask 0x broadcast 10.0.255.255 vr2: flags=28b43UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST,NOINET6 mtu 1500 lladdr 00:00:24:cd:7d:fa priority: 0 media: Ethernet autoselect (none) status: no carrier vr3: flags=28b02BROADCAST,PROMISC,ALLMULTI,SIMPLEX,MULTICAST,NOINET6 mtu 1500 lladdr 00:00:24:cd:7d:fb priority: 0 media: Ethernet autoselect (none) status: no carrier enc0: flags=2NOINET6 priority: 0 groups: enc status: active ral0: flags=28802BROADCAST,SIMPLEX,MULTICAST,NOINET6 mtu 1500 lladdr 00:12:0e:61:48:98 priority: 4 groups: wlan media: IEEE802.11 autoselect status: no network ieee80211: nwid 100dBm vlan4: flags=28943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,NOINET6 mtu 1500 lladdr 00:00:24:cd:7d:f8 description: IPTV_vlan priority: 0 vlan: 4 parent interface: vr0 groups: vlan status: active vlan6: flags=28843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6 mtu 1500 lladdr 00:00:24:cd:7d:f8 description: Internet_vlan priority: 0 vlan: 6 parent interface: vr0 groups: vlan status: active pppoe0: flags=28851UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST,NOINET6 mtu 1492 priority: 0 dev: vlan6 state: session sid: 0x1a04 PADI retries: 0 PADR retries: 0 time: 00:47:59 sppp: phase network authproto pap groups: pppoe egress status: active inet 80.100.141.131 -- 194.109.5.175 netmask 0x bridge0: flags=20041UP,RUNNING,NOINET6 description: LAN groups: bridge priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp vr1 flags=3LEARNING,DISCOVER port 2 ifpriority 0 ifcost 0 vr3 flags=3LEARNING,DISCOVER port 4 ifpriority 0 ifcost 0 bridge1: flags=20041UP,RUNNING,NOINET6 description: IPTV groups: bridge priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp vlan4 flags=13LEARNING,DISCOVER,EDGE port 8 ifpriority 0 ifcost 0 vr2 flags=13LEARNING,DISCOVER,EDGE port 3 ifpriority 0 ifcost 0 pflog0: flags=20141UP,RUNNING,PROMISC,NOINET6 mtu 33192 priority: 0 groups: pflog $ $ ifconfig bridge1 bridge1: flags=20041UP,RUNNING,NOINET6 description: IPTV groups: bridge priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp designated: id 00:00:00:00:00:00 priority 0 vlan4 flags=13LEARNING,DISCOVER,EDGE port 8 ifpriority 0 ifcost 0 vr2 flags=13LEARNING,DISCOVER,EDGE port 3 ifpriority 0 ifcost 0 Addresses (max cache: 100, timeout: 240): 00:90:d0:63:ff:00 vlan4 1 flags=0 50:7e:5d:b8:53:22 vr2 0 flags=0
ACPIEC error has vanished
Good day to everyone, I've had this problem [1] for sometime now (2+ years apparently). During the latest snapshot upgrade which I downloaded 30-10-2014, I decided to give a shot and boot without acpiec disabled. To my surprise it worked like a charm! Previously netlivelocks had really high values but expectedly calmed down once the ACPI was working properly. The perfpolicy is also kicking butts. Superb. To show my appreciation towards your work I made an extra donation. I'd also like to congratulate all the devs about the another neat release. Thanks. [1] http://thread.gmane.org/gmane.os.openbsd.misc/194383 -- Sincerely, Ville Valkonen
Re: uscom/ucom hardware question [was: OpenBSD 5.6 Released]
On 2014-11-01, ropers rop...@gmail.com wrote: * Does uscom(4) make this any easier/is it more compatible than ucom(4)? Nope. uscom is afaik only tested so far with HP graphing calculators. It is *really* simple, just provides a way to transfer data, it does not allow setting port speed etc. Also it is not built into GENERIC at present so it requires a custom kernel. ucom(4) is a different layer. ucom attaches *to* the hardware device driver (uftdi, uark, ubsa, uscom, ...) to provide tty(4)-like access. * If I buy a random USB-to-serial dongle, is it likely that it'll work with either uscom(4) or ucom(4)? If not, does anyone have any hardware recommendations, i.e. what do you use? My suggestion: pick a random cheap single-port rs232/usb adapter, don't spend much money on it. If it doesn't work, try a different one, and send lsusb -v outpout and see if anyone would like to have the non-working device to play with and try and add support.. (multi-port ones may also work, but you have a higher chance of a single-port one just working). FTDI clones might be particularly cheap at the moment :)
Re: OpenBSD 5.6/amd64 WLE200NX (Atheros AR9280) athn issues
On 2014-11-03, Stefan Sperling s...@stsp.name wrote: Perhaps changing the channel, asking your neighbours to switch their APs off, or coating walls to neighbouring houses or appartments with tinfoil will improve things a bit. http://www.theargus.co.uk/news/11547439.Gran_spends_nearly___4_000_to_protect_her_house_against_wi_fi_and_mobile_phone_signals/ (ok, the tinfoil is probably cheaper :)
kde4-4.13.3p0 on OpenBSD 5.6 10/15/2014 AMD64 snapshot
Does anyone besides me experience crashes with Dolphin on kde4-4.13.3p0? When I click on the kde crash handler developer information tab it churns forever and ever and ever and never returns any information. $ cat /etc/rc.conf.local sshd_flags=NO multicast_host=YES pkg_scripts=dbus_daemon avahi_daemon cupsd $ cat /etc/sysctl.conf machdep.allowaperture=2 # See xf86(4) $ $ dmesg OpenBSD 5.6-current (GENERIC.MP) #424: Wed Oct 15 17:01:29 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8535351296 (8139MB) avail mem = 8299438080 (7914MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xed460 (58 entries) bios0: vendor American Megatrends Inc. version FD date 01/23/2013 bios0: Gigabyte Technology Co., Ltd. 970A-DS3 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT MCFG HPET SSDT BGRT acpi0: wakeup devices SBAZ(S4) PS2K(S3) PS2M(S3) P0PC(S4) GEC_(S4) UHC1(S4) UHC2(S4) USB3(S4) UHC4(S4) USB5(S4) UHC6(S4) UHC7(S4) PE20(S4) PE21(S4) PE22(S4) PE23(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 16 (boot processor) cpu0: AMD FX(tm)-4100 Quad-Core Processor , 3616.99 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TOPEXT,ITSC cpu0: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache cpu0: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 32 4MB entries fully associative cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 200MHz cpu1 at mainbus0: apid 17 (application processor) cpu1: AMD FX(tm)-4100 Quad-Core Processor , 3616.57 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TOPEXT,ITSC cpu1: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache cpu1: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu1: DTLB 32 4KB entries fully associative, 32 4MB entries fully associative cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 18 (application processor) cpu2: AMD FX(tm)-4100 Quad-Core Processor , 3616.57 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TOPEXT,ITSC cpu2: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache cpu2: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu2: DTLB 32 4KB entries fully associative, 32 4MB entries fully associative cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 19 (application processor) cpu3: AMD FX(tm)-4100 Quad-Core Processor , 3616.57 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TOPEXT,ITSC cpu3: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache cpu3: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu3: DTLB 32 4KB entries fully associative, 32 4MB entries fully associative cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 5 pa 0xfec0, version 21, 24 pins ioapic1 at mainbus0: apid 6 pa 0xfec2, version 21, 32 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318180 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 3 (P0PC) acpiprt2 at acpi0: bus 4 (PE20) acpiprt3 at acpi0: bus -1 (PE21) acpiprt4 at acpi0: bus -1 (PE22) acpiprt5 at acpi0: bus -1 (PE23) acpiprt6 at acpi0: bus -1 (PC02) acpiprt7 at acpi0: bus -1 (PC03) acpiprt8 at acpi0: bus 1 (PC04) acpiprt9 at acpi0: bus -1 (PC05) acpiprt10 at acpi0: bus -1 (PC06) acpiprt11 at acpi0: bus -1 (PC07) acpiprt12 at acpi0: bus 2 (PC09) acpiprt13 at acpi0: bus -1 (PC0A) acpiprt14 at acpi0: bus -1 (PC0B) acpiprt15 at acpi0: bus -1 (PC0C) acpiprt16 at acpi0: bus -1 (PC0D) acpicpu0 at acpi0: C2, PSS acpicpu1 at acpi0: C2, PSS
Intel HD cards / How can I tell support
Hello, I'm looking at an Intel NUC i5-4250U, which includes an Intel HD graphics 5000 (dmesg courtesy Gabriel Guzman here: http://gabe.svbtle.com/openbsd-and-the-intel-nuc) The chip seems to be a gen7, but I'm having trouble finding what the genN names line up with driver-wise. Are these part of the i915 group, or do they have a different name? From the dmesg I can see inteldrm attaches to the chip, so I know it's known about, but drm(4) and intel(4) don't mention this chip by name, and I haven't been able to find any definitive way to say what extent it's supported to. What docs/search terms am I missing here? On a side note, anyone have experience with the new NUCs? Thanks,
Re: IPv6 nonfunctional after upgrade from 5.5 to 5.6
Had difficulties with my mail client and unsure if the original message
was sent, so I apologize in advance if this was already received.
Hi,
Sure no problem,
I have no mygate as my IPv4 default gateway is determined via dhcp from
my cable modem (or ISP).
My hostname.if files are as follows:
/etc/hostname.em0
inet 192.168.82.1 255.255.255.0 192.168.82.255
inet6 autoconf
up
/etc/hostname.vr0
dhcp
inet6 autoconf
up
The method that I use to provision the primary IPv6 address on the vr0
(external or public) interface is via the 3rd party software called
Dibbler. Somehow it is able to plumb up the address, but I have to
manually add the default route from information obtained via the same
Dibbler client.
My route add default command works as expected and puts the box online
IPv6. The command is as follows:
route -n delete -inet6 default
route -n add -inet6 default ${default_route}
Where $default_route is the IPv6 address returned by the dibbler client
as the IP that should be the default gateway despite the fact that the
Dibbler client is unable to add that route itself for OpenBSD.
My script successfully adds the default gateway route.
Then when my script obtains the delegated prefix, Dibbler also cannot
plumb up the IP on the em0 (the internal private LAN) interface, so my
script does it using the following ifconfig command:
ifconfig $PREFIXIFACE inet6 $PREFIX11 prefixlen $PREFIX1LEN
My script determines $PREFIXIFACE is em0, $PREFIX1 is the prefix
obtained from my ISP via Dibbler and $PREFIX1LEN is determined to be 64.
So the resulting command was:
ifconfig em0 inet6 2601:7:5780:c99::1 prefixlen 64
But the route for the subnet is missing.
% netstat -nr | grep 2601
2601:7:5780:c99::1 00:1b:21:4e:d4:a2
UHLl 0 5834 - 1 lo0
However the one setup directly via Dibbler on vr0 has such a route:
default2001:558:6030:44::1
UGS0 8530 - 8 vr0
2001:558:6030:44::/64 link#1
UC 10 - 4 vr0
2001:558:6030:44::100:01:5c:6f:f6:46
UHLc 1 544 - 4 vr0
2001:558:6030:44:35cc:9a5e:65f7:c139 00:40:63:e6:42:a5
UHLl 10 - 1 lo0
2001:558:6030:44::/64 link#1
UC 10 - 4 vr0
Thanks!
SlyM
On 11/03/2014 02:42 PM, Reyk Floeter wrote:
Hi,
can you show us the contents of your hostname.* and mygate files?
What are the specific configuration steps?
Reyk
Am 03.11.2014 um 18:04 schrieb Sly Midnight slymidni...@yahoo.com:
Hello everyone.
I am new to this list but I am in need of some help.
I have been running OpenBSD since 4.6 as my firewall and gateway with
much success (transitioned from FreeBSD) and it was working out great as
a light weight and secure OS for my Internet router and gateway.
One of the uses of this box is to route IPv6 for my local subnet out to
the Internet. It used to use a free tunnel service that worked great.
But I have since transitioned to the IPv6 that my ISP provides me
directly. This was a bit painful at first but I got it working with the
help of some 3rd party software not available in the ports collection
called Dibbler. This software is not perfect, but with the help of a
script I fleshed out myself i got it to do what I needed. The client
portion of that DHCPv6 program reaches out to the DHCPv6 server on my
ISP's network and obtains all the information I need. The only thing it
is currently able to do on it's own is plumb up the primary IPv6 address
it obtains from the ISP. But I still have to add the requisite default
route information. Also I have to then manually plumb up the delegated
IPv6 prefix assigned to my subnet (that I request) to my internal interface.
I then use rtadvd to advertise that route and allow for SLAAC to work on
my internal network to all IPv6 aware hosts.
This used to work just fine until I upgraded my router to 5.6 from 5.5.
After adding 'inet6 autoconf' to my hostname.if files, it appeared I got
my IPv6 functionality back.
However, while the box itself is back on IPv6 Internet, the subnet it
acts as a router for can no longer get onto the Internet.
After looking into it further it appears there is something wrong with
the routing table. There is no route for the subnet of the address I
manually add via ifconfig to the internal interface. I do not know how
to do this, nor was this previously necessary. The ifconfig command I
call to add the address specified the prefixlen 64 which *should* imply
the address is part of a /64 subnet where all other addresses within
that subnet should be reachable via the same interface the address is
plumbed up on.
When I do a route show or a netstat -nr I do not see such a route nor
have I been successful in figuring out how to call the route add command
to add such a
strange behavior in disklabel partitioning of new disk
I'm trying to set up 5.6/amd64 on a new-from-the-factory 750GB disk
which I've just had installed in a Thinkpad T60. (This Thinkpad had
previously been running 5.5/amd64 using an older/smaller disk, with
no problems).
I want to try having the entire new disk secured with softraid crypto.
So, I booted the Thinkpad (with the new disk installed) from my 5.6/amd64
CD (dmesg below) and dropped into the shell. The dmesg shows that the
bsd.rd kernel detected the new disk as sd0.
To try to set up the new disk, I first did
# fdisk -i sd0
to set up the MBR partitions, then
# disklabel -E sd0
to add a single 'a' partition of type 'RAID' containing all the space
after the first 64 sectors (reserved as per Disklabel tricks and tips
in section 14.3 of the OpenBSD FAQ). So far so good:
# fdisk sd0
Disk: sd0 geometry: 91201/255/63 [1465149168 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending LBA Info:
#: id C H S - C H S [ start:size ]
---
0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
*3: A6 0 1 2 - 91200 254 63 [ 64: 1465144001 ] OpenBSD
# disklabel sd0
# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: WDC WD7500BPKX-2
duid: 407d46caba526d90
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 91201
total sectors: 1465149168
boundstart: 64
boundend: 1465144065
drivedata: 0
16 partitions:
#size offset fstype [fsize bsize cpg]
a: 1465144001 64RAID
c: 14651491680 unused
#
Next I tried to follow the instructions in section 14.21 of the FAQ
and zero the first megabyte of the new partition:
# dd if=/dev/zero bs=1m count=1 of=/dev/rsd0a
Now the strange behavior: Checking the output of fdisk and disklabel
again as a sanity check, I find that the fdisk output is unchanged (as it
should be!), but disklabel now shows that the newly-created 'a' partition
has vanished, and the duid has been zeroed:
# disklabel sd0
# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: WDC WD7500BPKX-2
duid:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 91201
total sectors: 1465149168
boundstart: 64
boundend: 1465144065
drivedata: 0
16 partitions:
#size offset fstype [fsize bsize cpg]
c: 14651491680 unused
#
It's as if the 'a' partition I created (which started at offset 64) was
actually overlapping the disklabel metadata!
One other data point: I also saw the same behavior ('a' partition gone,
duid zeroed) when I repeated the same commands but with the (recreated)
'a' partition having the default '4.2BSD' fstype instead of 'RAID'.
Can anyone clue me in as to what's I'm doing wrong?
I thought I understood disk partitioning (and I'm fully aware that
overlapping partitions are doubleplusungood!), but I have the feeling
I'm missing something obvious here
--- begin dmesg ---
OpenBSD 5.6 (RAMDISK_CD) #303: Fri Aug 8 00:25:26 MDT 2014
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 3203203072 (3054MB)
avail mem = 3112607744 (2968MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (68 entries)
bios0: vendor LENOVO version 7IET23WW (1.04 ) date 12/27/2006
bios0: LENOVO 87424GU
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT SSDT SSDT SSDT
SSDT
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1995.33 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,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF
cpu0: 4MB 64b/line 16-way L2 cache
cpu0: apic clock running at 166MHz
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 2, remapped to apid 1
acpi0: WARNING EC not initialized
acpi0: WARNING EC not initialized
acpi0: WARNING EC not initialized
acpi0: WARNING EC not initialized
acpi0: WARNING EC not initialized
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (AGP_)
acpiprt2 at acpi0: bus 2 (EXP0)
acpiprt3 at acpi0: bus 3 (EXP1)
acpiprt4 at acpi0: bus 4 (EXP2)
acpiprt5 at acpi0: bus 12 (EXP3)
acpiprt6 at acpi0: bus 21 (PCI1)
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 Intel 82945GM Host rev 0x03
ppb0 at pci0 dev 1 function 0 Intel 82945GM PCIE rev 0x03: msi
pci1 at ppb0 bus 1
vga1
Re: bridge + vlan broke after 5.5 5.6 upgrade
On 4 Nov 2014, at 06:41, Pieter Verberne pieterverbe...@xs4all.nl wrote: On 2014-11-02 13:51, Jorge Schrauwen wrote: Hey All, TL;DR: traffic leaving a bridge over a vlan does not get tagged but leaves untagged after upgrade. Is this by design? Looks exactly like my problem. Running 5.6 release. bridge(4) puts frames on the wire by calling the outgoing interfaces start routine, which in this case is vlan_start() because you're bridging vlan(4) interfaces. mpi@ and weerd@ correctly identified the diff where henning@ changed vlan_start(). he assumed that ether_output is always called before vlan_start, and moved the tagging code into ether_output to make injecting the vlan tag more streamlined. bridge obviously breaks this assumption cos it just shoves the packet into vlan_start() which then just shoves the packet onto the parent interface. i have a massive headache and sleep deficit right now so im not going to suggest a way to fix this. dlg
Re: strange behavior in disklabel partitioning of new disk
On 11/03/14 22:33, Jonathan Thornburg wrote: I'm trying to set up 5.6/amd64 on a new-from-the-factory 750GB disk which I've just had installed in a Thinkpad T60. (This Thinkpad had previously been running 5.5/amd64 using an older/smaller disk, with no problems). I want to try having the entire new disk secured with softraid crypto. So, I booted the Thinkpad (with the new disk installed) from my 5.6/amd64 CD (dmesg below) and dropped into the shell. The dmesg shows that the bsd.rd kernel detected the new disk as sd0. I do fdisk -iy sd0 then create the RAID on sd0 then MAKEDEV sd1 then run #bioctl -c C -l /dev/sd0a softraid0 then zero 1m of rsd1c then install to sd1
Re: kde4-4.13.3p0 on OpenBSD 5.6 10/15/2014 AMD64 snapshot
04 ноÑб. 2014 г. 3:11 полÑзоваÑÐµÐ»Ñ Stan Gammons sg063...@gmail.com напиÑал: Does anyone besides me experience crashes with Dolphin on kde4-4.13.3p0? When I click on the kde crash handler developer information tab it churns forever and ever and ever and never returns any information. What the ulimit -a command says? Also, could you post all uncommented global options in your /etc/samba/smb.conf? -- Vadim Zhukov
Re: audio in linux emulation, skype friends
On Mon, Nov 03, 2014 at 07:16:34PM +0100, Alexandre Ratchov wrote: On Mon, Nov 03, 2014 at 08:58:29AM -0800, Ryan Freeman wrote: On Fri, Oct 31, 2014 at 08:58:15AM +0100, Alexandre Ratchov wrote: On Fri, Oct 31, 2014 at 11:48:00AM +0530, Jay Patel wrote: Try https://jitsi.org/ or tox https://tox.im/ Hope this helps. thanks for the links. The question is more about audio support in linux emulation itself. Does anyone use it? does it even work? what about deleting it? I haven't used i386 for a year or so and i thought linux compat was still pretty much not usable anymore :-) but when i last used it, it was just for binary released linux games such as unreal tournament. Not sure to understand, did you manage to play with unreal tournament on OpenBSD, with working audio? yes indeed, i used to haha so, i guess linux binaries that used sdl had sound. BTW, sdl (on linux) could be configured to use sndio, which would make sound work, as long as the linux binaries are dynamically linked against sdl. just for informational purposes, i would presume linux sdl binaries must have been using the ossaudio type layer as we have (had?) no alsa stuff. i don't use this anymore as my machines are amd64, cheers! so you won't object if ossaudio is removed for linux emulation, right? -- Alex
