Re: Bgpd multipath conf
I'm working on something similar right now for bgpd, where any connected /128 ipv6 address will be announced over bgp. For example if the router is connected to an adjacent host that has assigned itself an address through slaac such that the router has an entry for that particular host in the routing table, then the router will announce the host's /128 address. On Thu, May 16, 2024 at 6:24 AM Stuart Henderson wrote: > > On 2024-05-16, Marco Agostani wrote: > > Ok so in the end is there a way to install more then one route in the > > kernel table through bgpd or not ? > > No. That is what "bgpd ... does not handle adding multiple paths for the > same prefix to the FIB" means. (FIB = "forwarding information base" = > kernel route table) > > > And if it's something that could be done in the future ? > > could? sure, if someone were to write the code to support it. > > I don't think it will be a particularly easy thing to do though. > > > -- > Please keep replies on the mailing list. >
Re: bgpd(8) not announcing IPv6 addresses from local network
> Is it possible to have a sample network diagram or at least a better > description of how you setup your network? Sure. My router is connected to two other routers via mgre0 to 2 other routers (routes should be sent to those 2 routers). The router which is sending routes has 4 NICs sit on a veb0 and are connected to some hosts on the network. These hosts are given prefix information by the router and autoconfigure their ipv6 addresses. > I'm not sure you must use BGP to advertise all your connected and static > routes. Of course it depends on your setup and goals but ideally before > BGP you may use an IGP for any prefix related to your infrastructure. > Then use BGP for what you consider as your 'end-user' prefix What I want to do is have the router that is connected to all of the hosts on my network to advertise the autoconfigured addresses of these hosts. I can see these hosts in the routers routing table, however bgpd doesn't advertise these routes, even though these routes are present within my routing table and I've specifically configured bgpd to advertise connected routes.
Re: bgpd(8) not announcing IPv6 addresses from local network
Sorry wrong address in my previous email
I meant to show this entry in my routing table
2620:ba:6000:3:58d2:48ff:fee6:270a 56:af:97:0f:66:6e
UHL0 12 - 4 vport0
On Mon, May 6, 2024 at 2:03 PM Benjamin Raskin
wrote:
>
> As mentioned in my previous email, I'm looking to advertise global
> addresses such as 2620:ba:6000:3:58d2:48ff:fee6:270a, but then
> I took a look at my routing table and noticed that gateway/nexthop
> for this global address is a MAC address
>
> fe80::58d2:48ff:fee6:270a%vport056:af:97:0f:66:6e
> UHLc 0 75 - 3 vport0
>
> So I'm curious, does bgpd(8) even detect that this address' nexthop
> is a MAC address? I'm taking a look at the source code of bgpd and
> I don't see any mention of MAC or hardware addresses.
>
> I'm not sure where to go from here or who to get in touch with, but I
> want to make sure that this is reproducible first and then go from there.
> This might be a bug or it might be something that I'm doing incorrectly.
>
> On Mon, May 6, 2024 at 11:55 AM Peter Hessler wrote:
> >
> > On 2024 May 06 (Mon) at 10:14:21 -0400 (-0400), Benjamin Raskin wrote:
> > :Hello, all;
> > :
> > :I've been having some issues getting bgpd to announce IPv6 routes,
> >
> > ...
> >
> > :
> > :bgpd(8) is configued to advertise all connected and static routes,
> > :however bgpd(8) only advertises routes that are connected to the wg0
> > :interface and none that are connected on the vport0 interface. Below is
> > :the output of `bgpctl show fib connected inet6` for reference.
> > :
> > :
> > :flags prio destination gateway
> > :C1 ::1/128 link#8
> > :C4 fd80::/64link#11
> > :C1 fd80::fce1:baff:fe6e:d685/128link#11
> > :C3 fd80::fce1:baff:fea6:bf3a/128link#11
> > :C3 fd80::fce1:baff:fed1:1740/128link#11
> > :C4 fe80::%vport0/64 link#10
> > :C4 fe80::%mgre0/64 link#12
> > :C1 fe80::1%lo0/128 link#8
> > :CN 1 fe80::1efd:8ff:fe7e:6b38%mgre0/128 link#12
> > :C8 fe80::9ab7:85ff:fe00:3726%mgre0/128 link#12
> > :C8 fe80::9ab7:85ff:fe00:3727%mgre0/128 link#12
> > :C4 ff01::%lo0/32link#8
> > :C4 ff01::%vport0/32 link#10
> > :C4 ff01::%wg0/32link#11
> > :C4 ff01::%mgre0/32 link#12
> > :C4 ff02::%lo0/32link#8
> > :C4 ff02::%vport0/32 link#10
> > :C4 ff02::%wg0/32link#11
> > :C4 ff02::%mgre0/32 link#12
> > :
> > :
> > :As far as I can tell bgpd(8) is configured correctly, and there are no
> > :anomalies when it comes to routes. Below is a sample of my bgpd(8)
> > :configuration for reference.
> > :
> >
> > fe80:: addresses are "link-local" addressess. Which means they are only
> > local to the link, and cannot be announced to other links.
> >
> > You'll need to assign ULA or Global addresses to the links in order for
> > them to be announced.
> >
> >
> > :
> > :AS 10261
> > :
> > :neighbor fe80::9ab7:85ff:fe00:3726%mgre0 {
> > :remote-as 10261
> > :}
> > :neighbor fe80::9ab7:85ff:fe00:3727%mgre0 {
> > :remote-as 10261
> > :}
> > :
> > :network inet6 priority 4
> > :network inet6 connected
> > :network inet6 static
> > :
> > :allow from ibgp
> > :allow to ibgp set { nexthop fe80::1efd:8ff:fe7e:6b38%mgre0 prepend-self 1 }
> > :
> > :
> > :Am I missing something? Am I making some assumption when it comes to how
> > :bgpd(8) works with IPv6 addresses? Thank you in advance.
> > :
> > :
> > :Ben Raskin
> > :
> >
> > --
> > With a rubber duck, one's never alone.
> > -- "The Hitchhiker's Guide to the Galaxy"
Re: bgpd(8) not announcing IPv6 addresses from local network
vport0 is a member of veb0, along with em0, em1, em2, and em3, with rad(8) running on vport0 announcing 2620:ba:6000:3:: vport0 only has a link-local address. The premise of not having a dedicated route for 2620:ba:6000:3::/64 is that multiple routers in various locations can advertise a prefix to hosts such as 2620:ba:6000:3:: without a route to one subnet, thus creating a single logical subnet across multiple routers. Hosts connected to the router would then assign themselves a /128 such as 2620:ba:6000:3:58d2:48ff:fee6:270a and bpgd(8) would then announce these /128 hosts to all other routers. On Mon, May 6, 2024 at 2:58 PM Claudio Jeker wrote: > > On Mon, May 06, 2024 at 02:36:07PM -0400, Benjamin Raskin wrote: > > Hello, Claudio; > > > > Sorry about the mistake, I meant to paste the route entry for > > 2620:ba:6000:3:58d2:48ff:fee6:270a > > and instead pasted the link local address. > > I looked at your route output and it makes little sense. > How is vport0 setup? It seems you just get ND entries for things like > 2620:ba:6000:3:58d2:48ff:fee6:270a but there is no network route for > 2620:ba:6000:3::/64 or similar setup. So very strange... > This is for sure not how I would route stuff. > > > Here is the output of the two commands > > > > prod-router-wat-01$ bgpctl show fib 2620:ba:6000:3:58d2:48ff:fee6:270a > > flags: B = BGP, C = Connected, S = Static > >N = BGP Nexthop reachable via this route > >r = reject route, b = blackhole route > > > > flags prio destination gateway > > B 48 ::/0 fe80::9ab7:85ff:fe00:3726%mgre0 > > prod-router-wat-01$ bgpctl show rib 2620:ba:6000:3:58d2:48ff:fee6:270a > > flags: * = Valid, > = Selected, I = via IBGP, A = Announced, > >S = Stale, E = Error > > origin validation state: N = not-found, V = valid, ! = invalid > > aspa validation state: ? = unknown, V = valid, ! = invalid > > origin: i = IGP, e = EGP, ? = Incomplete > > > > flags vs destination gateway lpref med aspath origin > > AI*> N-? 2620:ba:6000::/48::100 0 i > > I*N-? 2620:ba:6000::/48fe80::9ab7:85ff:fe00:3726%mgre0 100 > > 0 10261 i > > I*N-? 2620:ba:6000::/48fe80::9ab7:85ff:fe00:3727%mgre0 100 > > 0 10261 i > > > > I'm not seeing any output with the global address in question, which > > is pretty weird. > > > > > > On Mon, May 6, 2024 at 2:29 PM Claudio Jeker > > wrote: > > > > > > On Mon, May 06, 2024 at 02:03:52PM -0400, Benjamin Raskin wrote: > > > > As mentioned in my previous email, I'm looking to advertise global > > > > addresses such as 2620:ba:6000:3:58d2:48ff:fee6:270a, but then > > > > I took a look at my routing table and noticed that gateway/nexthop > > > > for this global address is a MAC address > > > > > > > > fe80::58d2:48ff:fee6:270a%vport056:af:97:0f:66:6e > > > > UHLc 0 75 - 3 vport0 > > > > > > This is a link local route and therefor not distributed. Also this is a > > > cloned ND6 entry which is also skipped. > > > > > > Your 2620:ba:6000:3:58d2:48ff:fee6:270a routes look like host routes to > > > me. They don't have C or S and so are neither connected nor static routes. > > > So you bgpctl show fib command does not show them. > > > > > > Please send output of `bgpctl show fib 2620:ba:6000:3:58d2:48ff:fee6:270a` > > > and `bgpctl show rib 2620:ba:6000:3:58d2:48ff:fee6:270a` maybe that helps > > > to get closer to the issue. > > > > > > > So I'm curious, does bgpd(8) even detect that this address' nexthop > > > > is a MAC address? I'm taking a look at the source code of bgpd and > > > > I don't see any mention of MAC or hardware addresses. > > > > > > > > I'm not sure where to go from here or who to get in touch with, but I > > > > want to make sure that this is reproducible first and then go from > > > > there. > > > > This might be a bug or it might be something that I'm doing incorrectly. > > > > > > > > On Mon, May 6, 2024 at 11:55 AM Peter Hessler > > > > wrote: > > > > > > > > > > On 2024 May 06 (Mon) at 10:14:21 -0400 (-0400), Benjamin Raskin wrote: > > > > > :Hello, all; > > > > > : > > > > > :I've been having some issues getting bgpd to announce IPv6 routes, > > > > > > > > > > ... > > > > >
Re: bgpd(8) not announcing IPv6 addresses from local network
Hello, Claudio; Sorry about the mistake, I meant to paste the route entry for 2620:ba:6000:3:58d2:48ff:fee6:270a and instead pasted the link local address. Here is the output of the two commands prod-router-wat-01$ bgpctl show fib 2620:ba:6000:3:58d2:48ff:fee6:270a flags: B = BGP, C = Connected, S = Static N = BGP Nexthop reachable via this route r = reject route, b = blackhole route flags prio destination gateway B 48 ::/0 fe80::9ab7:85ff:fe00:3726%mgre0 prod-router-wat-01$ bgpctl show rib 2620:ba:6000:3:58d2:48ff:fee6:270a flags: * = Valid, > = Selected, I = via IBGP, A = Announced, S = Stale, E = Error origin validation state: N = not-found, V = valid, ! = invalid aspa validation state: ? = unknown, V = valid, ! = invalid origin: i = IGP, e = EGP, ? = Incomplete flags vs destination gateway lpref med aspath origin AI*> N-? 2620:ba:6000::/48::100 0 i I*N-? 2620:ba:6000::/48fe80::9ab7:85ff:fe00:3726%mgre0 100 0 10261 i I*N-? 2620:ba:6000::/48fe80::9ab7:85ff:fe00:3727%mgre0 100 0 10261 i I'm not seeing any output with the global address in question, which is pretty weird. On Mon, May 6, 2024 at 2:29 PM Claudio Jeker wrote: > > On Mon, May 06, 2024 at 02:03:52PM -0400, Benjamin Raskin wrote: > > As mentioned in my previous email, I'm looking to advertise global > > addresses such as 2620:ba:6000:3:58d2:48ff:fee6:270a, but then > > I took a look at my routing table and noticed that gateway/nexthop > > for this global address is a MAC address > > > > fe80::58d2:48ff:fee6:270a%vport056:af:97:0f:66:6e > > UHLc 0 75 - 3 vport0 > > This is a link local route and therefor not distributed. Also this is a > cloned ND6 entry which is also skipped. > > Your 2620:ba:6000:3:58d2:48ff:fee6:270a routes look like host routes to > me. They don't have C or S and so are neither connected nor static routes. > So you bgpctl show fib command does not show them. > > Please send output of `bgpctl show fib 2620:ba:6000:3:58d2:48ff:fee6:270a` > and `bgpctl show rib 2620:ba:6000:3:58d2:48ff:fee6:270a` maybe that helps > to get closer to the issue. > > > So I'm curious, does bgpd(8) even detect that this address' nexthop > > is a MAC address? I'm taking a look at the source code of bgpd and > > I don't see any mention of MAC or hardware addresses. > > > > I'm not sure where to go from here or who to get in touch with, but I > > want to make sure that this is reproducible first and then go from there. > > This might be a bug or it might be something that I'm doing incorrectly. > > > > On Mon, May 6, 2024 at 11:55 AM Peter Hessler wrote: > > > > > > On 2024 May 06 (Mon) at 10:14:21 -0400 (-0400), Benjamin Raskin wrote: > > > :Hello, all; > > > : > > > :I've been having some issues getting bgpd to announce IPv6 routes, > > > > > > ... > > > > > > : > > > :bgpd(8) is configued to advertise all connected and static routes, > > > :however bgpd(8) only advertises routes that are connected to the wg0 > > > :interface and none that are connected on the vport0 interface. Below is > > > :the output of `bgpctl show fib connected inet6` for reference. > > > : > > > : > > > :flags prio destination gateway > > > :C1 ::1/128 link#8 > > > :C4 fd80::/64link#11 > > > :C1 fd80::fce1:baff:fe6e:d685/128link#11 > > > :C3 fd80::fce1:baff:fea6:bf3a/128link#11 > > > :C3 fd80::fce1:baff:fed1:1740/128link#11 > > > :C4 fe80::%vport0/64 link#10 > > > :C4 fe80::%mgre0/64 link#12 > > > :C1 fe80::1%lo0/128 link#8 > > > :CN 1 fe80::1efd:8ff:fe7e:6b38%mgre0/128 link#12 > > > :C8 fe80::9ab7:85ff:fe00:3726%mgre0/128 link#12 > > > :C8 fe80::9ab7:85ff:fe00:3727%mgre0/128 link#12 > > > :C4 ff01::%lo0/32link#8 > > > :C4 ff01::%vport0/32 link#10 > > > :C4 ff01::%wg0/32link#11 > > > :C4 ff01::%mgre0/32 link#12 > > > :C4 ff02::%lo0/32link#8 > > > :C4 ff02::%vport0/32 link#10 > > > :C4 ff02::%wg0/32link#11 > > > :C4 ff02::%mgre0/32 link#12 > > > : > > > : > > > :
Re: bgpd(8) not announcing IPv6 addresses from local network
As mentioned in my previous email, I'm looking to advertise global
addresses such as 2620:ba:6000:3:58d2:48ff:fee6:270a, but then
I took a look at my routing table and noticed that gateway/nexthop
for this global address is a MAC address
fe80::58d2:48ff:fee6:270a%vport056:af:97:0f:66:6e
UHLc 0 75 - 3 vport0
So I'm curious, does bgpd(8) even detect that this address' nexthop
is a MAC address? I'm taking a look at the source code of bgpd and
I don't see any mention of MAC or hardware addresses.
I'm not sure where to go from here or who to get in touch with, but I
want to make sure that this is reproducible first and then go from there.
This might be a bug or it might be something that I'm doing incorrectly.
On Mon, May 6, 2024 at 11:55 AM Peter Hessler wrote:
>
> On 2024 May 06 (Mon) at 10:14:21 -0400 (-0400), Benjamin Raskin wrote:
> :Hello, all;
> :
> :I've been having some issues getting bgpd to announce IPv6 routes,
>
> ...
>
> :
> :bgpd(8) is configued to advertise all connected and static routes,
> :however bgpd(8) only advertises routes that are connected to the wg0
> :interface and none that are connected on the vport0 interface. Below is
> :the output of `bgpctl show fib connected inet6` for reference.
> :
> :
> :flags prio destination gateway
> :C1 ::1/128 link#8
> :C4 fd80::/64link#11
> :C1 fd80::fce1:baff:fe6e:d685/128link#11
> :C3 fd80::fce1:baff:fea6:bf3a/128link#11
> :C3 fd80::fce1:baff:fed1:1740/128link#11
> :C4 fe80::%vport0/64 link#10
> :C4 fe80::%mgre0/64 link#12
> :C1 fe80::1%lo0/128 link#8
> :CN 1 fe80::1efd:8ff:fe7e:6b38%mgre0/128 link#12
> :C8 fe80::9ab7:85ff:fe00:3726%mgre0/128 link#12
> :C8 fe80::9ab7:85ff:fe00:3727%mgre0/128 link#12
> :C4 ff01::%lo0/32link#8
> :C4 ff01::%vport0/32 link#10
> :C4 ff01::%wg0/32link#11
> :C4 ff01::%mgre0/32 link#12
> :C4 ff02::%lo0/32link#8
> :C4 ff02::%vport0/32 link#10
> :C4 ff02::%wg0/32link#11
> :C4 ff02::%mgre0/32 link#12
> :
> :
> :As far as I can tell bgpd(8) is configured correctly, and there are no
> :anomalies when it comes to routes. Below is a sample of my bgpd(8)
> :configuration for reference.
> :
>
> fe80:: addresses are "link-local" addressess. Which means they are only
> local to the link, and cannot be announced to other links.
>
> You'll need to assign ULA or Global addresses to the links in order for
> them to be announced.
>
>
> :
> :AS 10261
> :
> :neighbor fe80::9ab7:85ff:fe00:3726%mgre0 {
> :remote-as 10261
> :}
> :neighbor fe80::9ab7:85ff:fe00:3727%mgre0 {
> :remote-as 10261
> :}
> :
> :network inet6 priority 4
> :network inet6 connected
> :network inet6 static
> :
> :allow from ibgp
> :allow to ibgp set { nexthop fe80::1efd:8ff:fe7e:6b38%mgre0 prepend-self 1 }
> :
> :
> :Am I missing something? Am I making some assumption when it comes to how
> :bgpd(8) works with IPv6 addresses? Thank you in advance.
> :
> :
> :Ben Raskin
> :
>
> --
> With a rubber duck, one's never alone.
> -- "The Hitchhiker's Guide to the Galaxy"
Re: bgpd(8) not announcing IPv6 addresses from local network
Hello, Peter;
The addresses I'm trying to announce are global i.e.
2620:ba:6000:3:58d2:48ff:fee6:270a , however bgpd(8)
doesn't want to announce them for some reason.
When I check my routing table they appear however, when
taking a look at bgpctl they are not announced.
Ben Raskin
On Mon, May 6, 2024 at 11:55 AM Peter Hessler wrote:
>
> On 2024 May 06 (Mon) at 10:14:21 -0400 (-0400), Benjamin Raskin wrote:
> :Hello, all;
> :
> :I've been having some issues getting bgpd to announce IPv6 routes,
>
> ...
>
> :
> :bgpd(8) is configued to advertise all connected and static routes,
> :however bgpd(8) only advertises routes that are connected to the wg0
> :interface and none that are connected on the vport0 interface. Below is
> :the output of `bgpctl show fib connected inet6` for reference.
> :
> :
> :flags prio destination gateway
> :C1 ::1/128 link#8
> :C4 fd80::/64link#11
> :C1 fd80::fce1:baff:fe6e:d685/128link#11
> :C3 fd80::fce1:baff:fea6:bf3a/128link#11
> :C3 fd80::fce1:baff:fed1:1740/128link#11
> :C4 fe80::%vport0/64 link#10
> :C4 fe80::%mgre0/64 link#12
> :C1 fe80::1%lo0/128 link#8
> :CN 1 fe80::1efd:8ff:fe7e:6b38%mgre0/128 link#12
> :C8 fe80::9ab7:85ff:fe00:3726%mgre0/128 link#12
> :C8 fe80::9ab7:85ff:fe00:3727%mgre0/128 link#12
> :C4 ff01::%lo0/32link#8
> :C4 ff01::%vport0/32 link#10
> :C4 ff01::%wg0/32link#11
> :C4 ff01::%mgre0/32 link#12
> :C4 ff02::%lo0/32link#8
> :C4 ff02::%vport0/32 link#10
> :C4 ff02::%wg0/32link#11
> :C4 ff02::%mgre0/32 link#12
> :
> :
> :As far as I can tell bgpd(8) is configured correctly, and there are no
> :anomalies when it comes to routes. Below is a sample of my bgpd(8)
> :configuration for reference.
> :
>
> fe80:: addresses are "link-local" addressess. Which means they are only
> local to the link, and cannot be announced to other links.
>
> You'll need to assign ULA or Global addresses to the links in order for
> them to be announced.
>
>
> :
> :AS 10261
> :
> :neighbor fe80::9ab7:85ff:fe00:3726%mgre0 {
> :remote-as 10261
> :}
> :neighbor fe80::9ab7:85ff:fe00:3727%mgre0 {
> :remote-as 10261
> :}
> :
> :network inet6 priority 4
> :network inet6 connected
> :network inet6 static
> :
> :allow from ibgp
> :allow to ibgp set { nexthop fe80::1efd:8ff:fe7e:6b38%mgre0 prepend-self 1 }
> :
> :
> :Am I missing something? Am I making some assumption when it comes to how
> :bgpd(8) works with IPv6 addresses? Thank you in advance.
> :
> :
> :Ben Raskin
> :
>
> --
> With a rubber duck, one's never alone.
> -- "The Hitchhiker's Guide to the Galaxy"
bgpd(8) not announcing IPv6 addresses from local network
Hello, all; I've been having some issues getting bgpd to announce IPv6 routes, apologies for the dumb question in advance. I've setup rad(8) and bgpd(8) on an OpenBSD machine. bgpd(8) is sending routes over to some neighbors (routes such as fd80::fce1:baff:fea6:bf3a) while rad(8) is sending prefix information for hosts to auto assign themselves some address (such as 2620:ba:6000:3:21db:f1bb:8ad9:21d6). Below is my routing table just for reference Routing tables Internet6: Destination Gateway Flags Refs Use Mtu Prio Iface ::/96 ::1 UGRS 00 32768 8 lo0 ::1 ::1 UHhl 11 6049 32768 1 lo0 :::0.0.0.0/96 ::1 UGRS 00 32768 8 lo0 2002::/24 ::1 UGRS 00 32768 8 lo0 2002:7f00::/24 ::1 UGRS 00 32768 8 lo0 2002:e000::/20 ::1 UGRS 00 32768 8 lo0 2002:ff00::/24 ::1 UGRS 00 32768 8 lo0 2620:ba:6000:3:21db:f1bb:8ad9:21d6 56:af:97:0f:66:6e UHL0 29 - 4 vport0 2620:ba:6000:3:58d2:48ff:fee6:270a 56:af:97:0f:66:6e UHL0 12 - 4 vport0 2620:ba:6000:3:6390:a68d:985b:167e 56:af:97:0f:66:6e UHL02 - 4 vport0 2620:ba:6000:3:fbc7:2dc3:5415:472f 56:af:97:0f:66:6e UHL02 - 4 vport0 fd80::/64 fd80::fce1:baff:fe6e:d685 UCn20 - 4 wg0 fd80::fce1:baff:fe6e:d685 wg0 UHl053176 - 1 wg0 fd80::fce1:baff:fea6:bf3a link#0 UHc018780 - 3 wg0 fd80::fce1:baff:fed1:1740 link#0 UHc017267 - 3 wg0 fe80::/10 ::1 UGRS 02 32768 8 lo0 fec0::/10 ::1 UGRS 00 32768 8 lo0 fe80::1%lo0 fe80::1%lo0 UHl00 32768 1 lo0 fe80::%vport0/64 fe80::fce1:baff:fed0:1651%vport0UCn6 13 - 4 vport0 fe80::f2:ef53:e182:f2b9%vport0 ca:17:26:5a:6c:4c UHLc 0 55 - 3 vport0 fe80::c9c:cf47:45fd:c478%vport0 6c:7e:67:ba:f4:bf UHLc 0 60 - 3 vport0 fe80::102e:8ee8:1221:17cd%vport032:b3:c9:b3:5b:da UHLc 0 47 - 3 vport0 fe80::1425:7ad2:8b72:50ae%vport000:e0:4c:6a:01:c7 UHLc 0 62 - 3 vport0 fe80::14d2:ffbf:d222:2a3c%vport056:af:97:0f:66:6e UHLc 0 144 - 3 vport0 fe80::58d2:48ff:fee6:270a%vport056:af:97:0f:66:6e UHLc 0 75 - 3 vport0 fe80::fce1:baff:fed0:1651%vport0fe:e1:ba:d0:16:51 UHLl 0 147 - 1 vport0 fe80::%mgre0/64 fe80::1efd:8ff:fe7e:6b38%mgre0 UCn00 - 4 mgre0 fe80::1efd:8ff:fe7e:6b38%mgre0 mgre0 UHl0 74 - 1 mgre0 fe80::9ab7:85ff:fe00:3726%mgre0 fd80::fce1:baff:fea6:bf3a UHS0 2398949 - 8 mgre0 fe80::9ab7:85ff:fe00:3727%mgre0 fd80::fce1:baff:fed1:1740 UHS0 556106 - 8 mgre0 bgpd(8) is configued to advertise all connected and static routes, however bgpd(8) only advertises routes that are connected to the wg0 interface and none that are connected on the vport0 interface. Below is the output of `bgpctl show fib connected inet6` for reference. flags prio destination gateway C1 ::1/128 link#8 C4 fd80::/64link#11 C1 fd80::fce1:baff:fe6e:d685/128link#11 C3 fd80::fce1:baff:fea6:bf3a/128link#11 C3 fd80::fce1:baff:fed1:1740/128link#11 C4 fe80::%vport0/64 link#10 C4 fe80::%mgre0/64 link#12 C1 fe80::1%lo0/128 link#8 CN 1 fe80::1efd:8ff:fe7e:6b38%mgre0/128 link#12 C8 fe80::9ab7:85ff:fe00:3726%mgre0/128 link#12 C8 fe80::9ab7:85ff:fe00:3727%mgre0/128 link#12 C4 ff01::%lo0/32link#8 C4 ff01::%vport0/32 link#10 C4 ff01::%wg0/32link#11 C4 ff01::%mgre0/32 link#12 C4 ff02::%lo0/32link#8 C4
Re: Realtek RTL8111H re(0) NIC not working on Raspberry Pi CM4
Hello, Mizsei; I took a look at Linkstar H68K and it looks to be using the same Realtek chip as the CM4 carrier board I have (RTL8111H). It seems that this is an issue on ARM64 devices. I'm not sure who's maintaining wrote the re(4) driver but I'm more than happy to help add support to for ARM64 devices, whether that be contributing code or sending devices to help debug the issue. Ben Raskin
Realtek RTL8111H re(0) NIC not working on Raspberry Pi CM4
Hello, All; I've been trying to configure a Realtek RTL8111H NIC on a Raspberry Pi CM4 board, however I have encountered several issues. This is the CM4 breakout board I'm using, the NIC is attached to the Pi via PCIe bus. Below is the `pcidump` output 0:0:0: Broadcom BCM2711 1:0:0: Realtek 8168 The first issue is that the MAC address of the NIC is all zeros. While it's no problem for me to set a MAC address for the device, upon attempting to ping the LAN router no packets exit the NIC. However other devices on the network can ping the NIC. In other words the NIC cannot send packets, but it can receive packets. tcpdump shows no packets either, so I'm left blind and can't seem to figure out how to diagnose the issue. Below is the `ifconfig re0` output re0: flags=808843 mtu 1500 lladdr 00:e0:4c:eb:9d:15 index 1 priority 0 llprio 3 groups: egress media: Ethernet autoselect (1000baseT full-duplex,master,rxpause,txpause) status: active inet 192.168.0.42 netmask 0xff00 broadcast 192.168.0.255 Below is the `dmesg` output for the re(0) device re0 at pci1 dev 0 function 0 "Realtek 8168" rev 0x15: RTL8168H/8111H (0x5400), intx, address 00:00:00:00:00:00 rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0 Has anyone else seen this issue? Is there something else I need to configure to make the NIC work? Thank you in advance. Ben Raskin
Relayd SSL Configuration with Cerbot Certs
Hello, Misc;
I'm attempting to configure relayd to work as a reverse proxy, such that all
web traffic goes through relayd prior to reaching some web server. I'm
confused as to how I am to configure the ssl cert and key options in the
relayd configuration. The manual configures the protocol as follows:
http protocol httpfilter {
tls ca key "/etc/ssl/private/ca.key" password "password123"
tls ca cert "/etc/ssl/ca.crt"
}
Where do I get the password for the key? I'm using certbot to generate the
certs, and at no time was I prompted to enter, or given a password. Am I
missing something in terms of configuration or cert generation, or have I
gotten everything all wrong? Thank you in advance.
Ben Raskin
libxcb finding winpid issues
Hello, misc;
I've been attempting to use OpenBSD libxcb to find the process ID of a window.
The function used to retrieve the PID is as follows:
pid_t
winpid(Window w)
{
pid_t result = 0;
xcb_res_client_id_spec_t spec = {0};
spec.client = w;
spec.mask = XCB_RES_CLIENT_ID_MASK_LOCAL_CLIENT_PID;
xcb_res_query_client_ids_cookie_t c =
xcb_res_query_client_ids(xcon, 1, );
xcb_res_query_client_ids_reply_t *r =
xcb_res_query_client_ids_reply(xcon, c, NULL);
if (!r)
return (pid_t)0;
xcb_res_client_id_value_iterator_t i =
xcb_res_query_client_ids_ids_iterator(r);
for (; i.rem; xcb_res_client_id_value_next()) {
spec = i.data->spec;
if (spec.mask & XCB_RES_CLIENT_ID_MASK_LOCAL_CLIENT_PID) {
uint32_t *t = xcb_res_client_id_value_value(i.data);
result = *t;
break;
}
}
free(r);
if (result == (pid_t)-1)
result = 0;
return result;
}
The code compiles, however the function returns 0 as a result. I've checked
the value of i.rem; it's always 0. I've made sure that the XCB connection
(represented by xcon) exists.
Has anyone else encountered this error? Thank you in advance.
Ben Raskin.
