How to (help) diagnose a system hang?

Hi there, I'm running 4.3-RELEASE on amd64, with a GENERIC kernel that has RAIDframe and the option RAID_AUTOCONFIG enabled. Yesterday, I experienced some sort of a system hang. The system responded to echo requests and routing and NAT kept working. When I tried to connect to several services on

Re: dhcpd dying

On Fri, May 09, 2008 at 08:17:23PM -0500, Emilio Perea wrote: | I have been running amd64 GENERIC.MP -current on my home server for a | about 2-1/2 years. Two or three days ago dhcpd started dying without | any error message. Since I see that there have been quite a few changes | in the last few

Re: dhcpd dying

On Sat, May 10, 2008 at 9:29 AM, Emilio Perea <[EMAIL PROTECTED]> wrote: > On Sat, May 10, 2008 at 08:47:06AM +0300, Denis Doroshenko wrote: >> dhcpd seems to be being intensively worked on. there is some new stuff >> in the tree to sync several dhcpd or something. perhaps you might want >> to look

Re: teTeX

On Fri, May 9, 2008 at 6:20 PM, Predrag Punosevac <[EMAIL PROTECTED]> wrote: > One could also argue that much finer TeXLive port could have been done as > certain parts of TeXLive experience rapid > development. I think that would be making work for the sake of it. TeXLive release once a year, so

Re: PF Congestion and state table question

I was still wondering what could be considered "maximum" session concurrency that I could expect, with various hardware combinations? Is anyone that can tell me if it could be feasible with OpenBSD and better hardware? Even if we have to move to a different platform than i386, like maybe a Sun

Broken CF or what?

