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

    /default.ipxe... Connection timed out | fog_1.0.1 | Ubuntu 14.04 LTS | Winxp32 Vbox Client

    Scheduled Pinned Locked Moved
    Tutorials
    7
    69
    55.6k
    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.
    • Wayne WorkmanW
      Wayne Workman
      last edited by

      [quote=“PaganLinuxGeek, post: 42686, member: 2226”]You are recommending a format and fresh install of the OS? then install a development version of the software? I just want to make sure I understand you correctly. Before you respond please see my post just prior to this showing that nfs is active and exporting the images and dev directories[/quote]

      Because everything else that was tried hasn’t worked & because you don’t have a functioning 1.2.0 FOG machine, I think that re-installing the OS and going with SVN 2922 (or 2948) is very safe and probably the best next-step.

      The installation script alone in 2922 does so much small tweaking for Fedora 21, it really vastly cut down on the things that had to be done to get FOG working on Fedora 21. As you did, I tried putting 1.2.0 on Fedora 21 originally; I documented what I did. My instructions were a mile long, consisted of over a dozen web page links, several dozen commands, notes, etc. I didn’t even know exactly what commands were making it work… But I did get uni-cast working on my own. Tom got me straightened out further with multicasting, and other issues. We worked together so he could fine tune the installation script for Fedora 21.

      After SVN 2920, my instructions dropped from 12(ish) pages to six simple, uncomplicated pages.

      We know beyond doubt that SVN 2922 works on Fedora 21, and have instructions written specifically for this.

      If you don’t want to do a re-install or use the SVN, maybe Tom will help.

      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
      • P
        PaganLinuxGeek
        last edited by

        Ugh. this machine doubles as my workstation. Lots of work to re-install this beast… Where can I get svn 2922? Perhaps I can round up a older alower machine to install 21 on and then this developmental version.

        If I knew what the failed actions were I could likely ammend or perform them manually. I had to do that with 0.32 on fedora 19, and 20…

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

          [quote=“PaganLinuxGeek, post: 42688, member: 2226”]Ugh. this machine doubles as my workstation. Lots of work to re-install this beast… Where can I get svn 2922? Perhaps I can round up a older alower machine to install 21 on and then this developmental version.

          If I knew what the failed actions were I could likely ammend or perform them manually. I had to do that with 0.32 on fedora 19, and 20…[/quote]

          The command to get 2922 is in the Fedora 21 instructions on the Wiki.

          Literally every single step is covered there.

          [url]http://fogproject.org/wiki/index.php/FOG_(r2922)_Configuration_on_Fedora_21_Workstation_inside_Windows_Server_2012_Hyper-V_using_ProxyDHCP[/url]

          As far as amending 1.2.0, that’s a Tom question.

          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
          • P
            PaganLinuxGeek
            last edited by

            I noticed today that the last line shown on the vbox console has the WRONG ip address. (It’s showing tftp://192.168.1.1/default.ipxe…
            Now I’ve set dnsmasq.conf to use .116 What would cause the clients to default to the .1 ip instead? is there another file somewhere that undionly.kpxe is referencing?

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

              [quote=“PaganLinuxGeek, post: 42706, member: 2226”]I noticed today that the last line shown on the vbox console has the WRONG ip address. (It’s showing tftp://192.168.1.1/default.ipxe…
              Now I’ve set dnsmasq.conf to use .116 What would cause the clients to default to the .1 ip instead? is there another file somewhere that undionly.kpxe is referencing?[/quote]

              Simple question but, in your install log, you answered no for using FOG as a dhcp server. Have you covered DHCP options 66 & 67, made sure they are correct?

              [url]http://fogproject.org/wiki/index.php/FOGUserGuide#DHCP_Settings[/url]

              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
              • JunkhackerJ
                Junkhacker Developer
                last edited by

                the line in the ipxe embeded script that loads default.ipxe is [CODE]chain tftp://${next-server}/default.ipxe[/CODE] i’m not sure how it could both load the undionly.kpxe file and get the location of the default.ipxe file wrong

                signature:
                Junkhacker
                We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

                1 Reply Last reply Reply Quote 0
                • P
                  PaganLinuxGeek
                  last edited by

                  I cannot modify those options in the router my ISP provided. That is why I am using dnsmasq
                  I tried installing the svn suggested over my existing fog install. The “devel” version I guess shows the server IP…
                  I’m trying to understand why it’s pulling the router’s IP instead of what dnsmasq is sending…

                  [CODE][root@jezebelle tftp]# cat /etc/dnsmasq.conf
                  tftp-root=/tftpboot
                  #enable-tftp
                  dhcp-option=vendor:PXEClient,6,2b
                  dhcp-no-override
                  dhcp-range=192.168.1.107,proxy
                  #port=0
                  log-dhcp
                  dhcp-boot=undionly.kpxe,192.168.1.107
                  dhcp-option=17,/images
                  dhcp-option=pxe,66,192.168.1.107
                  pxe-prompt=“Press F8 for boot menu”, 9
                  pxe-service=X86PC,“iPXE Boot (Newer for Secure Boots)”, undionly
                  pxe-service=X86PC,“PXE Boot (Older machines)”, pxelinux
                  pxe-service=X86PC,“Boot from local hard disk”, 0
                  #interface=eno1,enp7s0,enp4s0,lo
                  [/CODE]

                  [CODE][root@jezebelle tftp]# ifconfig
                  eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
                  inet 192.168.1.116 netmask 255.255.255.0 broadcast 192.168.1.255
                  inet6 fe80::922b:34ff:fed4:e03 prefixlen 64 scopeid 0x20<link>
                  ether 90:2b:34:d4:0e:03 txqueuelen 1000 (Ethernet)
                  RX packets 2713 bytes 207258 (202.4 KiB)
                  RX errors 0 dropped 0 overruns 0 frame 0
                  TX packets 40 bytes 9597 (9.3 KiB)
                  TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
                  device interrupt 20 memory 0xf7600000-f7620000

                  enp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
                  inet 192.168.1.115 netmask 255.255.255.0 broadcast 192.168.1.255
                  inet6 fe80::6a05:caff:fe0a:5e3 prefixlen 64 scopeid 0x20<link>
                  ether 68:05:ca:0a:05:e3 txqueuelen 1000 (Ethernet)
                  RX packets 2704 bytes 205402 (200.5 KiB)
                  RX errors 0 dropped 0 overruns 0 frame 0
                  TX packets 35 bytes 9194 (8.9 KiB)
                  TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
                  device interrupt 16 memory 0xf74c0000-f74e0000

                  enp7s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
                  inet 192.168.1.107 netmask 255.255.255.0 broadcast 192.168.1.255
                  inet6 fe80::922b:34ff:fed4:df3 prefixlen 64 scopeid 0x20<link>
                  ether 90:2b:34:d4:0d:f3 txqueuelen 1000 (Ethernet)
                  RX packets 441929 bytes 66602075 (63.5 MiB)
                  RX errors 0 dropped 0 overruns 0 frame 0
                  TX packets 1299172 bytes 1874321485 (1.7 GiB)
                  TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
                  device interrupt 18

                  lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
                  inet 127.0.0.1 netmask 255.0.0.0
                  inet6 ::1 prefixlen 128 scopeid 0x10<host>
                  loop txqueuelen 0 (Local Loopback)
                  RX packets 76552 bytes 1155843438 (1.0 GiB)
                  RX errors 0 dropped 0 overruns 0 frame 0
                  TX packets 76552 bytes 1155843438 (1.0 GiB)
                  TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

                  virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
                  inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
                  ether 6e:1a:c0:4e:a2:a6 txqueuelen 0 (Ethernet)
                  RX packets 0 bytes 0 (0.0 B)
                  RX errors 0 dropped 0 overruns 0 frame 0
                  TX packets 0 bytes 0 (0.0 B)
                  TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
                  [/CODE]

                  1 Reply Last reply Reply Quote 0
                  • P
                    PaganLinuxGeek
                    last edited by

                    If it helps any, this is the router/modem they provided as much as I hate this device I am forced to use it
                    [url]http://docs.technicolor.com/data/files/cm/DMS-CTC-20130228-0000.pdf[/url]

                    1 Reply Last reply Reply Quote 0
                    • Tom ElliottT
                      Tom Elliott
                      last edited by

                      As you’re using dnsmasq, have you made a link or copy of the “bootfile” on the /tftpboot as undionly.0

                      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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                      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
                      • P
                        PaganLinuxGeek
                        last edited by

                        Yes I did 🙂 undionly.0

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

                          Just kicking around ideas…

                          Turn DHCP off for that device you have, and install FOG with DHCP turned on… see what happens…

                          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
                          • P
                            PaganLinuxGeek
                            last edited by

                            Already considered that. It’s not an option on this device. 😕 I have a raspberry PI running on the home lan that could handle dhcp as it’s always on.

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

                              [quote=“PaganLinuxGeek, post: 42774, member: 2226”]Already considered that. It’s not an option on this device. 😕 I have a raspberry PI running on the home lan that could handle dhcp as it’s always on.[/quote]

                              Install FOG with DHCP anyways, then disconnect from that modem/router thing. Use a cross over cable to connect directly to the target machine.

                              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
                              • 1
                              • 2
                              • 3
                              • 4
                              • 4 / 4
                              • First post
                                Last post

                              222

                              Online

                              12.0k

                              Users

                              17.3k

                              Topics

                              155.2k

                              Posts
                              Copyright © 2012-2024 FOG Project