Re: ixl(4) troubles
hi Matthew,
We are using multiple ixl(4) quad cards and encountered the same issue when
testing with 3rd party optics.
Using official intel optics or re-branded optics works ok for us on openbsd
7.4.
Kind regards,
Wouter
On Fri, Oct 4, 2024 at 12:27 PM matthew j weaver wrote:
> Thanks, Jan & Stuart -- I'll grab some more likely intel compatible
> transceivers and give them a shot.
>
> I appreciate the pointers.
>
> weaver
>
> On Fri, Oct 4, 2024, at 04:32, Stuart Henderson wrote:
> > On 2024-10-04, Jan Klemkow wrote:
> >> Hi Matthew,
> >>
> >> On Thu, Oct 03, 2024 at 01:52:11PM -0500, matthew j weaver wrote:
> >>> Howdy, all. I'm having basic trouble with some ixl(4) interfaces and
> >>> cannot figure out what I am overlooking.
> >>>
> >>> The hardware is an Intel X710 SFP+ card with two interfaces. I cannot
> >>> seem to get the interfaces to achieve carrier link. The interfaces are
> >>> always status: no carrier. I've tried a few transceivers, cables,
> different
> >>> equipment on the far end, to no avail.
> >>>
> >>> The transceivers and cables currently set up have worked fine in
> >>> other hardware.
> >>>
> >>> Install is OpenBSD 7.5, dmesg is below.
> >>>
> >>> For ease of experiment, I've put matching transceivers into the two
> >>> interfaces, connected by an appropriate cable. Even in this
> >>> configuration I can't get link, as can be seen here in output from
> >>> ifconfig ixl{0,1} transceiver:
> >>>
> >>> -
> >>> ixl0: 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
Hello Martin, Make sure you adhere to the docs: https://www.openbsd.org/faq/faq6.html#Bridge You need to rename vlan101 to the vether101 (for example) interface. You will need a separate bridge interface per vlan if you want to keep layer 2 separated. First try to test the bridge without pf, and then isolate the problem to pf. On Fri, Jun 7, 2024 at 5:06 AM Martin wrote: > Are you supposed to "bridge" the vlan with the physical interface? > > I have: > > $ cat /etc/hostname.em0 > up > > $ cat /etc/hostname.vlan101 > vnetid 101 parent em0 > inet autoconf > up > > In /etc/pf.conf I have replaced em0 with vlan101 for ext_if. > > I get "No route to host" if I try to ping something, etc. > > But if add: > > $ cat /etc/hostname.bridge0 > add vlan101 > add em0 > up > > Then it works. > > 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
Thank you Laurent and Claudio, We have an identical setup (hardware specs), i am sure we need this in the near future. :) /Wouter On Thu, Dec 14, 2023 at 3:08 PM Claudio Jeker wrote: > On Tue, Nov 28, 2023 at 05:55:03PM +0100, Laurent CARON wrote: > > > > Le 28/11/2023 à 17:46, Claudio Jeker a écrit : > > > The problem is that the symbol nkmempages moved into .bss and is > therefor > > > no longer modifiable by config(8). I think you can still use ukc via > > > boot -c to alter it (but that is not sticky). > > > > > > The alternative is to set "option NKMEMPAGES=131072" in your GENERIC > > > config file (or option NKMEMPAGES_MAX=131072). See also options(4). > > > > > > Long term is the fix this proper. All of this was built when computers > had > > > 100MB of memory not 100GB. > > > > > > > Got it. Thanks. > > > > It means I'll stick with this kernel for now and see if it helps (it > seems > > promising for now). > > > > Is there a way you can submit this patch (option NKMEMPAGES=131072) to > 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? > > >> The manpage doesn't mention anything about the type of > > >> bridge interface required (bridge/veb)? > > > > > > I have not tried it but I think mpw(4) should work with veb(4) just fine. > > > > Agreed. Does it work? I just tested the l2vpn setup between openbsd and cisco, with the veb(4) bridge the mac addresses are not learned from the mpw(4) interface. When replacing the veb(4) with a bridge(4) the mac addresses are learned from the mpw(4) interface and the pseudowire is working correctly. If you want the configuration, please let me know but it should be easy to replicate (if it needs to be fixed :)) /Wouter
Re: OpenBSD and l3VPN
Hello Juan, On Wed, Oct 4, 2023 at 10:28 AM jv.cameros wrote: > > Hello pals, > > I'm a telecommunications engineer studying a master while working in an > internship at my uni. I'm new to OpenBSD, and i have been working lately > in defining a network with a l2VPN. In that case i had a king of > tutorial > https://github.com/rwestphal/openbsd-ldpd/wiki/VPLS-basic-test-setup A lot of students these days on OpenBSD, good stuff. :) The example has Cisco boxes as PE and CE's, this can all be replaced by OpenBSD. > > i found from a developer but now i find myself with my hands empty. The > proposed scenario will be based on 5 customers CE defining two instances > conected to by an MPLS network which has 3 PE. My final goal would be to > define one only network scenario where i could define both l2vpn and > l3vpn. > Do you know where i can find some sort of guide or tutorial for defining > this kind of netwrok? So, i would made this part of your internship and figure out how it works to be honest. :) OpenBSD has support for the MPLS applications L2VPN and L3VPN, and they work ok. If you want to break out of a MPLS 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-client generates for other
> routers too).
>
> Since the 8th of may, it crashes on reload, after rpki-client ran
> Only emptying the rpki-client config file makes it start again, until
> it's reloaded after rpki run again.
>
> /etc/bgpd.conf:
>
> AS 212834
> router-id 10.126.0.39
>
> prefix-set mynetworks {
>2001:678:de8::/48
> }
>
> include "/var/db/rpki-client/openbgpd.6"
>
> socket "/var/www/run/bgpd.rsock" restricted
>
> deny quick from ebgp prefix-set mynetworks or-longer
> allow from ibgp
> deny to ibgp
>
> network prefix-set mynetworks
>
> group "ibgp" {
>remote-as 212834
>local-address 2001:678:de8:x
>neighbor 2001:678:de8:y {
> descr "r1"
>}
>neighbor 2001:678:de8:z {
> descr "r2"
>}
> }
>
>
> /var/db/rpki-client/openbgpd.6 is an ipv6-only view of /var/db/rpki-
> client/openbgpd, generated by cron :
>
> grep -v -E '[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+/[0-9]+'
> /var/db/rpki-client/openbgpd > /var/db/rpki-client/openbgpd.6
>
>
> When openbgpd.6 is non-empty, the log file contains :
>
> May 11 14:49:15 rpki bgpd[47637]: startup
> May 11 14:49:15 rpki bgpd[84245]: rtr engine ready
> May 11 14:49:15 rpki bgpd[17015]: route decision engine ready
> May 11 14:49:15 rpki bgpd[28135]: session engine ready
> May 11 14:49:16 rpki bgpd[28135]: listening on 0.0.0.0
> May 11 14:49:16 rpki bgpd[28135]: listening on ::
> May 11 14:49:16 rpki bgpd[28135]: SE reconfigured
> May 11 14:49:16 rpki bgpd[28135]: neighbor 2001:678:de8:z (r2): state change
> None -> Idle, reason: None
> May 11 14:49:16 rpki bgpd[28135]: neighbor 2001:678:de8:y (r1): state change
> None -> Idle, reason: None
> May 11 14:49:16 rpki bgpd[17015]: RDE reconfigured
> May 11 14:49:16 rpki bgpd[17015]: running softreconfig in
> May 11 14:49:16 rpki bgpd[17015]: softreconfig in done
> May 11 14:49:16 rpki bgpd[17015]: starting softreconfig out for rib Loc-RIB
> May 11 14:49:16 rpki bgpd[17015]: softreconfig out done for Loc-RIB
> May 11 14:49:16 rpki bgpd[17015]: RDE soft reconfiguration done
> May 11 14:49:16 rpki bgpd[84245]: RTR engine reconfigured
> May 11 14:49:16 rpki bgpd[17015]: fatal in RDE: aspa_add_set: bad order of
> adds
> May 11 14:49:16 rpki bgpd[84245]: peer closed imsg connection
> May 11 14:49:16 rpki bgpd[84245]: RTR: Lost connection to RDE
> May 11 14:49:16 rpki bgpd[28135]: peer closed imsg connection
> May 11 14:49:16 rpki bgpd[28135]: SE: Lost connection to RDE
> May 11 14:49:16 rpki bgpd[28135]: peer closed imsg connection
> May 11 14:49:16 rpki bgpd[28135]: SE: Lost connection to RDE control
> May 11 14:49:16 rpki bgpd[47637]: peer closed imsg connection
> May 11 14:49:16 rpki bgpd[47637]: main: Lost connection to RDE
> May 11 14:49:16 rpki bgpd[28135]: peer closed imsg connection
> May 11 14:49:16 rpki bgpd[84245]: peer closed imsg connection
> May 11 14:49:16 rpki bgpd[28135]: SE: Lost connection to parent
> May 11 14:49:16 rpki bgpd[47637]: kernel routing table 0 (Loc-RIB) decoupled
> May 11 14:49:16 rpki bgpd[28135]: session engine exiting
> May 11 14:49:16 rpki bgpd[84245]: fatal in RTR: Lost connection to parent
> May 11 14:49:16 rpki bgpd[47637]: terminating
>
> I guess the aspa_add_set: bad order of adds is the cause of the
> termination...
>
>
> When openbgpd.6 is empty, bgpd start correctly :
>
> May 11 14:49:31 rpki bgpd[23169]: startup
> May 11 14:49:31 rpki bgpd[82407]: route decision engine ready
> May 11 14:49:31 rpki bgpd[71345]: session engine ready
> May 11 14:49:31 rpki bgpd[86603]: rtr engine ready
> May 11 14:49:31 rpki bgpd[71345]: listening on 0.0.0.0
> May 11 14:49:31 rpki bgpd[71345]: listening on ::
> May 11 14:49:31 rpki bgpd[71345]: SE reconfigured
> May 11 14:49:31 rpki bgpd[71345]: neighbor 2001:678:de8:z (r2): state change
> None -> Idle, reason: None
> May 11 14:49:31 rpki bgpd[71345]: neighbor 2001:678:de8:y (r1): state change
> None -> Idle, reason: None
> May 11 14:49:31 rpki bgpd[86603]: RTR engine reconfigured
> May 11 14:49:31 rpki bgpd[82407]: RDE reconfigured
> May 11 14:49:31 rpki bgpd[82407]: running softreconfig in
> May 11 14:49:31 rpki bgpd[82407]: softreconfig in done
> May 11 14:49:31 rpki bgpd[82407]: starting softreconfig out for rib Loc-RIB
> May 11 14:49:31 rpki bgpd[82407]: softreconfig out done for Loc-RIB
> May 11 14:49:31 rpki bgpd[82407]: RDE soft reconfiguration done
> May 11 14:49:32 rpki bgpd[71345]: neighbor 2001:678:de8:y (r1): state change
> Idle -> Active, reason: Start
> May 11 14:49:32 rpki bgpd[71345]: neighbor 2001:678:de8:y (r1): state change
> Active -> OpenSent, reason: Connection opened
> May 11 14:49:32 rpki bgpd[71345]: neighbor 2001:678:de8:y (r1): state change
> OpenSent -> OpenConfirm, re
Re: Intel nic on Dell R710: failed to allocate interrupt slot for PIC msix
quot; rev > > 0x01: msi > > mfii0: "PERC H740P Mini ", firmware 51.14.0-3900, 8192MB cache > > scsibus3 at mfii0: 64 targets > > sd0 at scsibus3 targ 0 lun 0: > > naa.64cd98f07028c90024ba5c9db8f13a > > sd0: 285568MB, 512 bytes/sector, 584843264 sectors > > scsibus4 at mfii0: 256 targets > > "Intel Xeon Scalable VT-d" rev 0x04 at pci7 dev 5 function 0 not > configured > > "Intel Xeon Scalable RAS" rev 0x04 at pci7 dev 5 function 2 not > configured > > "Intel Xeon Scalable IOxAPIC" rev 0x04 at pci7 dev 5 function 4 not > > configured > > "Intel Xeon Scalable IMC" rev 0x04 at pci7 dev 8 function 0 not > configured > > "Intel Xeon Scalable IMC" rev 0x04 at pci7 dev 9 function 0 not > configured > > "Intel Xeon Scalable IMC" rev 0x04 at pci7 dev 10 function 0 not > configured > > "Intel Xeon Scalable IMC" rev 0x04 at pci7 dev 10 function 1 not > configured > > "Intel Xeon Scalable IMC" rev 0x04 at pci7 dev 10 function 2 not > configured > > "Intel Xeon Scalable IMC" rev 0x04 at pci7 dev 10 function 3 not > configured > > "Intel Xeon Scalable IMC" rev 0x04 at pci7 dev 10 function 4 not > configured > > "Intel Xeon Scalable LM" rev 0x04 at pci7 dev 10 function 5 not > configured > > "Intel Xeon Scalable LMS" rev 0x04 at pci7 dev 10 function 6 not > configured > > "Intel Xeon Scalable LMDP" rev 0x04 at pci7 dev 10 function 7 not > > configured > > "Intel Xeon Scalable DECS" rev 0x04 at pci7 dev 11 function 0 not > > configured > > "Intel Xeon Scalable LM" rev 0x04 at pci7 dev 11 function 1 not > configured > > "Intel Xeon Scalable LMS" rev 0x04 at pci7 dev 11 function 2 not > configured > > "Intel Xeon Scalable LMDP" rev 0x04 at pci7 dev 11 function 3 not > > configured > > "Intel Xeon Scalable IMC" rev 0x04 at pci7 dev 12 function 0 not > configured > > "Intel Xeon Scalable IMC" rev 0x04 at pci7 dev 12 function 1 not > configured > > "Intel Xeon Scalable IMC" rev 0x04 at pci7 dev 12 function 2 not > configured > > "Intel Xeon Scalable IMC" rev 0x04 at pci7 dev 12 function 3 not > configured > > "Intel Xeon Scalable IMC" rev 0x04 at pci7 dev 12 function 4 not > configured > > "Intel Xeon Scalable LM" rev 0x04 at pci7 dev 12 function 5 not > configured > > "Intel Xeon Scalable LMS" rev 0x04 at pci7 dev 12 function 6 not > configured > > "Intel Xeon Scalable LMDP" rev 0x04 at pci7 dev 12 function 7 not > > configured > > "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
hello, Using OpenBSD 7.2 (and previous versions), i noticed when running ospf6d on a loopback interface, the output of 'doas ospf6ctl show interface' HelloTimer field contains a weird value: dev$ doas ospf6ctl show interface Interface Address State 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
