- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Mar 5 2024
For 1.5 fix works as expected
vyos@r4:~$ cat /run/opennhrp/opennhrp.conf # Created by VyOS - manual changes will be overwritten
works with version 1.5-rolling-202403050022
Mar 4 2024
Should be fixed in the next rolling release.
Can you recheck it after 20240304 ?
PR created: https://github.com/vyos/vyos-1x/pull/3085
Duplicated: https://vyos.dev/T6061
@paigeadelethompson it is another issue, open a separate bug report
table inet vrf_zones {
map ct_iface_map {
typeof iifname : ct zone
elements = { "HE" : 132,
"WAN" : 128,
"eth0" : 128,
"tun0" : 132,
"eth1" : 256,
"eth2" : 384,
"veth0" : 132,
"veth1" : 256,
"VMNET" : 256,
"FASTNETMON" : 384 }
}Mar 3 2024
Do you refer to initially admin-down or oper-down?
Mar 2 2024
Reviewing the logs
When the interface "xfrmi-test-...." appears, opennhrp stops
Using the same router/config I noted previously, I see an "empty" config per T6084.
admin@removed# cat /run/opennhrp/opennhrp.conf # Created by VyOS - manual changes will be overwritten
I then modified the nhrp vyos config and saved, and the opennhrp.conf was re-populated. Upon reboot, the file reverted to "empty".
If I comment out this line then everything works.
Check opennhrp.conf file
Could be bug if the ispec in the config T6084
@fernando I think you mixed up ospf vs ospfv3.
Still broken in 1.4.0-epa1 (self-built).
Mar 1 2024
If the peer reconnects after the first disconnect - does the local VTI interface go "UP" again?
PR https://github.com/vyos/vyos-1x/pull/2157 closed due to long standing conflicting files.
Feb 29 2024
I don't know what testing you might want to do, but for me it now works as expected.
That commit has the side effect that using sudo or even just committing some configurations will return "sudo: unable to resolve host vyos: System error" every time. Applications that rely on the system hostname will also not be able to reach localhost if the hostname is not a FQDN.