unable to get packet from source using networking-sfc

asked 2018-12-19 02:41:10 -0500

sonic gravatar image

updated 2018-12-19 04:51:54 -0500

Hello, I'm doing sfc using networking-sfc right now, and I have some problem about the routing I have three VM in openstack, client, chain-vm and server After creating the port chain with the following command:

openstack sfc flow classifier create \
      --ethertype IPv4 \
      --source-ip-prefix \
      --destination-ip-prefix \
      --protocol tcp \
      --source-port 51818:51818 \
      --destination-port 8080:8080 \
      --logical-source-port daab6bcc-39c9-4963-802b-f944d3d0f58f \
      --logical-destination-port fc6a92f6-ce28-43ad-801e-471c19e69983 FC1

openstack sfc port pair create --ingress f63a75ff-5fff-4b80-8176-989c11076263 --egress f63a75ff-5fff-4b80-8176-989c11076263  PP1

openstack sfc port pair group create --port-pair PP1 PG1

openstack sfc port chain create --port-pair-group PG1 --flow-classifier FC1 --chain-parameters symmetric=true PC1

from client I use curl --local-port 51818, and in chain-vm I can capture the packet from client to server using tcpdump but server didn't receive it, so there's no response I tried to enable the ipv4 routing by setting the net.ipv4.ip_forward=1 in /etc/sysctl.conf in chain-vm(ubuntu) But still not working, can somebody help me? Thank you.

edit retag flag offensive close merge delete


I use echo 1 > /proc/sys/net/ipv4/ip_forward on the vnf with cloud-init instead of changing systctl.conf. May be this?

Eduardo Gonzalez gravatar imageEduardo Gonzalez ( 2018-12-19 04:55:21 -0500 )edit

Eduardo Gonzalez, Thank you very much, I try this and it works well for me. Just wondering the difference between them?

sonic gravatar imagesonic ( 2018-12-19 06:12:28 -0500 )edit