RouterOS Serializer #119

aascedu · 2024-09-25T12:06:41Z

aascedu
Sep 25, 2024

Hey guys, I was trying to add a Mikrotik Serializer using RouterOS as extraction method and I get this in my Netbox logs :

10.200.84.112 - - [25/Sep/2024:11:58:25 +0000] "POST /plugins/validity/serializers/2/edit/ HTTP/1.1" 302 0 "http://netbox.ipline.bur:8000/plugins/validity/serializers/2/edit/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:130.0) Gecko/20100101 Firefox/130.0" Serializer Mikrotik Serializer has no template and no Data File defined

When I try to see the Serialized State of a device :

My device is from a Data Source, that works for Cisco Device, with my own TTP Template.
Here is more info on the data source :

These are the fields I get when trying to add a RouterOS Serializer for Mikrotik equipment :

Since there is not many errors popping off and not many debug info, I am coming here for some help, also I don't know if my problems come from the compatibility issues or if it is me who is not understanding the process and way things work !
ALSO I tested with a TTP Serializer on the same file and it does work well...
And obviously my config is in the correct format because it is exported from the router itself.

Thank you so much in advance if you have some tips to give me !

Arthur.

amyasnikov · 2024-09-25T21:40:39Z

amyasnikov
Sep 25, 2024
Maintainer

Hey @aascedu, looks like your serializer (Mikrotik Serializer) is not bound to the device (mikrotik-lbr009). You can bind it at individual device level, as well as at Device Type or Manufacturer levels

0 replies

aascedu · 2024-09-26T05:52:43Z

aascedu
Sep 26, 2024
Author

Hey @amyasnikov I did bind it, I tried the 3 different ways to bind it,but nothing. As I said, I know everything else is setup well because I tried with a custom made TTP Serializer, and I got a Serialized State. Any clues ? Thank you ;)

…

On Wed 25 Sep 2024 at 23:40, Anton ***@***.***> wrote: Hey @aascedu <https://github.com/aascedu>, looks like your serializer (Mikrotik Serializer) is not bound to the device (mikrotik-lbr009). You can bind it at individual device level, as well as at Device Type of Manufacturer levels — Reply to this email directly, view it on GitHub <#119 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2DITZGVXEJJ6BVVHXYEZQTZYMUWXAVCNFSM6AAAAABO2MGAPOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZVGY3DAMY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

0 replies

aascedu · 2024-09-26T08:33:20Z

aascedu
Sep 26, 2024
Author

Hello Anton,
I made it work,

In my Mikrotik config, I suspected that some \ char made the Python parser unhappy, so I removed them.
And it was that. Do you know why ? Do you know if it is possible to make it work with backslashes ???

Anyways, thank you for your help. I will probably be asking a lot of questions for the next 3-5 months since I am working with Validity everyday ! ❤️

0 replies

amyasnikov · 2024-09-26T09:18:29Z

amyasnikov
Sep 26, 2024
Maintainer

@aascedu do you have an example of the config with these backslashes? Few lines will be enough

2 replies

aascedu Sep 26, 2024
Author

@amyasnikov Yes absolutly here are the two elements I changed :
set note="*********************************\ \nADMINISTRATION\ \nFor further information\ \nMail : [email protected]\ \nPhone : +33333333333\ \n*********************************" show-at-login=no
which I changed to set note="*********************************" show-at-login=no
and
add as=xxxxx connect=yes disabled=no hold-time=20s keepalive-time=5s listen=yes local.address=x.x.x.x .role=ebgp multihop=yes name=NAME output.filter-chain=LAN .keep-sent-attributes=yes \ .network=bgp-network remote.address=x.x.x.x .as=65535 router-id=x.x.x.x
which I changed to :
add as=xxxxx connect=yes disabled=no hold-time=20s keepalive-time=5s listen=yes local.address=x.x.x.x .role=ebgp multihop=yes name=NAME output.filter-chain=LAN .keep-sent-attributes=yes .network=bgp-network remote.address=x.x.x.x .as=65535 router-id=x.x.x.x

Would that be why it didn't work ?

amyasnikov Sep 26, 2024
Maintainer

Probably yes, I have to check it first. As I see there are 2 different cases: backslash inside quotes and and outside of them. Perhaps only one of the cases is causing this problem.

aascedu · 2024-09-26T11:48:29Z

aascedu
Sep 26, 2024
Author

I can check both cases and come back to you!

…

On Thu 26 Sep 2024 at 13:40, Anton ***@***.***> wrote: Probably yes, I have to check it first. As I see there are 2 different cases: backslash inside quotes and and outside of them. Perhaps only one of the cases is causing this problem. — Reply to this email directly, view it on GitHub <#119 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2DITZFLQIPA7LGAZV5OIO3ZYPXDDAVCNFSM6AAAAABO2MGAPOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZWGI2TSMI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

4 replies

aascedu Oct 1, 2024
Author

I am a bit late but here is a part of the config I found to be annoying RouterOS parser :

