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

Fresh Install of Fog - Setup PXE Boot

Scheduled Pinned Locked Moved Solved
FOG Problems
3
47
10.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.
  • G
    george1421 Moderator @dpotesta50
    last edited by Mar 12, 2018, 9:23 PM

    @dpotesta50 Did you remember to disable the ubuntu firewall and set the selinux permissions to permissive as recommended in the prerequisites?

    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!

    D 1 Reply Last reply Mar 13, 2018, 12:39 PM Reply Quote 0
    • G
      george1421 Moderator @dpotesta50
      last edited by Mar 12, 2018, 9:28 PM

      @dpotesta50 said in Fresh Install of Fog - Setup PXE Boot:

      192.168.100.100/fog/management

      This will only work if you are on the imaging network, to access the managment interface from the business side you will need to find the IP address of the wifi adapter.

      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!

      1 Reply Last reply Reply Quote 0
      • D
        dpotesta50 @george1421
        last edited by dpotesta50 Mar 13, 2018, 6:40 AM Mar 13, 2018, 12:39 PM

        @george1421 I’m running on Ubuntu desktop, is this still required? (selinux permissions)

        G 1 Reply Last reply Mar 13, 2018, 12:43 PM Reply Quote 0
        • G
          george1421 Moderator @dpotesta50
          last edited by Mar 13, 2018, 12:43 PM

          @dpotesta50 (sorry I’m a rhel guy) I’m not sure if ubuntu has selinux enabled or not by default. If its on, then its mandatory that you set it to permissive. If from the linux command prompt you key in cat /etc/selinux/config look for a line that says SELINUX=permissive or SELINUX=disabled If that is set then selinux will not cause you pain. If its set to enforcing then you need to change it as root and reboot.

          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!

          D 1 Reply Last reply Mar 13, 2018, 12:50 PM Reply Quote 0
          • D
            dpotesta50 @george1421
            last edited by Mar 13, 2018, 12:50 PM

            @george1421 It shows "SELinux status: Disabled

            G 1 Reply Last reply Mar 13, 2018, 12:54 PM Reply Quote 0
            • G
              george1421 Moderator @dpotesta50
              last edited by Mar 13, 2018, 12:54 PM

              @dpotesta50 Ok so then selinux will not be in your way. Did you ensure that the firewall has been disabled? I know that IS on by default for ubuntu.

              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!

              D 1 Reply Last reply Mar 13, 2018, 12:56 PM Reply Quote 0
              • D
                dpotesta50 @george1421
                last edited by Mar 13, 2018, 12:56 PM

                @george1421 Yes I ran “sudo ufw disable”

                G 1 Reply Last reply Mar 13, 2018, 12:58 PM Reply Quote 0
                • G
                  george1421 Moderator @dpotesta50
                  last edited by Mar 13, 2018, 12:58 PM

                  @dpotesta50 So if you run ip addr show to get the IP address of the wireless interface and then from the business network attempt to connect to that ip addresss /fog ?

                  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!

                  D 1 Reply Last reply Mar 13, 2018, 1:00 PM Reply Quote 0
                  • D
                    dpotesta50 @george1421
                    last edited by Mar 13, 2018, 1:00 PM

                    @george1421 The dashboard is up and running. I can access it and all the options. I just tried to PXE boot a laptop to it, no server found.

                    D 1 Reply Last reply Mar 13, 2018, 1:03 PM Reply Quote 0
                    • D
                      dpotesta50 @dpotesta50
                      last edited by Mar 13, 2018, 1:03 PM

                      @dpotesta50 It’s very very slow though. Changing from option to option within the FOG program takes a minute or so.

                      G 1 Reply Last reply Mar 13, 2018, 1:07 PM Reply Quote 0
                      • G
                        george1421 Moderator @dpotesta50
                        last edited by Mar 13, 2018, 1:07 PM

                        @dpotesta50 Ok the slowness is from both networks?

                        OK, now lets work on one issue at a time.

                        So fog is the dhcp server, we need to make sure that isc-dhcp service is running on the fog server. Run this ps aux|grep dhcp and/or you can check to see if its listening netstat -an|grep 67

                        The fog installer should setup the isc-dhcp config file to look like this: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Example_1

                        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!

                        D 1 Reply Last reply Mar 13, 2018, 1:29 PM Reply Quote 0
                        • D
                          dpotesta50 @george1421
                          last edited by Mar 13, 2018, 1:29 PM

                          @george1421 0_1520947757620_IMG_1851.jpg

                          G 1 Reply Last reply Mar 13, 2018, 1:44 PM Reply Quote 0
                          • G
                            george1421 Moderator @dpotesta50
                            last edited by Mar 13, 2018, 1:44 PM

                            @dpotesta50 well that explains why no dhcp boot. Its not running.

                            First lets try to start it. This might be the command systemctl start isc-dhcp-server See if that gives you a positive.

                            When you run the netstat command you should see something that looks like this

                            udp    0   0.0.0.0:67
                            

                            If that works then you will want to run this command
                            systemctl enable isc-dhcp-server to enable the server to start at each reboot.

                            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!

                            D 1 Reply Last reply Mar 13, 2018, 1:53 PM Reply Quote 0
                            • D
                              dpotesta50 @george1421
                              last edited by Mar 13, 2018, 1:53 PM

                              @george1421 0_1520949174994_IMG_1852.jpg
                              That list is so long I have to roll the scroll wheel about a dozen times to get to the bottom.

                              1 Reply Last reply Reply Quote 0
                              • G
                                george1421 Moderator
                                last edited by Mar 13, 2018, 3:08 PM

                                I remoted in with teamviewer and helped the OP get things working correctly. We had to ensure that the dhcp server only bound to the imaging lan NIC adapter and not both. We also found a nuance with ubuntu where it only wanted one interface up at a time by default. Once we had both interfaces up, fog installed correctly and like the OP needed it. Solving this case.

                                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!

                                1 Reply Last reply Reply Quote 1
                                • 1
                                • 2
                                • 3
                                • 2 / 3
                                2 / 3
                                • First post
                                  42/47
                                  Last post

                                156

                                Online

                                12.0k

                                Users

                                17.3k

                                Topics

                                155.2k

                                Posts
                                Copyright © 2012-2024 FOG Project