Aries Technology Inc. Social Media Release

2011-08-17 Thread aries . technology
aries.technol...@gmx.co.uk has sent you a Aries Technology Inc. Social Media Press Release. We're Giving Away 90 days FREE on Courses! Increase Enrollment By Offering Certification Programs Need the IC3, Living online and Key apps GET A a 90 day trial!! Request a Free Demo call Click here

LAC LNS server with OpenBSD

2011-08-17 Thread Gruel Bruno
Hello, I just want to know if it plan to have a real implitation of L2TP on OpenBSD. Is there a work in progress ? or never ? Thank's Bruno Gruel This message has been scanned for viruses and dangerous content by Amavisd-new, and is believed to be clean.

Re: LAC LNS server with OpenBSD

2011-08-17 Thread Jeremie Courreges-Anglas
Gruel Bruno b.gr...@woody.hopto.org writes: Hello, Hi. I just want to know if it plan to have a real implitation of L2TP on OpenBSD. Is there a work in progress ? or never ? Without knowing what you already know about OpenBSD and L2TP, it's a bit difficult to answer. Consider taking a look

Re: LAC LNS server with OpenBSD

2011-08-17 Thread Stuart Henderson
On 2011/08/17 12:18, Gruel Bruno wrote: Hello, I just want to know if it plan to have a real implitation of L2TP on OpenBSD. Is there a work in progress ? or never ? See /usr/src/usr.sbin/npppd; it is not built/distributed by default yet, but the code is there.

sysctl__string fails to return old length

2011-08-17 Thread Joel Sing
According to the sysctl(3) man page, calling sysctl with a NULL value for oldp should result in the current size being returned. This works correctly for sysctl_rdstring(), but not for sysctl__string(). ok? Index: kern_sysctl.c ===

Re: sysctl__string fails to return old length

2011-08-17 Thread Matthew Dempsky
On Wed, Aug 17, 2011 at 11:43:54PM +1000, Joel Sing wrote: According to the sysctl(3) man page, calling sysctl with a NULL value for oldp should result in the current size being returned. Hm, it also says when ENOMEM is returned, that we'll fill in as much data as possible, which doesn't seem

allow ospfd -v to set verbose logging in ospfe/rde

2011-08-17 Thread Stuart Henderson
Currently when ospfd is started with ospfd -v, the verbose logging flag is only set for the parent process, so the detailed messages from rde/ospfe are not logged. The diff below passes it to the other processes so that if you store all ospfd logs you'll get the same information logged with -v as

Re: allow ospfd -v to set verbose logging in ospfe/rde

2011-08-17 Thread Stuart Henderson
On 2011/08/17 17:28, Stuart Henderson wrote: I guess ripd, ldpd, ospf6d, bgpd, ldapd and dvmrpd will have a similar problem, oh, and a few others, I was just looking for IMSG_CTL_LOG_VERBOSE...

Re: allow ospfd -v to set verbose logging in ospfe/rde

2011-08-17 Thread Stuart Henderson
On 2011/08/17 17:28, Stuart Henderson wrote: Currently when ospfd is started with ospfd -v, the verbose logging flag is only set for the parent process, so the detailed messages from rde/ospfe are not logged. The diff below passes it to the other processes so that if you store all ospfd

Re: allow ospfd -v to set verbose logging in ospfe/rde

2011-08-17 Thread Claudio Jeker
On Wed, Aug 17, 2011 at 06:07:21PM +0100, Stuart Henderson wrote: On 2011/08/17 17:28, Stuart Henderson wrote: Currently when ospfd is started with ospfd -v, the verbose logging flag is only set for the parent process, so the detailed messages from rde/ospfe are not logged. The diff

Re: LAC LNS server with OpenBSD

2011-08-17 Thread Gruel Bruno
Hello, First thank's for your help et very good jobs for npppd, it's realy a good tool. But it seem not to do what i want. (http://fai.woody.hopto.org/Docs/bsdrp-example-pppoe-l2tp.png). I will try rp-l2tp How can i have a full doc off npppd ?? But i confirm that npppd work fine on my lab.

vmware is stupid wrt to the giaddrs in dhcp packets when pxe booting

2011-08-17 Thread David Gwynne
vmwares pxe rom in guests uses the giaddr (the address of the dhcp relay) as the default ip gateway. this is a problem if you're running carped firewalls, because you'll be running a dhcrelay on each of them attached to the hardware interface, not the carped interface. if the vmware client

touch(1): subsecond and POSIX 2008 support

2011-08-17 Thread Philip Guenther
This diff adds to touch(1) support for the -d option specified by POSIX 2008 that permits specifying subsecond timestamps, as well as nanosecond support in the -r option, and a general simplification over the main loop. oks? Philip Index: usr.bin/touch/touch.1