Skip to content

Commit

Permalink
v1.6.2-1
Browse files Browse the repository at this point in the history
  • Loading branch information
biplamal committed Jun 28, 2024
1 parent deb5b19 commit 35d0168
Show file tree
Hide file tree
Showing 3 changed files with 79 additions and 5 deletions.
2 changes: 1 addition & 1 deletion conformance
Submodule conformance updated 0 files
41 changes: 39 additions & 2 deletions docs/releases.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,10 +23,47 @@


# Release Features(s)
* TBD
* <b><i>Ixia Chassis & Appliances(Novus, AresOne)</i></b>: Support added for DHCPv4 client interfaces to be used as source/destination for device traffic.
- In this the learned IPv4 address from the DHCPv4 server is automatically populated in `ipv4.src/dst` if the choice is set to `auto.dhcp`.

```go
clientToServerFlow.SetName("ClientToServer").TxRx().Device().
SetTxNames([]string{"DHCPv4ClientName"}).
SetRxNames([]string{"DHCPv4ServerInterfaceName"})
clientToServerFlowIp := clientToServerFlow.Packet().Add().Ipv4()
clientToServerFlowIp.Src().Auto().Dhcp()

serverToClientFlow.SetName("ServerToClient").TxRx().Device().
SetTxNames([]string{"DHCPv4ServerInterfaceName"}).
SetRxNames([]string{"DHCPv4ClientName"})
serverToClientFlowIp := serverToClientFlow.Packet().Add().Ipv4()
serverToClientFlowIp.Dst().Auto().Dhcp()
```
Note: For DHCPv4 client to DHCPv4 server each flow supports only one source endpoint in `tx_rx.device.tx_names`, hence a separate flow has to be configured for each DHCPv4 client if `packet[i].ipv4.src.auto.dhcp` is set.

* <b><i>Ixia-C</i></b>: Support added for multiple address groups in BGPv4/v6 routes.
```go
route = peer.V4Routes().Add().​
SetNextHopIpv4Address("2.2.2.2").​
SetName("peer1.rr1")​

route.Addresses().Add().​
SetAddress("20.20.20.1").SetPrefix(32).SetCount(2).SetStep(2)​

route.Addresses().Add().​
SetAddress("20.20.21.1").SetPrefix(32).SetCount(2).SetStep(2)​
```

### Bug Fix(s)
* TBD
* <b><i>Ixia-C, Ixia Chassis & Appliances(Novus, AresOne)</i></b>: Issue where if a BGPv4/v6 prefix with extended-community or community attributes was updated via a BGP Update with the extended-community or community attribute deleted without a Route Withdraw in between , the subsequent get_states call on the bgp prefixes would incorrectly continue to show the extended-community or community attributes learned via the previous received Update is fixed.

* <b><i>Ixia-C</i></b>: Issue where If a test was setup such that only test port would initiate ARP/ND and time taken to configure the soft-DUT connected to the test port was taking extended time such that it would not respond to ARP/ND requests within 10s, ARP/ND procedures would fail resulting in test failures in ARP/ND verification step is fixed.

* <b><i>Ixia-C</i></b>: Issue where if a IPv6 address on the emulated interface was configured in non-shortest format e.g. `2001:0db8::192:0:2:2` instead of `2001:db8::192:0:2:2` (notice the redundant leading 0 in :0db8), the test port would not initiate IPv6 Neighbor Discovery for corresponding IPv6 gateway result in Neighbor Discovery failure is fixed.

* <b><i>Keng-Operator</i></b>: Some fixes are provided to handle security warnings raised by k8s security scanning tool such as <i>`'container "manager" in Deployment "ixiatg-op-controller-manager" does not set readOnlyRootFilesystem: true in its securityContext. This setting is encouraged because it can prevent attackers from writing malicious binaries into runnable locations in the container filesystem.'`</i>.

* <b><i>UHD400</i></b>: Issue is fixed where `frames_rx` is reported twice of `frames_tx` in `flow_metrics` is fixed.


#### Known Issues
Expand Down
41 changes: 39 additions & 2 deletions notes.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,10 +17,47 @@


# Release Features(s)
* TBD
* <b><i>Ixia Chassis & Appliances(Novus, AresOne)</i></b>: Support added for DHCPv4 client interfaces to be used as source/destination for device traffic.
- In this the learned IPv4 address from the DHCPv4 server is automatically populated in `ipv4.src/dst` if the choice is set to `auto.dhcp`.

```go
clientToServerFlow.SetName("ClientToServer").TxRx().Device().
SetTxNames([]string{"DHCPv4ClientName"}).
SetRxNames([]string{"DHCPv4ServerInterfaceName"})
clientToServerFlowIp := clientToServerFlow.Packet().Add().Ipv4()
clientToServerFlowIp.Src().Auto().Dhcp()

serverToClientFlow.SetName("ServerToClient").TxRx().Device().
SetTxNames([]string{"DHCPv4ServerInterfaceName"}).
SetRxNames([]string{"DHCPv4ClientName"})
serverToClientFlowIp := serverToClientFlow.Packet().Add().Ipv4()
serverToClientFlowIp.Dst().Auto().Dhcp()
```
Note: For DHCPv4 client to DHCPv4 server each flow supports only one source endpoint in `tx_rx.device.tx_names`, hence a separate flow has to be configured for each DHCPv4 client if `packet[i].ipv4.src.auto.dhcp` is set.

* <b><i>Ixia-C</i></b>: Support added for multiple address groups in BGPv4/v6 routes.
```go
route = peer.V4Routes().Add().​
SetNextHopIpv4Address("2.2.2.2").​
SetName("peer1.rr1")​

route.Addresses().Add().​
SetAddress("20.20.20.1").SetPrefix(32).SetCount(2).SetStep(2)​

route.Addresses().Add().​
SetAddress("20.20.21.1").SetPrefix(32).SetCount(2).SetStep(2)​
```

### Bug Fix(s)
* TBD
* <b><i>Ixia-C, Ixia Chassis & Appliances(Novus, AresOne)</i></b>: Issue where if a BGPv4/v6 prefix with extended-community or community attributes was updated via a BGP Update with the extended-community or community attribute deleted without a Route Withdraw in between , the subsequent get_states call on the bgp prefixes would incorrectly continue to show the extended-community or community attributes learned via the previous received Update is fixed.

* <b><i>Ixia-C</i></b>: Issue where If a test was setup such that only test port would initiate ARP/ND and time taken to configure the soft-DUT connected to the test port was taking extended time such that it would not respond to ARP/ND requests within 10s, ARP/ND procedures would fail resulting in test failures in ARP/ND verification step is fixed.

* <b><i>Ixia-C</i></b>: Issue where if a IPv6 address on the emulated interface was configured in non-shortest format e.g. `2001:0db8::192:0:2:2` instead of `2001:db8::192:0:2:2` (notice the redundant leading 0 in :0db8), the test port would not initiate IPv6 Neighbor Discovery for corresponding IPv6 gateway result in Neighbor Discovery failure is fixed.

* <b><i>Keng-Operator</i></b>: Some fixes are provided to handle security warnings raised by k8s security scanning tool such as <i>`'container "manager" in Deployment "ixiatg-op-controller-manager" does not set readOnlyRootFilesystem: true in its securityContext. This setting is encouraged because it can prevent attackers from writing malicious binaries into runnable locations in the container filesystem.'`</i>.

* <b><i>UHD400</i></b>: Issue is fixed where `frames_rx` is reported twice of `frames_tx` in `flow_metrics` is fixed.


#### Known Issues
Expand Down

0 comments on commit 35d0168

Please sign in to comment.