rtsock: Why shouldn't rt flags be changeable in RTM_CHANGE messages?

2012-11-28 Thread Florian Riehm
Hi, because of a bug in ospf6d I tried to allow ospf6d to change cloning routes to gateway routes and the other way around. I've noticed there is a check which tries to forbid this, but the check is broken. It allows to toggle ALL rt flags, if ONE common bit in RTF_FMASK and rtm_fmask is set. Beca

Re: cloneable tun

2012-11-28 Thread Reyk Floeter
On Wed, Nov 28, 2012 at 10:42 PM, Mark Kettenis wrote: > But currently /dev/tunN is usable from any programming language that > that can do reads and writes. With Reyk's changes you need to do an > ioctl even for basic usage, which is at best quirky in languages other > than C/C++. That feels li

Re: clonable bpf

2012-11-28 Thread Mike Belopuhov
On Wed, Nov 28, 2012 at 11:38 PM, Theo de Raadt wrote: >> there's not supposed to be bpf0,1,2,3... > > Unfortunately history argues otherwise. no, i meant if we move to the clonable bpf, we will need only one node. sorry for not making it clear.

Re: clonable bpf

2012-11-28 Thread Theo de Raadt
> there's not supposed to be bpf0,1,2,3... Unfortunately history argues otherwise.

Re: cloneable tun

2012-11-28 Thread Philip Guenther
On Wed, Nov 28, 2012 at 1:42 PM, Mark Kettenis wrote: > But currently /dev/tunN is usable from any programming language that > that can do reads and writes. With Reyk's changes you need to do an > ioctl even for basic usage, which is at best quirky in languages other > than C/C++. That feels lik

Re: cloneable tun

2012-11-28 Thread Mark Kettenis
> From: Mike Belopuhov > Date: Wed, 28 Nov 2012 22:21:07 +0100 > > On Wed, Nov 28, 2012 at 8:21 PM, Mark Kettenis > wrote: > >> Date: Wed, 28 Nov 2012 17:39:24 +0100 > >> From: Reyk Floeter > >> > >> Hi, > >> > >> inspired by mikeb@'s clonable bpf patch, this slightly more complex > >> diff im

Re: cloneable tun

2012-11-28 Thread Mike Belopuhov
On Wed, Nov 28, 2012 at 8:21 PM, Mark Kettenis wrote: >> Date: Wed, 28 Nov 2012 17:39:24 +0100 >> From: Reyk Floeter >> >> Hi, >> >> inspired by mikeb@'s clonable bpf patch, this slightly more complex >> diff implements clonable interface support to tun(4). >> >> The idea is to split the fixed re

Re: cloneable tun

2012-11-28 Thread Mark Kettenis
> Date: Wed, 28 Nov 2012 17:39:24 +0100 > From: Reyk Floeter > > Hi, > > inspired by mikeb@'s clonable bpf patch, this slightly more complex > diff implements clonable interface support to tun(4). > > The idea is to split the fixed relation between device minor number > (/dev/tunX) and interfac

cloneable tun

2012-11-28 Thread Reyk Floeter
Hi, inspired by mikeb@'s clonable bpf patch, this slightly more complex diff implements clonable interface support to tun(4). The idea is to split the fixed relation between device minor number (/dev/tunX) and interface unit (ifconfig tunY). In difference to the current tun(4) implementation, op

Re: PMAP_NOCACHE -> PMAP_NC

2012-11-28 Thread Mark Kettenis
> Date: Tue, 27 Nov 2012 15:02:31 +0100 > From: Martin Pieuchot > > While working on drm support for macppc that makes use of non-cached > memory I found that some platforms (amd64, i386, powerpc) use the MD > PMAP_NOCACHE flag where others (sparc, sparc64, solbourne) use PMAP_NC > for the same p

Re: hostname.if(5) clarification

2012-11-28 Thread Christian Weisgerber
Alexander Hall wrote: > IIRC, isn't there a few distinct (non-ifconfig-compatible) cases we > handle specially, and the rest is passed as-is to ifconfig? Is it? Okay, I've looked at the netstart code again. It messes with any lines where * the first word is "dhcp", "rtsol", "inet", or "inet6"

Re: clonable bpf

