- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Apr 2 2023
Apr 1 2023
The packet-drop events are not really samples in the same way as the packets are random-samples and the counters are time-samples. Even if there is only 1 dropped packet it will be sent. So it might be better to change the wording from “Samples drop events sent” to something like “Packet drop events sent” or just “Packet drops sent”. Make sense?
Apologies. I believe it is corrected now.
PR for VyOS 1.3 https://github.com/vyos/vyos-1x/pull/1928
In T5125#146162, @neilmckee wrote:I think there should be one more metric - the number of packet-drop-events sent. I just checked in a change that adds to the example telemetry.py script:
https://github.com/sflow/host-sflow/commit/5b01779abf21a7553e07188ff2f54850c568f786But we should also expose the number of drops that were suppressed by the mod_dropmon rate limit. I'll check in 2.0.50-4 later today to add that option too.
when I enter 'show dns dynamic status' it gives me 'no connect' result for the hosts
In T2819#145957, @indrajitr wrote:Should we revive this consideration again? See https://github.com/ddclient/ddclient/issues/528.
They did have a recent release, but things continue to be unpredictable. So we'll either have to have a different tool (and rewrite the configs) or have to maintain a fork. I see that there used to be a VyOS-maintained fork in the past.
Mar 31 2023
I think there should be one more metric - the number of packet-drop-events sent. I just checked in a change that adds to the example telemetry.py script:
https://github.com/sflow/host-sflow/commit/5b01779abf21a7553e07188ff2f54850c568f786
@fernando Can you see them now? I attached them to the main post.
merge done, it fixed the issues :
Running '1.4-rolling-202303270317' i'm experiencing the opposite behaviour. A VRRP health-check script in a VRRP group that is a member of a VRRP sync group stops working (VRRP group immediately transitions to 'FAULT' state upon start of keepalived). If i take out the 'track_script' block in the produced '/run/keepalived/keepalived.conf' and restart keepalived (sudo systemctl restart keepalived) the health-check script functions as expected again. Any pointers ? Or shall I create a new issue containing the appropriate details ?
sorry , but it seems files doesn't share .
PR https://github.com/vyos/vyos-1x/pull/1927
Formatted output:
vyos@r14:~$ show sflow -------------------------- ----------------------------------- Agent address 192.168.122.14 sFlow interfaces ['eth0', 'eth1'] sFlow servers ['192.168.122.1', '192.168.122.11'] Datagrams sent 306 Packet samples sent 18 Packet samples dropped 0 Counter samples sent 917 Flow samples suppressed 0 Counter samples suppressed 0 -------------------------- ----------------------------------- vyos@r14:~$
Raw output:
vyos@r14:~$ sudo /usr/libexec/vyos/op_mode/sflow.py show --raw
{
"agent_address": "192.168.122.14",
"sflow_interfaces": [
"eth0",
"eth1"
],
"sflow_servers": [
"192.168.122.1",
"192.168.122.11"
],
"counter_samples_sent": 1077,
"datagrams_sent": 359,
"packet_samples_dropped": 0,
"packet_samples_sent": 19,
"rtmetric_samples": 0,
"flow_samples_suppressed": 0,
"counter_samples_suppressed": 0,
"hsflowd_version": "2.0.50"
}
vyos@r14:~$PR for VyOS 1.3 https://github.com/vyos/vyos-build/pull/330
Building from source always results in:
10.0.0.0/24 is a connected network.
Mar 30 2023
Yet about the before comment, when I make a flush in the NFT without maintain the empty structure this error occurs:
Bellow, there are some procedures that I used to unload the conntrack module in my environment.
confirm, it's working :