- **status**: review --> fixed
- **Comment**:
changeset: 5299:2d00261d00bc
parent: 5297:e07b4b15f255
user: A V Mahesh <[email protected]>
date: Thu May 22 11:54:09 2014 +0530
summary: dtm: Segregate IPv4-Sub-net & IPv6 Link-Local/Global for discovery
broadcast [#913]
changeset: 5298:e29a57102499
branch: opensaf-4.4.x
parent: 5296:8226290b2309
user: A V Mahesh <[email protected]>
date: Thu May 22 11:50:42 2014 +0530
summary: dtm: Segregate IPv4-Sub-net & IPv6 Link-Local/Global for discovery
broadcast [#913]
---
** [tickets:#913] dtm : discovery broadcast messagesshould be resticted to same
ipv4 sub-net/ Ipv6 Link-local /Ipv6 Link-Global**
**Status:** fixed
**Milestone:** 4.5.0
**Created:** Mon May 19, 2014 03:27 AM UTC by A V Mahesh (AVM)
**Last Updated:** Fri Aug 15, 2014 03:06 PM UTC
**Owner:** A V Mahesh (AVM)
Use global IPv6 addresses for DTM_NODE_IP in /etc/opensaf/dtmd.conf ,but
discovered that OpenSAF was sending broadcast messages from port 6900 using
the link local address of the interface instead of the global address listed in
dtmd.conf. Port 6900 is for DTM_UDP_BCAST_REV_PORT.
OpenSAF Dtm Broadcast Sender and Listener should segregate IPV6 link local /
global address
and link local should be disable and force broadcast communications through
the global address when global address is configured in dtmd.conf and
vice-versa.
Following are the test case to reproduce :
---------------------------------------------------------------------------------
Test case 1) Bring-up 2 -Controllers with TCP IPV6 Scope:Global , when A Third
party IPV6 UDP Application bind to same Opensf dtm port 6900 on Scope:Link
Local Mcast address to receive broadcast messages.
- Third party IPv6 UDP Application is receiveing broadcast messages
Test case 2) Bring-up 2 -Controllers with TCP IPv6 Scope:Link Local , when A
Third party IPv6 UDP Application bind to same Opensf dtm port 6900 on
Scope:Global Mcast address to receive broadcast messages.
- Third party IPv6 UDP Application is receiveing broadcast messages
Test case 3) Bring-up 2 -Controllers with TCP IPv4 with one sub-net say
10.176.179.xxx address ,when A Third party IPV4 UDP Application bind to same
Opensf dtm port 6900
different say 192.168.56.255 address to receive broadcast messages.
- Third party IPv4 UDP Application is receiveing broadcast messages
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
