--- Original Message ---
On Wednesday, June 14th, 2023 at 12:36, Alexander Chernikov
wrote:
> > On 14 Jun 2023, at 11:26, Benoit Chesneau beno...@enki-multimedia.eu wrote:
> >
> > I found an interresting log in dmesg (see below). Not sure how it can
> > happens.
> >
> > Could it b
> On 14 Jun 2023, at 11:26, Benoit Chesneau wrote:
>
> I found an interresting log in dmesg (see below). Not sure how it can happens.
>
> Could it be related to the usage of bird?
>
> The log:
>
> ```
> [rtsock] fill_blackholeinfo: PID 72835: Unable to find ifa for
> blackhole/reject nhop
I found an interresting log in dmesg (see below). Not sure how it can happens.
Could it be related to the usage of bird?
The log:
```
[rtsock] fill_blackholeinfo: PID 72835: Unable to find ifa for blackhole/reject
nhop
[rtsock] fill_blackholeinfo: PID 72837: Unable to find ifa for blackhole/rej
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:
recvpipe sendpipe ssthresh rtt,msecmtuweightexpire
0 0 0 0 9000
--- Original Message ---
On Wednesday, June 14th, 2023 at 11:56, Alexander Chernikov
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
> On 14 Jun 2023, at 10:42, Alexander Chernikov wrote:
>
>
>
>> On 14 Jun 2023, at 10:06, Benoit Chesneau wrote:
>>
>> I forgot oto add the error message , sorry.
>>
>> When I try to set the theblackhole flag I get the following error:
>>
>> ```
>> route: writing to routing socket: Oper
(resending, after an pekab issue).
I tried it but if I delete the route, I will have the same kind of error when
adding it. I can only add it using the `-iface` flag. This error is weird.
BenoƮt
--- Original Message ---
On Wednesday, June 14th, 2023 at 11:46, Patrick M. Hausen
wrote
Here is the ifconfig for loopbacks:
```
ifconfig lo1
lo1: flags=8049 metric 0 mtu 16384
options=680003
inet6 fe80::1%lo1 prefixlen 64 scopeid 0x9
inet6 ::1:1::1 prefixlen 128
inet 1.1.1.1 netmask 0x
groups: lo
nd6 options=21
root@cor
> On 14 Jun 2023, at 10:06, Benoit Chesneau wrote:
>
> I forgot oto add the error message , sorry.
>
> When I try to set the theblackhole flag I get the following error:
>
> ```
> route: writing to routing socket: Operation not supported
> change net 1.1.1.0 fib 0: Operation not supported
>
I forgot oto add the error message , sorry.
When I try to set the theblackhole flag I get the following error:
```
route: writing to routing socket: Operation not supported
change net 1.1.1.0 fib 0: Operation not supported
```
--- Original Message ---
On Wednesday, June 14th, 2023 at 1
Hi,
Thanks for your answer. I'm using Freebsd 13.2 latest version:
$ uname -srm
FreeBSD 13.2-RELEASE amd64
I edited the filtred result of the table since it has a full view:
netstat -4rnW |grep -e "1.1.1"
1.1.1.0/24127.0.0.1 USB14 16384lo0
1.1.1.1 link#9
> On 14 Jun 2023, at 07:05, Benoit Chesneau wrote:
>
> Hi,
>
> When I setup a loopback to a /32 , I can add a /24 as a blackhole route
> anymore. I can only create a /24 attached to this looopback. Ie.
Could you add a bit more context?
What is the FreeBSD version (uname -srm)?
What does 'rou
12 matches
Mail list logo