I don't consider myself expert at this, but, yes, I think that is the case. At least for me, it has worked well. I have an ipsec tunnel set up between two residential cable internet connections. Both are DHCP, so there is no static endpoint. I use dDNS to keep the endpoint IP's up to date (I do own my own domain, but I suppose you don't have to). The tunnel goes down for a few minutes from time to time (I think mostly because of problems with my internet connections, not so much DNS ...

Marcelino, Pan y Vino, ven a vivir el milagro [demime 1.01d removed an attachment of type image/jpeg which had a name of 1.jpg]

Hi. I have a problem in computer memory results. My computer has got 3.5Gbyte Ram, but memory amount seems 2.6 Gbyte on some command output. How could i fix this ? Here is the "Dmesg output" and "faulty result". -- bash-4.1# dmesg OpenBSD 4.8 (GENERIC.MP) #359: Mon Aug 16 09:16:26 MDT 2010 deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ ("AuthenticAMD" 686-class, 512KB L2 cache) 2.41 ...

Hi, Are there any changes in Xorg that affects the way I change the keyboard layout? I'm running -current. I have an US keyboard but need the dead keys, since my native language have accents and other local punctuation. 1. I'm running current and I tried every possible combination that worked in the past in xorg.conf: Option "XkbRules" "xorg" Option "XkbModel" "us" Option "XkbLayout" "intl" (and a lot of other confs...) 2. Tried different ...

Using amd64 instead of i386 will give you more memory. Additionally, you should look for "bigmem" in the archivals if the previous solution is not enough. Luis.

Roughly speaking, vmstat only shows available mem *for processes*, that is, mem that isn't reserved by the kernel for the buffer cache and other usefull things. Also, currently we have some limitation to address all physical mem, as can be seen on the mem lines in the dmesg. The kernel only "sees" about 3G of your mem.

Just found the problem. I was setting LC_CTYPE="en_US.UTF-8" in .xsession, as suggested by stsp@ at http://www.undeadly.org/cgi?action=article&sid=20100729233638 This was having no effect in Xorg at all. In firefox, when typing an accented character, I was getting: ** (firefox-bin:13132): WARNING **: Error converting text from IM to UTF-8: Invalid byte sequence in conversion input Just put all the stuff I normally put in .xsession in .xinitrc (like setting LC_CTYPE). Problem solved. ...

Hi, thanks to the recent enhancements in openbsd 4.8-current (thanks!), I started playing with l3vpn's between openbsd and JUNOS (10.4R1) and finally got it working, but I needed to disable RFC 3479 (fault tolerance for ldp) and use the interface's IP as transport-address on the router side and make a small modification in ldpd/hello.c in order to get the ldp hello's from the router accepted. Maybe someone can have a look at the diff below and see if it makes sense. Marcel # cvs diff -u ...