Hello all, i'm writing hear because i have a problem with some simulation
that i'm making, the simulation is on my laptop with VM.
I'm focusing on the hold timer expiration, i want to make this timer expire
and see the differences.
This is my topology:
H1---H2H3H4H5
H1 and H5 are the
On May 17, 2018 12:56:22 PM GMT+02:00, Mattia Milani
wrote:
>Hello all, i'm writing hear because i have a problem with some
>simulation
>that i'm making, the simulation is on my laptop with VM.
>I'm focusing on the hold timer expiration, i want to make this timer
>expire
>and see the difference
>3) so i was thinking that before closing itself bird send a signal to
>other
>bird connected (i didn't search in the code) so i use the command "sudo
>kill -9 *pid*" on the pid of the bird relative to H3, but with a big
>surprised i see that not only the process associated with H3 is killed
>but
> Have you looked into the logs? There should be written why these processes
> are also down. Or you should somewhere collect their status to see whether
> they ended correctly or failed somehow.
>
> Maria
>
yeah, i had looked into the logs but I diddn't see anything strange, here
is the last part
>all the log is brusquely interruptet, and i don't know why.
They may also have crashed (which would be bad). Try running the Birds in debug
mode (don't remember the flag, see bird --help) and collecting their exit
value.
>and after this...do you know if there is in bird some check in the
>
> They may also have crashed (which would be bad). Try running the Birds in
> debug mode (don't remember the flag, see bird --help) and collecting their
> exit value.
>
I used the command bird -c *confFile* -s *socketFile* -D *debugFile*
in the conf file I inserted:
debug protocols all;
debug com
making ifconfig eth* down in the interface of H3, on H2 and H4 it relevated
this in the log:
2018-05-17 16:26:38.462 kernel1 < interface h1_1-eth2 changes link
2018-05-17 16:26:38.462 direct1 < interface h1_1-eth2 changes link
2018-05-17 16:26:38.462 h2_2_h3_3: Link down
2018-05-17 16:26:38.462
On May 17, 2018 3:58:43 PM GMT+02:00, Mattia Milani
wrote:
>> They may also have crashed (which would be bad). Try running the
>Birds in
>> debug mode (don't remember the flag, see bird --help) and collecting
>their
>> exit value.
>>
>
>I used the command bird -c *confFile* -s *socketFile* -D *
On May 17, 2018 4:31:18 PM GMT+02:00, Mattia Milani
wrote:
>making ifconfig eth* down in the interface of H3, on H2 and H4 it
>relevated
>this in the log:
>
>2018-05-17 16:26:38.462 kernel1 < interface h1_1-eth2 changes
>link
>2018-05-17 16:26:38.462 direct1 < interface h1_1-eth2 changes
>lin
The same way as making any other tcp session disconnect immediately. You
> may try iptables or dropping the link in your virtual hypervisor or
> whatever else is applicable to your config.
>
> Maria
>
i've used the "tc" command to insert a delay/loss rate on the interface so
now it works.
for the
Hi BIRD experts,
My name is Soan Duong. I am a newbie of routing protocols, and of course of
The BIRD internet routing daemon as well.
I would like to get more understanding about one simple routing protocol
(e.g. RIP) in BIRD by debugging the code step-by-step. However, I have got
stuck at confi
11 matches
Mail list logo
