Testing something more.
If i change the Storage Node’s ip then yes, multicast works into associated nic.
What is the purpouse of the nic interface on Storage Node General?
@blainey It is possible to access your internal server using the router’s public IP address/forwarded port, but your router must support loopback network address translation (a.k.a. hairpin NAT) and be configured accordingly.
Without loopback translation in effect, IP packets destined for your router’s public IP address will arrive on its private network interface. Here the packets are simply dropped, usually because the router requires packets destined for its public IP address to arrive on its physical WAN interface (there are other possible ways this traffic may be handled, including NAT occurring, but the end result is always that the connection cannot be completed).
However, with loopback translation configured, when the packets destined for the public address arrive on the private interface, their destination address will be rewritten to be that of the internal server. Then the normal port translation will be applied, further resulting in the destination port being rewritten as well.
There are other options.
I’m trying to enable multicast on my installation. And I have a problem.
Trying to change nic on node definition or in fog settings dont change on the multicast command.
FOG try to send the stream always from the eth0.
All my nodes are multihomed with at least 3 VLANs, and eth0 is a management interface on the management network.
I try to locate where the task get the nic to use but i can’t find it. Well i find some places but forcing manually by nic name and by nic ip dont works.
Testing manually udp-sender and udp-location is multicast capable.
The installation are Normal and Node v1.5.6
Thanks in advance.
I’m thinking about your post and I’ve done a revision of some computers’ history.
And I can confirm that i have snapin sequences, that i know that they are executed on launching time order, not in alpha-numeric.
BUT this has been caused by a procedure change.
After reviewing the procedure and some tests I have noticed that:
a snapin sequence launched to computers is executed in alpha-numeric order
a snapin sequence launched to groups is executed in launching time order
Thank’s for make me think a few.
Upgraded to 1.5.6 as you suggested.
It seems to be a bit faster, but i need to do the corrections on the server with the same values.
Now i’m experiencing another issue posted as https://forums.fogproject.org/topic/13328/fog-snapins-not-ordered-on-launching-time