diff --git a/conformance b/conformance
index b9fea1ef..8b04cf27 160000
--- a/conformance
+++ b/conformance
@@ -1 +1 @@
-Subproject commit b9fea1ef04620d25207330a75da135664f37816e
+Subproject commit 8b04cf27a3fdd172ccc61257ab9f211c2c58e443
diff --git a/docs/releases.md b/docs/releases.md
index e0b33dc4..e26251a1 100644
--- a/docs/releases.md
+++ b/docs/releases.md
@@ -23,10 +23,47 @@
# Release Features(s)
-* TBD
+* Ixia Chassis & Appliances(Novus, AresOne): 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.
+
+* Ixia-C: 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
+* Ixia-C, Ixia Chassis & Appliances(Novus, AresOne): 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.
+
+* Ixia-C: 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.
+
+* Ixia-C: 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.
+
+* Keng-Operator: Some fixes are provided to handle security warnings raised by k8s security scanning tool such as `'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.'`.
+
+* UHD400: Issue is fixed where `frames_rx` is reported twice of `frames_tx` in `flow_metrics` is fixed.
#### Known Issues
diff --git a/notes.md b/notes.md
index 54e0809e..414ee574 100644
--- a/notes.md
+++ b/notes.md
@@ -17,10 +17,47 @@
# Release Features(s)
-* TBD
+* Ixia Chassis & Appliances(Novus, AresOne): 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.
+
+* Ixia-C: 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
+* Ixia-C, Ixia Chassis & Appliances(Novus, AresOne): 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.
+
+* Ixia-C: 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.
+
+* Ixia-C: 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.
+
+* Keng-Operator: Some fixes are provided to handle security warnings raised by k8s security scanning tool such as `'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.'`.
+
+* UHD400: Issue is fixed where `frames_rx` is reported twice of `frames_tx` in `flow_metrics` is fixed.
#### Known Issues