Okay, the encrypted passwords are re-read from /var/lib/snmp/snmpd.conf and set on the CLI. The truncation originats from that file.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jun 5 2018
Ah, yes. In the past the Perl scripts re-read the newly generated configuration and altered the running configuration using /opt/vyatta/sbin/my_set or /opt/vyatta/sbin/my_delete. That's indeed missing. Thanks for the commands and I'll fix it this evening.
@Line2 thanks for the feedback. Could you tell me how you generated that encrypted key so I can retest this evening and bugfix this?
Jun 4 2018
A first implementation is merged
Tested using:
Jun 3 2018
Jun 2 2018
Working again with 1.2.0-rolling+201806020337
Jun 1 2018
May 29 2018
This one should be closed and reopened if required @syncer
Good catch. The proper solution should be:
May 27 2018
As soon as someone sets set system ntp allow-clients address 172.16.0.0/12 we act as NTP server for this network,too. It's a bit odd that this node is under system but ... it is as it is.
@syncer we do offer NTP as service (unfortunately it's unter the system tree instead of service.
May 22 2018
any updates on this?
looks like a missing check on commit. Will add this case to the new Python script.
Ah, there it is! Thanks!
May 21 2018
Even after changing the configuration to
snmp {
listen-address 172.16.37.241 {
}
v3 {
engineid 0xff42
user test {
auth {
encrypted-key 0x63119b4e19ce4d69c7ad678ffe110047
type sha
}
engineid 0xff42
mode rw
privacy {
encrypted-key 0x63119b4e19ce4d69c7ad678ffe110047
type aes
}
}
}
}Commands will be:
@syncer this seems to be the option, plese correct if wrong.
May 17 2018
fixed by @higebu in VyOS 1.2.0-rolling+201805171657
May 16 2018
... reverting ...
Maybe I got something wrong but my Test indicated by upgrading from VyOS 1.1.7 to 1.2.x worked. the service ssh allow-root config line just vanished and remote login worked like a charm. I always tried to be backwards compatible at least with VyOS 1.1.7.
May 15 2018
Proposal for command:
Merged as discussed via slack
May 14 2018
It's a general problem with the new Python scripts. Somehow the lib is injured :/ @dmbaturin