set note="*********************************\
    \nIPLINE ADMINISTRATION\
    \nFor further information\
    \nMail : [email protected]\
    \nPhone : +334 27 70 90 00\
    \n*********************************" show-at-login=no

will cause that error :

but when changed to this (without \ or \n) :

set note="*********************************" show-at-login=no

amyasnikov Oct 1, 2024
Maintainer

Do you see exactly this one (attention to special characters) when browsing the file in the data source?

set note="*********************************\
    \nIPLINE ADMINISTRATION\
    \nFor further information\
    \nMail : [email protected]\
    \nPhone : +334 27 70 90 00\
    \n*********************************" show-at-login=no

I'm asking because I've tried it and the parser works well

aascedu Oct 14, 2024
Author

Hey @amyasnikov, to address this, I think what the parser doesn't like is whitespaces, for exemple in my config :

add chain=LAN disabled=no rule=\
    "if (dst in bgp-network) {set bgp-path-prepend 1; accept}"

doesn't work because in the config file, there is a \ and MOST IMPORTANTLY, a new line just after rule= so it thinks there is multiple whitespaces after... and probably doesn't accept it !
Do you think it would be fixable ?

amyasnikov Oct 15, 2024
Maintainer

Unfortunately, just copy-pasting from here doesn't help to reproduce the issue. The parser still works fine with the line you provided.

You can do the following to make it reproducible:

Create public repository (e.g. on github)
Place your full (or at least those parts which in your opinion cause errors) config file there
Use this repository as a data source for device configurations in netbox.
Make sure you still have the error with config parsing usgin this repository.
Share the repository with me, so I will be able to perform steps 3 and 4 on my own.

aascedu · 2024-10-02T04:08:18Z

aascedu
Oct 2, 2024
Author

Il check again

…

On Tue 1 Oct 2024 at 23:11, Anton ***@***.***> wrote: Do you see exactly this one (attention to special characters) when browsing the file in the data source? set note="*********************************\ \nIPLINE ADMINISTRATION\ \nFor further information\ \nMail : ***@***.***\ \nPhone : +334 27 70 90 00\ \n*********************************" show-at-login=no I'm asking because I've tried it and the parser works well — Reply to this email directly, view it on GitHub <#119 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2DITZBJ4J6G7M37FHPSZWDZZMFZNAVCNFSM6AAAAABO2MGAPOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAOBRGM3TANY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

0 replies

aascedu · 2024-10-15T12:56:45Z

aascedu
Oct 15, 2024
Author

I will tag you whenever I have done that! Thank you !

…

On Tue 15 Oct 2024 at 14:52, Anton ***@***.***> wrote: Unfortunately, just copy-pasting from here doesn't help to reproduce the issue. The parser still works fine with the line you provided. You can do the following to make it reproducible: 1. Create public repository (e.g. on github) 2. Place your full (or at least those parts which in your opinion cause errors) config file there 3. Use this repository as a data source for device configurations in netbox. 4. Make sure you still have the error with config parsing usgin this repository. 5. Share the repository with me, so I will be able to perform steps 3 and 4 on my own. — Reply to this email directly, view it on GitHub <#119 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2DITZEZN42W6UMCY72W4V3Z3UF2TAVCNFSM6AAAAABO2MGAPOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAOJUG43DIMQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

1 reply

amyasnikov Oct 15, 2024
Maintainer

@aascedu please create a separate issue in case of successful reproduction of the error.

I'm closing this discussion because it

has the answer
has gone far away from the initial question

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

RouterOS Serializer #119

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 7 comments 7 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

RouterOS Serializer #119

aascedu Sep 25, 2024

Replies: 7 comments · 7 replies

amyasnikov Sep 25, 2024 Maintainer

aascedu Sep 26, 2024 Author

aascedu Sep 26, 2024 Author

amyasnikov Sep 26, 2024 Maintainer

aascedu Sep 26, 2024 Author

amyasnikov Sep 26, 2024 Maintainer

aascedu Sep 26, 2024 Author

aascedu Oct 1, 2024 Author

amyasnikov Oct 1, 2024 Maintainer

aascedu Oct 14, 2024 Author

amyasnikov Oct 15, 2024 Maintainer

aascedu Oct 2, 2024 Author

aascedu Oct 15, 2024 Author

amyasnikov Oct 15, 2024 Maintainer

aascedu
Sep 25, 2024

Replies: 7 comments 7 replies

amyasnikov
Sep 25, 2024
Maintainer

aascedu
Sep 26, 2024
Author

aascedu
Sep 26, 2024
Author

amyasnikov
Sep 26, 2024
Maintainer

aascedu Sep 26, 2024
Author

amyasnikov Sep 26, 2024
Maintainer

aascedu
Sep 26, 2024
Author

aascedu Oct 1, 2024
Author

amyasnikov Oct 1, 2024
Maintainer

aascedu Oct 14, 2024
Author

amyasnikov Oct 15, 2024
Maintainer

aascedu
Oct 2, 2024
Author

aascedu
Oct 15, 2024
Author

amyasnikov Oct 15, 2024
Maintainer