@jack9603301 Do you know of a version of that FRR exporter that doesn't fork sub processes?
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Oct 18 2020
What information do you need access to from within op-mode?
I hope to implement an operation mode command, but too many interface parameters are generated according to the configuration in the interface. I don't know how to call these existing configurations. Can I call the user's configuration information through config in operation mode?
It seems that we need to think about it now
You can pull the host configuration in operation mode using the following command:
generate tinc tincN host-conf <user@service:/path>
I hope to implement an operation mode command, but too many interface parameters are generated according to the configuration in the interface. I don't know how to call these existing configurations. Can I call the user's configuration information through config in operation mode?
Note: my test found that when the server is in switch mode, the client cannot Ping to the peer in routing mode (more tests may be needed)
To prevent forgetting, write the address of the exporter to task
The root cause of this problem is that OpenVPN when the deamon is started and in tries to connect to the server, yet did not create the vtun11 interface on the system. Thus all calls to the ifconfig python library will fail big time.
I updated pr. so far, tinc VPN cli will automatically generate the local node key file, such as the following code:
Isn't anyone implementing this feature right now?
Oct 17 2020
My last comment was wrong, here are the outputs for bridge fdb show dev vxlan122:
I can't reproduce it with VyOS 1.3-rolling-202010170146 and other october releases
source-interface cannot be used as the routers are not in the same multicast group, neither can communicate via multicast
In T2987#77730, @Viacheslav wrote:@tom.siewert
What will be if you delete the source-address on "October" node?
@tom.siewert
What will be if you delete the source-address on "October" node?
We should avoid having a constellation of exporters, but favour having a single one. I feel like starting and stopping those would be pretty icky.
Must this command be executed from docker now?
This will break builds in out Docker environment where we ship a packer version. See T2792 and https://github.com/vyos/vyos-build/commit/e2dd9db8a2539b6d13c98d89e18872336cf8f974
Also very interested in this. Ready and willing to test.
@Cheeze_It thanks, works fine.
Oct 16 2020
That would be a workaround only - see IPv6 syntax above. Using the refactored interface handling (T2653) makes this a low-hanging fruit.
I'll be giving those a test once T2981 is done. I'll report back here with results :)
PR is added here...
Quite interesting, support, in fact some information can not be captured from SNMP very well
How about this?
@D0peX That's correct? I updated pr
Thank you Viacheslav
@c-po @dmbaturin It can be safely cherry-picked to the "crux".
I tested this on 1.2.6-s1, it works.
@trae32566 Will be added in the next rolling release.
Check, please.
The possible reason, that it can't get the lease file, because that directory not present in the LiveCD
lease_file = "/config/dhcpd.leases"
That sounds great to me! I actually like that more.
Proposed cli
One of them
It was fixed in the rolling T2573
https://phabricator.vyos.net/rVYOSONEXf812c5d1ce01efa8323bfb797c57f68f474665bb
Oct 15 2020
@Robot82
It will be by default in the new BGP implementation.
https://github.com/vyos/vyos-1x/blob/current/data/templates/frr/bgp.frr.tmpl#L5
Proposed CLI
reset mpls ldp neighbor x.x.x.x