• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Problems multicasting fog on different vlans

    Scheduled Pinned Locked Moved
    Linux Problems
    4
    35
    14.0k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Q
      Quazz Moderator @Yamakazi
      last edited by

      @Yamakazi You can specify the multicast address, but not the broadcast address I think. This seems like a routing issue, not a FOG problem, but I don’t really know enough about networking to say for sure.

      Y 1 Reply Last reply Reply Quote 0
      • Y
        Yamakazi @Quazz
        last edited by

        @Quazz

        Where could i change the multicast adress? Haven’t seen it anywhere in the options.

        Q 1 Reply Last reply Reply Quote 0
        • Q
          Quazz Moderator @Yamakazi
          last edited by

          @Yamakazi Under Multicast settings - FOG_MULTICAST_ADDRESS default value is 0

          Y 1 Reply Last reply Reply Quote 0
          • Y
            Yamakazi @Quazz
            last edited by

            @Quazz

            Don’t seem to have that option.

            0_1464692640768_105.PNG

            Q 1 Reply Last reply Reply Quote 0
            • Q
              Quazz Moderator @Yamakazi
              last edited by

              @Yamakazi I’m guessing you’re on FOG 1.2 then? Not on trunk? Might be worth upgrading and see if that helps.

              1 Reply Last reply Reply Quote 0
              • Wayne WorkmanW
                Wayne Workman
                last edited by

                I’m not sure that 1.2.0 or trunk can multicast to more than one address. In 1.2.0 it uses the broadcast address of the broadcast domain the server resides in. In trunk, the same is true unless you define a custom address.

                You can setup some custom multicast handling if you want, and have that traffic sent throughout your organization - but there’s no easy way to swap destination addresses easily in 1.2.0. Even with FOG Trunk it’ll be repetitive but doable.

                You will need to figure out how to handle the traffic on your switches and routers.

                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                Daily Clean Installation Results:
                https://fogtesting.fogproject.us/
                FOG Reporting:
                https://fog-external-reporting-results.fogproject.us/

                1 Reply Last reply Reply Quote 0
                • S
                  Sebastian Roth Moderator
                  last edited by

                  @Yamakazi Good finds! Check out udp-sender’s man page and you’ll see options like --mcast-rdv-address and --mcast-data-address. I guess you could play with those and patch your PHP files in FOG 1.2.0 to achieve this. On the other hand I think this shouldn’t be need as multicast addresses ought to be “universal” and not depend on IP addresses used in the subnets. But possibly I just don’t know enough about multicast. What I know is that we were using multicast for three different subnets (separated via VLANs!) at my old working place. Worked like a charm after I had setup the multicast routing stuff on all the switches properly. Unfortunately I can’t remember all those settings in detail as this was years ago.

                  Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                  Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                  Y 1 Reply Last reply Reply Quote 0
                  • Y
                    Yamakazi @Sebastian Roth
                    last edited by

                    @Sebastian-Roth

                    Thank you. I’m going to try to get my hands on a sever and a few routers to try this in a real environment and not a virtual one. I think this is giving me issues.

                    But i’m still not sure on what address fog multicasts? Is this a fixed address? or based on your current subnet? can i find it anywhere in the config files? I know the trunk version let’s you chose the multicast address but i’m having other troubles with that version + a friend of mine got this version perfectly working in his business environment so i want to atleast try to get this working.

                    Wayne WorkmanW 1 Reply Last reply Reply Quote 0
                    • Wayne WorkmanW
                      Wayne Workman @Yamakazi
                      last edited by

                      @Yamakazi It’s based on the fog server’s subnet, specifically the node settings in Storage Management. It uses the last address in the range, the broadcast address, by default. Again in Trunk, you’re able to change this. In 1.2.0 you cannot unless you want to do it in PHP.

                      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                      Daily Clean Installation Results:
                      https://fogtesting.fogproject.us/
                      FOG Reporting:
                      https://fog-external-reporting-results.fogproject.us/

                      1 Reply Last reply Reply Quote 0
                      • S
                        Sebastian Roth Moderator
                        last edited by

                        @Yamakazi It’s all explained in the man page I posted:

                        –mcast-rdv-address address
                        Uses a non-standard multicast address for the control (rendez-vous) connection.
                        …
                        By default “mcast-rdv-address” is the Ethernet broadcast address if “ttl” is 1, and 224.0.0.1 otherwise. …

                        So multicast control connection should be on address 224.0.0.1 I suspect! And then:

                        –mcast-data-address address
                        Uses the given address for multicasting the data. If not specified, the program will
                        automatically derive a multicast address from its own IP (by keeping the last 27 bits
                        of the IP and then prepending 232).

                        Means 232.x.x.x if I don’t get that wrong.

                        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                        1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 2 / 2
                        • First post
                          Last post

                        163

                        Online

                        12.1k

                        Users

                        17.3k

                        Topics

                        155.3k

                        Posts
                        Copyright © 2012-2024 FOG Project