Need some dumps to see what sent/received

In general I like the idea.

@Line2 I tested a RHEL7 (currently at work) and a debian 9. I can only imagine that their either used the patch you mentioned, or do it a similar way like observium does it with their perl script. it looks like the patch never made it into upstream in net-snmp, I haven't checked the source yet.

@hagbard :
Sorry for the misunderstanding. I checked on an old openSUSE box. but after that the SNMP OID was still empty.
On latest VyOS rolling release I get with 'cat /sys/class/net/eth0/ifalias' the description from 'set interfaces ethernet eth0 description TEST'.
I also saw on EdgeOS (Ubiquiti) the OID is working, I get the interface descriptions. Maybe that helps.

The only thing I can think about is, to read ifAlias from /sys and insert it into the snmp table. @c-po what do you think about this?

Did you do that on vyos? I tried and it doesn't work. That alias is usually set under /sys/class/net/<device>/ifalias, but the ip command didn't do it, nor was I successful setting it manually.

I just set alias on another linux system 'ip link set dev eth0 alias TEST', now I can see the alias with 'ip link show eth0', but nothing in the SNMP OID. Here an old discussion in net-snmp project:
https://sourceforge.net/p/net-snmp/feature-requests/185/

I see, yes .1.3.6.1.2.1.31.1.1.1.18 is empty and would have to be updated/set when the interface description is set. I believe it is not set in any Linux distribution, I also checked RHEL and the such, they leave it all empty. So, I would think it's a feature request than, rather than a bug, isn't it?

@robinelfrink I'm sorry but I deleted the task for open-vmdk. I fixed it.

OID .1.3.6.1.2.1.2.2.1.2 is interface description, here we see content like 'eth0', 'eth1'.
For interface alias it's OID .1.3.6.1.2.1.31.1.1.1.18 from SNMP table ifXTable, this one is empty in VyOS 1.2.0-rolling+201806251824.

"Intel Corporation 82540EM Gigabit Ethernet Controller" is not that description that you configure with following cli command:

@hagbard set it to you and will be checking permissions because normally you should be able to claim it

possibly affected:
./interfaces/bonding/node.tag/pppoe/node.tag/user-id
./interfaces/bonding/node.tag/vif/node.tag/pppoe/node.tag/user-id
./interfaces/ethernet/node.tag/pppoe/node.tag/user-id
./interfaces/ethernet/node.tag/vif/node.tag/pppoe/node.tag/user-id
./interfaces/openvpn/node.tag/authentication/username
./service/pppoe-server/authentication/local-users/username
./service/snmp/v3/trap-target/node.tag/user
./service/snmp/v3/user
./service/ssh/access-control/allow/user
./service/ssh/access-control/deny/user
./service/webproxy/authentication/ldap/username-attribute
./service/webproxy/url-filtering/squidguard/source-group/node.tag/user
./system/login/user
./system/package/repository/node.tag/username
./system/syslog/user
./vpn/l2tp/remote-access/authentication/local-users/username
./vpn/pptp/remote-access/authentication/local-users/username

does only affect username in pptp and l2tp.

Validated OID 1.3.6.1.2.1.2.2.1.2 (ifDescr), I think the task here can be closed as invalid request.

Are you sure?

Big fan of HTop here :)
@dmbaturin do we have iftop like thing somewhere already? (to see traffic usage)

@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.

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.

in vyos-1x:

Other vendors put in restrictions for that (cisco for instance allows only alpha numerical characters), that could be done in the xml with a regex to prevent the issue you have raised. I only had a look into the snmp configuration for now, but I expect that on many other places too.
Any objections about restricting the input?

c-po, thank you for the response. I did get it working, with the following comments:

The pull request was merged.

maybe you could assist us by trying the following steps on your system:

in my latest PR i've also added a rewrite of "show host *" in show-host.xml. this rewrite does not need any wrapper scripts.

@dmbaturin ahh, my fault.

@runar Found an issue: show-raid.xml refers to ${vyos_op_scripts_dir}/show_raid.sh file, but that file does not exist.

Yes, it's been fixed a while ago.

There was a bug in show version some rolling releases back. Please update.

I just tested on VyOS 1.2.0-rolling+201806220337 and 'show version' works here. Can you maybe update?

We got 0 replies from zerotier folks so it looks like they not really interesting in collaboration
therefore we will not be adding support for zerotier into VyOS

Sorry, I'm still not able to reproduce your issue. I used the same config you posted, just changed the IPs and used 19,20 and the rolling from today, everything looks just good.
When you have the issue what is the output of ' sh interfaces detail | match br'.

Fix applied to current and helium branch (if there will be a 1.1.9 release)

Little more testing..

relevant parts below. The interfaces seem to be added to the bridge, but the bridge interface is not assigned an ip address.