Re: ixl(4) troubles

flags=8843 mtu 1500 > >>> lladdr 40:a6:b7:b3:4b:28 > >>> index 1 priority 0 llprio 3 > >>> media: Ethernet autoselect > >>> status: no carrier > >> > >>> transceiver: SFP LC, 850 nm, 300m OM1, 300m OM2, 600m OM3 > >>> model: Ubiquiti Inc. OM-MM-10G-D rev A1 > >> > >> This kind of transceiver may incompatible with Intel NICs. > >> Do you have Intel-Transceivers to verify that? > > > > or Finisar usually work in ixl, or something intel-coded (fs.com, > > flexoptix, etc). > > > > -- > > Please keep replies on the mailing list. > > -- Wouter Prins w...@null0.nl

Re: VLAN-tagging - follow-up

Was the bridge part missed in the previous emails about how to use > VLAN-tagging or am I missing something? > > -- Wouter Prins w...@null0.nl

Re: OpenBSD SMP - BGPd - send_rtmsg: action 1, prefix A.B.C.D/24: No buffer space available - panic: malloc: out of space in kmem_map

the > > current branch ? > > A better calculation logic for nkmempages was added to -current. > On most 64bit archs nkmempages now scales to much larger values. > > See https://marc.info/?l=openbsd-cvs&m=170255507530513&w=2 for more > details. > > -- > :wq Claudio > > -- Wouter Prins w...@null0.nl

Re: l2vpn pseudowire and bridge type interface

Switching from tech@ to misc@ > > > On Sat, Oct 14, 2023 at 11:07:11AM +0200, Wouter Prins wrote: > > >> hello list, > > >> > > >> Was wondering if the veb interface is supported as a bridge for > > >> pseudowires? > > >>

Re: OpenBSD and l3VPN

L3VPN using a eBGP session, the best way to do this is to run a second instance of OpenBGPD. (imho) > > > cheers, > Juan > -- Wouter Prins w...@null0.nl

Re: bgpd crashes when fed by rpki-client (aspa_add_set: bad order of adds)

