• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. jhumpf
    3. Topics
    J
    • Profile
    • Following 0
    • Followers 0
    • Topics 5
    • Posts 15
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by jhumpf

    • J

      Solved Custom Tasks issues

      FOG Problems
      • • • jhumpf
      4
      0
      Votes
      4
      Posts
      432
      Views

      S

      @jhumpf Any news on this? What sort of task is this? Capture, deploy, multicast, other?

    • J

      Join Ubuntu Client to domain, snapin script (realm and SSSD)

      Linux Problems
      • • • jhumpf
      3
      0
      Votes
      3
      Posts
      318
      Views

      J

      @Sebastian-Roth I was hoping for a completely new one. Mine is less of a script and more of a realm join in a bash file

    • J

      Solved Linux Imaging and Fog Client

      Linux Problems
      • • • jhumpf
      4
      0
      Votes
      4
      Posts
      612
      Views

      S

      @jhumpf Have you tried the scripts? Can we mark this closed or do you need any further help with this?

    • J

      Solved Clients will not consistently boot into PXE environment - dnsmasq

      FOG Problems
      • • • jhumpf
      16
      0
      Votes
      16
      Posts
      1.8k
      Views

      george1421G

      @jhumpf All I can say is that based on the two to three years of using that configuration for different fog admins, we haven’t needed to deviate from that configuration since dnsmasq is not giving out dhcp addresses the mask “should be” irrelevant. The remote subnets should just work as long as dnsmasq is being informed of them requesting a dhcp address.

      If you want to debug deeper into the matter, I would suggest that you reset the configuration back to what I have in the article then follow this procedure to see if we can capture a bad remote proxydhcp request and then capture a good remote proxydhcp request so we can compare. There also may be some value in taking a computer on the remote “bad” subnet and loading wireshark on it. Start the capture filter of port “67 or port 68”. That would capture what the dhcp and dnsmasq are sending to the target computer, from the target computer’s point of view. https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

      Upload those 3 captures to a share file site and share them as public. Either DM me directly or post the links here and I will review them.

      My gut feeling is that you have something not configured right in your infrastructure not related to FOG or dnsmasq.

    • J

      Search Function for Hosts and groups missing

      FOG Problems
      • • • jhumpf
      3
      0
      Votes
      3
      Posts
      159
      Views

      S

      @jhumpf We need more information to be able to help!

    • 1 / 1