Re: [vpp-dev] PPPoE plugin documentation/support
OK, thank you. Please let me know when the patch is available. -Original Message- From: Ni, Hongjun [mailto:hongjun...@intel.com] Sent: Monday, November 12, 2018 9:36 AM To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io Subject: RE: [vpp-dev] PPPoE plugin documentation/support Hi Alp Arslan, Since PPPoE control packet is special, which destination MAC is the PPPoE client's MAC. Need to submit a patch to identify it and not perform L3 MAC filter in ethernet-input-inline() function. Thanks, Hongjun -Original Message- From: alp.ars...@xflowresearch.com [mailto:alp.ars...@xflowresearch.com] Sent: Friday, November 9, 2018 4:04 PM To: Ni, Hongjun ; vpp-dev@lists.fd.io Subject: RE: [vpp-dev] PPPoE plugin documentation/support Yes, that seems to be the problem. The control plane interface is dropping the replies with error "L3 MAC MISMATCH". How do I set the interface to l2? Using the command " set interface l2 bridge 1" is not working, as it starts to drop the PADI packets also. After using the above mentioned command: Packet 1 01:11:18:827637: vhost-user-input VirtualEthernet0/0/0 queue 0 virtio flags: INDIRECT Indirect descriptor virtio_net_hdr first_desc_len 12 flags 0x00 gso_type 0 num_buff 0 01:11:18:827641: ethernet-input PPPOE_DISCOVERY: 52:54:00:cc:3a:0e -> ff:ff:ff:ff:ff:ff 01:11:18:827643: l2-input l2-input: sw_if_index 3 dst ff:ff:ff:ff:ff:ff src 52:54:00:cc:3a:0e 01:11:18:827644: l2-learn l2-learn: sw_if_index 3 dst ff:ff:ff:ff:ff:ff src 52:54:00:cc:3a:0e bd_index 1 01:11:18:827646: error-drop l2-flood: L2 replication complete Regards, Alp Arslan -Original Message- From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Ni, Hongjun Sent: Thursday, November 8, 2018 5:18 PM To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] PPPoE plugin documentation/support Hi alp arslan, It works in my server. Below is my configuration: vpp# set int state TenGigabitEthernet5/0/0 up vpp# set int ip table TenGigabitEthernet5/0/0 0 vpp# set int ip address TenGigabitEthernet5/0/0 100.1.1.3/32 vpp# vpp# set int state TenGigabitEthernet5/0/1 up vpp# set int ip table TenGigabitEthernet5/0/1 0 vpp# set int ip address TenGigabitEthernet5/0/1 100.1.1.200/32 vpp# ip route add 100.1.1.100/24 via 100.1.1.4 TenGigabitEthernet5/0/1 vpp# set ip arp TenGigabitEthernet5/0/1 100.1.1.100 ..0001 vpp# vpp# create pppoe cp cp-if-index 2 vpp# vpp# trace add dpdk-input 10 //Then you sent PADI packet: vpp# vpp# sh trace --- Start of thread 0 vpp_main --- Packet 1 00:00:49:834924: dpdk-input TenGigabitEthernet5/0/0 rx queue 0 buffer 0xa4e03: current data 0, length 60, free-list 0, clone-count 0, totlen-nifb 0, trace 0x0 ext-hdr-valid l4-cksum-computed l4-cksum-correct l2-hdr-offset 0 PKT MBUF: port 0, nb_segs 1, pkt_len 60 buf_len 2176, data_len 60, ol_flags 0x180, data_off 128, phys_addr 0x6dd38140 packet_type 0x1 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0 rss 0x0 fdir.hi 0x0 fdir.lo 0x0 Packet Offload Flags PKT_RX_IP_CKSUM_GOOD (0x0080) IP cksum of RX pkt. is valid PKT_RX_L4_CKSUM_GOOD (0x0100) L4 cksum of RX pkt. is valid Packet Types RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet PPPOE_DISCOVERY: 00:11:01:00:00:01 -> ff:ff:ff:ff:ff:ff 00:00:49:834959: ethernet-input PPPOE_DISCOVERY: 00:11:01:00:00:01 -> ff:ff:ff:ff:ff:ff 00:00:49:834978: pppoe-cp-dispatch PPPoE dispatch from sw_if_index -1 next 1 error 0 pppoe_code 0x9 ppp_proto 0x101 00:00:49:835469: TenGigabitEthernet5/0/1-output TenGigabitEthernet5/0/1 PPPOE_DISCOVERY: 00:11:01:00:00:01 -> ff:ff:ff:ff:ff:ff 00:00:49:835473: TenGigabitEthernet5/0/1-tx TenGigabitEthernet5/0/1 tx queue 0 buffer 0xa4e03: current data 0, length 60, free-list 0, clone-count 0, totlen-nifb 0, trace 0x0 ext-hdr-valid l4-cksum-computed l4-cksum-correct l2-hdr-offset 0 l3-hdr-offset 14 PKT MBUF: port 0, nb_segs 1, pkt_len 60 buf_len 2176, data_len 60, ol_flags 0x180, data_off 128, phys_addr 0x6dd38140 packet_type 0x1 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0 rss 0x0 fdir.hi 0x0 fdir.lo 0x0 Packet Offload Flags PKT_RX_IP_CKSUM_GOOD (0x0080) IP cksum of RX pkt. is valid PKT_RX_L4_CKSUM_GOOD (0x0100) L4 cksum of RX pkt. is valid Packet Types RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet PPPOE_DISCOVERY: 00:11:01:00:00:01 -> ff:ff:ff:ff:ff:ff vpp# vpp# vpp# sh pppoe session No pppoe sessions configured... vpp# vpp# sh pppoe fib no pppoe fib entries vpp# vpp# //Then you need to configure pppoe session: vpp# create pppoe session client-ip 100.1.1.2 session-id 1 client-mac 00:11:01:00:00:01 pppoe_session0 vpp# sh pppoe fib Mac-Address session_id sw_if_index session_index 00:11:01:00:00:01 1 1 0 1 p
Re: [vpp-dev] PPPoE plugin documentation/support
Hi Alp Arslan, Since PPPoE control packet is special, which destination MAC is the PPPoE client's MAC. Need to submit a patch to identify it and not perform L3 MAC filter in ethernet-input-inline() function. Thanks, Hongjun -Original Message- From: alp.ars...@xflowresearch.com [mailto:alp.ars...@xflowresearch.com] Sent: Friday, November 9, 2018 4:04 PM To: Ni, Hongjun ; vpp-dev@lists.fd.io Subject: RE: [vpp-dev] PPPoE plugin documentation/support Yes, that seems to be the problem. The control plane interface is dropping the replies with error "L3 MAC MISMATCH". How do I set the interface to l2? Using the command " set interface l2 bridge 1" is not working, as it starts to drop the PADI packets also. After using the above mentioned command: Packet 1 01:11:18:827637: vhost-user-input VirtualEthernet0/0/0 queue 0 virtio flags: INDIRECT Indirect descriptor virtio_net_hdr first_desc_len 12 flags 0x00 gso_type 0 num_buff 0 01:11:18:827641: ethernet-input PPPOE_DISCOVERY: 52:54:00:cc:3a:0e -> ff:ff:ff:ff:ff:ff 01:11:18:827643: l2-input l2-input: sw_if_index 3 dst ff:ff:ff:ff:ff:ff src 52:54:00:cc:3a:0e 01:11:18:827644: l2-learn l2-learn: sw_if_index 3 dst ff:ff:ff:ff:ff:ff src 52:54:00:cc:3a:0e bd_index 1 01:11:18:827646: error-drop l2-flood: L2 replication complete Regards, Alp Arslan -Original Message- From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Ni, Hongjun Sent: Thursday, November 8, 2018 5:18 PM To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] PPPoE plugin documentation/support Hi alp arslan, It works in my server. Below is my configuration: vpp# set int state TenGigabitEthernet5/0/0 up vpp# set int ip table TenGigabitEthernet5/0/0 0 vpp# set int ip address TenGigabitEthernet5/0/0 100.1.1.3/32 vpp# vpp# set int state TenGigabitEthernet5/0/1 up vpp# set int ip table TenGigabitEthernet5/0/1 0 vpp# set int ip address TenGigabitEthernet5/0/1 100.1.1.200/32 vpp# ip route add 100.1.1.100/24 via 100.1.1.4 TenGigabitEthernet5/0/1 vpp# set ip arp TenGigabitEthernet5/0/1 100.1.1.100 ..0001 vpp# vpp# create pppoe cp cp-if-index 2 vpp# vpp# trace add dpdk-input 10 //Then you sent PADI packet: vpp# vpp# sh trace --- Start of thread 0 vpp_main --- Packet 1 00:00:49:834924: dpdk-input TenGigabitEthernet5/0/0 rx queue 0 buffer 0xa4e03: current data 0, length 60, free-list 0, clone-count 0, totlen-nifb 0, trace 0x0 ext-hdr-valid l4-cksum-computed l4-cksum-correct l2-hdr-offset 0 PKT MBUF: port 0, nb_segs 1, pkt_len 60 buf_len 2176, data_len 60, ol_flags 0x180, data_off 128, phys_addr 0x6dd38140 packet_type 0x1 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0 rss 0x0 fdir.hi 0x0 fdir.lo 0x0 Packet Offload Flags PKT_RX_IP_CKSUM_GOOD (0x0080) IP cksum of RX pkt. is valid PKT_RX_L4_CKSUM_GOOD (0x0100) L4 cksum of RX pkt. is valid Packet Types RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet PPPOE_DISCOVERY: 00:11:01:00:00:01 -> ff:ff:ff:ff:ff:ff 00:00:49:834959: ethernet-input PPPOE_DISCOVERY: 00:11:01:00:00:01 -> ff:ff:ff:ff:ff:ff 00:00:49:834978: pppoe-cp-dispatch PPPoE dispatch from sw_if_index -1 next 1 error 0 pppoe_code 0x9 ppp_proto 0x101 00:00:49:835469: TenGigabitEthernet5/0/1-output TenGigabitEthernet5/0/1 PPPOE_DISCOVERY: 00:11:01:00:00:01 -> ff:ff:ff:ff:ff:ff 00:00:49:835473: TenGigabitEthernet5/0/1-tx TenGigabitEthernet5/0/1 tx queue 0 buffer 0xa4e03: current data 0, length 60, free-list 0, clone-count 0, totlen-nifb 0, trace 0x0 ext-hdr-valid l4-cksum-computed l4-cksum-correct l2-hdr-offset 0 l3-hdr-offset 14 PKT MBUF: port 0, nb_segs 1, pkt_len 60 buf_len 2176, data_len 60, ol_flags 0x180, data_off 128, phys_addr 0x6dd38140 packet_type 0x1 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0 rss 0x0 fdir.hi 0x0 fdir.lo 0x0 Packet Offload Flags PKT_RX_IP_CKSUM_GOOD (0x0080) IP cksum of RX pkt. is valid PKT_RX_L4_CKSUM_GOOD (0x0100) L4 cksum of RX pkt. is valid Packet Types RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet PPPOE_DISCOVERY: 00:11:01:00:00:01 -> ff:ff:ff:ff:ff:ff vpp# vpp# vpp# sh pppoe session No pppoe sessions configured... vpp# vpp# sh pppoe fib no pppoe fib entries vpp# vpp# //Then you need to configure pppoe session: vpp# create pppoe session client-ip 100.1.1.2 session-id 1 client-mac 00:11:01:00:00:01 pppoe_session0 vpp# sh pppoe fib Mac-Address session_id sw_if_index session_index 00:11:01:00:00:01 1 1 0 1 pppoe fib entries vpp# vpp# sh pppoe session [0] sw-if-index 3 client-ip 100.1.1.2 session-id 1 encap-if-index 1 decap-fib-index 0 local-mac 90:e2:ba:48:7a:80 client-mac 00:11:01:00:00:01 //For l3 mac mismatch, maybe you need to set your control interface to l2 mode. Thanks, Hongju
Re: [vpp-dev] PPPoE plugin documentation/support
Yes, that seems to be the problem. The control plane interface is dropping the replies with error "L3 MAC MISMATCH". How do I set the interface to l2? Using the command " set interface l2 bridge 1" is not working, as it starts to drop the PADI packets also. After using the above mentioned command: Packet 1 01:11:18:827637: vhost-user-input VirtualEthernet0/0/0 queue 0 virtio flags: INDIRECT Indirect descriptor virtio_net_hdr first_desc_len 12 flags 0x00 gso_type 0 num_buff 0 01:11:18:827641: ethernet-input PPPOE_DISCOVERY: 52:54:00:cc:3a:0e -> ff:ff:ff:ff:ff:ff 01:11:18:827643: l2-input l2-input: sw_if_index 3 dst ff:ff:ff:ff:ff:ff src 52:54:00:cc:3a:0e 01:11:18:827644: l2-learn l2-learn: sw_if_index 3 dst ff:ff:ff:ff:ff:ff src 52:54:00:cc:3a:0e bd_index 1 01:11:18:827646: error-drop l2-flood: L2 replication complete Regards, Alp Arslan -Original Message- From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Ni, Hongjun Sent: Thursday, November 8, 2018 5:18 PM To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] PPPoE plugin documentation/support Hi alp arslan, It works in my server. Below is my configuration: vpp# set int state TenGigabitEthernet5/0/0 up vpp# set int ip table TenGigabitEthernet5/0/0 0 vpp# set int ip address TenGigabitEthernet5/0/0 100.1.1.3/32 vpp# vpp# set int state TenGigabitEthernet5/0/1 up vpp# set int ip table TenGigabitEthernet5/0/1 0 vpp# set int ip address TenGigabitEthernet5/0/1 100.1.1.200/32 vpp# ip route add 100.1.1.100/24 via 100.1.1.4 TenGigabitEthernet5/0/1 vpp# set ip arp TenGigabitEthernet5/0/1 100.1.1.100 ..0001 vpp# vpp# create pppoe cp cp-if-index 2 vpp# vpp# trace add dpdk-input 10 //Then you sent PADI packet: vpp# vpp# sh trace --- Start of thread 0 vpp_main --- Packet 1 00:00:49:834924: dpdk-input TenGigabitEthernet5/0/0 rx queue 0 buffer 0xa4e03: current data 0, length 60, free-list 0, clone-count 0, totlen-nifb 0, trace 0x0 ext-hdr-valid l4-cksum-computed l4-cksum-correct l2-hdr-offset 0 PKT MBUF: port 0, nb_segs 1, pkt_len 60 buf_len 2176, data_len 60, ol_flags 0x180, data_off 128, phys_addr 0x6dd38140 packet_type 0x1 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0 rss 0x0 fdir.hi 0x0 fdir.lo 0x0 Packet Offload Flags PKT_RX_IP_CKSUM_GOOD (0x0080) IP cksum of RX pkt. is valid PKT_RX_L4_CKSUM_GOOD (0x0100) L4 cksum of RX pkt. is valid Packet Types RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet PPPOE_DISCOVERY: 00:11:01:00:00:01 -> ff:ff:ff:ff:ff:ff 00:00:49:834959: ethernet-input PPPOE_DISCOVERY: 00:11:01:00:00:01 -> ff:ff:ff:ff:ff:ff 00:00:49:834978: pppoe-cp-dispatch PPPoE dispatch from sw_if_index -1 next 1 error 0 pppoe_code 0x9 ppp_proto 0x101 00:00:49:835469: TenGigabitEthernet5/0/1-output TenGigabitEthernet5/0/1 PPPOE_DISCOVERY: 00:11:01:00:00:01 -> ff:ff:ff:ff:ff:ff 00:00:49:835473: TenGigabitEthernet5/0/1-tx TenGigabitEthernet5/0/1 tx queue 0 buffer 0xa4e03: current data 0, length 60, free-list 0, clone-count 0, totlen-nifb 0, trace 0x0 ext-hdr-valid l4-cksum-computed l4-cksum-correct l2-hdr-offset 0 l3-hdr-offset 14 PKT MBUF: port 0, nb_segs 1, pkt_len 60 buf_len 2176, data_len 60, ol_flags 0x180, data_off 128, phys_addr 0x6dd38140 packet_type 0x1 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0 rss 0x0 fdir.hi 0x0 fdir.lo 0x0 Packet Offload Flags PKT_RX_IP_CKSUM_GOOD (0x0080) IP cksum of RX pkt. is valid PKT_RX_L4_CKSUM_GOOD (0x0100) L4 cksum of RX pkt. is valid Packet Types RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet PPPOE_DISCOVERY: 00:11:01:00:00:01 -> ff:ff:ff:ff:ff:ff vpp# vpp# vpp# sh pppoe session No pppoe sessions configured... vpp# vpp# sh pppoe fib no pppoe fib entries vpp# vpp# //Then you need to configure pppoe session: vpp# create pppoe session client-ip 100.1.1.2 session-id 1 client-mac 00:11:01:00:00:01 pppoe_session0 vpp# sh pppoe fib Mac-Address session_id sw_if_index session_index 00:11:01:00:00:01 1 1 0 1 pppoe fib entries vpp# vpp# sh pppoe session [0] sw-if-index 3 client-ip 100.1.1.2 session-id 1 encap-if-index 1 decap-fib-index 0 local-mac 90:e2:ba:48:7a:80 client-mac 00:11:01:00:00:01 //For l3 mac mismatch, maybe you need to set your control interface to l2 mode. Thanks, Hongjun -Original Message- From: alp.ars...@xflowresearch.com [mailto:alp.ars...@xflowresearch.com] Sent: Thursday, November 8, 2018 6:38 PM To: Ni, Hongjun ; vpp-dev@lists.fd.io Subject: RE: [vpp-dev] PPPoE plugin documentation/support Still waiting on this. Can anyone help me on this one? -Original Message- From: Muhammad Alp Arslan (alp.ars...@xflowresearch.com) [mailto:alp.ars...@xflowresearch.com] Sent: Friday, November 2, 2018 4:07 PM To: 'Ni, Hong
Re: [vpp-dev] PPPoE plugin documentation/support
Hi alp arslan, It works in my server. Below is my configuration: vpp# set int state TenGigabitEthernet5/0/0 up vpp# set int ip table TenGigabitEthernet5/0/0 0 vpp# set int ip address TenGigabitEthernet5/0/0 100.1.1.3/32 vpp# vpp# set int state TenGigabitEthernet5/0/1 up vpp# set int ip table TenGigabitEthernet5/0/1 0 vpp# set int ip address TenGigabitEthernet5/0/1 100.1.1.200/32 vpp# ip route add 100.1.1.100/24 via 100.1.1.4 TenGigabitEthernet5/0/1 vpp# set ip arp TenGigabitEthernet5/0/1 100.1.1.100 ..0001 vpp# vpp# create pppoe cp cp-if-index 2 vpp# vpp# trace add dpdk-input 10 //Then you sent PADI packet: vpp# vpp# sh trace --- Start of thread 0 vpp_main --- Packet 1 00:00:49:834924: dpdk-input TenGigabitEthernet5/0/0 rx queue 0 buffer 0xa4e03: current data 0, length 60, free-list 0, clone-count 0, totlen-nifb 0, trace 0x0 ext-hdr-valid l4-cksum-computed l4-cksum-correct l2-hdr-offset 0 PKT MBUF: port 0, nb_segs 1, pkt_len 60 buf_len 2176, data_len 60, ol_flags 0x180, data_off 128, phys_addr 0x6dd38140 packet_type 0x1 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0 rss 0x0 fdir.hi 0x0 fdir.lo 0x0 Packet Offload Flags PKT_RX_IP_CKSUM_GOOD (0x0080) IP cksum of RX pkt. is valid PKT_RX_L4_CKSUM_GOOD (0x0100) L4 cksum of RX pkt. is valid Packet Types RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet PPPOE_DISCOVERY: 00:11:01:00:00:01 -> ff:ff:ff:ff:ff:ff 00:00:49:834959: ethernet-input PPPOE_DISCOVERY: 00:11:01:00:00:01 -> ff:ff:ff:ff:ff:ff 00:00:49:834978: pppoe-cp-dispatch PPPoE dispatch from sw_if_index -1 next 1 error 0 pppoe_code 0x9 ppp_proto 0x101 00:00:49:835469: TenGigabitEthernet5/0/1-output TenGigabitEthernet5/0/1 PPPOE_DISCOVERY: 00:11:01:00:00:01 -> ff:ff:ff:ff:ff:ff 00:00:49:835473: TenGigabitEthernet5/0/1-tx TenGigabitEthernet5/0/1 tx queue 0 buffer 0xa4e03: current data 0, length 60, free-list 0, clone-count 0, totlen-nifb 0, trace 0x0 ext-hdr-valid l4-cksum-computed l4-cksum-correct l2-hdr-offset 0 l3-hdr-offset 14 PKT MBUF: port 0, nb_segs 1, pkt_len 60 buf_len 2176, data_len 60, ol_flags 0x180, data_off 128, phys_addr 0x6dd38140 packet_type 0x1 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0 rss 0x0 fdir.hi 0x0 fdir.lo 0x0 Packet Offload Flags PKT_RX_IP_CKSUM_GOOD (0x0080) IP cksum of RX pkt. is valid PKT_RX_L4_CKSUM_GOOD (0x0100) L4 cksum of RX pkt. is valid Packet Types RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet PPPOE_DISCOVERY: 00:11:01:00:00:01 -> ff:ff:ff:ff:ff:ff vpp# vpp# vpp# sh pppoe session No pppoe sessions configured... vpp# vpp# sh pppoe fib no pppoe fib entries vpp# vpp# //Then you need to configure pppoe session: vpp# create pppoe session client-ip 100.1.1.2 session-id 1 client-mac 00:11:01:00:00:01 pppoe_session0 vpp# sh pppoe fib Mac-Address session_id sw_if_index session_index 00:11:01:00:00:01 1 1 0 1 pppoe fib entries vpp# vpp# sh pppoe session [0] sw-if-index 3 client-ip 100.1.1.2 session-id 1 encap-if-index 1 decap-fib-index 0 local-mac 90:e2:ba:48:7a:80 client-mac 00:11:01:00:00:01 //For l3 mac mismatch, maybe you need to set your control interface to l2 mode. Thanks, Hongjun -Original Message- From: alp.ars...@xflowresearch.com [mailto:alp.ars...@xflowresearch.com] Sent: Thursday, November 8, 2018 6:38 PM To: Ni, Hongjun ; vpp-dev@lists.fd.io Subject: RE: [vpp-dev] PPPoE plugin documentation/support Still waiting on this. Can anyone help me on this one? -Original Message- From: Muhammad Alp Arslan (alp.ars...@xflowresearch.com) [mailto:alp.ars...@xflowresearch.com] Sent: Friday, November 2, 2018 4:07 PM To: 'Ni, Hongjun'; 'vpp-dev@lists.fd.io' Subject: RE: [vpp-dev] PPPoE plugin documentation/support Hello, I want to use the latest VPP, instead of 17.10. The latest ( 18.10 ) version pppoe plugin is not working correctly. The PADI packets are successfully sent to the cp interface, but it is not creating and pppoe fib, due to which the PADO packets are being dropped. Packet 1 02:34:23:456994: virtio-input virtio: hw_if_index 3 next-index 4 vring 0 len 63 hdr: flags 0x00 gso_type 0x00 hdr_len 0 gso_size 0 csum_start 0 csum_offset 0 num_buffers 1 02:34:23:457015: ethernet-input PPPOE_DISCOVERY: e6:b1:bd:65:91:c1 -> 52:54:00:79:64:b9 02:34:23:457031: error-drop ethernet-input: l3 mac mismatch vpp# show pppoe fib no pppoe fib entries Is this behavior intentional? Do I need to configure anything else other than the cp interface? -Original Message- From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of alp.ars...@xflowresearch.com Sent: Wednesday, October 24, 2018 2:51 PM To: 'Ni, Hongjun'; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] PPPoE plugin documentation/support Its working fine with VPP 17.10. I can see t
Re: [vpp-dev] PPPoE plugin documentation/support
Still waiting on this. Can anyone help me on this one? -Original Message- From: Muhammad Alp Arslan (alp.ars...@xflowresearch.com) [mailto:alp.ars...@xflowresearch.com] Sent: Friday, November 2, 2018 4:07 PM To: 'Ni, Hongjun'; 'vpp-dev@lists.fd.io' Subject: RE: [vpp-dev] PPPoE plugin documentation/support Hello, I want to use the latest VPP, instead of 17.10. The latest ( 18.10 ) version pppoe plugin is not working correctly. The PADI packets are successfully sent to the cp interface, but it is not creating and pppoe fib, due to which the PADO packets are being dropped. Packet 1 02:34:23:456994: virtio-input virtio: hw_if_index 3 next-index 4 vring 0 len 63 hdr: flags 0x00 gso_type 0x00 hdr_len 0 gso_size 0 csum_start 0 csum_offset 0 num_buffers 1 02:34:23:457015: ethernet-input PPPOE_DISCOVERY: e6:b1:bd:65:91:c1 -> 52:54:00:79:64:b9 02:34:23:457031: error-drop ethernet-input: l3 mac mismatch vpp# show pppoe fib no pppoe fib entries Is this behavior intentional? Do I need to configure anything else other than the cp interface? -Original Message- From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of alp.ars...@xflowresearch.com Sent: Wednesday, October 24, 2018 2:51 PM To: 'Ni, Hongjun'; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] PPPoE plugin documentation/support Its working fine with VPP 17.10. I can see that a pppoe fib is created as soon as the 1st PADI request arrives, which sets up the reverse path. However, in VPP 18.07 & 18.10 there is no fib entry created and the PADO packets are being dropped. The slides don't show a trace for the PADO replies. -Original Message- From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Ni, Hongjun Sent: Wednesday, October 24, 2018 1:38 PM To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] PPPoE plugin documentation/support Hi Alp Arslan, Please see below slides for more details. There is some packet trace for your reference. https://schd.ws/hosted_files/onsna18/cf/Accelerated%20Open%20Source%20vBRAS% 20Solution%20Based%20on%20OpenBRAS%20and%20VPP%26DPDK.PPTX Thanks, Hongjun -Original Message- From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of alp.ars...@xflowresearch.com Sent: Wednesday, October 24, 2018 2:49 PM To: Ni, Hongjun ; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] PPPoE plugin documentation/support Dell - Internal Use - Confidential Dear Hongjun, I was able to correctly set up the cp interface, my mistake as I was giving the wrong interface index. Now the PADI packets are passed to cp interface. I started a pppoe-server on the Linux side (tap0) interface, but VPP is dropping the PADO packets. Adding a trace on the virtio-input shows this: 00:04:07:498195: virtio-input virtio: hw_if_index 2 next-index 4 vring 0 len 71 hdr: flags 0x00 gso_type 0x00 hdr_len 0 gso_size 0 csum_start 0 csum_offset 0 num_buffers 1 00:04:07:498204: ethernet-input PPPOE_DISCOVERY: f6:a0:85:84:98:e6 -> 3c:fd:fe:25:e6:20 00:04:07:498209: error-drop ethernet-input: l3 mac mismatch The destination MAC address belongs to the pppoe-client, that's connected to the 10G interface. However, VPP doesn't seem to know where to forward the PADO replies. Also there are no entries in the pppoe fib for this client. Can you please help me with this one? Please let me know if you need any more information. Regards, Alp Arslan -Original Message- From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Ni, Hongjun Sent: Tuesday, October 23, 2018 1:07 PM To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] PPPoE plugin documentation/support Hi Alp Arslan, To make tap_cli work, you need to revert the code as per this patch: https://gerrit.fd.io/r/#/c/9467/ Thanks, Hongjun -Original Message- From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of alp.ars...@xflowresearch.com Sent: Tuesday, October 23, 2018 4:01 PM To: Ni, Hongjun ; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] PPPoE plugin documentation/support Dell - Internal Use - Confidential Dear Hongjun, Thanks for the reply. I am using the VPP version 18.07. If the tap_cli is still present, can you please point me towards what could be the problem with the existing plugin. I would like to see this one working a little bit, before starting to look into tapv2. Regards, Alp Arslan -Original Message- From: Ni, Hongjun [mailto:hongjun...@intel.com] Sent: Tuesday, October 23, 2018 12:51 PM To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io Subject: RE: [vpp-dev] PPPoE plugin documentation/support Hi Alp Arslan, Since tap_cli code is going to be deprecated in favour of tapv2. I suggest you leverage tapv2, and also need some rework for PPPoE plugin. Thanks, Hongjun -Original Message- From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of alp.ars...@xflowresearc
Re: [vpp-dev] PPPoE plugin documentation/support
Hello,
I want to use the latest VPP, instead of 17.10. The latest ( 18.10 ) version
pppoe plugin is not working correctly.
The PADI packets are successfully sent to the cp interface, but it is not
creating and pppoe fib, due to which the PADO packets are being dropped.
Packet 1
02:34:23:456994: virtio-input
virtio: hw_if_index 3 next-index 4 vring 0 len 63
hdr: flags 0x00 gso_type 0x00 hdr_len 0 gso_size 0 csum_start 0
csum_offset 0 num_buffers 1
02:34:23:457015: ethernet-input
PPPOE_DISCOVERY: e6:b1:bd:65:91:c1 -> 52:54:00:79:64:b9
02:34:23:457031: error-drop
ethernet-input: l3 mac mismatch
vpp# show pppoe fib
no pppoe fib entries
Is this behavior intentional? Do I need to configure anything else other
than the cp interface?
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
alp.ars...@xflowresearch.com
Sent: Wednesday, October 24, 2018 2:51 PM
To: 'Ni, Hongjun'; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] PPPoE plugin documentation/support
Its working fine with VPP 17.10. I can see that a pppoe fib is created as
soon as the 1st PADI request arrives, which sets up the reverse path.
However, in VPP 18.07 & 18.10 there is no fib entry created and the PADO
packets are being dropped.
The slides don't show a trace for the PADO replies.
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Ni,
Hongjun
Sent: Wednesday, October 24, 2018 1:38 PM
To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] PPPoE plugin documentation/support
Hi Alp Arslan,
Please see below slides for more details. There is some packet trace for
your reference.
https://schd.ws/hosted_files/onsna18/cf/Accelerated%20Open%20Source%20vBRAS%
20Solution%20Based%20on%20OpenBRAS%20and%20VPP%26DPDK.PPTX
Thanks,
Hongjun
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
alp.ars...@xflowresearch.com
Sent: Wednesday, October 24, 2018 2:49 PM
To: Ni, Hongjun ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] PPPoE plugin documentation/support
Dell - Internal Use - Confidential
Dear Hongjun,
I was able to correctly set up the cp interface, my mistake as I was giving
the wrong interface index.
Now the PADI packets are passed to cp interface.
I started a pppoe-server on the Linux side (tap0) interface, but VPP is
dropping the PADO packets.
Adding a trace on the virtio-input shows this:
00:04:07:498195: virtio-input
virtio: hw_if_index 2 next-index 4 vring 0 len 71
hdr: flags 0x00 gso_type 0x00 hdr_len 0 gso_size 0 csum_start 0
csum_offset 0 num_buffers 1
00:04:07:498204: ethernet-input
PPPOE_DISCOVERY: f6:a0:85:84:98:e6 -> 3c:fd:fe:25:e6:20
00:04:07:498209: error-drop
ethernet-input: l3 mac mismatch
The destination MAC address belongs to the pppoe-client, that's connected to
the 10G interface. However, VPP doesn't seem to know where to forward the
PADO replies.
Also there are no entries in the pppoe fib for this client. Can you please
help me with this one? Please let me know if you need any more information.
Regards,
Alp Arslan
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Ni,
Hongjun
Sent: Tuesday, October 23, 2018 1:07 PM
To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] PPPoE plugin documentation/support
Hi Alp Arslan,
To make tap_cli work, you need to revert the code as per this patch:
https://gerrit.fd.io/r/#/c/9467/
Thanks,
Hongjun
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
alp.ars...@xflowresearch.com
Sent: Tuesday, October 23, 2018 4:01 PM
To: Ni, Hongjun ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] PPPoE plugin documentation/support
Dell - Internal Use - Confidential
Dear Hongjun,
Thanks for the reply.
I am using the VPP version 18.07. If the tap_cli is still present, can you
please point me towards what could be the problem with the existing plugin.
I would like to see this one working a little bit, before starting to look
into tapv2.
Regards,
Alp Arslan
-Original Message-
From: Ni, Hongjun [mailto:hongjun...@intel.com]
Sent: Tuesday, October 23, 2018 12:51 PM
To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io
Subject: RE: [vpp-dev] PPPoE plugin documentation/support
Hi Alp Arslan,
Since tap_cli code is going to be deprecated in favour of tapv2.
I suggest you leverage tapv2, and also need some rework for PPPoE plugin.
Thanks,
Hongjun
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
alp.ars...@xflowresearch.com
Sent: Tuesday, October 23, 2018 3:08 PM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] PPPoE plugin documentation/support
Dear All,
I am trying to evaluate the support of pppoe in vpp. However, I am facing
some issues, here is my startup conf file.
unix {
nodaemon
log /var/log/vpp/vpp.log
full-coredump
cli-l
Re: [vpp-dev] PPPoE plugin documentation/support
Its working fine with VPP 17.10. I can see that a pppoe fib is created as
soon as the 1st PADI request arrives, which sets up the reverse path.
However, in VPP 18.07 & 18.10 there is no fib entry created and the PADO
packets are being dropped.
The slides don't show a trace for the PADO replies.
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Ni,
Hongjun
Sent: Wednesday, October 24, 2018 1:38 PM
To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] PPPoE plugin documentation/support
Hi Alp Arslan,
Please see below slides for more details. There is some packet trace for
your reference.
https://schd.ws/hosted_files/onsna18/cf/Accelerated%20Open%20Source%20vBRAS%
20Solution%20Based%20on%20OpenBRAS%20and%20VPP%26DPDK.PPTX
Thanks,
Hongjun
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
alp.ars...@xflowresearch.com
Sent: Wednesday, October 24, 2018 2:49 PM
To: Ni, Hongjun ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] PPPoE plugin documentation/support
Dell - Internal Use - Confidential
Dear Hongjun,
I was able to correctly set up the cp interface, my mistake as I was giving
the wrong interface index.
Now the PADI packets are passed to cp interface.
I started a pppoe-server on the Linux side (tap0) interface, but VPP is
dropping the PADO packets.
Adding a trace on the virtio-input shows this:
00:04:07:498195: virtio-input
virtio: hw_if_index 2 next-index 4 vring 0 len 71
hdr: flags 0x00 gso_type 0x00 hdr_len 0 gso_size 0 csum_start 0
csum_offset 0 num_buffers 1
00:04:07:498204: ethernet-input
PPPOE_DISCOVERY: f6:a0:85:84:98:e6 -> 3c:fd:fe:25:e6:20
00:04:07:498209: error-drop
ethernet-input: l3 mac mismatch
The destination MAC address belongs to the pppoe-client, that's connected to
the 10G interface. However, VPP doesn't seem to know where to forward the
PADO replies.
Also there are no entries in the pppoe fib for this client. Can you please
help me with this one? Please let me know if you need any more information.
Regards,
Alp Arslan
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Ni,
Hongjun
Sent: Tuesday, October 23, 2018 1:07 PM
To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] PPPoE plugin documentation/support
Hi Alp Arslan,
To make tap_cli work, you need to revert the code as per this patch:
https://gerrit.fd.io/r/#/c/9467/
Thanks,
Hongjun
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
alp.ars...@xflowresearch.com
Sent: Tuesday, October 23, 2018 4:01 PM
To: Ni, Hongjun ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] PPPoE plugin documentation/support
Dell - Internal Use - Confidential
Dear Hongjun,
Thanks for the reply.
I am using the VPP version 18.07. If the tap_cli is still present, can you
please point me towards what could be the problem with the existing plugin.
I would like to see this one working a little bit, before starting to look
into tapv2.
Regards,
Alp Arslan
-Original Message-
From: Ni, Hongjun [mailto:hongjun...@intel.com]
Sent: Tuesday, October 23, 2018 12:51 PM
To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io
Subject: RE: [vpp-dev] PPPoE plugin documentation/support
Hi Alp Arslan,
Since tap_cli code is going to be deprecated in favour of tapv2.
I suggest you leverage tapv2, and also need some rework for PPPoE plugin.
Thanks,
Hongjun
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
alp.ars...@xflowresearch.com
Sent: Tuesday, October 23, 2018 3:08 PM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] PPPoE plugin documentation/support
Dear All,
I am trying to evaluate the support of pppoe in vpp. However, I am facing
some issues, here is my startup conf file.
unix {
nodaemon
log /var/log/vpp/vpp.log
full-coredump
cli-listen /run/vpp/cli.sock
gid vpp
}
api-trace {
on
}
api-segment {
gid vpp
}
socksvr {
default
}
cpu {
main-core 1
corelist-workers 2,4,3,5
}
dpdk {
dev :05:00.1
uio-driver vfio-pci
socket-mem 2048,2048
}
plugins {
plugin default { enable}
}
tuntap {
enable
ethernet
name newtap
}
After that I run the following commands:
vpp# set interface state TenGigabitEthernet5/0/1 up vpp# set interface state
local0 up
Now at this point if I try to connect from the pppoe client, I can see three
PADI request reaching VPP, and VPP trying to forward them at local0
interface.
To forward this traffic to the tap port instead, I use this command.
vpp# create pppoe cp cp-if-index 2
The help and the documentation for this command show this "create pppoe cp
if-name [del]", which doesn't work.
Now at this moment, I was expecting the VPP to forward the PADI request to
tuntap-0 interface, but I don't see anything in the VPP counters, nor by
using tcp
Re: [vpp-dev] PPPoE plugin documentation/support
Hi Alp Arslan,
Please see below slides for more details. There is some packet trace for your
reference.
https://schd.ws/hosted_files/onsna18/cf/Accelerated%20Open%20Source%20vBRAS%20Solution%20Based%20on%20OpenBRAS%20and%20VPP%26DPDK.PPTX
Thanks,
Hongjun
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
alp.ars...@xflowresearch.com
Sent: Wednesday, October 24, 2018 2:49 PM
To: Ni, Hongjun ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] PPPoE plugin documentation/support
Dell - Internal Use - Confidential
Dear Hongjun,
I was able to correctly set up the cp interface, my mistake as I was giving the
wrong interface index.
Now the PADI packets are passed to cp interface.
I started a pppoe-server on the Linux side (tap0) interface, but VPP is
dropping the PADO packets.
Adding a trace on the virtio-input shows this:
00:04:07:498195: virtio-input
virtio: hw_if_index 2 next-index 4 vring 0 len 71
hdr: flags 0x00 gso_type 0x00 hdr_len 0 gso_size 0 csum_start 0 csum_offset
0 num_buffers 1
00:04:07:498204: ethernet-input
PPPOE_DISCOVERY: f6:a0:85:84:98:e6 -> 3c:fd:fe:25:e6:20
00:04:07:498209: error-drop
ethernet-input: l3 mac mismatch
The destination MAC address belongs to the pppoe-client, that's connected to
the 10G interface. However, VPP doesn't seem to know where to forward the PADO
replies.
Also there are no entries in the pppoe fib for this client. Can you please help
me with this one? Please let me know if you need any more information.
Regards,
Alp Arslan
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Ni, Hongjun
Sent: Tuesday, October 23, 2018 1:07 PM
To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] PPPoE plugin documentation/support
Hi Alp Arslan,
To make tap_cli work, you need to revert the code as per this patch:
https://gerrit.fd.io/r/#/c/9467/
Thanks,
Hongjun
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
alp.ars...@xflowresearch.com
Sent: Tuesday, October 23, 2018 4:01 PM
To: Ni, Hongjun ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] PPPoE plugin documentation/support
Dell - Internal Use - Confidential
Dear Hongjun,
Thanks for the reply.
I am using the VPP version 18.07. If the tap_cli is still present, can you
please point me towards what could be the problem with the existing plugin.
I would like to see this one working a little bit, before starting to look into
tapv2.
Regards,
Alp Arslan
-Original Message-
From: Ni, Hongjun [mailto:hongjun...@intel.com]
Sent: Tuesday, October 23, 2018 12:51 PM
To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io
Subject: RE: [vpp-dev] PPPoE plugin documentation/support
Hi Alp Arslan,
Since tap_cli code is going to be deprecated in favour of tapv2.
I suggest you leverage tapv2, and also need some rework for PPPoE plugin.
Thanks,
Hongjun
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
alp.ars...@xflowresearch.com
Sent: Tuesday, October 23, 2018 3:08 PM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] PPPoE plugin documentation/support
Dear All,
I am trying to evaluate the support of pppoe in vpp. However, I am facing some
issues, here is my startup conf file.
unix {
nodaemon
log /var/log/vpp/vpp.log
full-coredump
cli-listen /run/vpp/cli.sock
gid vpp
}
api-trace {
on
}
api-segment {
gid vpp
}
socksvr {
default
}
cpu {
main-core 1
corelist-workers 2,4,3,5
}
dpdk {
dev :05:00.1
uio-driver vfio-pci
socket-mem 2048,2048
}
plugins {
plugin default { enable}
}
tuntap {
enable
ethernet
name newtap
}
After that I run the following commands:
vpp# set interface state TenGigabitEthernet5/0/1 up vpp# set interface state
local0 up
Now at this point if I try to connect from the pppoe client, I can see three
PADI request reaching VPP, and VPP trying to forward them at local0 interface.
To forward this traffic to the tap port instead, I use this command.
vpp# create pppoe cp cp-if-index 2
The help and the documentation for this command show this "create pppoe cp
if-name [del]", which doesn't work.
Now at this moment, I was expecting the VPP to forward the PADI request to
tuntap-0 interface, but I don't see anything in the VPP counters, nor by using
tcpdump on interface "newtap" which is the kernel facing side of "tuntap-0"
interface.
My question is, Is my approach correct? Are the PADI requests forwarded to the
tuntap-0 interface? If not where do they go? I cannot find any good
documentation on this anywhere.
Any help regarding this would be highly appreciated.
Regards,
Alp Arslan
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10942): https://lists.fd.io/g/vpp-dev/message/10942
Mute This Topic: https://lists.fd.io/m
Re: [vpp-dev] PPPoE plugin documentation/support
Dell - Internal Use - Confidential
Dear Hongjun,
I was able to correctly set up the cp interface, my mistake as I was giving
the wrong interface index.
Now the PADI packets are passed to cp interface.
I started a pppoe-server on the Linux side (tap0) interface, but VPP is
dropping the PADO packets.
Adding a trace on the virtio-input shows this:
00:04:07:498195: virtio-input
virtio: hw_if_index 2 next-index 4 vring 0 len 71
hdr: flags 0x00 gso_type 0x00 hdr_len 0 gso_size 0 csum_start 0
csum_offset 0 num_buffers 1
00:04:07:498204: ethernet-input
PPPOE_DISCOVERY: f6:a0:85:84:98:e6 -> 3c:fd:fe:25:e6:20
00:04:07:498209: error-drop
ethernet-input: l3 mac mismatch
The destination MAC address belongs to the pppoe-client, that's connected to
the 10G interface. However, VPP doesn't seem to know where to forward the
PADO replies.
Also there are no entries in the pppoe fib for this client. Can you please
help me with this one? Please let me know if you need any more information.
Regards,
Alp Arslan
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Ni,
Hongjun
Sent: Tuesday, October 23, 2018 1:07 PM
To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] PPPoE plugin documentation/support
Hi Alp Arslan,
To make tap_cli work, you need to revert the code as per this patch:
https://gerrit.fd.io/r/#/c/9467/
Thanks,
Hongjun
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
alp.ars...@xflowresearch.com
Sent: Tuesday, October 23, 2018 4:01 PM
To: Ni, Hongjun ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] PPPoE plugin documentation/support
Dell - Internal Use - Confidential
Dear Hongjun,
Thanks for the reply.
I am using the VPP version 18.07. If the tap_cli is still present, can you
please point me towards what could be the problem with the existing plugin.
I would like to see this one working a little bit, before starting to look
into tapv2.
Regards,
Alp Arslan
-Original Message-
From: Ni, Hongjun [mailto:hongjun...@intel.com]
Sent: Tuesday, October 23, 2018 12:51 PM
To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io
Subject: RE: [vpp-dev] PPPoE plugin documentation/support
Hi Alp Arslan,
Since tap_cli code is going to be deprecated in favour of tapv2.
I suggest you leverage tapv2, and also need some rework for PPPoE plugin.
Thanks,
Hongjun
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
alp.ars...@xflowresearch.com
Sent: Tuesday, October 23, 2018 3:08 PM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] PPPoE plugin documentation/support
Dear All,
I am trying to evaluate the support of pppoe in vpp. However, I am facing
some issues, here is my startup conf file.
unix {
nodaemon
log /var/log/vpp/vpp.log
full-coredump
cli-listen /run/vpp/cli.sock
gid vpp
}
api-trace {
on
}
api-segment {
gid vpp
}
socksvr {
default
}
cpu {
main-core 1
corelist-workers 2,4,3,5
}
dpdk {
dev :05:00.1
uio-driver vfio-pci
socket-mem 2048,2048
}
plugins {
plugin default { enable}
}
tuntap {
enable
ethernet
name newtap
}
After that I run the following commands:
vpp# set interface state TenGigabitEthernet5/0/1 up vpp# set interface state
local0 up
Now at this point if I try to connect from the pppoe client, I can see three
PADI request reaching VPP, and VPP trying to forward them at local0
interface.
To forward this traffic to the tap port instead, I use this command.
vpp# create pppoe cp cp-if-index 2
The help and the documentation for this command show this "create pppoe cp
if-name [del]", which doesn't work.
Now at this moment, I was expecting the VPP to forward the PADI request to
tuntap-0 interface, but I don't see anything in the VPP counters, nor by
using tcpdump on interface "newtap" which is the kernel facing side of
"tuntap-0" interface.
My question is, Is my approach correct? Are the PADI requests forwarded to
the tuntap-0 interface? If not where do they go? I cannot find any good
documentation on this anywhere.
Any help regarding this would be highly appreciated.
Regards,
Alp Arslan
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10936): https://lists.fd.io/g/vpp-dev/message/10936
Mute This Topic: https://lists.fd.io/mt/27566265/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] PPPoE plugin documentation/support
Hi Alp Arslan,
To make tap_cli work, you need to revert the code as per this patch:
https://gerrit.fd.io/r/#/c/9467/
Thanks,
Hongjun
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
alp.ars...@xflowresearch.com
Sent: Tuesday, October 23, 2018 4:01 PM
To: Ni, Hongjun ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] PPPoE plugin documentation/support
Dell - Internal Use - Confidential
Dear Hongjun,
Thanks for the reply.
I am using the VPP version 18.07. If the tap_cli is still present, can you
please point me towards what could be the problem with the existing plugin.
I would like to see this one working a little bit, before starting to look into
tapv2.
Regards,
Alp Arslan
-Original Message-
From: Ni, Hongjun [mailto:hongjun...@intel.com]
Sent: Tuesday, October 23, 2018 12:51 PM
To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io
Subject: RE: [vpp-dev] PPPoE plugin documentation/support
Hi Alp Arslan,
Since tap_cli code is going to be deprecated in favour of tapv2.
I suggest you leverage tapv2, and also need some rework for PPPoE plugin.
Thanks,
Hongjun
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
alp.ars...@xflowresearch.com
Sent: Tuesday, October 23, 2018 3:08 PM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] PPPoE plugin documentation/support
Dear All,
I am trying to evaluate the support of pppoe in vpp. However, I am facing some
issues, here is my startup conf file.
unix {
nodaemon
log /var/log/vpp/vpp.log
full-coredump
cli-listen /run/vpp/cli.sock
gid vpp
}
api-trace {
on
}
api-segment {
gid vpp
}
socksvr {
default
}
cpu {
main-core 1
corelist-workers 2,4,3,5
}
dpdk {
dev :05:00.1
uio-driver vfio-pci
socket-mem 2048,2048
}
plugins {
plugin default { enable}
}
tuntap {
enable
ethernet
name newtap
}
After that I run the following commands:
vpp# set interface state TenGigabitEthernet5/0/1 up vpp# set interface state
local0 up
Now at this point if I try to connect from the pppoe client, I can see three
PADI request reaching VPP, and VPP trying to forward them at local0 interface.
To forward this traffic to the tap port instead, I use this command.
vpp# create pppoe cp cp-if-index 2
The help and the documentation for this command show this "create pppoe cp
if-name [del]", which doesn't work.
Now at this moment, I was expecting the VPP to forward the PADI request to
tuntap-0 interface, but I don't see anything in the VPP counters, nor by using
tcpdump on interface "newtap" which is the kernel facing side of "tuntap-0"
interface.
My question is, Is my approach correct? Are the PADI requests forwarded to the
tuntap-0 interface? If not where do they go? I cannot find any good
documentation on this anywhere.
Any help regarding this would be highly appreciated.
Regards,
Alp Arslan
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10915): https://lists.fd.io/g/vpp-dev/message/10915
Mute This Topic: https://lists.fd.io/mt/27566265/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] PPPoE plugin documentation/support
Dell - Internal Use - Confidential
Dear Hongjun,
Thanks for the reply.
I am using the VPP version 18.07. If the tap_cli is still present, can you
please point me towards what could be the problem with the existing plugin.
I would like to see this one working a little bit, before starting to look
into tapv2.
Regards,
Alp Arslan
-Original Message-
From: Ni, Hongjun [mailto:hongjun...@intel.com]
Sent: Tuesday, October 23, 2018 12:51 PM
To: alp.ars...@xflowresearch.com; vpp-dev@lists.fd.io
Subject: RE: [vpp-dev] PPPoE plugin documentation/support
Hi Alp Arslan,
Since tap_cli code is going to be deprecated in favour of tapv2.
I suggest you leverage tapv2, and also need some rework for PPPoE plugin.
Thanks,
Hongjun
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
alp.ars...@xflowresearch.com
Sent: Tuesday, October 23, 2018 3:08 PM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] PPPoE plugin documentation/support
Dear All,
I am trying to evaluate the support of pppoe in vpp. However, I am facing
some issues, here is my startup conf file.
unix {
nodaemon
log /var/log/vpp/vpp.log
full-coredump
cli-listen /run/vpp/cli.sock
gid vpp
}
api-trace {
on
}
api-segment {
gid vpp
}
socksvr {
default
}
cpu {
main-core 1
corelist-workers 2,4,3,5
}
dpdk {
dev :05:00.1
uio-driver vfio-pci
socket-mem 2048,2048
}
plugins {
plugin default { enable}
}
tuntap {
enable
ethernet
name newtap
}
After that I run the following commands:
vpp# set interface state TenGigabitEthernet5/0/1 up vpp# set interface state
local0 up
Now at this point if I try to connect from the pppoe client, I can see three
PADI request reaching VPP, and VPP trying to forward them at local0
interface.
To forward this traffic to the tap port instead, I use this command.
vpp# create pppoe cp cp-if-index 2
The help and the documentation for this command show this "create pppoe cp
if-name [del]", which doesn't work.
Now at this moment, I was expecting the VPP to forward the PADI request to
tuntap-0 interface, but I don't see anything in the VPP counters, nor by
using tcpdump on interface "newtap" which is the kernel facing side of
"tuntap-0" interface.
My question is, Is my approach correct? Are the PADI requests forwarded to
the tuntap-0 interface? If not where do they go? I cannot find any good
documentation on this anywhere.
Any help regarding this would be highly appreciated.
Regards,
Alp Arslan
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10914): https://lists.fd.io/g/vpp-dev/message/10914
Mute This Topic: https://lists.fd.io/mt/27566265/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] PPPoE plugin documentation/support
Hi Alp Arslan,
Since tap_cli code is going to be deprecated in favour of tapv2.
I suggest you leverage tapv2, and also need some rework for PPPoE plugin.
Thanks,
Hongjun
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
alp.ars...@xflowresearch.com
Sent: Tuesday, October 23, 2018 3:08 PM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] PPPoE plugin documentation/support
Dear All,
I am trying to evaluate the support of pppoe in vpp. However, I am facing some
issues, here is my startup conf file.
unix {
nodaemon
log /var/log/vpp/vpp.log
full-coredump
cli-listen /run/vpp/cli.sock
gid vpp
}
api-trace {
on
}
api-segment {
gid vpp
}
socksvr {
default
}
cpu {
main-core 1
corelist-workers 2,4,3,5
}
dpdk {
dev :05:00.1
uio-driver vfio-pci
socket-mem 2048,2048
}
plugins {
plugin default { enable}
}
tuntap {
enable
ethernet
name newtap
}
After that I run the following commands:
vpp# set interface state TenGigabitEthernet5/0/1 up vpp# set interface state
local0 up
Now at this point if I try to connect from the pppoe client, I can see three
PADI request reaching VPP, and VPP trying to forward them at local0 interface.
To forward this traffic to the tap port instead, I use this command.
vpp# create pppoe cp cp-if-index 2
The help and the documentation for this command show this "create pppoe cp
if-name [del]", which doesn't work.
Now at this moment, I was expecting the VPP to forward the PADI request to
tuntap-0 interface, but I don't see anything in the VPP counters, nor by using
tcpdump on interface "newtap" which is the kernel facing side of "tuntap-0"
interface.
My question is, Is my approach correct? Are the PADI requests forwarded to the
tuntap-0 interface? If not where do they go? I cannot find any good
documentation on this anywhere.
Any help regarding this would be highly appreciated.
Regards,
Alp Arslan
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10913): https://lists.fd.io/g/vpp-dev/message/10913
Mute This Topic: https://lists.fd.io/mt/27566265/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
