Nate Sales
Nate Sales
I think communities should be handled via a new configuration directive, i.e. https://github.com/natesales/pathvector/issues/135 What do you think about using both only-announce and prefix-communities for this use case?
Just following up on this, is there a license you would feel comfortable with adding? GPL/MIT/etc?
I had this same issue. @neoneggplant If you need help, I have a patch for it.
I have `xdp/id:32` on ens5np0, which I've dumped with the following commands. I'm not quite sure what I'm looking for here, although map 11 seems to be problematic. ``` #...
Here are my interfaces (index 10 and 11) ``` 10: ens5np0: mtu 1500 xdp/id:32 qdisc mq state UP group default qlen 1000 11: ens5np1: mtu 1500 xdp/id:40 qdisc mq state...
Adding a bpf_printk indicates ifindex 11 the vast majority of the time, although occasionally there's an ifindex 5 (a different interface on the system not XDP enabled, used for management)...
Ah, got it. I've added that check for XDP_ABORTED which resulted in no output so I've added `action` to the trace output which revealed that all messages have an action...
Yes, I'm still getting the XDP_ABORTED actions. Just to make sure I'm logging at the right place, here's the block where I've added the bpf_printk call. ``` memcpy(eth->h_source, fib_params.smac, ETH_ALEN);...
Oops, that makes total sense now :) I'm now getting action 4 (XDP_REDIRECT) `-0 [007] ..s. 63468.817247: 0: iface index: 11, action 4`
Not exclusively - after adding the check for just XDP_ABORTED actions I'm seeing just action 0 lines (as expected).