Hi Neale,
Thank you for the help. We are trying to exercise vpp mpls vpn and we are
preferring label per prefix only. Anyway I am fine even with per VRF label but
adding more local labels which seems fine while adding.
I am trying to evaluate VRF with non-default ip fib tables.
While I tried
From: vpp-dev@lists.fd.io on behalf of Sastry Sista via
lists.fd.io
Date: Thursday, 2 December 2021 at 13:25
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] MPLS: fib table 1 display issue #mpls
Thank you Neale. We may need to develop something like show mpls bind for our
purpose.
My test
Hi Wei,
I think you need to specify proto=UDP in your ACL setup so that your desired
port is honoured.
You might also want to pass a ‘priority’ to your attachments so they run in a
deterministic order.
/neale
From: Wei Huang
Date: Tuesday, 7 December 2021 at 20:13
To: vpp-dev@lists.fd.io
On my VPP setup, I have two IPSec tunnels can reach 192.168.200.0/24, the
interfaces for those two IPSec tunnels are ipip0 and ipip1.
I try to set up abf to direct UDP packets to 192.168.200.20 based on
destination port. If dport is 5001, use ipip0, if dport is 5002, use ipip1.
All those packets
I found the problem, it's in unformat_l4_match().
On 21.06, it "return 0" for "else", this make it can't take anything after the
"l4 dst_port"
while (unformat_check_input (input) != UNFORMAT_END_OF_INPUT)
{
if (unformat (input, "src_port %d", _port))
;
else if (unformat (input,
I'm on master (note that I just rebased the plugin on master to accommodate
fib_node_register_new_type() change).
Best
ben
> -Original Message-
> From: Wei Huang
> Sent: mardi 7 décembre 2021 14:43
> To: vpp-dev@lists.fd.io; Benoit Ganne (bganne)
> Subject: Re: [vpp-dev] Use classify
Tried same, still have problem. What version are you using?
vpp# loop create-interface
loop0
vpp# classify table mask l3 ip4 dst l4 dst_port
vpp# ip session redirect table 0 match l3 ip4 dst 192.168.21.2 l4 dst_port 2156
via loop0
ip session redirect: parse error `l4 dst_port 2156 via loop0'
Hi All,
We are trying to ping the ipv4 neighbor via MPLS path. We are seeing
packets drop when we send ping packets with size more than 1468 bytes.
Also note that the same ping works via plain IPv4 path with fragmentation.
Please find the test log as below:
VPP version used*: 20.09*
DBGvpp#
Hi,
> vpp# classify table mask l3 ip4 dst l4 dst_port
> vpp# ip session redirect table 0 match l3 ip4 dst 192.168.21.2 l4 dst_port
> 2156 via ipip0
> ip session redirect: parse error `l4 dst_port 2156 via ipip0'
Not sure what is wrong, this works for me:
DBGvpp# loop create-interface
loop0
Hi Team - Can you kindly update on this. Awaiting response.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20590): https://lists.fd.io/g/vpp-dev/message/20590
Mute This Topic: https://lists.fd.io/mt/87534283/21656
Mute
[Edited Message Follows]
Hi Team,
It has been observed that for a single tx packet, the "tx packets" counter at
the loop interface is exactly double of the "tx packets" at the sub-interface
level. In code, the interface counter gets incremented in "interface_output"
node as expected. But it is
11 matches
Mail list logo
