Please retest with latest ISO
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 30 2018
@oleksandr.mamenko could you please provide a config snippet?
... and also working with latest rolling version VyOS 1.2.0-rolling+201806300337. Please note there was a time with a "bad" StrongSWAN version, maybe that's what you have.
I can confirm it was working with Version: VyOS 1.2.0-rolling+201806050337
Just spawn a VyOS 1.1.8 VM and the ifAlias appears on my libreNMS instance.
Jun 29 2018
In general I like the idea.
Jun 28 2018
cpo@LR1:~$ show snmp mib ifmib ifAlias eth0 eth0: ifAlias = NET-MYBLL-MUCI-BACKBONE
Jun 27 2018
@Asteroza usually htop only gives you a snapshot about the current system behavior/missbehavior. For this kind of thing I use SNMP monitoring with libreNMS so I get a detailed graph + backlog about the routers utilisation.
Jun 26 2018
The "problem" is inherited from the old SNMP CLI definition which was re-generated in XML by me and is now generated here: https://github.com/vyos/vyos-1x/blob/current/interface-definitions/snmp.xml#L230-L237.
@begetan thanks for this detialed description.
Jun 24 2018
maybe you could assist us by trying the following steps on your system:
Jun 22 2018
cpo@LR1:~$ show version Version: VyOS 1.2.0-rolling+201806220337 Built by: [email protected] Built on: Fri 22 Jun 2018 03:37 UTC Build ID: 02d18d8e-5aa4-4d62-b424-10092ea446de
There was a bug in show version some rolling releases back. Please update.
Jun 21 2018
Fix applied to current and helium branch (if there will be a 1.1.9 release)
cpo@LR1# set system flow-accounting netflow source-ip 192.168.253.13 [edit] cpo@LR1# show system flow-accounting +netflow { + source-ip 192.168.253.13 +}
Wireguard is only available from Debian unstable (https://www.wireguard.com/install/). @dmbaturin managed to install packages from newer Debian releases IIRC. Maybe he can assist b/c last time I tried, I failed.
This problem exists at least with VyOS 1.2.0-rolling+201806040337 as I've stumbled accross this one, too.
Jun 14 2018
Jun 13 2018
Create/update/delete are all called implicit by the execution of the given Python script.
Jun 12 2018
@Asteroza can you add the approriate Task here in the comments?
Jun 11 2018
Jun 10 2018
By this you mean VyOS should act as TFTP server and provide files to clients?
This would make sense. Some could imagine that there is a P2P linkt between two sites and a WAN IPSec Backup link
Is there a CSR1000v license available or will we stick with the bandwidth limitation?
We should rewrite legacy DDNS first and then could add aws53 as alternative provider that would make sense.
Besides the typo,
Hmm I'm wondering b/c I've seen a provider in germany (HETZNER) where they do NAT (not PAT) for their cloud customers. Every vServer has the same IP configuration with RFC1918 addresses and an outside router does the mapping. Implementing this would break such a szenario if it can't be disabled.
Jun 8 2018
Jun 7 2018
We can't do anything about the truncated encrypted-key b/c it's actually truncated by SNMP itself.
Jun 6 2018
Issue should be fixed starting with vyos-1.2.0-rolling+201806062125-amd64.iso at least it was tested positively when updating from 1.2.0-rolling+201806040337 to 1.2.0-rolling+201806062125
Okay, when not executing the marked part (https://github.com/vyos/vyos-1x/blob/743b16de1aac4c6b579767f28d57bc2156d3acdf/src/conf_mode/snmp.py#L704-L729) reboots work but then we loose transformation from plaintext o encrypted passwords. So the bug is definately here. Will check!
Okay, when rebooting both encrypted keys change, thats a bug in the Python script too ... sorry for the trouble.
Okay, there was definately a problem with the listen address which is fixed now. Waiting for a new ISO and then I try upgrading from old version, too
Thanks @hagbard
Looks like there is no listen address agentaddress unix:/run/snmpd.socket configured and if there is none inside the configuration, we won't listen on all addresses. This is likely the cause. Could you please add for validation a set service snmp listen-address <ipv4> and check if you can now reach the server again?
Could you please paste the content of the following files:
Could you check if the snmpd process is running at all? Please execute ps faux | grep snmp in the commandline.
Jun 5 2018
@Line2 new ISO building right now which converts plaintext-keys to encrypted keys again.
Okay, the encrypted passwords are re-read from /var/lib/snmp/snmpd.conf and set on the CLI. The truncation originats from that file.
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