I was trying to install 4.3 to a SanDisk 1GB CF disk but the installer aborts when it tries to create the partitions to the disk I get following when the creating partitions: pciide:0:0:0: timeout waiting for DRQ, st=0x51 , err=0x00 wd0e: device timeout writing fsbn 47908 (wd0 bn 2100672, cn 521

IPsec clients

Hi, Does OpenBSD provide a possibility to assign specific PF rules to a user or group, using IPsec for remote access. For example to exclusively allow User A to access System A and user B to access System B. Thx in advance. Met vriendelijke groet, Paul Liebregts ICT Consultant Liebr

Re: IPsec clients

On 2008-05-09, Paul Liebregts <[EMAIL PROTECTED]> wrote: > > Does OpenBSD provide a possibility to assign specific PF rules to a user > or group, using IPsec for remote access. For example to exclusively > allow User A to access System A and user B to access System B. Yes, read about tags in ipsec

netstart(8) brings interface down in case of dhcp

hello, in case there is a "dhcp" in hostname.if(5), netstart does the following: cmd="ifconfig $if $name $mask $bcaddr $ext1 $ext2 down" cmd="$cmd;dhclient $if" in my case if have /etc/hostname.ath0 like: up nwid openwlan dhcp the interface comes up within the network "openwlan" and then is br

Re: PF Congestion and state table question

Jordi Espasa Clofent wrote: I was still wondering what could be considered "maximum" session concurrency that I could expect, with various hardware combinations? Is anyone that can tell me if it could be feasible with OpenBSD and better hardware? Even if we have to move to a different platform

Re: dhcpd dying

On Sat, May 10, 2008 at 09:37:10AM +0200, Paul de Weerd wrote: > Maybe this has something to do with it : > > -- > From: Bob Beck <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Date: Wed, 7 May 2008 23:3

zyd(4) {xfer,frame} too short (length=XX)

Hi all, Today I stumbled across a dirt cheap (~6 EUR) wireless + bluetooth combo USB device. Turns out the wireless part is supported (it's a zyd(4)) : uhub3 at uhub0 port 1 "Genesys Logic USB2.0 Hub" rev 2.00/6.0b addr 2 zyd0 at uhub3 port 1 configuration 1 interface 0 "ZyDAS USB2.0 WLAN" rev

Re: Broken CF or what?

On Sat, May 10, 2008 at 12:48:10PM +0300, Timo Myyr? wrote: > I was trying to install 4.3 to a SanDisk 1GB CF disk but the installer > aborts when it tries to create the partitions to the disk > > I get following when the creating partitions: > pciide:0:0:0: timeout waiting for DRQ, st=0x51 , err=

[4.3]: ThinkPad X61s cannot boot i386 or amd64 ISO's with AHCI

Hello misc@, My laptop wouldn't finish booting either the i386 or amd64 ISO's from the 4.3 CD set using an Ultrabase X6 and ultrabay slim CDRW/DVD drive. It hung after detecting the fingerprint reader. I tried disabling 'acpidock' in the boot config (mentioned in http://marc.info/?l=openbsd-misc&m

Re: zyd(4) {xfer,frame} too short (length=XX)

Paul de Weerd ha scritto: Hi all, Today I stumbled across a dirt cheap (~6 EUR) wireless + bluetooth combo USB device. Turns out the wireless part is supported (it's a zyd(4)) : uhub3 at uhub0 port 1 "Genesys Logic USB2.0 Hub" rev 2.00/6.0b addr 2 zyd0 at uhub3 port 1 configuration 1 interfac

Re: [4.3]: ThinkPad X61s cannot boot i386 or amd64 ISO's with AHCI

On Sat, 2008-05-10 at 10:37 -0600, Brad Walker wrote: > [demime 1.01d removed an attachment of type text/x-log which had a name of > i386-ahci-problem.log] > > [demime 1.01d removed an attachment of type text/x-log which had a name of > i386-no-ahci-success.log] > > [demime 1.01d removed an att

PF parsing error

As of 4.3 the following syntax to define a macro is no longer allowed in PF portlist = "{" 10 "}"

Screen,colorls,xterms issue. 4.2

Hi, I'm using OpenBSD 4.2, a clean install. I have experienced some problems using screen and X with colorsls. The issue is that when I launch 'screen' on virtual terminals (C0,C1...) I don't have any problem but when launch X, on the xterm/rxvt I have open I can't launch a screen because the col

Newbie x509 question

Hi all, appreciate any advice. I currently have numerous OpenBSD devices acting as FW/routers, all happily taking to each other with IPSec using ipv4 publickeys. I'm now ready to dive into the world of Road Warriors using OSX and Windows. As far as I can tell, I'm pretty much forced to use an x

Re: PF parsing error

On 2008-05-10, Peter Fraser <[EMAIL PROTECTED]> wrote: > As of 4.3 the following syntax to define a macro is no longer allowed in PF > portlist = "{" 10 "}" It works again in -current (in the last few days; quite possibly not in a snapshot yet).

Re: Screen,colorls,xterms issue. 4.2

On 2008-05-10, Jesus Sanchez <[EMAIL PROTECTED]> wrote: > I have set an alias for ls='colorls -GF' (color output) and this causes > the problems on a screen session. I have set the TERM="xterm-color" on > my /etc/profile. Why do that? That will override the correct terminal configuration and send

Re: Screen,colorls,xterms issue. 4.2

Stuart Henderson escribis: On 2008-05-10, Jesus Sanchez <[EMAIL PROTECTED]> wrote: I have set an alias for ls='colorls -GF' (color output) and this causes the problems on a screen session. I have set the TERM="xterm-color" on my /etc/profile. Why do that? That will override the correct

Re: Screen,colorls,xterms issue. 4.2

On 22:20:18 May 10, Jesus Sanchez wrote: > Hi, I'm using OpenBSD 4.2, a clean install. > > I have experienced some problems using screen and X with colorsls. The > issue is that when I launch 'screen' on virtual terminals (C0,C1...) I > don't have any problem but when launch X, on the xterm/rxvt I

WPA in -current

OpenBSD 4.3-current (GENERIC) #853: Fri May 2 04:37:23 MDT 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC Hardware Info: ral0 at pci0 dev 9 function 0 "Ralink RT2561S" rev 0x00: irq 5, address 00:0e:2e:xx:xx:xx ral0: MAC/BBP RT2561C, RF RT2527 # ifconfig ral0 ral0: flags=8843

Re: netstart(8) brings interface down in case of dhcp

On Sat, May 10, 2008 at 02:50:05PM +0300, Denis Doroshenko wrote: > hello, > > in case there is a "dhcp" in hostname.if(5), netstart does > the following: > > cmd="ifconfig $if $name $mask $bcaddr $ext1 $ext2 down" > cmd="$cmd;dhclient $if" > > in my case if have /etc/hostname.ath0 like: > > up

Re: PF Congestion and state table question

* Steve Johnson <[EMAIL PROTECTED]> [2008-05-10 14:33]: > Nice to know. We're currently far from reaching those packets per second > output at the moment. I'd say with all our traffic we'd probably be looking > at 200K. I guess the platform might be the issue then, as even after > putting in pla

Re: WPA in -current

http://www.openbsd.org/plus.html "Enter wpa-psk(8), a tool to generate WPA-PSK keys from the ssid and passphrase." http://www.openbsd.org/cgi-bin/man.cgi?query=wpa-psk&apropos=0&sektion=0&manp ath=OpenBSD+Current&arch=i386&format=html Regards Hagen Volpers > -Urspr|ngliche Nachricht

Re: WPA in -current

On Sun, May 11, 2008 at 12:21 AM, openbsd misc <[EMAIL PROTECTED]> wrote: > http://www.openbsd.org/plus.html > > "Enter wpa-psk(8), a tool to generate WPA-PSK keys from the ssid and > passphrase." > > http://www.openbsd.org/cgi-bin/man.cgi?query=wpa-psk&apropos=0&sektion=0&manp > ath=OpenBSD+Curren

Re: Screen,colorls,xterms issue. 4.2

Girish Venkatachalam escribis: On 22:20:18 May 10, Jesus Sanchez wrote: Hi, I'm using OpenBSD 4.2, a clean install. I have experienced some problems using screen and X with colorsls. The issue is that when I launch 'screen' on virtual terminals (C0,C1...) I don't have any problem but when la

Re: Newbie x509 question

On Sat, May 10, 2008 at 12:52:38PM -0700, scott learmonth wrote: > I currently have numerous OpenBSD devices acting as FW/routers, [and] > IPSec using ipv4 publickeys. > > I'm now ready to dive into the world of Road Warriors using OSX and > Windows. (...) I'm pretty much forced to use an x509 > c

Re: Screen,colorls,xterms issue. 4.2

On Sun, May 11, 2008 at 03:59:17AM +0200, Jesus Sanchez wrote: > Stuart Henderson escribis: >> On 2008-05-10, Jesus Sanchez <[EMAIL PROTECTED]> wrote: >>> I have set an alias for ls='colorls -GF' (color output) and this causes >>> the problems on a screen session. I have set the TERM="xterm-color"