Re: nc in inetd - under which account?

2017-06-08 Thread Stuart Henderson
On 2017-06-07, Marko Cupać wrote: > Now as for relayd, I never used it. If someone gave me working example > and an explanation why it is better than my current solution, I'd be > glad to switch, and pass the word around :) When your proxy is nc run from inetd, you have to fork when answering eac

Re: Unable to establish ikev2 vpn with ios using current - OpenBSD 6.1 GENERIC.MP#106 amd64 - can anyone help?

2017-06-08 Thread Stuart Henderson
On 2017-06-07, Theodore Wynnychenko wrote: > I have updated to the last several snapshots as they have come out, but > continue > to be unable to establish a VPN between iOS and OpenBSD. As the iOS device > has > not been updated recently, the "problem" appears to relate to something that > cha

Re: re0 and re1 watchdog timeouts, and system freeze

2017-06-08 Thread Martin Pieuchot
On 07/06/17(Wed) 09:43, Björn Ketelaars wrote: > On Sat 03/06/2017 08:44, Björn Ketelaars wrote: > > > > Reverting back to the previous kernel fixed the issue above. Question: can > > someone give a hint on how to track this issue? > > After a bit of experimenting I'm able to reproduce the proble

SCSI Enclosure Service

2017-06-08 Thread Jens A. Griepentrog
Dear Listeners, Let me know, please, if enclosure monitoring is supported for disks attached to Supermicro M28SAB drive cages (with two AMI MG9071 chips) or similar backplanes. Drives work fine when attached to some LSI 2008 controller but there appear no "ses* at scsibus?" boot messages (see bel

booting 6.1

2017-06-08 Thread Friedrich Locke
Hi folks, i burnt and install61.iso cd and tried to boot uefi, but could not. Does anybody know this amd64 6.1 install image support booting UEFI ? Thanks in advance

Re: re0 and re1 watchdog timeouts, and system freeze

2017-06-08 Thread Björn Ketelaars
On Thu 08/06/2017 16:55, Martin Pieuchot wrote: > On 07/06/17(Wed) 09:43, Björn Ketelaars wrote: > > On Sat 03/06/2017 08:44, Björn Ketelaars wrote: > > > > > > Reverting back to the previous kernel fixed the issue above. Question: can > > > someone give a hint on how to track this issue? > > > >

oss-sec use-after-free after mysql_stmt_close()

2017-06-08 Thread Alceu R. de Freitas Jr.
Hello folks, I thought that you might be interested about that, and be glad to know that what helped discovering this bug was just setting up and running a CPAN Smoker on OpenBSD: this bug wasn't detected before in any other OS that supports Perl and DBD::Mysql. http://seclists.org/oss-sec/2017/

Help setting up an IKEv2 IPSec Road Warrior VPN on OpenBSD

2017-06-08 Thread thebloggu
Hello! I’m trying to build a road warrior style ikev2 ipsec vpn for my home network on openbsd. The idea is to learn a bit of openbsd since its something I've been meaning to do for some time now and to setup a vpn for me to reach my home network as securely as possible (even if I need to compromi

Re: SCSI Enclosure Service

2017-06-08 Thread David Gwynne
hey jens, from what i can tell, you talk to the ami mg9071 chips on that enclosure using sgpio, not in band using smp (sas mgmt protocol) or ses as a scsi device. i get the impression that mpii hardware does have some understanding of enclosures connected via sgpio, but i'm not sure what benefi

Re: booting 6.1

2017-06-08 Thread Jonathan Gray
On Thu, Jun 08, 2017 at 03:10:33PM -0300, Friedrich Locke wrote: > Hi folks, > > i burnt and install61.iso cd and tried to boot uefi, but could not. > Does anybody know this amd64 6.1 install image support booting UEFI ? > > Thanks in advance The iso does not handle uefi at the moment. Write in

LACP problem

2017-06-08 Thread Charles Lecklider
I'm trying to get LACP working over 2 ports (em0, em1). I've done this successfully with FreeBSD and 4 ports on the same switch so I know it can be done, I just can't get it working with OpenBSD. I'm hoping I've just botched the config somewhere. The switch is a TP-LINK TL-SG3424, latest firmware

Re: LACP problem

2017-06-08 Thread Lyndon Nerenberg
> On Jun 8, 2017, at 7:47 PM, Charles Lecklider wrote: > > em0: flags=8b43 > mtu 9000 >lladdr 0c:c4:7a:d9:ea:d0 >index 5 priority 0 llprio 3 >trunk: trunkdev trunk0 >media: Ethernet autoselect (1000baseT full-duplex,rxpause,txpause) >status: active > em1:

Re: LACP problem

2017-06-08 Thread Lyndon Nerenberg
> On Jun 8, 2017, at 7:54 PM, Lyndon Nerenberg wrote: > > Why do em0 and em1 have the same MAC address? Oh shit, never mind - it's the trunk interface :-P Sorry ...

Re: LACP problem

2017-06-08 Thread Lyndon Nerenberg
> On Jun 8, 2017, at 7:47 PM, Charles Lecklider wrote: > > The trunk is there, seems to be configured the right way, but the second > port doesn't come up. If I pull the cable on em0, em1 comes up, put the > cable back, em0 doesn't join the trunk. What you're showing looks fine. We run this al