Re: OpenBSD stickers

2022-05-15 Thread Amarendra Godbole
On Wed, May 11, 2022 at 8:05 PM Amarendra Godbole wrote: > > Hello Everyone, > > I had an opportunity to print a stack of OpenBSD logo stickers > (approx. 3" x 2"). They are transparent, matt print plastic. After > keeping a few aside, I still have several that remain - and hence this > email. Per

Re: Wireguard IP packets fragmentation issue

2022-05-15 Thread Stuart Henderson
On 2022-05-15, Tom Smyth wrote: > Hi Stuart, > I have huge regard for you and all you contribute to OpenBSD and the community > Im going to clarify what I meant and what my experience with PMTU and > constrained MTUs behind > NAT, > My humble experience is that if we have a constrained MTU behind

Re: Wireguard IP packets fragmentation issue

2022-05-15 Thread Tom Smyth
Hi Stuart, I have huge regard for you and all you contribute to OpenBSD and the community Im going to clarify what I meant and what my experience with PMTU and constrained MTUs behind NAT, My humble experience is that if we have a constrained MTU behind a NAT Path MTU discovery from the server to

Re: Wireguard IP packets fragmentation issue

2022-05-15 Thread Stuart Henderson
On 2022-05-15, Tom Smyth wrote: > IP fragments on internet are avoided generally through PMTU discovery (mtu > path > discovery) but > PMTU does not work beyond a Nat (if a smaller MTU interface exists > behind a NAT then the smaller > MTU will not be discovered. That's not right, NAT doesn't br

Re: Wireguard IP packets fragmentation issue

2022-05-15 Thread Stuart Henderson
On 2022-05-15, Theo de Raadt wrote: > .Bd -literal -offset indent > -inet 0.0.0.0 255.255.255.255 NONE \e > +inet 0.0.0.0 255.255.255.255 0.0.0.1 \e > pppoedev em0 authproto pap \e > authname 'testcaller' authkey 'donttell' up > -dest 0.0.0.1 > inet6 eui64 > > I don't think this

Re: Wireguard IP packets fragmentation issue

2022-05-15 Thread Jason McIntyre
On Sun, May 15, 2022 at 10:40:59AM -0600, Theo de Raadt wrote: > .Bd -literal -offset indent > -inet 0.0.0.0 255.255.255.255 NONE \e > +inet 0.0.0.0 255.255.255.255 0.0.0.1 \e > pppoedev em0 authproto pap \e > authname 'testcaller' authkey 'donttell' up > -dest 0.0.0.1 > inet6 eui

Re: Wireguard IP packets fragmentation issue

2022-05-15 Thread Theo de Raadt
.Bd -literal -offset indent -inet 0.0.0.0 255.255.255.255 NONE \e +inet 0.0.0.0 255.255.255.255 0.0.0.1 \e pppoedev em0 authproto pap \e authname 'testcaller' authkey 'donttell' up -dest 0.0.0.1 inet6 eui64 I don't think this is the right way to go. Yes, on p2p links the broadca

Re: Wireguard IP packets fragmentation issue

2022-05-15 Thread Jason McIntyre
On Sun, May 15, 2022 at 01:44:39PM -, Stuart Henderson wrote: > > > > - mixing mtu to 1500 and scrub: well, both concern issues with mtu. why > > wouldn;t they be together in there? > > They're related but one is for avoiding the problem in the first place > (which may or may not work, depen

Re: Cron running at 99% CPU for seemingly no reason

2022-05-15 Thread Theo de Raadt
This is a bug in a diff I put into snapshots.

Re: Cron running at 99% CPU for seemingly no reason

2022-05-15 Thread Hrvoje Popovski
On 15.5.2022. 16:56, Todd C. Miller wrote: > On Sun, 15 May 2022 16:02:03 +0200, Hrvoje Popovski wrote: > >> I know how to rebuild cron >> >> cd /usr/src/usr.sbin/cron/ >> make obj && make depend && make && make install >> >> but i don't know how to enabled debug symbols .. > > Easiest would be t

Re: Wireguard IP packets fragmentation issue

2022-05-15 Thread Tom Smyth
Hello all, one issue we have encountered with encapsulated packets is the IP fragment packets that are created when the would be encapsulated packet would exceed the MTU of an underlay interface. on non natted networks with firewalls that behave them selves the tunnels may work. however across t

Re: Cron running at 99% CPU for seemingly no reason

2022-05-15 Thread Todd C . Miller
On Sun, 15 May 2022 16:02:03 +0200, Hrvoje Popovski wrote: > I know how to rebuild cron > > cd /usr/src/usr.sbin/cron/ > make obj && make depend && make && make install > > but i don't know how to enabled debug symbols .. Easiest would be to do: cd /usr/src/usr.sbin/cron/ make obj && make depend

Re: Cron running at 99% CPU for seemingly no reason

2022-05-15 Thread Hrvoje Popovski
On 15.5.2022. 15:38, Todd C. Miller wrote: > On Sun, 15 May 2022 14:29:28 +0200, Hrvoje Popovski wrote: > >> I'm seeing same as Stephan on few servers in lab. >> I've killed cron and did ktrace -i cron. Is this ok? >> In attachment you can find kdump -f ktrace.out output. > > That's very odd. It

Re: Wireguard IP packets fragmentation issue

2022-05-15 Thread Stuart Henderson
On 2022-05-15, Jason McIntyre wrote: > On Sat, May 14, 2022 at 09:14:36PM -, Stuart Henderson wrote: >> On 2022-05-14, Georg Pfuetzenreuter wrote: >> > pppoe(4) already has a section on this, possibly this could be used as a >> > start. >> >> It's not a great start really. Mixes up informat

Re: Cron running at 99% CPU for seemingly no reason

2022-05-15 Thread Todd C . Miller
On Sun, 15 May 2022 14:29:28 +0200, Hrvoje Popovski wrote: > I'm seeing same as Stephan on few servers in lab. > I've killed cron and did ktrace -i cron. Is this ok? > In attachment you can find kdump -f ktrace.out output. That's very odd. It looks like cron parses root's crontab and then someho

Re: Cron running at 99% CPU for seemingly no reason

2022-05-15 Thread Hrvoje Popovski
On 15.5.2022. 14:39, Hrvoje Popovski wrote: > On 15.5.2022. 14:29, Hrvoje Popovski wrote: >> On 15.5.2022. 12:32, Claudio Jeker wrote: >>> Also for cron, please attach ktrace to the cron process for a few seconds >>> and look at the kdump of that. Most probably it is constantly woken up for >>> som

Re: Cron running at 99% CPU for seemingly no reason

2022-05-15 Thread Hrvoje Popovski
On 15.5.2022. 12:32, Claudio Jeker wrote: > Also for cron, please attach ktrace to the cron process for a few seconds > and look at the kdump of that. Most probably it is constantly woken up for > some reasons. Hi, I'm seeing same as Stephan on few servers in lab. I've killed cron and did ktrace

Re: Cron running at 99% CPU for seemingly no reason

2022-05-15 Thread Stuart Henderson
On 2022-05-15, Stephan Mending wrote: > Especially the line stating "the kernel did not panic" surprises me, as I am > greeted by the kernel debugger. Not sure how to interpret that. ddb is entered for panics (which are explicit calls from kernel code) and for other exceptions (which are not) -

Re: Cron running at 99% CPU for seemingly no reason

2022-05-15 Thread Claudio Jeker
On Sun, May 15, 2022 at 12:06:33PM +0200, Stephan Mending wrote: > Hi *, > I've got a system running -current that keeps crashing on me every couple of > days. > Output of ddb: > > Connected to /dev/cuaU0 (speed 115200) > > ddb{0}> show panic > the kernel did not panic > ddb{0}> show uvm > Cu

Re: Cron running at 99% CPU for seemingly no reason

2022-05-15 Thread Claudio Jeker
On Sun, May 15, 2022 at 12:06:33PM +0200, Stephan Mending wrote: > Hi *, > I've got a system running -current that keeps crashing on me every couple of > days. > Output of ddb: > > Connected to /dev/cuaU0 (speed 115200) > > ddb{0}> show panic > the kernel did not panic > ddb{0}> show uvm > Cu

Cron running at 99% CPU for seemingly no reason

2022-05-15 Thread Stephan Mending
Hi *, I've got a system running -current that keeps crashing on me every couple of days. Output of ddb: Connected to /dev/cuaU0 (speed 115200) ddb{0}> show panic the kernel did not panic ddb{0}> show uvm Current UVM status: pagesize=4096 (0x1000), pagemask=0xfff, pageshift=12 482451 VM pa

trunk failover with detachable device (ure)

2022-05-15 Thread Matthias Schmidt
Hi everyone, I have a Laptop with iwx(4) only and using an ure(4) device in case I need wired Ethernet. I failed to create a trunk(4) port with iwx as master and ure as failover since the latter is usually not connected and only gets connected on demand. Is it possible at all to have a failover/