Re: Preferred configuration for SLAAC in hostname.if
On 07/21/17 00:29, Carlos Cardenas wrote: > Doing a new install from a long hiatus, I've noticed SLAAC is now > in the kernel. > > Looking through the archives: > https://marc.info/?l=openbsd-misc&m=14335917638&w=2 > > seems to indicate that the keyword 'rtsol' and 'inet6 autoconf' are > "equivalent" as far as /etc/netstart is concerned. > > What's the preferred setting for SLAAC in hostname.if(5)? "inet6 autoconf" is what you get if you choose the autoconf option during install. I wasn't even aware that the old style "rtsol" was still supported. - P -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: Read sysctl from file
On Thu, Jul 20, 2017 at 06:14:03PM -0700, Lyndon Nerenberg wrote: > > > On Jul 20, 2017, at 6:35 AM, BARDOU Pierre wrote: > > > > Hello, > > > > Is there a way to make sysctl re-read its conf file, or even another file, > > like sysctl -p does on linux systems ? > > Supporting this option would be nice, as it is used by the sysctl module of > > ansible. I'm also using Ansible to distribute sysctl configs to OpenBSD hosts. In the sysctl tasks I set sysctl_set to yes and reload to no. That works fine. Remi
Re: Mounting DVD with single file burned onto
Sending to ports@ to continue this part of the discussion.
Please remove misc@ in any replies.
On Thu, Jul 20, 2017 at 01:20:41AM +0200, Stefan Wollny wrote:
> >> When it comes to backups one usual advice (among others) is to make use
> >> of different storage types. So I have tar'ed one folder (~32GB) and
> >> zip'd with p7zip. man p7 explains the '-v{size}bkmg'-switch but I got
> >> "System ERROR: E_NOTIMPL".
> >
> > I am unable to recreate this problem on amd64. I just used
> >
> > $ vmctl create 100mb.file -s 100m
> > $ 7z a test.7z 100mb.file -v5k
> >
> > I obtained 4 output files, test.7z.0001 thru test.7z.0004.
> >
>
> This is the actual command and result:
>
> $ tar cf - /home/sw/Bilder/Nikon\ Transfer/20170430_Keukenhof/ | 7z a
> -t7z -m0=lzma -mx=9 -mfb=64 -md=32m -ms=on -v4880m -si
> Keukenhof_20170430.tar.7z
> tar: Removing leading / from absolute path names in the archive
>
> 7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
> p7zip Version 16.02 (locale=de_DE.UTF-8,Utf16=on,HugeFiles=on,64 bits,4
> CPUs x64)
>
> System ERROR:
> E_NOTIMPL
I ran the same command with a small 100MB test file, and didn't bump into
this either. I can guess that your large pipe is bumping up against a
limit. There's only one module where "System ERROR:" is produced:
CPP/7zip/UI/Console/MainAr.cpp. But it's a catch(). I can try to
reproduce but it will take me some time to prepare a test environment
large enough. You may be able to set a breakpoint there and obtain
a backtrace to determine the source of the error. That's what I will
do when I try to recreate with a 32GB test stream.
Re: Read sysctl from file
> On Jul 20, 2017, at 6:35 AM, BARDOU Pierre wrote:
>
> Hello,
>
> Is there a way to make sysctl re-read its conf file, or even another file,
> like sysctl -p does on linux systems ?
> Supporting this option would be nice, as it is used by the sysctl module of
> ansible.
Here's the script we call (ansible handler, or as an rdist 'special') whenever
we push a new sysctl.conf. It's the same code the system runs at boot time,
lifted out into a standalone script.
#!/bin/sh
# sysctlreload: apply sysctl.conf(5) settings.
# Strip in- and whole-line comments from a file.
# Strip leading and trailing whitespace if IFS is set.
# Usage: stripcom /path/to/file
stripcom() {
local _file=$1 _line
[[ -s $_file ]] || return
while read _line ; do
_line=${_line%%#*}
[[ -n $_line ]] && print -r -- "$_line"
done <$_file
}
stripcom /etc/sysctl.conf |
while read _line; do
sysctl "$_line"
done
Preferred configuration for SLAAC in hostname.if
Howdy. Doing a new install from a long hiatus, I've noticed SLAAC is now in the kernel. Looking through the archives: https://marc.info/?l=openbsd-misc&m=14335917638&w=2 seems to indicate that the keyword 'rtsol' and 'inet6 autoconf' are "equivalent" as far as /etc/netstart is concerned. What's the preferred setting for SLAAC in hostname.if(5)? +--+ Carlos
Re: Read sysctl from file
On 20/07/17 18:48, Consus wrote: On 07:08 Thu 20 Jul, Kai Wetlesen wrote: Because it's a nice way to apply configuration changes made to /etc/sysctl.conf without restarting the whole server? Systemctl doesn't offer hot reload unless the controlled daemon offers the capability in the first place. The only thing systemd does is hits the controlling process on the head with a known conf-reload signal or (gasp) a DBus control statement. Both of these can be done just as well with an rc script, and without restarting the service. What systemd has to do with anything? We are talking about sysctl(8) and sysctl.conf(5). Guys, it's easy to emulate sysctl -p with a simple 4 line (maybe less) script. In advance, /etc/rc already does that. G
Re: vmd: routing problem
On Thu, Jul 20, 2017 at 02:19:29PM +0200, Leo Unglaub wrote: > Hey, > > On 07/20/17 13:05, Mischa Peters wrote: > > Can you ask them how they route the separate subnet to you? > > as far as i understand it they route the subnet on my main ip address. > > > From there documentation: > > Newly assigned IPv4 subnets are statically routed on the main IP address of > > the server, so no gateway is required. > > I hope that answers your question. > Thanks and greetings > Leo Like I said before, I'm not a networking expert, but what you've said there doesn't make sense (at least to me). You'll probably need to explain to them what you are trying to do and have them help you. I don't think this is a vmd related network issue. -ml
Re: Read sysctl from file
> Because it's a nice way to apply configuration changes made to > /etc/sysctl.conf without restarting the whole server? Systemctl doesn't offer hot reload unless the controlled daemon offers the capability in the first place. The only thing systemd does is hits the controlling process on the head with a known conf-reload signal or (gasp) a DBus control statement. Both of these can be done just as well with an rc script, and without restarting the service.
Re: Read sysctl from file
On 07:08 Thu 20 Jul, Kai Wetlesen wrote: > > Because it's a nice way to apply configuration changes made to > > /etc/sysctl.conf without restarting the whole server? > > Systemctl doesn't offer hot reload unless the controlled daemon offers > the capability in the first place. The only thing systemd does is hits > the controlling process on the head with a known conf-reload signal or > (gasp) a DBus control statement. Both of these can be done just as > well with an rc script, and without restarting the service. What systemd has to do with anything? We are talking about sysctl(8) and sysctl.conf(5).
Re: vmd: routing problem
> What would be the difference to your version where i use vether instead of > an alias? Or did i missunderstand you? > The difference is broadcast trafic won't be sent over your provider network.
Re: OT: protonmail mail body
Rupert Gallagher writes: > If you make business in Europe, or with people in Europe, then you > know about legal compliance with the Commision's standards, and their > pdf and p7m signed attachments. Similar standards exist in other > countries, and they use mime parts. If your email client cannot read > mime parts, you are out of business. If your email server rejects mime > messages, you are out of business. None of which changes the terms of use for this list, which are (from the FAQ): Plain text, 72 characters per line ALlan
Re: Openbsd 6.1 and Current Console Freezes and lockup Proxmox PVE5.0
Alex Bihlmaier writes: > the only issue i had running OpenBSD/Proxmox so far is a constant > system load of ~1 in the OpenBSD guest. The kvm-qemu process on the VM > host also has a quite constant load. In 6.1, load average display changed, typical "at rest" load averages are now ~1 at least that's what I see on my amd64 desktop machine. See http://marc.info/?l=openbsd-misc&m=149302502306466&w=2 Allan
Re: Read sysctl from file
> > > On 07:39 Thu 20 Jul, Theo de Raadt wrote: > > > > someone in linux land went off the map here. and then another piece of > > > > software started un-portably assuming that's the way to do things? > > > > > > Because it's a nice way to apply configuration changes made to > > > /etc/sysctl.conf without restarting the whole server? > > > > only thinking of yourself, and missing the point. > > > > the point is that the 25-year old sysctl design had no such feature, > > and now other things are changing that. > > > > No, what you want does not exist. > > He just asks if OpenBSD supports such a feature. Why so butthurt? I said no the first time, and provided a detailed explaination. Why did you feel the need jump in? Ichy butt?
Re: Read sysctl from file
On 07:45 Thu 20 Jul, Theo de Raadt wrote: > > On 07:39 Thu 20 Jul, Theo de Raadt wrote: > > > someone in linux land went off the map here. and then another piece of > > > software started un-portably assuming that's the way to do things? > > > > Because it's a nice way to apply configuration changes made to > > /etc/sysctl.conf without restarting the whole server? > > only thinking of yourself, and missing the point. > > the point is that the 25-year old sysctl design had no such feature, > and now other things are changing that. > > No, what you want does not exist. He just asks if OpenBSD supports such a feature. Why so butthurt?
Re: Read sysctl from file
> On 07:39 Thu 20 Jul, Theo de Raadt wrote: > > someone in linux land went off the map here. and then another piece of > > software started un-portably assuming that's the way to do things? > > Because it's a nice way to apply configuration changes made to > /etc/sysctl.conf without restarting the whole server? only thinking of yourself, and missing the point. the point is that the 25-year old sysctl design had no such feature, and now other things are changing that. No, what you want does not exist.
Re: Read sysctl from file
On 07:39 Thu 20 Jul, Theo de Raadt wrote: > someone in linux land went off the map here. and then another piece of > software started un-portably assuming that's the way to do things? Because it's a nice way to apply configuration changes made to /etc/sysctl.conf without restarting the whole server?
Re: Openbsd 6.1 and Current Console Freezes and lockup Proxmox PVE5.0
Am Tue, 18 Jul 2017 21:14:07 -0400 schrieb "trondd" : > When you do come back, mention if this is new with Proxmox 5.0 and if > you've used previous versions succesfully. > > I have been running OpenBSD on Proxmox for 2 or 3 years with no > problems. I think I am still on 4.x, though. I'll check tomorrow. the only issue i had running OpenBSD/Proxmox so far is a constant system load of ~1 in the OpenBSD guest. The kvm-qemu process on the VM host also has a quite constant load. thal
Re: Read sysctl from file
> Is there a way to make sysctl re-read its conf file, or even another file, > like sysctl -p does on linux systems ? > Supporting this option would be nice, as it is used by the sysctl module of= > ansible. But sysctl doesn't have a configuration file. there is a file called sysctl.conf, but it isn't a configuration file for the command. It is a list of sysctl changes, which will be made by the rc scripts at startup. someone in linux land went off the map here. and then another piece of software started un-portably assuming that's the way to do things?
Read sysctl from file
Hello, Is there a way to make sysctl re-read its conf file, or even another file, like sysctl -p does on linux systems ? Supporting this option would be nice, as it is used by the sysctl module of ansible. -- Cordialement, Pierre BARDOU
Re: OT: protonmail mail body
If you make business in Europe, or with people in Europe, then you know about legal compliance with the Commision's standards, and their pdf and p7m signed attachments. Similar standards exist in other countries, and they use mime parts. If your email client cannot read mime parts, you are out of business. If your email server rejects mime messages, you are out of business. Sent from ProtonMail Mobile On Thu, Jul 20, 2017 at 10:22 AM, Paul de Weerd wrote: > On Thu, Jul 20, 2017 at 02:46:02AM -0400, Rupert Gallagher wrote: | Out of > curiosity, I just checked what all the fuss is about. It turns out that > someone reads mail with a non-RFC compliant client, and thus fails to read > mime parts. Screw it, update your client. | The other problem seemed to be > with the list archive. It turns out that at least one archive has no problem > at all (*). If other archives have mime problems, they can update themselves > or just delete the mail. All of this while large parts of the world consider > those sending such mails to be spam (after spammers abused trick this to > evade anti-spam solutions), never to deliver them. Your base64-encoded mime > parts are braindead, but nobody is really worried: those e-mails will simply > be ignored by those that might otherwise have had useful replies. Just > because something is a standard, doesn't mean everybody should do it. There > are (very many) harmful standards (caused in large part by a lack of > ax-murderers, I hear). Cheers, Paul 'WEiRD' de Weerd -- > >[<++>-]<+++.>+++[<-->-]<.>+++[<+ > +++>-]<.>++[<>-]<+.--.[-] > http://www.weirdnet.nl/
Re: vmd: routing problem
Hey, On 07/20/17 09:46, Denis Fondras wrote: Can you people see something that i might missed? The easy way would be enable forwarding, add a vether(4) on the host, bridge it with tap0 and configure it with an IP in the 136.243.186.160/29 subnet. Use that IP as the gateway in your VMs. i did a try where i did the following: 1: I enabled forwarding. 2: I added one IP from the 136.243.186.160/29 subnet as an alias to the main interface of the host 3: I added the main interface em0 and the by vmd created tap0 to a bridge0 4: I tryed to assign the same IP as the alias on em0 to the virtual machine. What would be the difference to your version where i use vether instead of an alias? Or did i missunderstand you? Thanks and greetings Leo
Re: vmd: routing problem
Hey, On 07/20/17 13:05, Mischa Peters wrote: Can you ask them how they route the separate subnet to you? as far as i understand it they route the subnet on my main ip address. From there documentation: Newly assigned IPv4 subnets are statically routed on the main IP address of the server, so no gateway is required. I hope that answers your question. Thanks and greetings Leo
Re: vmd: routing problem
Hi Leo, Can you ask them how they route the separate subnet to you? Mischa > On 20 Jul 2017, at 12:59, Leo Unglaub wrote: > > Hey, > >> On 07/20/17 06:25, Mike Larkin wrote: >> sysctl net.inet.ip.forwarding=1 ? >> I'm not a networking expert but I think your VM's subnet mask is wrong for >> the gateway you are trying to use. > > thank you for your response. I tryed it with net.inet.ip.forwarding being 1 > and 0. Both don't work. About the subnet, thats what confuses me as well, but > the data center tells me that it is correct. As far as i understand it they > do some crazy stuff there with there IPv4 routing: > > https://wiki.hetzner.de/index.php/Zusaetzliche_IP-Adressen/en#Subnets > > Thanks and greetings > Leo >
Re: vmd: routing problem
Hey, On 07/20/17 06:25, Mike Larkin wrote: sysctl net.inet.ip.forwarding=1 ? I'm not a networking expert but I think your VM's subnet mask is wrong for the gateway you are trying to use. thank you for your response. I tryed it with net.inet.ip.forwarding being 1 and 0. Both don't work. About the subnet, thats what confuses me as well, but the data center tells me that it is correct. As far as i understand it they do some crazy stuff there with there IPv4 routing: https://wiki.hetzner.de/index.php/Zusaetzliche_IP-Adressen/en#Subnets Thanks and greetings Leo
Re: DUMP: Invalid argument: [block -60912738518]
Hi Jan, On Tue, 18 Jul 2017 21:53:03 +0200 Jan Stary wrote: > ... During the dump, there was some activity on the filesystem ... Try altering your scripts stop relevant daemons, then umount the partition before dumping & see if the problem persists. See sections '5.0 Conclusions' and '2.0 Active Tests' of Elizabeth D. Zwicky's paper "Torture-testing Backup and Archive Programs: Things You Ought to Know But Probably Would Rather Not". http://www.CoreDumps.De/doc/dump/zwicky/testdump.doc.html Specifically for /home;- also see '/etc/nologin' in login(1), which file I've found to be usefully created & nuked by my dump driving scripts. Cheers, -- Craig Skinner | http://twitter.com/Craig_Skinner | http://linkd.in/yGqkv7
Re: OT: protonmail mail body
On Thu, Jul 20, 2017 at 02:46:02AM -0400, Rupert Gallagher wrote: | Out of curiosity, I just checked what all the fuss is about. It turns out that someone reads mail with a non-RFC compliant client, and thus fails to read mime parts. Screw it, update your client. | The other problem seemed to be with the list archive. It turns out that at least one archive has no problem at all (*). If other archives have mime problems, they can update themselves or just delete the mail. All of this while large parts of the world consider those sending such mails to be spam (after spammers abused trick this to evade anti-spam solutions), never to deliver them. Your base64-encoded mime parts are braindead, but nobody is really worried: those e-mails will simply be ignored by those that might otherwise have had useful replies. Just because something is a standard, doesn't mean everybody should do it. There are (very many) harmful standards (caused in large part by a lack of ax-murderers, I hear). Cheers, Paul 'WEiRD' de Weerd -- >[<++>-]<+++.>+++[<-->-]<.>+++[<+ +++>-]<.>++[<>-]<+.--.[-] http://www.weirdnet.nl/
Re: vmd: routing problem
Hello, > Can you people see something that i might missed? The easy way would be enable forwarding, add a vether(4) on the host, bridge it with tap0 and configure it with an IP in the 136.243.186.160/29 subnet. Use that IP as the gateway in your VMs.
Re: vmd: routing problem
Hi List,
Hetzner has like other dedicated hosting providers an "crazy" looking
network setup for ipv4. Here point to point for the default gw in a
different network segment.
So it's important also to keep that in mind.
Maybe this document helps a bit, need to adapt to Openbsd.
https://wiki.hetzner.de/index.php/KVM_mit_Nutzung_aller_IPs_aus_Subnetz/en
Cheers
Karsten
Am 20.07.2017 6:29 vorm. schrieb "Mike Larkin" :
On Thu, Jul 20, 2017 at 04:23:40AM +0200, Leo Unglaub wrote:
> Hey friends,
> i am trying out vmd and I have a little problem getting networking going
> inside the guest machine. I am not sure if this is a problem in vmd or
> simply my misconfiguration.
>
> From my datacenter i got the following data:
>
> Main Server (OpenBSD GENERIC.MP#99 amd64)
> #
> IP: 144.76.102.204
> Netmask: 255.255.255.224
> Gateway: 144.76.102.193
>
>
> Virtual Machine (OpenBSD GENERIC.MP#99 amd64)
> #
> I got an entire subnet from the datacenter. 136.243.186.160/29 So i
decided
> to use the following IP in it.
>
> IP: 136.243.186.161
> Netmask: 255.255.255.248
> Gateway: 144.76.102.204
>
>
> According to there documentation they always route all subnets on the main
> IP. In my case 144.76.102.204.
>
>
> On my host I configured the em0 interface according to the datacenter data
> and it works fine. The host who runs vmd is connected correctly. In my
> /etc/vm.conf i created a switch called "uplink" and added em0 to it. When
i
> check the current config via ifconfig i get the following.
>
> > em0: flags=8b43
mtu 1500
> > lladdr 90:1b:0e:8b:0f:34
> > description: hetzner-uplink
> > index 1 priority 0 llprio 3
> > groups: egress
> > media: Ethernet autoselect (1000baseT
full-duplex,rxpause,txpause)
> > status: active
> > inet 144.76.102.204 netmask 0xffe0 broadcast 144.76.102.223
> >
> >
> > tap0: flags=8943 mtu
1500
> > lladdr fe:e1:ba:d0:7e:0a
> > description: vm1-if0-foobar
> > index 5 priority 0 llprio 3
> > groups: tap
> > status: active
> >
> > bridge0: flags=41
> > description: switch1-uplink
> > index 7 llprio 3
> > groups: bridge
> > priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6
proto rstp
> > em0 flags=3
> > port 1 ifpriority 0 ifcost 0
> > tap0 flags=3
> > port 5 ifpriority 0 ifcost 0
> > Addresses (max cache: 100, timeout: 240):
> > 0c:86:10:ed:35:58 em0 1 flags=0<>
>
> My /etc/vm.conf looks like this:
>
> > switch "uplink" {
> > add em0
> > }
> >
> > vm "foobar" {
> > memory 2G
> > disk "/tmp/1.vdi"
> > interface {
> > switch "uplink"
> > }
> > }
>
> When i start the vm with my current /bsd.rd i start the installer and
insert
> the following:
>
> > Available network interfaces are: vio0 vlan0.
> > Which network interface do you wish to configure? (or 'done') [vio0]
> > IPv4 address for vio0? (or 'dhcp' or 'none') [dhcp] 136.243.186.161
> > Netmask for vio0? [255.255.255.248] IPv6 address for vio0? (or
> > 'autoconf' or 'none') [none] Available network interfaces are: vio0
> > vlan0.
> > Which network interface do you wish to configure? (or 'done') [done]
> > Default IPv4 route? (IPv4 address or none) 144.76.102.204
> > add net default: gateway 144.76.102.204: Network is unreachable
>
> Can you people see something that i might missed?
> Big thanks in advance and greetings
> Leo
>
>
sysctl net.inet.ip.forwarding=1 ?
I'm not a networking expert but I think your VM's subnet mask is wrong for
the gateway you are trying to use.
-ml
