kernel hiccups with two OpenVPN tunnels
So a few releases ago, I found that if I had OpenVPN running on an OpenBSD box as a hub, and I did a large transfer from one client to another, the OpenBSD box would occasionally kernel panic - something about mbufs, I can pull the kernel stack traces up if desired. The hosting company said they saw this quite often with OpenBSD boxes. As of 4.8, I notice that if I do a similar large transfer, the system just stops responding to all network traffic for a period of time, perhaps around 10 minutes or longer. During this time it's unpingable and won't forward any packets. It eventually recovers, which is WAY better than a kernel panic (the mbuf corruption actually corrupted my root disk on more than one occasion). Before I go digging into this, I was wondering if anyone else has had this experience, and how I should consider troubleshooting it. -- http://www.subspacefield.org/~travis/ What do you call this music? Hadouken Hadouken? It's down right fierce If you are a spammer, please email j...@subspacefield.org to get blacklisted. [demime 1.01d removed an attachment of type application/pgp-signature]
openvpn openbsd = kernel lockups
Hey there, I have been asked to help a friend whose system is used as a VPN hub. It used to be an older OpenBSD, possibly 4.5 or 4.6, and he got many kernel panics around some buffer routines (possibly mbuf) that led to disk corruption. It's now OpenBSD 4.8 amd64, and if the system has transit traffic - going from one leaf through the hub to another - in excess of 100MB at 200kB/s or more, the system stops responding to network traffic for a minute or three. During this time, it becomes unpingable, and the VPN basically stops working temporarily. Often it will start up again, but if the connection is lossy (like a wifi connection), then it sometimes won't recover. Before I investigate further, does anyone have a clue as to what my be going on here? If not, what would be the suggested method for investigating? -- Effing the ineffable since 1997. | http://www.subspacefield.org/~travis/ My emails do not usually have attachments; it's a digital signature that your mail program doesn't understand. If you are a spammer, please email j...@subspacefield.org to get blacklisted. [demime 1.01d removed an attachment of type application/pgp-signature]
Re: equivalent of Linux mount -o bind
On Fri, Jan 28, 2011 at 03:52:53PM -0800, Travis H. wrote: So I'm curious if there's something in OpenBSD that's similar to the mount -o bind /dir1 /dir2 to make dir1 appear where dir2 is. For those who asked, one sample use is for something like this: Starting with the 2.4-series Linux kernels, it has been possible to mount a filesystem simultaneously in two different places. Aha! you might think, as I did. Then surely we can mount the backups read-only in /snapshot, and read-write in /root/snapshot at the same time! Alas, no. Say your backups are on the partition /dev/hdb1. If you run the following commands, mount /dev/hdb1 /root/snapshot mount --bind -o ro /root/snapshot /snapshot then (at least as of the 2.4.9 Linux kernel--updated, still present in the 2.4.20 kernel), mount will report /dev/hdb1 as being mounted read-write in /root/snapshot and read-only in /snapshot, just as you requested. Don't let the system mislead you! In the example above, the second mount call will cause both of the mounts to become read-only, and the backup process will be unable to run. Scratch this one. Update: I have it on fairly good authority that this behavior is considered a bug in the Linux kernel, which will be fixed as soon as someone gets around to it. If you are a kernel maintainer and know more about this issue, or are willing to fix it, I'd love to hear from you! -- Effing the ineffable since 1997. | http://www.subspacefield.org/~travis/ My emails do not usually have attachments; it's a digital signature that your mail program doesn't understand. If you are a spammer, please email j...@subspacefield.org to get blacklisted. [demime 1.01d removed an attachment of type application/pgp-signature]
host(1) oddities
Hey all, I ran host www.google.com on a new OpenBSD 4.8 install and got this: 13:50:28.132052 127.0.0.1.41209 127.0.0.1.48830: udp 31 13:50:28.132081 127.0.0.1 127.0.0.1: icmp: 127.0.0.1 udp port 48830 unreachable 13:50:29.133552 ::1.38033 ::1.48830: udp 31 13:50:29.133577 ::1 ::1: icmp6: ::1 udp port 48830 unreachable 13:50:34.143471 127.0.0.1.41209 127.0.0.1.48830: udp 31 What gives? Nothing's on port 48830; should there be something there? -- Effing the ineffable since 1997. | http://www.subspacefield.org/~travis/ My emails do not usually have attachments; it's a digital signature that your mail program doesn't understand. If you are a spammer, please email j...@subspacefield.org to get blacklisted. [demime 1.01d removed an attachment of type application/pgp-signature]
miscellaneous unofficial OpenBSD ports
http://www.subspacefield.org/~travis/OpenBSD/ Need to be updated - last update was for 4.1 -- A Weapon of Mass Construction My emails do not have attachments; it's a digital signature that your mail program doesn't understand. | http://www.subspacefield.org/~travis/ If you are a spammer, please email j...@subspacefield.org to get blacklisted. [demime 1.01d removed an attachment of type application/pgp-signature]
