Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - ninj4

Pages: [1]
1
Zodiac FX General / Re: IP checksum calculation not done
« on: January 28, 2018, 06:19:56 AM »
Hello Paul,

Is there a deadline you are targeting for releasing the new firmware?
One of my research projects heavily depend on this to work, it would be great if this could be done as soon as possible.

Regards,

2
Zodiac FX General / Re: IP checksum calculation not done
« on: January 23, 2018, 06:15:51 AM »
Thanks a lot Paul.

3
Zodiac FX General / Re: IP checksum calculation not done
« on: January 22, 2018, 04:51:50 AM »
Hello, I hope this thread doesn't go on in sleep mode.

I am stuck with my project because of this issue and is eagerly awaiting response.

Thanks.

4
Zodiac FX General / Re: IP checksum calculation not done
« on: January 08, 2018, 12:40:31 AM »
Hi,

Do let me know if the information provided above is enough, or something else is needed too.

5
Zodiac FX General / Re: NORMAL action support
« on: January 06, 2018, 04:43:25 AM »
Thanks a lot Paul for this information.  :) :)

6
Zodiac FX General / Re: IP checksum calculation not done
« on: January 06, 2018, 04:27:33 AM »
The topology i have can be considered as follows :
10.0.1.2<------->switch<------>10.0.1.3
                                   ^
                                   |
                                   |
                                   V
                             10.0.1.4


So the IP address modification rules i have are provided below.

Flow 11
 Match:
  ETH Type: IPv4
  Source IP:  10.0.1.2
  Destination IP:  10.0.1.3
 Attributes:
  Table ID: 0                           Cookie:0x0
  Priority: 3000                                Duration: 3 secs
  Hard Timeout: 100 secs                        Idle Timeout: 0 secs
  Byte Count: 0                 Packet Count: 0
  Last Match: 00:00:03
 Instructions:
  Apply Actions:
   Set Source IP:  10.0.1.4
  Goto Table: 1



Flow 10
 Match:
  ETH Type: IPv4
  Source IP:  10.0.1.3
  Destination IP:  10.0.1.4
 Attributes:
  Table ID: 0                           Cookie:0x0
  Priority: 3000                                Duration: 3 secs
  Hard Timeout: 100 secs                        Idle Timeout: 0 secs
  Byte Count: 0                 Packet Count: 0
  Last Match: 00:00:03
 Instructions:
  Apply Actions:
   Set Destination IP:  10.0.1.2
  Goto Table: 1

Table 1 contains normal routing rules.

After these rules when any of the IPs receive a packet whose source or destination IP is modified by the switch, they show a IP header checksum error on wireshark.

On the other hand, for normal openflow rules to forward to a particular port, there is no error.
Flow 8
 Match:
  ETH Type: IPv4
  Destination IP:  10.0.1.4
 Attributes:
  Table ID: 1                           Cookie:0x1
  Priority: 35                          Duration: 958 secs
  Hard Timeout: 0 secs                  Idle Timeout: 1800 secs
  Byte Count: 5194                      Packet Count: 53
  Last Match: 00:15:33
 Instructions:
  Apply Actions:
   Set Source MAC: BE:64:00:2D:C7:03
   Set Destination MAC: 6C:3B:E5:35:C1:BC
   Output Port: 2

 How i see this problem is that, primarily for any flow which doesn't require IP address modification, everything works fine.
But, for flows requiring IP address modification, the IP header checksum is not calculated and hence packets are discarded at the end hosts.


7
Zodiac FX General / NORMAL action support
« on: January 05, 2018, 06:08:17 AM »
Hello folks,

I am using RYU controller to perform some tasks and i see that the "NORMAL" action is not being supported in zodiac fx because, the flow action field is blank when there is a NORMAL action.

So is it true that zodiac fx switches do not support NORMAL action.

8
Zodiac FX General / IP checksum calculation not done
« on: January 05, 2018, 06:01:22 AM »
Hello folks,

I am using zodiac fx switch to perform kind of NAT operation which requires to modify source and destination IP address.
However, i am facing an issue that after the rule is matched and the action of modifying the IP is done, the IP checksum isn't calculated by the switch.
 This is leading to a lot of problems as the packets are being discarded due to checksum failures.

Has anybody faced this issue earlier, and are there some suggestions as to how to work around this problem.

Thanks.

Pages: [1]