Skip to Content.
Sympa Menu

rare-dev - Re: [rare-dev] Install RARE/freeRtr on Lanner Luna D-125

Subject: Rare project developers

List archive

Re: [rare-dev] Install RARE/freeRtr on Lanner Luna D-125


Chronological Thread 
  • From: mc36 <>
  • To: , Edgard da Cunha Pontes <>
  • Subject: Re: [rare-dev] Install RARE/freeRtr on Lanner Luna D-125
  • Date: Thu, 19 May 2022 12:14:03 +0200

hi,
the later two, enp1s0 entered promisc means to me that your system is up &
running...
one thing to note regarding how freerouter takes over the serial console is
that,
it uses 9600-8-n-1 (as most cisco devices) so after you see the above
mentioned
messages, you should change to that speed in your minicom/picocom/whatever...
let me know if this helps to recover at least the serial console...
an other thing i spotted is that only 2 of your 4 nics come up indicating
to me that they must have changed names in the newer kernel of sid so once
you recovered the serial console, we should not stop there.... :)
br,
cs



On 5/19/22 11:23, Edgard da Cunha Pontes wrote:
Hi all,

After some unsuccessful attempts to install RARE/freeRtr on Luna D-125, I
decided to come here for help.
I made an installation tutorial (step by step) that maybe can help to
understand the problem.
https://docs.google.com/document/d/1jrXgkYxFyIiKOjQ-tS8bKF-eyoHN4MHVrD9gaX8gPho/edit?usp=sharing <https://docs.google.com/document/d/1jrXgkYxFyIiKOjQ-tS8bKF-eyoHN4MHVrD9gaX8gPho/edit?usp=sharing>
The installation ends with a success message, but when restarting the OS, the system
"freezes".

Include the "initcall_debug ignore_loglevel" parameters at system boot, to
analyze how far it goes. These are the latest messages:
[ 42.038700] calling nf_nat_init+0x0/0x1000 [nf_nat] @ 508
[ 42.044453] initcall nf_nat_init+0x0/0x1000 [nf_nat] returned 0 after 162
usecs
[ 42.064865] calling nf_conncount_modinit+0x0/0x1000 [nf_conncount] @ 508
[ 42.071886] initcall nf_conncount_modinit+0x0/0x1000 [nf_conncount]
returned 0 after 102 usecs
[ 42.084514] device enp0s20f1 entered promiscuous mode
[ 42.101402] calling nsh_init_module+0x0/0x1000 [nsh] @ 508
[ 42.107239] initcall nsh_init_module+0x0/0x1000 [nsh] returned 0 after 2
usecs
[ 42.199975] calling dp_init+0x0/0x107 [openvswitch] @ 508
[ 42.205665] openvswitch: Open vSwitch switching datapath
[ 42.494589] initcall dp_init+0x0/0x107 [openvswitch] returned 0 after
282151 usecs
[ 42.525521] device enp1s0 entered promiscuous mode
[ 42.642649] device enp2s0 entered promiscuous mode

I hope someone has had a similar problem and can shed some "light".



Archive powered by MHonArc 2.6.19.

Top of Page