Re: Intel Ethernet (?Synopsys based) on Filet3 Elkhart Lake unconfigured on recent snapshot

2023-11-15 Thread Ted Ri
Onboard ethernet is now recognized and displays nonblinking orange status LED. No address is acquired. Nothing shows on tcpdump -i dwqe0 when /bin/sh -x /etc/netstart dwqe0 is executed. However tcpdump -i dwqe1 yields multiple bootp messages with netstart also failing to lead to acquisition of

Re: wcsftime() outputs in wrong language

2023-11-15 Thread Ingo Schwarze
Hi Sean, Sean McBride wrote on Wed, Nov 15, 2023 at 08:36:25PM -0500: > I tried building the fmt library on OpenBSD 7.4 on x86_64 and a few of > its unit tests fail. First we thought it was maybe a libc++ bug, but in > fact it seems to be an OpenBSD bug: > > Reduced case: > > ```c >

Re: pflogd spamming syslog

2023-11-15 Thread Dave Voutila
Alexandr Nedvedicky writes: > Hello, > > diff below seems to make empty log message go way. I can't speak for correctness, but I can confirm pflogd stops writing empty messages on my machine with the diff. -dv > we have to check if sig_alrm fired here in pflogd: > > > 725 while (1)

wcsftime() outputs in wrong language

2023-11-15 Thread Sean McBride
Hi OpenBSD folks, I tried building the fmt library on OpenBSD 7.4 on x86_64 and a few of its unit tests fail. First we thought it was maybe a libc++ bug, but in fact it seems to be an OpenBSD bug: Reduced case: ```c #include #include #include #include int main() { setlocale(LC_TIME,

Re: pflogd spamming syslog

2023-11-15 Thread Alexandr Nedvedicky
Hello, diff below seems to make empty log message go way. we have to check if sig_alrm fired here in pflogd: 725 while (1) { 726 np = pcap_dispatch(hpcap, PCAP_NUM_PKTS, 727 phandler, (u_char *)dpcap); 728 if (np < 0) { 729

Re: vxlan(4) custom destination UDP port seems not working

2023-11-15 Thread Luca Di Gregorio
Fair enough. So, I think that man page(s), and maybe code, should be corrected. Thanks Il giorno mer 15 nov 2023 alle ore 14:13 Theo de Raadt ha scritto: > Luca Di Gregorio wrote: > > > I'm not sure about this, but I think that public cloud datacenters > filter out > > (or do something with)

Re: vxlan(4) custom destination UDP port seems not working

2023-11-15 Thread Theo de Raadt
Luca Di Gregorio wrote: > I'm not sure about this, but I think that public cloud datacenters filter out > (or do something with) udp traffic to standard udp vxlan port. But that would not be a reason for allowing selection of the pre-standard port number. Rather, it would be a reason for

Re: vxlan(4) custom destination UDP port seems not working

2023-11-15 Thread Luca Di Gregorio
I'm not sure about this, but I think that public cloud datacenters filter out (or do something with) udp traffic to standard udp vxlan port. Maybe it's because they have their vlanx infrastructure running on the standard port, don't know. I see no traffic coming from a VPS that tries to send to

Re: vxlan(4) custom destination UDP port seems not working

2023-11-15 Thread Theo de Raadt
Stuart Henderson wrote: > On 2023/11/15 05:59, Theo de Raadt wrote: > > Otto Moerbeek wrote: > > > > > On Wed, Nov 15, 2023 at 12:42:46PM +0100, Luca Di Gregorio wrote: > > > > > > > # uname -a > > > > OpenBSD X.my.domain 7.4 GENERIC#0 amd64 > > > > > > > > # ifconfig vxlan0 tunnel

Re: vxlan(4) custom destination UDP port seems not working

2023-11-15 Thread Stuart Henderson
On 2023/11/15 05:59, Theo de Raadt wrote: > Otto Moerbeek wrote: > > > On Wed, Nov 15, 2023 at 12:42:46PM +0100, Luca Di Gregorio wrote: > > > > > # uname -a > > > OpenBSD X.my.domain 7.4 GENERIC#0 amd64 > > > > > > # ifconfig vxlan0 tunnel SOURCE_IP DEST_IP:8472 vnetid 5 > > > # ifconfig

Re: vxlan(4) custom destination UDP port seems not working

2023-11-15 Thread Theo de Raadt
Otto Moerbeek wrote: > On Wed, Nov 15, 2023 at 12:42:46PM +0100, Luca Di Gregorio wrote: > > > # uname -a > > OpenBSD X.my.domain 7.4 GENERIC#0 amd64 > > > > # ifconfig vxlan0 tunnel SOURCE_IP DEST_IP:8472 vnetid 5 > > # ifconfig vxlan0 inet 192.168.5.1/30 > > # ifconfig vxlan0 up > > > >

Re: vxlan(4) custom destination UDP port seems not working

2023-11-15 Thread Luca Di Gregorio
In the EXAMPLES section of vxlan(4) manpage, I see a multicast dest address 239.1.1.100 with the non standard dest port 8472. Does it mean that for point-to-point tunnels the destination port is static to 4789? If this is the case, I think that the ifconfig command should at least raise an alert,

Re: vxlan(4) custom destination UDP port seems not working

2023-11-15 Thread Stuart Henderson
On 2023/11/15 13:03, Otto Moerbeek wrote: > On Wed, Nov 15, 2023 at 12:42:46PM +0100, Luca Di Gregorio wrote: > > > # uname -a > > OpenBSD X.my.domain 7.4 GENERIC#0 amd64 ... > > # ifconfig vxlan0 tunnel SOURCE_IP DEST_IP:8472 vnetid 5 ... > It helps to read the vxlan(4) manpage, specifcially

Re: vxlan(4) custom destination UDP port seems not working

2023-11-15 Thread Otto Moerbeek
On Wed, Nov 15, 2023 at 12:42:46PM +0100, Luca Di Gregorio wrote: > # uname -a > OpenBSD X.my.domain 7.4 GENERIC#0 amd64 > > # ifconfig vxlan0 tunnel SOURCE_IP DEST_IP:8472 vnetid 5 > # ifconfig vxlan0 inet 192.168.5.1/30 > # ifconfig vxlan0 up > > # ifconfig vxlan0: I can't see the dest

vxlan(4) custom destination UDP port seems not working

2023-11-15 Thread Luca Di Gregorio
# uname -a OpenBSD X.my.domain 7.4 GENERIC#0 amd64 # ifconfig vxlan0 tunnel SOURCE_IP DEST_IP:8472 vnetid 5 # ifconfig vxlan0 inet 192.168.5.1/30 # ifconfig vxlan0 up # ifconfig vxlan0: I can't see the dest UDP port 8472 anywhere vxlan0: flags=8843 mtu 1500 lladdr fe:e1:ba:d9:e4:0b

Re: arm64 panic: malloc: out of space in kmem_map

2023-11-15 Thread Mark Kettenis
> Date: Thu, 9 Nov 2023 13:21:09 +0100 > From: Alexander Bluhm > > Hi, > > During make build my arm64 machine with 32 CPUs crashed. Next time this happens, please include "show malloc" output. > ddb{24}> x/s version > version:OpenBSD 7.4-current (GENERIC.MP) #16: Fri Nov 3 21:38:55