Date: Wed, 14 Jun 2023 10:21:12 +0000 From: Benoit Chesneau <benoitc@enki-multimedia.eu> To: Benoit Chesneau <benoitc@enki-multimedia.eu> Cc: Alexander Chernikov <melifaro@FreeBSD.org>, "freebsd-net@FreeBSD.org" <freebsd-net@freebsd.org> Subject: Re: can't add a /24 blackhole route with a /32 loopback Message-ID: <LU7-MOZFMVrOadQfz8udVgYPFqtg5m3mlOaX1H7l1BYQYFS_D6_qVYYagjhhS4tDJkmL8qtsoLEr7XSQ4W1lM8obuAj2p-NNMFdKqQdBj74=@enki-multimedia.eu> In-Reply-To: <U2t98l4c8iB0VFmMFD9ET2Qd-xAeybUqjfNmvBPjEA5OBWiSpLdBRT9Ci6GHqryyLo8JJVnV4rMqNFvWiOKv-_6DkeVcpOTmf6c7HRAA-Qk=@enki-multimedia.eu> References: <9Jh8lSg93tjEc0-UEU3MQkGuQc7R9Aht0NBt4kEr6-wtgMdf673nws_jGaHelYwz0U78ik2BM4WLUca2JZAjrX-WSbP5QS4rsvoBHZo_JZo=@enki-multimedia.eu> <4DF565CC-D8AE-4F35-A7CF-7ED5AAD27B49@FreeBSD.org> <t_gT66nRcCT4fte7HbEMcM6J2spH-rEGFNYtZqX0GsUlxW4R5_pEVx3ZqtAwphKT4UBZsGZKX9gxeym1SKdc5GmceXGy1rRYEnSU1X6-_8c=@enki-multimedia.eu> <sgx1BljfJfV-Bn0PlfJ0va7yWHE9QraHpTjPBB6jlJWq4aehFwihem8C8f3ikkjvdEGIYY15S3ppTkQpWDfR3LDi_IKewBg7XQ1v9_u3SC4=@enki-multimedia.eu> <5747CC08-6903-4E2F-B0A5-D0CAB08F8165@FreeBSD.org> <0C23EFD2-1535-46B0-9E69-93D58B376CC3@FreeBSD.org> <U2t98l4c8iB0VFmMFD9ET2Qd-xAeybUqjfNmvBPjEA5OBWiSpLdBRT9Ci6GHqryyLo8JJVnV4rMqNFvWiOKv-_6DkeVcpOTmf6c7HRAA-Qk=@enki-multimedia.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
disreguard the part containing
```
# route -n get 1.1.1.1/32
route to: 1.1.1.1
destination: 1.1.1.1
gateway: 10.3.1.2
fib: 0
interface: vlan212
flags: <UP,GATEWAY,HOST,DONE,PROTO1>
recvpipe sendpipe ssthresh rtt,msec mtu weight expire
0 0 0 0 9000 1 0
```
It was actually a bad edit and should have been 1.1.1.2 there. This specific route is created dynamically with bird.
Benoît Chesneau, Enki Multimedia
—
t. +33608655490
Sent with Proton Mail secure email.
------- Original Message -------
On Wednesday, June 14th, 2023 at 12:18, Benoit Chesneau <benoitc@enki-multimedia.eu> wrote:
>
> ------- Original Message -------
> On Wednesday, June 14th, 2023 at 11:56, Alexander Chernikov melifaro@FreeBSD.org wrote:
>
> > Could you try:
> > 1) removing the 1.1.1.0/24 route
> > 2) removing the 1.1.1.1/32 from the lo1
> > 3) provide the output for `route -n get 1.1.1.0/24`
> > 4) provide the output for `route -n get 1.1.1.1/32`
> > 5) assign 1.1.1.1/32 to lo1
> > 6) provide the output for `route -n get 1.1.1.0/24`
> > 7) provide the output for `route -n get 1.1.1.1/32`
> > 8) provide the output for `route add -net 1.1.1.0/24 -blackhole`
>
>
> Find the result below. Such thing worked on another machine, I am not sure why. No obvious logs.
>
> ```
> # route -n get 1.1.1.0/24
> route to: 1.1.1.0
> destination: 1.1.1.0
> mask: 255.255.255.0
> fib: 0
> interface: lo1
> flags: <UP,DONE,STATIC>
>
> recvpipe sendpipe ssthresh rtt,msec mtu weight expire
> 0 0 0 0 16384 1 0
> # route -n get 1.1.1.1/32
> route to: 1.1.1.1
> destination: 1.1.1.1
> gateway: 10.3.1.2
> fib: 0
> interface: vlan212
> flags: <UP,GATEWAY,HOST,DONE,PROTO1>
>
> recvpipe sendpipe ssthresh rtt,msec mtu weight expire
> 0 0 0 0 9000 1 0
> # route delete 1.1.1.0/24
> delete net 1.1.1.0
> # route -n get 1.1.1.1/32
> route: route has not been found
> # ifconfig lo1 inet 1.1.1.1/32
> # route -n get 1.1.1.1/32
> route to: 1.1.1.1
> destination: 1.1.1.1
> fib: 0
> interface: lo1
> flags: <UP,HOST,DONE,PINNED>
>
> recvpipe sendpipe ssthresh rtt,msec mtu weight expire
> 0 0 0 0 16384 1 0
> # route add -net 1.1.1.0/24 -blackhole
> route: writing to routing socket: Operation not supported
> add net 1.1.1.0 fib 0: Operation not supported
> # route -n get 1.1.1.0/24
> route: route has not been found
> ```
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?LU7-MOZFMVrOadQfz8udVgYPFqtg5m3mlOaX1H7l1BYQYFS_D6_qVYYagjhhS4tDJkmL8qtsoLEr7XSQ4W1lM8obuAj2p-NNMFdKqQdBj74=>