1. Durbek Gafurov

Durbek Gafurov

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • Durbek Gafurov
    Participant

      For some reason, now we have to manually turn up the interface.
      You can first install
      sudo apt install -y net-tools

      and

      sudo ifconfig ens7 up && sudo ifconfig ens8 up && sudo ifconfig ens9 up && sudo ifconfig ens10 up

      Alternatively you can use the code below, to turn on all interfaces
      try:
      for node in slice.get_nodes():
      print(“—-“)
      print(“Node:”)
      print(f” Name : {node.get_name()}”)
      for component in node.get_components():
      print(f” Name : {component.get_name()}”)
      for interface in node.get_interfaces():
      print(f” Name : {interface.get_name()}”)
      stdout, stderr = node.execute(f’sudo apt install -y net-tools && sudo ifconfig {interface.get_os_interface()} up ‘)
      except Exception as e:
      print(f”Fail: {e}”)
      traceback.print_exc()

      in reply to: Packets with bad checksum being dropped. #2876
      Durbek Gafurov
      Participant

        When the checksum is correct I receive it in receiving node.

        in reply to: Packets with bad checksum being dropped. #2874
        Durbek Gafurov
        Participant

          Short answer yes, I am intentionally sending bad packets.

          Longer version: I am working with P4 lang, I am changing ipv4 headers with p4lang, p4lang at this point unable to generate correct checksum, because in the header i have array and as far as I know p4lang cannot loop. Hence the generated checksum is wrong.

          in reply to: Packets with bad checksum being dropped. #2872
          Durbek Gafurov
          Participant

            Thanks for reply and suggestion. I tried to use NIC5 and NIC6 the same issue. When the packet has good checksum it accepts and packets with bad checksum are lost. I can see those packets leaving interface from sending node, but don’t see them at the receiving node.

            Any suggestion is appreciated.

            in reply to: Updated P4langTutorials #2776
            Durbek Gafurov
            Participant

              One of the reasons that was contributing to the error  is that old variables were used in docker command:

               

              #port1_iface=$1
              #port2_iface=$2
              #port3_iface=$3
              #ip_type=$4

              ……
              docker exec -d -it fabric_p4 sh -c ‘simple_switch –interface 1@’${port1_iface}’ –interface 2@’${port2_iface}’ –interface 3@’${port3_iface}’ /root/tutorials/exercises/basic_tunnel/basic_tunnel.json’

              I have created a pull request pr that should fix  this issue.

            Viewing 5 posts - 1 through 5 (of 5 total)