While doing RPF check for ECMP nh, source ip/intf is compared against all
component NH, to check if they are valid source. If valid and the source
is different then packet is trapped to agent, to mark forward flow to goto
new source. Correcting component NH index to picked up for validation.
Merge pull request #14 from naveen-n/master

While doing RPF check for ECMP nh, source ip/intf is compared against al...
xen: Fix xen server crash in ping broadcast from vm

- Ping broadcast causes xen server to crash. The fix is to make network header
  offset calculation proper for 32bit host (xenserver).

Signed-off-by: Anirban Chakraborty <abchak@juniper.net>
Fix whitespace issue

Signed-off-by: Anirban Chakraborty <abchak@juniper.net>
Merge pull request #16 from anirban-c/master

xen: Fix for server crash
Don't validate NH index for flow delete requests
Merge pull request #17 from ashoksr/master

Don't validate NH index for flow delete requests
[Double commit]

-Should not touch checksum type and value, if it is really not required.
One side effect was that we were overwriting the field indicating that
checksum is unnecessary.

For mpls over udp, we calculate checksum of the entire packet and store it in
udp header. In the receiving end, we will verify the outer checksum, and mark
the packet as one where calculation of checksum is unnecessary, indicating to
the vm that it should not calculate checksum of the inner packet (since inner
packet checksum was not calculated even at the sending end). Once the type was
overwritten, packets were dropped in vm.
1) Not freeing the Bridge table memory as part of soft_reset 2) Adding module parameters for the bridge entries 3) Stopping the init incase of failures
Merge pull request #19 from Juniper/soft_reset

1) Not freeing the Bridge table memory as part of soft_reset 2) Adding m...
Merge pull request #18 from Juniper/mplsoudp

[Double commit]
xen: Fix pkt tail comparison for 32 bit systems

- Issue detected from compilation warning

Signed-off-by: Anirban Chakraborty <abchak@juniper.net>
Merge pull request #20 from anirban-c/master

xen: Fix pkt tail comparison for 32 bit systems
1)Accessing the component nh of composite nh only if it has valid flag 2)Doing a vr_delay_op() while modifying the nh flags 3) Decrementing the reference count of nh_dev in nh while making the nh invalid 4) Marking the skb->ip_summed to CHECKSUM_UNNECESSARY for l2 packets received on Physical if checksum is partial 5) code alignment
1)Updating Tunnel NH, Receive NH and Encap nh_dev only if it is valid 2) Fixing the memory leak of soft_reset 3)Accessing componenent NH only if Non-NULL incase of composite NH processing 4) Decrementing the nh_dev reference count while updating new nh_dev 5) Stricter validations for composite multicast NH updation from Agent 6) Printing component and coposite nh if nh_dev is NULL while processing fabric NH 7) Marking the NH as valid only after making the complete nexthop while transitioning from invalid to valid 8) Strict check while adding multi_proto nexthop to have only one L2 and L3 mcast nexthop 9) Freeing the packet in error condition
Merge pull request #21 from divakardhar/master

1)Accessing the component nh of composite nh only if it has valid flag 2...
Assigning nh_discard() as reach_nh while updating the nexthop
Merge pull request #23 from divakardhar/master

Assigning nh_discard() as reach_nh while updating the nexthop
- If the packet has to go to agent and needs to be held in the flow entry,
do not cache the nexthop in the packet, since a cached nexthop need not be valid
when the packet gets flushed subsequently. Nexthop caching for packets which were
held in flow entry was introduced as part of ECMP support, since a route lookup
will not return the same nexthop as the one from MPLS table. This issue has
now been solved by doing a relookup in the MPLS table for packets that are
held. Also, similar problem can happen for interface pointer cached in the
packet. Fix that behavior too by doing a relook in the interface table and
comparing pointers. While it could so happen that the old interface was deleted,
and the new interface gets the same memory, this check is the best we could do
for sanity.
Merge pull request #24 from Juniper/fix

- If the packet has to go to agent and needs to be held in the flow entr...