Re: smtpd: trailing CR

2020-04-21 Thread gilles
April 21, 2020 4:28 AM, "Todd C. Miller" wrote: > On Mon, 20 Apr 2020 15:01:31 +0200, Eric Faurot wrote: > >> There has been a discussion a while ago about the issue of trailing CR >> in smtp lines (https://marc.info/?l=openbsd-tech&m=156890805128121&w=2). >> >> It is agreed that stripping an o

Re: smtpd: fix smtpctl discover

2020-04-21 Thread gilles
April 20, 2020 9:07 PM, "Eric Faurot" wrote: > Hi again, > > We had a report of a crash when running "smtpctl discover" on an > envelope that has a invalid dispatcher (action name changed in the > config). > > The issue is that the dispatcher is not checked after the envelope is > loaded as a r

OBSD version 6.6: dhclient send DHCP-release to destination address INADDR_ANY

2020-04-21 Thread alexander.mark...@siemens.com
Hi, If the DHCP-server doesn't provide the option DHO_DHCP_SERVER_IDENTIFIER, the broadcast address is used as fallback (see state_bound). However, things are different when sending DHCP-release. If the option DHO_DHCP_SERVER_IDENTIFIER is missing, INADDR_ANY is used resulting in an error ENETU

OBSD version 6.6: dhclient sends DHCP requests infinitely if no ACK is received

2020-04-21 Thread alexander.mark...@siemens.com
Hi, When entering state S_REQUESTING, the dhclient starts sending DHCP requests. If the dhclient doesn't receive an ACK (meaning either NAK or no answer at all), the dhclient keeps sending DHCP requests infinitely. Shouldn't the dhclient switch to state S_INIT after a certain amount of time

clear pf state when reconnecting a udp socket

2020-04-21 Thread Tim Kuijsten
Whenever a connected UDP socket is connected to another peer, any previous state should be cleared in PF so that only datagrams from the newly connected peer are deliverd to the socket. Without this patch the following scenario can occur on machines with PF enabled using keep state on matching rul

Re: unwind(8): recommend supersede in dhclient.conf

2020-04-21 Thread Sebastian Benoit
Florian Obser(flor...@openbsd.org) on 2020.04.21 06:57:49 +0200: > We didn't get around to run unwind per default and integrate it > tighter with dhclient this release cycle. > But there is also no need anymore to recomend prepend in > dhclient.conf, unwind(8) is no longer closing it's service port

Re: acme-client(1) and Buypass Go SSL

2020-04-21 Thread Sebastian Benoit
Bartosz Kuzma(bartosz.ku...@release11.com) on 2020.04.20 18:51:17 +0200: > Hello, > > I've tried to get a certificate from Buypass Go SSL provider using > acme-client(1) but it ends with the following error: > > acme-client: https://api.buypass.com/acme-v02/new-acct: bad HTTP: 400 > acme-client:

diff: em(4) deadlock fix

2020-04-21 Thread Jan Klemkow
Hi, The following diff fixes a deadlock in em(4) when system runs out of mbuf(9)s. Tested with current on amd64 with: em0 at pci0 dev 25 function 0 "Intel I217-LM" rev 0x05: msi, mac 0x1e phy 0xb, address d0:50:99:c1:67:94 When the system runs out of mbufs, the receive ring of the em-NIC also r

Re: acme-client(1) and Buypass Go SSL

2020-04-21 Thread Florian Obser
Hi, thanks for working on this and finding another acme implementor! On Mon, Apr 20, 2020 at 06:51:17PM +0200, Bartosz Kuzma wrote: > Hello, > > I've tried to get a certificate from Buypass Go SSL provider using > acme-client(1) but it ends with the following error: > > acme-client: https://api

Re: acme-client(1) and Buypass Go SSL

2020-04-21 Thread Bartosz Kuzma
Hello, thanks for looking at this! On 21/04/2020 17:43, Florian Obser wrote: Hi, thanks for working on this and finding another acme implementor! On Mon, Apr 20, 2020 at 06:51:17PM +0200, Bartosz Kuzma wrote: Hello, I've tried to get a certificate from Buypass Go SSL provider using acme-cli

Re: acme-client(1) and Buypass Go SSL

2020-04-21 Thread Sebastian Benoit
Bartosz Kuzma(bartosz.ku...@release11.com) on 2020.04.21 20:59:54 +0200: > Hello, > > thanks for looking at this! > > On 21/04/2020 17:43, Florian Obser wrote: > >Hi, > > > >thanks for working on this and finding another acme implementor! > > > >On Mon, Apr 20, 2020 at 06:51:17PM +0200, Bartosz K

Re: acme-client(1) and Buypass Go SSL

2020-04-21 Thread Bartosz Kuzma
On 21/04/2020 21:17, Sebastian Benoit wrote: Bartosz Kuzma(bartosz.ku...@release11.com) on 2020.04.21 20:59:54 +0200: Hello, thanks for looking at this! On 21/04/2020 17:43, Florian Obser wrote: Hi, thanks for working on this and finding another acme implementor! On Mon, Apr 20, 2020 at

Re: ADMtec aue(4) interface supporting VLAN_MTU ?

2020-04-21 Thread Christopher Zimmermann
On Sun, Jul 07, 2019 at 01:26:55PM -0700, Chris Cappuccio wrote: Christopher Zimmermann [chr...@openbsd.org] wrote: This works: doas ifconfig vlan67 mtu 1496 this doesn't: doas ifconfig vlan67 mtu 1497 Should we therefore disable VLAN_MTU on this chipset? - ifp->if_capabilities = IFC

Re: ADMtec aue(4) interface supporting VLAN_MTU ?

2020-04-21 Thread Tom Smyth
Hi Chrisz, 4 bytes for the vlan header .. have you tried increasing the parent intetface mtu by 4bytes So for vlan of 1500 mtu set parent interface mtu to 1504 bytes If you are doing q in q vlan nesting Then the parent interface should be 1500bytes +4× number of levels of nesting eg 1 vlan nes

Re: ADMtec aue(4) interface supporting VLAN_MTU ?

2020-04-21 Thread Chris Cappuccio
Tom Smyth [tom.sm...@wirelessconnect.eu] wrote: > Hi Chrisz, > > 4 bytes for the vlan header .. have you tried increasing the parent > intetface mtu by 4bytes > IFCAP_VLAN_MTU is a direct bypass for this. "hardmtu" on the parent interface is perhaps more interesting as it will limit everything i

Re: ADMtec aue(4) interface supporting VLAN_MTU ?

2020-04-21 Thread Tom Smyth
Ok thanks for the info i always find mtu confusing as i thought generally it was referring to ip mtu. while layer2 headers vlans and layer 2.5 headers such as mpls labels cw etc...would be outside the ip mtu... Thanks again On Wednesday, 22 April 2020, Chris Cappuccio wrote: > Tom Smyth [