haussli
haussli
why does this matter?
How about another device type? ```# Mikrotik routerOS - terse (ie commands) mikrotik-terse;alias;routeros-terse routeros-terse;script;rancid -t routeros-terse routeros-terse;login;mtlogin routeros-terse;module;routeros routeros-terse;inloop;routeros::inloop routeros-terse;command;routeros::SystemPackagePrintDetail;system package print detail without-paging routeros-terse;command;routeros::SystemRouterboardPrint;system routerboard print routeros-terse;command;routeros::SystemLicensePrint;system license print...
Can one mix the options? such as: export terse show-sensitive
I expect this would work for both v6 and v7 in one device type: https://github.com/haussli/rancid/tree/routeros67
Yes. If someone could confirm for me that it works, i'll commit that and add the terse type. TiA
It is now acctz.proto, but trying to address the questions: 1,2) it is not an ACK so much as it is a keepalive; that the client has not become brain-dead....
I think that this is resolved and another can be opened if there are remaining questions.
IMHO, support 1 format - protobuf. json inside protobuf seems unnecessarily kinky. But, I do not think this is my decision and there is clearly some precedence here with the...
Ja; I understand that the server code has implemented json. I think that that is its sloppy problem. :) For consistency, it should convert protobuf to json, if it insists...