You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Packets captured with the packetcapture service form two completely different timestamp sequences.
To Reproduce
Run the following script:
sudo ip netns del ns1 1>/dev/null 2>&1
sudo ip netns del ns2 1>/dev/null 2>&1
sudo ip link del veth1 1>/dev/null 2>&1
sudo ip link del veth2 1>/dev/null 2>&1
sudo ip netns add ns1
sudo ip link add veth1 type veth peer name veth1_
sudo ip link set veth1_ netns ns1
sudo ip link set veth1 up
sudo ip netns exec ns1 ip addr add 10.0.0.1/24 dev veth1_
sudo ip netns exec ns1 ip link set veth1_ up
sudo ip netns add ns2
sudo ip link add veth2 type veth peer name veth2_
sudo ip link set veth2_ netns ns2
sudo ip link set veth2 up
sudo ip netns exec ns2 ip addr add 10.0.0.2/24 dev veth2_
sudo ip netns exec ns2 ip link set veth2_ up
polycubectl helloworld add hw1
polycubectl hw1 ports add veth1 peer=veth1
polycubectl hw1 ports add veth2 peer=veth2
polycubectl hw1 set action=forward
polycubectl packetcapture add pc1
polycubectl pc1 set capture=bidirectional
polycubectl pc1 set filter="all"
polycubectl attach pc1 hw1:veth1
Generate some packets with ping command and inspect the capture.
Expected behavior
Timestamps should all be in sequence.
Additional context
This is probably related to the fact that some timestamps are retrieved from skb and others with pcn_ktime_get_ns().
The text was updated successfully, but these errors were encountered:
The timestamp in CubeType::XDP_DRV or CubeType::XDP_SKB are all retrieved with pcn_ktime_get_ns()
While in CubeType::TC timestamp are all retrieved with ctx->tstamp , only if ctx->tstamp == 0 the timestamp are retrieved with pcn_ktime_get_ns()
Mmmh I've just tried to replicate the problem again and this time everything is fine...
The other day some of the packets had timestamps completely different from the others but unfortunately I didn't take a screenshot.
I will open a new issue if I experience the problem again, paying more attention to my configuration.
Apologize for wasting you time.
Describe the bug
Packets captured with the packetcapture service form two completely different timestamp sequences.
To Reproduce
Run the following script:
Generate some packets with ping command and inspect the capture.
Expected behavior
Timestamps should all be in sequence.
Additional context
This is probably related to the fact that some timestamps are retrieved from
skb
and others withpcn_ktime_get_ns()
.The text was updated successfully, but these errors were encountered: