- **Comment**:
Following explored options are facilitating the all the Opensaf
discovery/control/application-data routing traffic through `dtmd.conf`
configured interface/device (IP addr).
1) Binding Opensaf stream sockets to a particular device like eth4,
with `setsockopt(<stream sockets>, SOL_SOCKET, SO_BINDTODEVICE,....)`
2a) Binding Opensaf multicast sender/receiver udp sockets with particular
device like "eth4", with setsockopt(<Multicast sockets>,IP_MULTICAST_IF /
IPV6_MULTICAST_IF,....)
OR/AND
2b) Joining multicast sender/receiver udp sockets to a group on a specific
interface/device with `setsockopt(<Multicast sockets>,IP_ADD_MEMBERSHIP /
IPV6_ADD_MEMBERSHIP ,....)`
3) Binding Opensaf broadcast sender/receiver udp sockets to a particular
device like eth4,
with `setsockopt(<udb sockets>, SOL_SOCKET, SO_BINDTODEVICE,....)
Note : still exploring other option , to do SO_BINDTODEVICE setsockopt `dtmd`
should be demonizes as root
---
** [tickets:#933] dtm : the udp receive/sender bcast/multicast traffic should
use configured IP interface/VLAN-interface **
**Status:** accepted
**Milestone:** 4.5.FC
**Created:** Thu Jun 05, 2014 03:41 AM UTC by A V Mahesh (AVM)
**Last Updated:** Thu Jun 05, 2014 03:41 AM UTC
**Owner:** A V Mahesh (AVM)
Currently the dtm discovery udp receive/sender socekts are NOT bind to a
device name which holds dtmd.conf configured IP address , it uses available
interface
which falls under same bcast/multicast group (IPV4/IPV6 Global /IPV6 link local
)
Fro example :
If you have node with 4 interfaces if you have IPv4 private ,IPv4 publuc ,
IPv6 Global & IPv6 Link local
and dtmd.conf configured :
1) IPV4 private IP (192.168.56.xxx) in dtmd.cong discovery udp receive/sender
socekts may use eth0 or eth1
2) IPV6 Scope:Global in dtmd.cong discovery udp receive/sender sockets may
use eth2 or eth3
3) IPV6 Scope:local in dtmd.cong discovery udp receive/sender sockets may use
eth0 or eth2 or eth3 or eth4
and this is fine as soon they are all in same VLAN , if we configured in to
different VLANs we will endup with NOT discovering peer node
so to isolate further we need force use dtmd.conf configured IP address
interface for all the opensaf traffic.
eth0 Link encap:Ethernet HWaddr 08:00:27:71:4B:4F
inet addr:192.168.56.101 Bcast:192.168.56.255
Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe71:4b98/64 Scope:Link
eth1 Link encap:Ethernet HWaddr 08:00:27:71:4B:5E
inet addr:192.168.56.102 Bcast:192.168.56.255
Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe71:454e/64 Scope:Link
eth2 Link encap:Ethernet HWaddr 08:00:27:04:45:4E
inet addr:10.176.176.143 Bcast:10.176.179.255
Mask:255.255.252.0
inet6 addr: 2606:b400:c10:e04c:a00:27ff:fe04:454e/64
Scope:Global
inet6 addr: fe80::a00:27ff:fe04:454e/64 Scope:Link
eth3 Link encap:Ethernet HWaddr 08:00:27:71:4B:98
inet6 addr: 2600:b400:c10:e04c:a00:27ff:fe71:4b98/64
Scope:Global
inet6 addr: 2606:b400:c10:e04c:a00:27ff:fe71:4b98/64
Scope:Global
inet6 addr: fe80::a00:27ff:fe71:4b98/64 Scope:Link
---
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.------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
