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

    No Subnet Declaration for virbr0 After Upgrade to 1.5.9

    Scheduled Pinned Locked Moved
    FOG Problems
    2
    11
    1.3k
    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.
    • S
      Sebastian Roth Moderator
      last edited by

      @SCavender Ok, so you are actually using the eth0 interface, right?

      In this case you can ignore the warning from the DHCP service if it works as intended.

      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

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

        @sebastian-roth Yes, I am using eth0 and DHCP works great. The problem is the clients don’t have internet access. They can ping external sites but webpages don’t load/resolve.

        Here’s a screenshot of the Windows network diagnostic:

        IMG_1075.jpeg

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

          @scavender said in No Subnet Declaration for virbr0 After Upgrade to 1.5.9:

          Yes, I am using eth0 and DHCP works great. The problem is the clients don’t have internet access. They can ping external sites but webpages don’t load/resolve.

          Sounds like a DNS issue. In the DHCP service config you have option domain-name-servers 192.168.22.1; - is this the correct DNS server in this subnet?

          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

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

            @sebastian-roth 192.168.22.1 is the Gateway IP/Subnet for the VLAN 22 this Fogserver is connected to. The main Gateway IP/Subnet/Name Server is 192.168.1.1.

            The Fogserver surfs the web just fine, though DHCP clients don’t.

            eth0 DNS address is set to Automatic.

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

              @scavender said in No Subnet Declaration for virbr0 After Upgrade to 1.5.9:

              192.168.22.1 is the Gateway IP/Subnet for the VLAN 22

              Does this gateway provide DNS as well? Either as a DNS service or by relaying the DNS queries to an upstream DNS server?

              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

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

                @sebastian-roth said in No Subnet Declaration for virbr0 After Upgrade to 1.5.9:

                Does this gateway provide DNS as well? Either as a DNS service or by relaying the DNS queries to an upstream DNS server?

                It must be, because this Fogserver instance is more than 2 years in production and has always worked great. Before upgrading to 1.5.9, the Fogserver and DHCP clients under it had internet access. After the upgrade, the Fogserver gets internet access/resolves webpages while the DHCP clients under it get LAN with “no internet access” though they can ping external sites.

                I just rebooted everything and there’s still no resolution.

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

                  @SCavender When you boot up a client, please run ipconfig /all in Windows CMD, take a picture and post here.

                  Just want to see if it receives the DNS server information from the DHCP or not.

                  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

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

                    @sebastian-roth IMG_1077.jpeg

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

                      @SCavender Ahh, I didn’t notice the gateway (in DHCP) is set to your FOG server IP 192.168.22.11 when looking at the dhcpd.conf. Are you sure this is what you want? From what you said so far I would think you want the router to be 192.168.22.1.

                      If your FOG server is meant to be a gateway it needs things like IP forwarding in the kernel enabled and iptables rules to pass packets through. Not something we provide with the FOG installer.

                      While looking at the dhcpd.conf once again I also notice that you might wand to change the line range dynamic-bootp 192.168.22.10 192.168.22.254; because the range starts at 10 but your FOG server is at 11. Make it start at 20 for example to prevent from duplicate IP issues.

                      Make sure you also change the values in /opt/fog/.fogsettings so the installer won’t reset things on the next upgrade!

                      After changing the config you need to restart the DHCP service or your FOG server altogether.

                      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

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

                        @sebastian-roth Ahh, I didn’t see that either. Okay, so in DHCP I changed the router to 192.168.22.1 and range starting IP to .20

                        In fogsettings, I changed both routeraddress and plain router from 192.168.22.11 to 22.1

                        The test client gets online just fine now.

                        Thank you again, Sebastian!

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

                        168

                        Online

                        12.1k

                        Users

                        17.3k

                        Topics

                        155.3k

                        Posts
                        Copyright © 2012-2024 FOG Project