I posted this to tech@ last week. As a workaround use -A in the rpki-client root crontab entry Sent from my mobile > On May 11, 2023, at 16:42, Bastien Durel wrote: > > Hello, > > I have an openbgpd running with only iBGP, and I run rpki-client on > this machine (the bgpd runs for LG, rpki-cl

Re: Intel nic on Dell R710: failed to allocate interrupt slot for PIC msix

gt; > "Intel Xeon Scalable DECS" rev 0x04 at pci7 dev 13 function 0 not > > configured > > "Intel Xeon Scalable LM" rev 0x04 at pci7 dev 13 function 1 not > configured > > "Intel Xeon Scalable LMS" rev 0x04 at pci7 dev 13 function 2 not > configured > > "Intel Xeon Scalable LMDP" rev 0x04 at pci7 dev 13 function 3 not > > configured > > pci10 at mainbus0 bus 178 > > ppb7 at pci10 dev 0 function 0 "Intel Xeon Scalable PCIE" rev 0x04: msi > > pci11 at ppb7 bus 179 > > 179:0:0: rom address conflict 0xfff8/0x8 > > 179:0:1: rom address conflict 0xfff8/0x8 > > 179:0:2: rom address conflict 0xfff8/0x8 > > 179:0:3: rom address conflict 0xfff8/0x8 > > ixl6 at pci11 dev 0 function 0 "Intel X710 SFP+" rev 0x02: port 3, FW > > 7.83.59945 API 1.9, msi0 > > ixl7 at pci11 dev 0 function 1 "Intel X710 SFP+" rev 0x02: port 2, FW > > 7.83.59945 API 1.9, msi1 > > ixl8 at pci11 dev 0 function 2 "Intel X710 SFP+" rev 0x02: port 0, FW > > 7.83.59945 API 1.9, msi2 > > ixl9 at pci11 dev 0 function 3 "Intel X710 SFP+" rev 0x02: port 1, FW > > 7.83.59945 API 1.9, msi3 > > ppb8 at pci10 dev 2 function 0 "Intel Xeon Scalable PCIE" rev 0x04: msi > > pci12 at ppb8 bus 180 > > 180:0:0: rom address conflict 0xfff8/0x8 > > 180:0:1: rom address conflict 0xfff8/0x8 > > 180:0:2: rom address conflict 0xfff8/0x8 > > 180:0:3: rom address conflict 0xfff8/0x8 > > ixl10 at pci12 dev 0 function 0 "Intel X710 SFP+" rev 0x02: port 3, FW > > 7.83.59945 API 1.9, ms0 > > ixl11 at pci12 dev 0 function 1 "Intel X710 SFP+" rev 0x02: port 2, FW > > 7.83.59945 API 1.9, ms1 > > failed to allocate interrupt slot for PIC msix pin -2135686911 > > ixl11: unable to establish interrupt 1 > > ixl12 at pci12 dev 0 function 2 "Intel X710 SFP+" rev 0x02: port 0, FW > > 7.83.59945 API 1.9, ms2 > > failed to allocate interrupt slot for PIC msix pin -2135686655 > > ixl12: unable to establish interrupt 1 > > ixl13 at pci12 dev 0 function 3 "Intel X710 SFP+" rev 0x02: port 1, FW > > 7.83.59945 API 1.9, ms3 > > failed to allocate interrupt slot for PIC msix pin -2135686399 > > ixl13: unable to establish interrupt 1 > > "Intel Xeon Scalable VT-d" rev 0x04 at pci10 dev 5 function 0 not > > configured > > "Intel Xeon Scalable RAS" rev 0x04 at pci10 dev 5 function 2 not > configured > > "Intel Xeon Scalable IOxAPIC" rev 0x04 at pci10 dev 5 function 4 not > > configured > > "Intel Xeon Scalable KTI" rev 0x04 at pci10 dev 14 function 0 not > > configured > > "Intel Xeon Scalable UPI" rev 0x04 at pci10 dev 14 function 1 not > > configured > > "Intel Xeon Scalable KTI" rev 0x04 at pci10 dev 15 function 0 not > > configured > > "Intel Xeon Scalable UPI" rev 0x04 at pci10 dev 15 function 1 not > > configured > > "Intel Xeon Scalable KTI" rev 0x04 at pci10 dev 16 function 0 not > > configured > > "Intel Xeon Scalable UPI" rev 0x04 at pci10 dev 16 function 1 not > > configured > > "Intel Xeon Scalable M3KTI" rev 0x04 at pci10 dev 18 function 0 not > > configured > > "Intel Xeon Scalable M3KTI" rev 0x04 at pci10 dev 18 function 1 not > > configured > > "Intel Xeon Scalable M3KTI" rev 0x04 at pci10 dev 18 function 2 not > > configured > > "Intel Xeon Scalable M3KTI" rev 0x04 at pci10 dev 18 function 4 not > > configured > > "Intel Xeon Scalable M3KTI" rev 0x04 at pci10 dev 18 function 5 not > > configured > > "Intel Xeon Scalable M2PCI" rev 0x04 at pci10 dev 21 function 0 not > > configured > > "Intel Xeon Scalable M2PCI" rev 0x04 at pci10 dev 22 function 0 not > > configured > > "Intel Xeon Scalable M2PCI" rev 0x04 at pci10 dev 22 function 4 not > > configured > > "Intel Xeon Scalable M2PCI" rev 0x04 at pci10 dev 23 function 0 not > > configured > > vmm0 at mainbus0: VMX/EPT > > uhub1 at uhub0 port 9 configuration 1 interface 0 "Microchip Tech > > USB2742" rev 2.10/2.07 addr2 > > uhub2 at uhub0 port 14 configuration 1 interface 0 "vendor 0x1604 > > product 0x10c0" rev 2.00/0.3 > > uhub3 at uhub2 port 1 configuration 1 interface 0 "vendor 0x1604 product > > 0x10c0" rev 2.00/0.04 > > uhub4 at uhub2 port 4 configuration 1 interface 0 "vendor 0x1604 product > > 0x10c0" rev 2.00/0.05 > > uhub5 at uhub0 port 18 configuration 1 interface 0 "Microchip Tech > > USB5742" rev 3.10/2.07 add6 > > vscsi0 at root > > scsibus5 at vscsi0: 256 targets > > softraid0 at root > > scsibus6 at softraid0: 256 targets > > root on sd0a (dcdc93eef85cda4c.a) swap on sd0b dump on sd0b > > Automatic boot in progress: starting file system checks. > > > > > > -- Wouter Prins w...@null0.nl

ospf6d and loopback interface hellotimer

Linkstate Uptime lo1 2001:db8::1 LOOP 7101w3d0 unknown00:00:02 Using ospfd (v4), the output of the HelloTimer field for a loopback interface defaults to '-'. -- Wouter Prins w...@null0.nl