{
"lldp": {
"interface": [
{
"eth0": {
"via": "LLDP",
"rid": "5",
"age": "0 day, 00:00:16",
"chassis": {
"id": {
"type": "mac",
"value": "3c:61:04:5b:68:c0"
},
"descr": "Juniper Networks, Inc. ex2200-c-12t-2g , version 11.4R7.5 Build date: 2013-03-01 09:18:42 UTC ",
"capability": [
{
"type": "Bridge",
"enabled": true
},
{
"type": "Router",
"enabled": true
}
]
},
"port": {
"id": {
"type": "local",
"value": "521"
},
"descr": "ge-0/0/9.0",
"ttl": "120"
},
"unknown-tlvs": {
"unknown-tlv": {
"oui": "00,90,69",
"subtype": "1",
"len": "12",
"value": "47,50,30,32,31,33,33,36,30,36,39,36"
}
}
}
}
]
}
}- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Nov 17 2021
Nov 16 2021
@daniil Can you provide the output of json format?
New PR was created https://github.com/vyos/vyos-1x/pull/1072
Nevermind, this was added through T3916.
When i remove from /etc/snmp/snmpd.conf ,('::1', '161') in agentaddress it solve the issue....
show system ipv6 disable
show service snmp
community public {
authorization ro
network 11.11.11.0/24
}
contact gg@g.com
listen-address 11.11.11.251 {
port 161
}
location ru-brnNov 16 16:23:27 r1-brn systemd[1]: snmpd.service: Main process exited, code=exited, status=1/FAILURE Nov 16 16:23:27 r1-brn systemd[1]: snmpd.service: Failed with result 'exit-code'.
Nov 15 2021
Nov 15 21:23:22 LR1 systemd[1]: Reloading OpenVPN connection to vtun1. Nov 15 21:23:22 LR1 openvpn-vtun1[13941]: event_wait : Interrupted system call (code=4) Nov 15 21:23:22 LR1 openvpn-vtun1[13941]: Closing TUN/TAP interface Nov 15 21:23:22 LR1 openvpn-vtun1[13941]: net_addr_ptp_v4_del: 10.255.1.1 dev vtun1 Nov 15 21:23:22 LR1 systemd[1]: Reloaded OpenVPN connection to vtun1. Nov 15 21:23:22 LR1 openvpn-vtun1[13941]: SIGHUP[hard,] received, process restarting Nov 15 21:23:22 LR1 openvpn-vtun1[13941]: Cipher negotiation is disabled since neither P2MP client nor server mode is enabled Nov 15 21:23:22 LR1 openvpn-vtun1[13941]: WARNING: file '/run/openvpn/vtun1_shared.key' is group or others accessible Nov 15 21:23:22 LR1 openvpn-vtun1[13941]: OpenVPN 2.5.1 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on May 14 2021 Nov 15 21:23:22 LR1 openvpn-vtun1[13941]: library versions: OpenSSL 1.1.1k 25 Mar 2021, LZO 2.10 Nov 15 21:23:22 LR1 openvpn-vtun1[13941]: Restart pause, 5 second(s)
By the way, mikrotik IPoE format doesn't compatible with VyOS
https://github.com/vyos/vyos-1x/blob/1353757247c027f6352000a9450b502c25c460c8/src/utils/vyos-hostsd-client#L123-L139
entry['address']] expect list
Zebra configuration:
root@r11-roll:/home/vyos# cat foo.txt ! frr version 7.5.1-20210619-12-g3f8a74e70 frr defaults traditional hostname r11-roll log syslog log facility local7 service integrated-vtysh-config ! vrf blue vni 2000 exit-vrf ! vrf red vni 3000 exit-vrf ! line vty ! end
Still reproducible VyOS 1.3-beta-202111150443
After reboot
For 1.4 it was implemented in T645
IPSec was completely rewritten in 1.4
Fixed VyOS 1.3-beta-202111150443
Duplicate T1292
Nov 14 2021
Nov 13 2021
Nov 12 2021
This brings up an interesting issue: validate_value.ml could easily be modified to print warnings, while maintaining T2759 (namely, only print fatal errors if _all_ validators fail for a given setting), however, is this reasonable behaviour ? One would think that a 'validator' is either pass or fail, and if it is just giving a warning, it is no longer a validator.
I will take a look; thanks for the report !
Note, the host was upgraded from 1.2.8
PRs 1069 and 1070 will be merged
Adding set zone-policy zone SERVER interface SERVER to the presented test case should solve the issue. This is because the traffic needs to pass both eth1 and its associated VRF "master" interface, in this case TEST.
From what I understand this looks to be due to https://github.com/vyos/vyos-utils/blob/master/src/validate_value.ml catching both stdout and stderr output from the validators and only printing the captured output if the validator exit status is 0 so there isn't a way to print warnings unless it always prints the output or handling for a special 'warning' exit code was added.
Nov 11 2021
This issue should be fixed after these changes https://phabricator.vyos.net/T1970 (udevadm settle)
Tested on EdgeCore SAF51015I with generic ISOs.
Does not possible to reproduce this behavior on 1.3-epa3.
Certificates can be wound there:
loaded certificate from '/etc/swanctl/x509/R1.pem' loaded certificate from '/etc/swanctl/x509ca/CA.pem' loaded RSA key from '/etc/swanctl/private/x509_R1.pem'