2012-11-28 Thread Mike Belopuhov
On Wed, Nov 28, 2012 at 12:43 PM, Reyk Floeter wrote: > On Tue, Nov 27, 2012 at 10:17 PM, Mike Belopuhov wrote: >> apparently it works just fine. the number of clones is limited >> by the v_specbitmap which currently allows for 64 clones total >> (per system, not per process). >> > > Please clar

Re: clonable bpf

2012-11-28 Thread Reyk Floeter
On Tue, Nov 27, 2012 at 10:17 PM, Mike Belopuhov wrote: > apparently it works just fine. the number of clones is limited > by the v_specbitmap which currently allows for 64 clones total > (per system, not per process). > Please clarify: Does it mean 64 cloned bpf devices per system or 64 cloned

Re: X540T: link is not detected

2012-11-28 Thread mxb
Compiling if_ix.c with IX_DEBUG yields ../../../../dev/pci/if_ix.c: In function 'ixgbe_print_hw_stats': ../../../../dev/pci/if_ix.c:3525: error: 'struct ix_softc' has no member named 'mbuf_alloc_failed' ../../../../dev/pci/if_ix.c:3526: error: 'struct ix_softc' has no member named 'mbuf_cluster_fa

Re: rc.d/dhcpd

2012-11-28 Thread Stuart Henderson
On 2012/11/28 10:24, mxb wrote: > Then running dhcpd with pf-support (-A -C ). > dhcpd spawns child process which is not handled by rc-script then > stop/restart. This is a bug in dhcpd, not the rc script.

Re: rc.d/dhcpd

2012-11-28 Thread Alexander Hall
mxb wrote: >Then running dhcpd with pf-support (-A -C ). >dhcpd spawns child process which is not handled by rc-script then >stop/restart. > >Here is a diff to fix it. > >Yes, I know, normally one might want to flush PF-tables as well and >this is not handled by the diff. >But at least I don't h

Re: clonable bpf

2012-11-28 Thread Janne Johansson
2012/11/27 Mike Belopuhov : > > apply the diff and see how all your apps are happily using single > device node: /dev/bpf0. > i'm not 100% sure we want this but why wouldn't we? > generally speaking we also need to move to a single /dev/bpf > node, but that can be done, once this diff is tested and

Re: Apple AGP support

2012-11-28 Thread Martin Pieuchot
On 23/11/12(Fri) 11:40, Martin Pieuchot wrote: > Diff below adds support for Uninorth AGP bridges found in most if not > all the macppc machines with a G3 or G4 microprocessor. > > These chips do not translate individual pages using the GART like it > is the case for most of the AGP chips on i386/

Re: rc.d/sshd reload test

2012-11-28 Thread Paul Irofti
On Wed, Nov 28, 2012 at 08:28:10AM +0100, Alexander Hall wrote: > Make sure new config is valid before SIGHUP'ing sshd, which would > otherwise just kill it. Invalid configuration now gives: > > # pgrep sshd > 18998 > # /etc/rc.d/sshd reload > sshd(failed) > # pgrep sshd > 18998 > > Pros: Less

rc.d/dhcpd

2012-11-28 Thread mxb
Then running dhcpd with pf-support (-A -C ). dhcpd spawns child process which is not handled by rc-script then stop/restart. Here is a diff to fix it. Yes, I know, normally one might want to flush PF-tables as well and this is not handled by the diff. But at least I don't have to kill child pro

Re: rc.d/sshd reload test

2012-11-28 Thread Damien Miller
I like this - it's what -t is intended for. On Wed, 28 Nov 2012, Alexander Hall wrote: > Make sure new config is valid before SIGHUP'ing sshd, which would > otherwise just kill it. Invalid configuration now gives: > > # pgrep sshd > 18998 > # /etc/rc.d/sshd reload > sshd(failed) > # pgrep sshd

Re: rc.d/sshd reload test

2012-11-28 Thread Alexander Hall
On 11/28/12 08:34, Antoine Jacoutot wrote: > On Wed, Nov 28, 2012 at 08:28:10AM +0100, Alexander Hall wrote: >> Make sure new config is valid before SIGHUP'ing sshd, which would >> otherwise just kill it. Invalid configuration now gives: >> >> # pgrep sshd >> 18998 >> # /etc/rc.d/sshd reload >> ssh